Guides/What Is PDF/A and Why Archives Use It
What Is PDF/A and Why Archives Use It
Open a PDF from 2005 on a modern computer and it will almost certainly look exactly the way it was intended to — which is remarkable for a twenty-year-old file. But "almost certainly" is not good enough for archives, courts, governments and institutions that need to guarantee a document will render identically not just today, but in fifty or a hundred years. PDF/A is the version of PDF designed specifically for that guarantee: a self-contained, fully specified document that does not depend on anything outside itself to be read correctly, now or in the future.
What makes PDF/A different from a regular PDF
A regular PDF can reference external resources — fonts installed on the viewer's system, linked images hosted elsewhere, JavaScript that runs when the document is opened. This is fine for everyday use, but it creates dependencies: if a font is missing, text reflows or substitutes with a different typeface; if a linked resource disappears, content is lost; if JavaScript stops being supported, interactive elements break. Any of these could make the document look different — or fail entirely — years from now.
PDF/A eliminates these dependencies by requiring that everything the document needs is embedded inside the file itself. All fonts must be fully embedded, not referenced. Images must be included, not linked. JavaScript is prohibited entirely. Color profiles must be specified explicitly. The result is a file that contains, within itself, every piece of information needed to render it exactly the same way on any viewer, on any operating system, at any point in the future — with no reliance on anything external.
PDF/A versions: 1b, 2b, 3b and what they mean
PDF/A comes in several versions, each building on the last. PDF/A-1 (based on PDF 1.4) was the original standard, introduced in 2005. PDF/A-2 (based on PDF 1.7) added support for JPEG2000 compression, transparency, and embedded PDF/A files — features that the earlier version did not allow. PDF/A-3 goes further by allowing any file type to be embedded as an attachment (not just other PDF/A documents), which makes it useful for things like embedding the source data (a spreadsheet, an XML dataset) alongside its human-readable representation.
Within each version, the "b" (basic) conformance level requires visual fidelity — the document must look correct — while "a" (accessible) additionally requires tagged, structured text that assistive technologies can interpret. In practice, most archival requirements specify PDF/A-1b or PDF/A-2b: the document must be visually self-contained and reproducible, which is the core guarantee that matters for long-term preservation.
Who requires PDF/A and when you will encounter it
Courts, government agencies, and regulatory bodies are the most common sources of PDF/A requirements. Many European courts require filings in PDF/A format. The United States federal courts' CM/ECF system accepts PDF/A. National archives in Germany, Switzerland, the Netherlands and other countries mandate it for official records. Universities often require theses and dissertations to be submitted as PDF/A for their institutional repositories.
In business, PDF/A shows up in long-term contract storage, financial recordkeeping, and any industry where regulatory compliance requires provable document integrity over time — banking, insurance, healthcare, pharmaceuticals. If you have ever been asked to submit a document in "PDF/A format" and had no idea what that meant, this is what they were asking for: a self-contained PDF that will be readable identically regardless of what software or operating system exists in the future.
How to check if a PDF is PDF/A
The easiest way to check is to open the file's properties or metadata: PDF/A-compliant files include a specific metadata entry (an XMP identification schema) declaring which version and conformance level they meet. Many PDF viewers will show this in their document properties panel — Adobe Reader, for example, displays a blue "PDF/A" banner at the top of the page when it detects a conforming file.
If you need to create a PDF/A document, the most reliable approach is to use a tool that explicitly exports to that standard — many PDF editors and office suites offer "Save as PDF/A" as an export option. Converting an existing regular PDF to PDF/A after the fact is possible but sometimes produces validation errors if the source file uses features (like JavaScript or external links) that PDF/A prohibits. Starting from the source document and exporting directly is usually cleaner than trying to retrofit compliance onto an existing file.
Tools mentioned in this guide