PDF vs PDF/A: which one should you keep?

If you've ever uploaded a document to a government portal or a court filing system, you may have hit a message like "this file must be PDF/A." It sounds like a typo, or a stricter version of a normal PDF. It's actually a different promise about the file: that it will still open and look the same decades from now. This post explains what PDF/A is, how it differs from a regular PDF, and when you actually need it.

A regular PDF is a snapshot of its moment

A standard PDF is remarkably flexible. It can link to external content, play audio, run JavaScript, reference fonts installed on your computer, and pull in resources from elsewhere. That flexibility is great for an interactive document today. It's a liability for a document meant to last. If a PDF relies on a font your future computer doesn't have, the text may reflow or substitute into something that looks wrong. If it points to an external resource that disappears, part of the document is gone. The file was never fully self-contained.

PDF/A is a PDF that promises to be self-contained

PDF/A is an ISO-standardized subset of PDF designed for long-term archiving (the "A" stands for archival). It takes the normal PDF format and adds rules. The core idea is simple: everything the document needs to render correctly must live inside the file itself. In practice that means:

• All fonts are embedded. No relying on the reader's system to have Arial or some corporate typeface.
• No external dependencies. No links to content that could vanish, no streaming, no "fetch this from a server."
• No JavaScript or executable content. An archive shouldn't run code, partly for stability and partly for security.
• Color is defined unambiguously. Color spaces are specified so the document looks the same regardless of the device.
• Metadata follows a standard format so future systems can catalog and index the file reliably.

The result is a file that a reader in 2050 should be able to open and see exactly what you saw, without hunting for fonts or chasing dead links.

The flavors: PDF/A-1, A-2, A-3

There are a few versions, and the difference matters if a system specifies one:

• PDF/A-1 is the original and the strictest. Based on PDF 1.4. No transparency, no layers. Maximum compatibility, least flexibility.
• PDF/A-2 adds support for things like JPEG2000 compression, transparency, and layers, while keeping the archival guarantees.
• PDF/A-3 is like A-2 but allows you to embed arbitrary files (for example, the original spreadsheet behind an invoice) inside the archive.

Each also has conformance levels (commonly "a" and "b"). Level "b" guarantees the visual appearance is preserved. Level "a" adds structural and accessibility requirements, like a tagged reading order for screen readers. If a portal just says "PDF/A," level "b" is usually what they mean.

When you actually need PDF/A

You need it when someone tells you to, and they usually have a reason:

• Court and legal filing systems, which must preserve records for years.
• Government submissions and public records.
• Academic thesis and dissertation repositories.
• Corporate compliance archives, where records must be retained and reproducible.
• Any "store this and don't touch it for a decade" scenario.

For everyday documents (a contract you'll sign this month, a report you'll email, a flyer) a regular PDF is fine and often better. PDF/A files tend to be larger because every font is embedded in full or subset, and you lose features like interactive forms behaving the way you might want.

When a regular PDF is the better choice

Don't convert to PDF/A by default. If your document has interactive form fields you need filled, JavaScript-driven validation, or links you want live, PDF/A will strip or restrict those. For sharing, reviewing, and general use, a standard PDF is more capable and lighter. Reserve PDF/A for the archive, not the working copy.

Converting between the two

Going from a regular PDF to PDF/A means embedding all fonts, removing disallowed features, and tagging the metadata correctly. Going the other way (PDF/A back to a regular PDF) is trivial, since PDF/A is already a valid PDF; you're just no longer bound by the extra rules. The harder direction is the conversion to PDF/A, because the tool has to find and fix everything the standard forbids.

A note on privacy during conversion

The documents that most often need PDF/A (legal filings, medical records, financial compliance files) are exactly the ones you'd least want to upload to a random converter. That's the irony of archival formats: the most sensitive material is the most likely to require special handling. Tools that process files in the browser keep the document on your device through the conversion, which matters more for this category than almost any other. The record you're preserving for ten years shouldn't pass through someone else's server on its way to the archive.

The short version

A regular PDF is flexible and great for today. PDF/A is a stricter, self-contained version built to survive decades, which you use when a system demands it or when you're archiving something for the long haul. Keep the regular PDF as your working copy, make a PDF/A when you need to file or store, and don't convert everything to PDF/A just because you can. The right format is the one that matches how long the document needs to live.