Skip to content

10 tools

Developer Tools

Look inside the file, not just at the page.

When a PDF misbehaves, the rendered page tells you nothing about why. The answer is in the structure: which PDF version, how objects are laid out, which fonts are embedded versus merely referenced, what is actually consuming the bytes, whether the page box and crop box disagree. These tools expose that layer for people who need to debug documents rather than just read them — and they are deliberately among the most detailed on the site.

About developer tools

Who are these tools for?

Developers generating PDFs programmatically, prepress and print operators, accessibility auditors, and anyone diagnosing a file that renders differently across viewers.

Can I see the raw object tree?

No raw object-tree browser is provided. The inspectors read the document structure and report selected facts such as indirect-object counts, cross-reference style, stream filters and page geometry. The size and object views add byte-attribution summaries. Each JSON report exports selected findings rather than every object and reference.