PDF/A Checker

Pre-check a PDF against common PDF/A requirements and see what to fix.

The PDF/A Checker tests 11 requirements that most often make a PDF fail PDF/A validation, such as the PDF/A declaration, embedded fonts, the color profile and encryption. It is a pre-check, not a certified validation: use veraPDF when you need proof of conformance.

Rate this tool
Secure HTTPS upload - your files stay private and are saved to your file manager.
PDF
PDF

How to check a PDF for PDF/A

  1. Press "Choose Files" and select the PDF you want to check, or drag and drop it.
  2. Press Check PDF/A. The file is read, never changed.
  3. Read the report: it shows the PDF/A part the file declares and marks each check Pass, Fail, Warning or Not applicable.
  4. Fix what failed, or convert the file with PDF to PDF/A, then check again and validate with veraPDF if you need proof.

Why use PDFBEAR for PDF/A Checker?

Free, no sign-up needed

Check a PDF as a guest with no account, no watermark and no install.

Explains every failure

Each problem comes with a short reason and the quickest way to fix it, not just a rule number.

Knows PDF/A-1, 2, 3 and 4

Part-dependent rules, such as transparency and attachments, are checked against the part your file declares.

Your PDF is never changed

The checker only reads the file. Your original stays exactly as it was.

Honest about what it is

It is a pre-check, not a certified validation, and it points you to veraPDF when you need proof.

Check, convert, check again

If the file fails, convert it with PDF to PDF/A and run the new file through the checker.


A pre-check, not a validation

PDF/A is the ISO 19005 family of standards for PDFs that must stay readable for decades. A PDF/A file has to carry everything it needs inside itself: fonts, a color profile, metadata that declares which part of the standard it follows, and nothing that could change or break over time, such as encryption, JavaScript or embedded video. If you are new to the format, what PDF/A is and when you are required to use it is the place to start.

This checker reads your PDF and tests 11 of the requirements that most often make a file fail. It tells you which part of PDF/A the file claims to follow, what failed, and how to fix it. It does not change your file, and it is not a certified validation. The standard has hundreds of detailed rules, and only a full validator tests them all. When an archive, court or auditor needs proof, validate the file with veraPDF, the free and open-source reference validator.

What gets checked

11
pre-checks
A-1 to A-4
parts recognized
0
changes made to your PDF
  • PDF/A declaration. Whether the XMP metadata declares a PDF/A part and conformance level, such as PDF/A-2b. A file that does not declare it is treated as a regular PDF by every validator.
  • Encryption. PDF/A allows no encryption at all, including permission restrictions on files that open without a password.
  • Color profile. An output intent with an embedded ICC profile, which PDF/A needs whenever a file uses device colors.
  • Embedded fonts. Every font has to be inside the file, including the common ones.
  • Scripts, actions and media. JavaScript, launch actions, audio, video and 3D content are not allowed.
  • Annotations. Comments and form fields must print and have a fixed appearance.
  • Transparency and attachments. Checked against the part the file declares: PDF/A-1 forbids transparency and attachments, PDF/A-2 allows transparency and PDF/A attachments, PDF/A-3 allows any attachment.
  • Document ID and metadata. A document ID in the file trailer, and matching values in the Info dictionary and the XMP metadata.

Fixing a file that fails

The quickest fix for most failures is to convert the file: PDF to PDF/A embeds fonts, adds a color profile and writes the PDF/A metadata. Run the result through this checker again, because conversion cannot fix everything; a font whose license forbids embedding, for example, has to be changed in the source. Encrypted files need their restrictions removed first with Unlock PDF.

The step-by-step guide to converting a regular PDF to PDF/A covers the choice between PDF/A-1, 2 and 3. If the document will also be published, the PDF Accessibility Checker tests the other half of a long-lived document: whether people using screen readers can read it.


PDF/A Checker formats, fidelity & use cases

Input formats
PDF
Output format
On-screen report + TXT file
Maximum file size
50 MB
Processing time
a few seconds
What is preserved
  • Your PDF is only read, never modified
  • Your original file stays exactly as it was
  • No watermark or branding added to your document
What changes
  • You get a report, not a new PDF
  • The declared PDF/A part and level are shown
  • Each check marked Pass, Fail, Warning or Not applicable
  • Every failure comes with a way to fix it

Popular use cases

Check a filing before uploading it to a court e-filing portal
Confirm a converted file declares PDF/A and embeds its fonts
Find out why a records system rejected a PDF
Spot encryption or JavaScript before archiving
Check invoices and statements before long-term storage
Decide whether a file needs PDF/A-2 or PDF/A-3

PDF/A Checker file requirements and limits

Free file size50 MB
This is a pre-check of the most common PDF/A failures, not a certified validation against every rule in ISO 19005. When you need proof of conformance, validate the file with veraPDF.

Common PDF/A Checker problems and how to fix them

The file fails "Declares PDF/A in its metadata"

Why it happens: The PDF was saved as a regular PDF, so it has no PDF/A identification in its XMP metadata.

Fix: Convert it with PDF to PDF/A, which writes the declaration, color profile and metadata, then check the new file. PDF to PDF/A →

The file is encrypted or asks for a password

Why it happens: PDF/A does not allow any encryption, including permission restrictions on files that open without a password.

Fix: Remove the password or restrictions from a file you own, then convert the unlocked copy to PDF/A. Unlock PDF →

The checker says the file could not be read

Why it happens: The PDF is damaged or incomplete, for example cut short during a download.

Fix: Repair the file first, then check the repaired copy. Repair PDF →


PDF/A Checker vs veraPDF (reference validator)

veraPDF is the free, open-source PDF/A validator developed by the Open Preservation Foundation and the PDF Association. It tests every rule in the standard; this checker is a faster, plain-English pre-check of the most common failures.

DimensionPDF/A Checker (PDFBEAR)veraPDF (reference validator)
Rule coverage11 most common failure pointsEvery rule in ISO 19005
Install neededRuns in any browserDesktop app or command line
ResultsPlain-English fixes per checkTechnical rule-by-rule report
Proof of conformanceNo, a pre-check onlyYes, widely accepted
CostFreeFree, open source

Who uses PDF/A Checker?

Paralegal
Checks exhibits and briefs before uploading them to a court e-filing system that rejects files that are not PDF/A.
Records manager
Pre-checks documents before they enter the long-term archive, and sends failures back for conversion.
Archivist
Triages incoming digital donations to see which files already declare PDF/A and which need converting.
Accounts payable clerk
Confirms that invoices kept for statutory retention embed their fonts and carry no encryption.
Thesis coordinator
Checks that a graduate's final thesis PDF meets the library repository's PDF/A deposit requirement before submission.
Compliance officer
Spot-checks reports archived by a document system to confirm they really are PDF/A and were not edited afterwards.

PDF/A Checker — Frequently Asked Questions

Yes. It is free to use without an account, within the same guest limits as the other free PDFBEAR tools.

No. It is a pre-check of the requirements that most often cause a file to fail. For proof of conformance, validate the file with veraPDF, the reference validator that most archives accept.

It reads the declaration for PDF/A-1, 2, 3 and 4 and adjusts the part-dependent checks, such as transparency and attachments, to the part the file claims.

The declaration is only a claim written into the metadata. A file can declare PDF/A and still have unembedded fonts, encryption or a missing color profile, often because it was edited after conversion.

No. It only reads the file and gives you a report. To fix a failing file, convert it with PDF to PDF/A and check the new file again.

An on-screen report with each check marked Pass, Fail, Warning or Not applicable, a short explanation and a fix, plus a plain-text copy to download or share.

It reports that the file is encrypted, which PDF/A never allows, but it cannot run the other checks until the password is removed.

Your PDF is uploaded over HTTPS and is only read by the checker. Guest result links expire after 24 hours; with a free account, results stay in your file manager for 30 days after your last activity and you can delete them at any time.

When to use PDF/A Checker

Use the PDF/A Checker to see, before you submit a file, whether it declares PDF/A and avoids the problems that most often fail validation: missing color profile, unembedded fonts, encryption, JavaScript, embedded media and mismatched metadata.

Best for

  • Checking a file before sending it to a court e-filing system, archive or records office.
  • Confirming that a file you converted actually declares PDF/A and embeds its fonts.
  • Finding out why a portal rejected a PDF that was supposed to be PDF/A.

Not best for

  • Certified validation; use veraPDF when you need proof of conformance.
  • Converting the file; use PDF to PDF/A for that.
  • Checking accessibility; use the PDF Accessibility Checker.

Optimize PDF workflow

Improve a PDF before delivery by reducing file size, fixing damaged files, making scans searchable and locking final page content.

Explore all optimize pdf tools