Choose a PDF and get a plain-language health report: whether it parses in two independent engines, its version, page count and sizes, whether it is encrypted, what metadata it carries, and whether the QPDF engine can rewrite it cleanly. This is a diagnostic, not a certification — formal PDF/A or print compliance needs dedicated validators. Runs fully in your browser — nothing is uploaded.
Is this PDF actually healthy? Two engines and QPDF give their verdicts in one honest report — what passes, what limps, what fails.
100% free · No sign-up · No daily limits · No watermarks · Processed in your browser — files never leave your device
Check a PDF’s health: header and version, two independent parser reads, an engine rewrite test, encryption status, page count and sizes, metadata and form fields — a clear diagnostic report, not a certification.
Before uploading a signed agreement to a court portal, a clerk validates it here: version 1.7, both parsers agree on 42 pages, not encrypted, no stray form fields — filed with confidence instead of a rejection email.
The checks are the same ones support engineers run: the file’s header is inspected for the PDF signature and claimed version; then two different parsing libraries (a writer-grade library and the renderer behind Firefox’s viewer) each attempt a full read; a dedicated PDF engine attempts a structural rewrite; and structure facts (encryption dictionary, page geometry, info metadata, AcroForm fields) are enumerated. Agreement between independent parsers is strong evidence a file is healthy.
Open it in the reader that works and Save As a fresh copy, or run Repair PDF here. Parser disagreement means some strict tool in your chain may also balk — fixing it now is cheap insurance.
No. Signature validity needs the signer’s certificate chain and a different class of tool; this report covers structure, not trust.
No — PDF/A conformance involves fonts embedding, colour profiles and metadata rules beyond structural parsing. The report says what it checks, and only that.
The file does not begin with a standard %PDF-x.y header — common for files generated by odd tooling. Parsers may still read it (the other rows will show), but strict portals may not.
No. Every check runs locally in your browser.