About the PDF/A Checker
PDF/A is the version of PDF made for long-term archiving, and courts, governments, universities and companies often require it. This checker reads a PDF in your browser and tells you whether it claims to be PDF/A, which part and level (such as PDF/A-1b or PDF/A-2u), and whether it meets the rules most often broken: fonts must be embedded, an output intent colour profile must be present, encryption and JavaScript aren't allowed, PDF/A-1 forbids transparency and LZW compression, and only PDF/A-3 may carry attachments. Each check is explained in plain words.
Updated October 2026
How to use the PDF/A Checker
- 1Select the PDF.
- 2Wait a moment while it is checked.
- 3Read the summary at the top.
- 4Look at each check marked Pass, Problem, Check or Note.
- 5Fix problems in the program that made the PDF and check again.
Reading the results
Pass means the check found no issue. Problem means a rule is broken. Check means something may be a problem depending on the PDF/A part. Note gives information that is allowed in some parts.
- Pass: requirement met
- Problem: must be fixed
- Check: depends on the PDF/A part
- Note: allowed in this part
Fixing common problems
Unembedded fonts and a missing colour profile are the most common failures. Re-export the document from the original program with PDF/A switched on, rather than editing the PDF, and remove any interactive features such as scripts.
Which part to use
PDF/A-1 is the oldest and strictest. PDF/A-2 allows transparency and JPEG 2000. PDF/A-3 also allows attached files, which e-invoice standards such as ZUGFeRD and Factur-X use.
Why a claim isn't enough
A file can say it is PDF/A in its metadata but still break rules if it was edited afterwards. That is why this tool checks the content as well as the claim.
What the checker reads
It looks at the PDF's header, the XMP metadata where PDF/A identification lives, the output intents in the document catalogue, and every object in the file for fonts, scripts, compression filters, soft masks and embedded files. Nothing is changed and the file isn't uploaded.
Phone and computer
The check runs quickly on any device. Archive files should be clean, and other PDF tools help with fixes. Use the PDF Metadata Editor to correct the title and author, Repair PDF for damaged files, and Compress PDF when the document is too large.
Features
- Detects the PDF/A part and level
- Embedded font check
- Colour profile (output intent) check
- Encryption and JavaScript checks
- PDF/A-1 transparency and LZW checks
- Attachments rule for PDF/A-3
Frequently asked questions
What is PDF/A?
An ISO standard (ISO 19005) for archiving PDFs so they look the same in decades: everything needed to display the file, such as fonts and colour profiles, must be inside it.
Is this a full validator?
No. It checks the most common requirements quickly. For official submissions, confirm with a full validator such as veraPDF, which tests hundreds of rules.
How do I make a PDF/A?
Export with PDF/A turned on: in Word, Save As PDF > Options > PDF/A compliant; in LibreOffice, Export as PDF > PDF/A; or use Acrobat's Save as PDF/A.
Why are fonts a problem?
If a font isn't embedded, another computer may substitute a different one and the document changes. PDF/A requires all fonts to be embedded.
What do the parts and levels mean?
Parts 1, 2 and 3 are versions of the standard; level b means the look is preserved, u adds searchable Unicode text, and a adds full accessibility tagging.
Can it check encrypted PDFs?
Yes. Encryption itself is reported as a problem, because PDF/A doesn't allow it.
Is my PDF uploaded?
No. Everything happens in your browser, so the PDF stays on your device.
Can it convert my PDF to PDF/A?
No. It only checks. Re-export the document with PDF/A switched on in the program that created it, then check the new file here.
Why does a normal PDF fail?
Most everyday PDFs aren't made as PDF/A: they don't claim it, have no colour profile and may use unembedded fonts. That is expected; it just means the file isn't ready for archiving.