1
Select the PDF
Choose the document whose technical properties and structure you want to inspect.
Private PDF structure inspection
How to inspect PDF properties before sharing or printing
Review supported page sizes, fonts, metadata, forms, attachments and document structure so potential production or sharing issues are easier to identify before further processing.
2
Run the inspection
Allow the browser to read supported page, font, form, attachment and metadata information.
3
Review the findings
Check reported properties and warnings against the requirements of the printer, archive or recipient.
4
Choose the next action
Use the findings to decide whether the source needs resizing, flattening, metadata editing, sanitizing or another supported workflow.
Key features
What you can do with PDF Preflight Inspector
Practical capabilities for this document workflow.
Page-size inspection
Review supported page dimensions and identify mixed document sizes.
Font information
Inspect font details exposed by the supported PDF structure.
Form detection
Identify supported interactive form information before flattening or sharing.
Attachment review
Check whether the PDF reports supported embedded files or attachments.
Metadata overview
Review supported document properties that may need correction or removal.
Read-only analysis
Inspect the source without intentionally changing its visible page content.
Privacy
Inspect PDF structure locally
The current PDF Preflight Inspector is designed to read supported document properties in your browser without uploading the source PDF to a Fylvexa analysis server.
Browser-first
Fast workflow
No desktop app
Frequently asked questions
PDF Preflight Inspector FAQ
Select a question to view the answer.
The current tool reports supported information such as page dimensions, fonts, metadata, forms, attachments and other document properties available to the browser parser.
No. Requirements vary by printer, archive and workflow. Treat the report as technical guidance and verify critical jobs against the recipient’s specification.
No. The inspector reads supported information and does not need to overwrite the selected source document.
PDF font structures, subsets, encodings and parser support vary. Some files may not expose every property in a form the browser tool can report.
Compare the warning with the destination requirements, then use the relevant repair, resize, flatten, metadata or sanitizing workflow and inspect the new output again.
The current inspector is designed to analyze supported document properties in your browser without a Fylvexa processing backend.
Related tools
Continue your document workflow
Open another Fylvexa tool that works well with this task.