PDF Object Counter

A PDF is built from many internal objects, and not every count is equally easy to compute reliably in a browser. This tool reports the counts that @cantoo/pdf-lib's public API exposes reliably: the number of pages, unique embedded images referenced across all pages, distinct fonts declared in page resource dictionaries, all annotations(comments, stamps, links, form widgets, etc.), the subset of those that are link annotations, and the total number of indirect objects in the file — every object the PDF assigns its own object number, via context.enumerateIndirectObjects(). This last count is a good rough proxy for how structurally complex a PDF is internally.

• Upload the PDF you want to analyze.
• Click Count Objects to scan the entire document.
• Review the breakdown of pages, images, fonts, annotations, links, and total indirect objects.

• Getting a quick structural fingerprint of a PDF before deciding whether to compress or optimize it.
• Sanity-checking that a generated PDF contains the expected number of images or fonts.
• Estimating how "heavy" or complex a PDF is internally relative to its visible page count.

• Why might the image or font count seem low? Counts are based on unique resources referenced in page resource dictionaries. Reused images or fonts across many pages are only counted once, and non-standard embeddings may not be detected.
• What does "total indirect PDF objects" mean? Every object in a PDF that's referenced by number (rather than embedded inline) counts as one indirect object — this includes pages, fonts, images, annotations, and many internal dictionaries and streams, so it's typically much larger than any individual count above.
• Does this include vector graphics or text runs? No — those live inside content streams rather than as separate countable objects with their own type, so they aren't broken out individually.
• Is my file uploaded anywhere? No — everything runs entirely in your browser.