Skip to main content

Private browser tool

PDF Preflight Inspector

PDF Preflight Inspector reports page geometry, text-font identifiers, metadata, attachments and interactive field names. Use its basic warnings to guide a review, then download the JSON report for your records.

Preparing the interactive workspace…

Your document processing stays in your browser.

Basic structural inspection, not certification

Inspect a PDF before choosing the next workflow

A PDF can contain mixed page sizes, rotations, attachments or form fields that are not obvious from a quick visual check. This inspector gathers supported properties and lists basic items to review. It helps you decide whether to standardize pages, inspect forms or edit metadata, but it does not certify a file against a print or accessibility standard.

1

Choose the PDF to inspect

Select a readable PDF and let the browser inspect it. Keep a known-good original if you plan to make changes afterward.

2

Review pages and identifiers

Check the page-size and rotation table. The font list comes from identifiers used by extracted page text, not a complete validation of font embedding or licensing.

3

Check document properties

Review reported metadata, attachment names and form identifiers. Missing title or author metadata is a review item, not proof that a document is invalid.

4

Save the report and act narrowly

Download JSON if you need a record. Choose an appropriate tool for any required change and inspect the changed PDF again; the inspector itself does not modify it.

Key features

What you can do with PDF Preflight Inspector

Geometry across the document

The report lists page dimensions, orientation and rotation, helping reveal mixed paper sizes or rotated pages before a layout workflow.

A readable inspection record

The local JSON includes the source name, size, inspection time and supported findings. Review it before sharing because it can contain document metadata and identifiers.

Formats, limits and tradeoffs

Accepts one PDF up to 150 MiB. The current workflow has no explicit page-count cap, but device memory and PDF complexity can limit inspection. Unreadable or protected files can fail to open.

This is not PDF/X, PDF/A or PDF/UA certification. It does not validate press separations, complete font embedding or every hidden object. A failed form inspection can yield an empty field list, so zero reported fields is not a universal guarantee.

When this tool helps

Check a merged report

Look for mixed dimensions or non-zero rotations before adding a consistent print layout. Confirm unusual pages visually before changing them.

Review a form handoff

Inspect field names before planning a data import or renaming task. Test actual interaction in the intended PDF reader as a separate check.

Record document properties

Save a basic technical report for a document review. Treat it as a description of supported findings rather than a formal compliance certificate.

Troubleshooting

Font names look like internal identifiers
The list uses identifiers from extracted text items. Do not interpret it as a complete list of commercial typeface names or proof that all fonts are embedded.
No warnings were found
The inspector checks only its supported basic conditions. Continue any required print, accessibility or security review with appropriate tools and standards.
Privacy

Inspect without uploading the PDF

The browser reads the PDF and builds its report locally. Document bytes are not uploaded to a Fylvexa inspection server. The report can contain source metadata; share it deliberately.

Browser-first
Browser workflow
No desktop app
Frequently asked questions

PDF Preflight Inspector FAQ

Select a question to view the answer.

No. This workflow reports supported properties and creates a separate JSON download.

No. It is a basic inspection report, without PDF/X validation or full commercial print preflight.

Yes. It lists page geometry and flags mixed sizes in its basic warnings.

Review it first. It includes the source filename and can include metadata, form identifiers and attachment names.