how to read float32array extracted from pdf?

[CODE-WITH-CODEER]

actually iam working on a pdf project using pdfjs-dist library any one hear who can make me understand that what my console output is trying to tell and how i get it in it's original form ?

code:
`const pdfjsLib =require("pdfjs-dist/legacy/build/pdf.mjs");
const express=require("express");
let app=express();
const fs =require("fs");

app.listen(8080,e=>{
console.log("conn");
});

const data=new Uint8Array(fs.readFileSync("cnr.pdf"));

const loadingTask = pdfjsLib.getDocument({data:data});

loadingTask.promise.then(async (pdf) => {

const page = await pdf.getPage(33);
let p=await page.getOperatorList();
const OPS = pdfjsLib.OPS;
console.log( OPS);
page.st
const opMap = {};
for (let key in OPS) {
opMap[OPS[key]] = key;
}
let k=0;
p.fnArray.forEach((fn,i)=>{
if(fn===91){
k++;
console.log(opMap[fn], p.argsArray[i]);
}

});
console.log("k",k);
}).catch(err=>{
console.log(err);
});`

console: closeStroke: 21 eoFill: 23 constructPath [ 21, [Float32Array(13) [0,0,841.8900146484375,1,595.2760009765625, 841.8900146484375,1, 595.2760009765625,0,1,0,0,4] ],Float32Array(4) [ 0, 0, 595.2760009765625, 841.8900146484375 ] ]

[calixteman]

You can check how the array is used in:

pdf.js/src/display/canvas.js

Line 1488 in ca13d00

constructPath(opIdx, op, data, minMax) {

[CODE-WITH-CODEER]

i have LAYERS (OCG) content in my pdf iam not getting those SVG properly on my canvas can you tell me why this happens sir ?

[Abdeltoto]

What your console is showing

You’re logging constructPath operations from page.getOperatorList(). In pdf.js, that’s a low-level vector-graphics instruction: it rebuilds the painting operators from the page content stream (paths, fills, strokes), not “text” or “structured fields”.

For each constructPath you’re printing, the arguments are roughly:

1. First Float32Array – packed path geometry + transform-related numbers for that operator (PDF user space). The exact layout depends on the path operator flags you see in the preceding args (your code filters fn === 91, which maps to constructPath).
2. Second Float32Array(4) – very often a bounding rectangle in user coordinates (e.g. clip / extent), here something like the page box in pt (595.276 × 841.89 looks like A4 in points).

So the message is: “here is numeric geometry the PDF painter is using,” not encrypted content.

If you want the data in a more usable “original” form

Pick the level you care about:

Goal	Better API than getOperatorList
Human-readable text	const text = await page.getTextContent() then walk text.items
Rendered pixels	page.render({ canvasContext, viewport }) to a canvas
Structured annotations	page.getAnnotations()
Vectors as SVG	use built-in helpers / examples that turn operator lists into SVG (heavier; custom)

getOperatorList() is for people implementing custom renderers or debugging the content stream. For most apps it’s the wrong first tool.

Small code notes

• There’s a stray page.st in your snippet — that would break parsing if it’s really in your file.
• Logging only fn === 91 misses most operators (text uses other op codes, etc.).

If you say whether you need text, images, or exact path geometry, the next step is narrower.

[CODE-WITH-CODEER]

sir i want to exact path geometry, why i have choused low-level vector-graphics is because i don't know how to extract path geometry or SVG content directly like page.getTextContent()?

[Abdeltoto]

hello@CODE-WITH-CODEER, pdf.js doesn’t have something like getTextContent() but for paths. If you want exact path geometry, getOperatorList() is the right place — there’s no simpler built-in that dumps SVG paths for you.

Those Float32Arrays are just numbers for the path / bbox in PDF user space. To use them you need to walk all operators (not only the one you filtered), and constructPath in canvas.js is the reference for how those arrays are meant to be read — basically you replay the same ops as the renderer and emit whatever format you want (SVG, etc.). That’s extra work, but it’s normal for this use case.

Layers / OCG on canvas vs SVG is a separate problem (visibility and draw order), not really about decoding the floats.

If this answers what you were stuck on, feel free to mark it as the accepted answer when you’re happy.