PDF Objects → JSON

Inventory the indirect objects of a PDF (references, dict/stream/array), analyze the XRef (table) and identify orphan/suspect objects. Export local JSON.

Import a PDF

No data is sent to a server: everything is done in your browser.

← Back to PDF tools

Use cases

Debugging a broken PDFUnderstand why a parser fails: missing objects, inconsistent offsets, abnormal streams.
Forensic analysisIdentify suspicious objects (JavaScript, embedded files, very large streams) in a security audit.
Targeted optimizationIdentify the heaviest objects/streams (images, fonts) before launching an optimization.

What you get

A JSON export listing the objects: number/generation, type (dict/stream/array…), size/length, references, and useful flags.

Practical hints: presence of compressed streams, orphaned objects, xref structure (depending on the engine).

Limits and points of attention

It is a "dev/forensic" tool: the output is technical and can be massive on large PDFs.
Streams may be compressed: the JSON describes the structure, not necessarily the decompressed content.
An encrypted PDF limits detailed inspection without a key.

Frequently asked questions

Does it replace a low-level PDF viewer?

No, but it is very useful for automating diagnostics and sharing a JSON report.

Why is the export huge?

A PDF often contains thousands of objects. Filter by size/type after export.

Can I find JavaScript in it?

Often yes via certain dictionaries/actions. For cleaning, use the sanitization tool.

Tip

Start by listing the heaviest objects: it is often the quickest way to explain a PDF of 50+ MB (HD images, fonts, scans).