PDF Capability & Quality Report - Free Online Browser Tool
Read-only report of PDF structure, quality signals, page boxes, and recommended next tools.
Before choosing a repair or conversion tool, find out what your PDF actually contains. This local inspection brings together document metadata, readable text, image and font counts, form widgets, encryption indicators and page geometry. It also flags attachment and action markers and suggests focused follow-up tools. The report describes observable signals rather than issuing a quality score or a compliance certificate.
This pdf capability & quality report utility runs completely inside your web browser. Your document is opened locally and processed on your own device using JavaScript and WebAssembly, so your file is never uploaded to any server. There is no signup, no watermark and no limit on how many documents you can handle.
- 100% client-side - files never leave your device
- Instant processing, no upload wait
- Works on desktop, tablet and mobile
- Free forever, no account required
Common next steps: Inspect PDF Page Boxes, Accessibility Checker (PDF/UA), PDF/A Readiness Check, Inspect Security & Permissions.
How to Use the PDF Capability & Quality Report Tool
Four steps, and the whole thing runs locally on your own device.
-
Select one document
Choose a PDF from your device. Its original bytes are read in the browser without rewriting the file.
-
Choose the export format
JSON includes the detailed report, page boxes and limitations. CSV and readable text provide a compact overview of the main signals and recommendations.
-
Run the inspection
The tool checks readable pages for text, image operators, font resources and form widgets, alongside document-level metadata and structural indicators.
-
Use the recommended next checks
Download the report and follow up with the relevant page-box, accessibility, archival, permission or text tools. Review unknown fields before drawing conclusions.
Frequently Asked Questions
Does the capability report change or upload my PDF?
No. Inspection and report export happen in your browser, and the source PDF is not modified. The download is a separate JSON, CSV or text file.
Does it certify PDF/A or PDF/UA compliance?
No. It records signals such as tagging, language, title, XMP, output intent and a PDF/A declaration. A declaration or a set of present signals is not proof of conformance; use dedicated validation for a formal requirement.
What happens if the PDF needs a password or cannot be parsed?
The tool exports a limited report with the filename, size, header version and available encryption indicator. Page-level checks remain unavailable, with a limitation explaining that the parser could not open the document.
Does a missing text layer prove the document is a scan?
No. A page without detected text might contain scanned images, outlined lettering or other non-text content. Failed extraction is reported as unknown rather than treated as proof that the document is scanned.
Are attachment, image and font checks exhaustive?
No. Attachments and actions are indicated by detected markers, which can miss compressed structures or match unrelated bytes. Images are counted from drawing operators and fonts from text resources; these counts do not establish image resolution or font embedding quality.
Which format keeps the full inspection detail?
JSON preserves metadata, per-page geometry, warnings and limitations. CSV and text summarise selected fields and follow-up recommendations, so use JSON when you need to review the detailed evidence.