Inspector limitations: PDF internals can include encrypted, malformed, compressed or vendor-specific structures. Resource inventories are best-effort structural reports, not exhaustive rendering, forensic validation, malware detection or accessibility certification.
Using PDF Structure Inspector
Inspect PDF objects, references, cross-reference evidence and document inventories locally without rendering pages or executing embedded actions.
Workflow
Open a PDF up to the local size limit
review object and reference inventories with parser notices
export the structural report and keep its evidence separate from a visual review.
Example
Inspect a PDF’s catalog and page-tree references, note unresolved objects in the report, and open the same file in a separate PDF reader to compare visible pages.
Limits and data handling
This is bounded structural inspection, not a page renderer or conformance/security certification. Encrypted files, object streams and unsupported cases may yield partial results. Xref offset consistency is not proof of integrity. The tool does not follow actions or extract embedded payloads. Inputs are limited to 64 MB and browser memory also applies. File data is processed locally; Worker support and hosting CSP require runtime acceptance.
FAQs
Does the inspector show the PDF pages as images?
No. It reports PDF structures and inventories but does not render page visuals.
Does a consistent xref prove a PDF is safe or valid?
No. Offset evidence is limited and does not establish conformance, integrity or safety.
