PDF guides

Read the page tree and declared resources in a PDF

·

Check whether a PDF’s catalog and page tree lead to the pages you expect. Use the resource and annotation evidence to decide where additional inspection is needed.

PDF Structure Analyzer

Follow the catalog to the visible page

Select Load example, then Analyze PDF structure. Catalog 1 0 R points to page tree root 2 0 R. The root declares one page and the report reaches one page, 3 0 R.

The page’s media rectangle is 200 × 300 pt. Its crop reduces the visible dimensions to 180 × 270 pt. The visible size shown comes from the intersection of the page boxes.

Download the one-page PDF revision fixtureAdobe PDF 32000-1 reference for document structure, resources and fonts

Check the font, image and link evidence

The page lists one font, one image resource and one annotation. The font is Helvetica with no embedded font program. Link annotations reports one link. The inspector keeps the action inactive.

The standard information dictionary lists Field proof inventory as the title. Compare these fields with the sample’s visible page when you need evidence about what actually rendered.

Check the font, image and link evidence
FindingFixture result
Reachable pages1
Visible size180 × 270 pt
Declared fontHelvetica, Type1
Embedded font programNo
Image resources1
Link annotations1

Download the one-page PDF revision fixtureAdobe PDF 32000-1 reference for document structure, resources and fonts

Verify and use the saved evidence

Download pdf-structure-report.json. Check declaredPages, pages[0].reference and metadata.Title. The xref block records two cross-reference sections and a final startxref offset of 1261.

A resource can be declared without being used on every page that inherits it. An unavailable node or mismatched /Count needs a separate review. Check the source in a PDF reader before assessing its complete appearance.

Download the one-page PDF revision fixtureAdobe PDF 32000-1 reference for document structure, resources and fonts

Common questions

Does a font subset prefix prove the font data is embedded?

The conventional prefix is a naming hint. Embedded program reports separately whether the inspected font descriptor points to a font stream.

Does the analyzer open any reported links?

The report counts link annotations without opening their destinations or exposing their URL text.

Sources

Put it into practice.

Related guides