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.
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.
Select a readable PDF and let the browser inspect it. Keep a known-good original if you plan to make changes afterward.
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.
Review reported metadata, attachment names and form identifiers. Missing title or author metadata is a review item, not proof that a document is invalid.
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.
Practical capabilities for this document workflow.
The report lists page dimensions, orientation and rotation, helping reveal mixed paper sizes or rotated pages before a layout workflow.
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.
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.
Look for mixed dimensions or non-zero rotations before adding a consistent print layout. Confirm unusual pages visually before changing them.
Inspect field names before planning a data import or renaming task. Test actual interaction in the intended PDF reader as a separate check.
Save a basic technical report for a document review. Treat it as a description of supported findings rather than a formal compliance certificate.
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.
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.
Open another Fylvexa tool that works well with this task.
Explore Browser Document Utilities
To inspect differences between two versions after checking their properties, open Compare PDF and review the comparison report.