Skip to main content

PDF/A Validator

Check a file's PDF/A claim, fonts and metadata before you submit it.

Drop your PDF here to check PDF/A indicators

or click to browse

Max file size: 50 MB

Checking PDF/A indicators...

Reading archival metadata...

Analysis Complete!

PDF/A Indicators Checked

Recommendations

Technical Details

PDF Version
Total Fonts
Fonts Embedded
XMP Metadata
Encryption
ICC Color Profiles

A screening of common PDF/A requirements, not a full conformance test. If the recipient names a validator such as veraPDF, run that too.

  • Declared PDF/A part and level
  • Font embedding and encryption
  • Archive metadata and colour profile

What is PDF/A?

PDF/A is an ISO-standardized version of PDF designed for the long-term archiving of electronic documents. It restricts certain features (encryption, external dependencies, audio/video) to ensure the file can be reliably reproduced in the future.

  • PDF/A-1b — Basic (Level B)
  • PDF/A-2b — Basic (Level B)
  • PDF/A-3b — Basic (Level B)
  • PDF/A-4 — Latest standard

Is my PDF really PDF/A, and why would an archive reject it?

Upload a PDF to see which PDF/A version it claims and whether it shows the usual reasons archives reject files: fonts left out, a password, JavaScript or a missing colour profile. This is a screen of eight indicators. A pass does not certify the file as PDF/A, and an archive may still run its own validator.

How do I check if a PDF is PDF/A?

Upload it and read the Declared Standard line. A PDF/A file states its version and level, such as PDF/A-2b, in its hidden details, and the check reads that claim. If nothing is declared you see "No PDF/A marker found in this document", and the file is not PDF/A, however tidy it is. Archives and validators look for that declaration first.

The overall result is "PDF/A indicators pass" or "PDF/A indicators fail", followed by each indicator and a recommendation for anything that needs fixing.

What does the PDF/A check look at?

Eight things that archives commonly reject files for:

  • Declaration: the file states which PDF/A version and level it follows.
  • Archive metadata: the file carries the block of descriptive data where that declaration lives.
  • Font embedding: every font travels inside the file. Fonts that do not are named, up to three of them.
  • No encryption: the file has no password or other protection.
  • PDF version: the file format version is new enough for the declared PDF/A version.
  • No JavaScript: the file contains no scripts.
  • Output intent: the file includes the colour profile PDF/A uses to say what its colours mean.
  • Colour space: a colour profile was found somewhere in the file.

What do pass, warning and fail mean?

Each indicator is marked Pass, Warning or Fail. The overall result passes only when the file declares a PDF/A version and no indicator failed. Warnings do not change the overall result, but they point to things a stricter validator may object to, so read them.

A pass means none of the eight common problems was found. It is not a certificate of PDF/A conformance. The standard has many more rules than this screen tests.

Which PDF/A version do I need?

Use the one the archive you are submitting to asks for. If they name a version and level, export to exactly that. The versions differ mainly in which PDF features they allow.

  • Level b (basic) aims to preserve how the pages look.
  • Level u adds that all text can be searched and copied.
  • Level a adds tagged structure and other accessibility requirements on top of u.
PDF/A versions and levels
Version Based on Levels
PDF/A-1 PDF 1.4 a, b
PDF/A-2 PDF 1.7 a, b, u
PDF/A-3 PDF 1.7, and allows attached files of any format a, b, u
PDF/A-4 PDF 2.0 No level letters

Why does my PDF/A file fail?

The usual causes are fonts that are not embedded, a password, JavaScript, and a missing colour profile. The last one catches people out: a file can be exported with a PDF/A setting and still fail because no colour profile was included.

A declaration is only a claim. A file can say it is PDF/A-2b and still have fonts missing, and this check fails it for that. The reverse also happens. A clean file with every font embedded is still not PDF/A until it is exported as PDF/A, because without the declaration an archive has nothing to accept.

How do I fix a PDF that fails?

Go back to the source document and export again with the PDF/A option turned on. That is more reliable than editing the finished PDF, and it fixes a missing declaration, missing fonts and a missing colour profile in one step.

  • No declaration: choose the PDF/A preset your archive requires when you export.
  • Fonts not embedded: turn on font embedding for all fonts, then export again.
  • Encrypted: remove the protection completely. PDF/A does not allow encryption, even when the file opens without a password.
  • JavaScript: this usually comes from interactive form features. Flatten or remove them before you convert.
  • No output intent or colour profile: use a PDF/A preset that embeds a colour profile such as sRGB.

Is this a full PDF/A validator?

No. It screens for common problems and reads the file's claim. It does not test transparency, the colours each page actually uses, the rules for attachments, actions other than JavaScript, or the tagging and text requirements of levels a and u.

If your archive names a validator such as veraPDF, run that as well before you submit. A pass here is a reason to move on to the formal check, not a replacement for it. If the declaration fails here on a file you know was exported as PDF/A, run the formal validator before changing anything, because this screen cannot read a declaration stored in compressed form.

File limits

Files can be up to 50 MB on the Free plan. Each file you check uses one upload from your allowance.

Last updated . Written from the checker's source code and from test PDFs we built for the purpose.

Do more with a free account

Keep your report history, share reports by link, check several PDFs at once and use the API.