What Is PDF/A? The Archiving Standard Explained

If you've ever tried to open an archived PDF from ten years ago only to find missing fonts, broken layouts, or unreadable content, you've experienced exactly the problem that PDF/A was designed to solve. So, what is PDF/A? In short, it's an ISO-standardized version of the PDF format built specifically for long-term digital archiving. Unlike a regular PDF, which can rely on external resources, encryption, or proprietary elements that may not exist in the future, PDF/A locks everything needed to render the document correctly inside the file itself. For operations teams managing compliance records, legal contracts, or financial reports, understanding this format isn't optional - it's essential.

Why PDF/A Was Created

The PDF format was introduced by Adobe in the early 1990s as a way to share documents reliably across different systems. It worked well for everyday use, but archiving is a different challenge entirely. Government agencies, courts, hospitals, and financial institutions needed a format that would still be perfectly readable in 25, 50, or even 100 years - regardless of what software or hardware existed at that point.

To address this, the International Organization for Standardization (ISO) published ISO 19005 in 2005, formally defining PDF/A as a self-contained, preservation-focused variant of PDF. The "A" stands for archiving. The standard has since been updated in multiple parts to accommodate evolving needs.

The Problem with Regular PDFs for Archiving

A standard PDF is surprisingly fragile from a long-term perspective. Here are the core issues that make regular PDFs a poor choice for the pdf archiving format role:

• Font dependencies: A standard PDF can reference fonts that are installed on the creator's system but not embedded in the file. If that font isn't available when someone opens the document years later, the viewer substitutes a different font - changing the layout or making text unreadable.
• Encryption and DRM: Password-protected PDFs or those with digital rights management (DRM) restrictions may become inaccessible if the decryption key or software is no longer available.
• External content: Regular PDFs can depend on content outside the file, such as external streams, Launch actions that open other files or programs, or JavaScript. If that content disappears or stops working, the page may no longer render as intended. Ordinary hyperlinks are different: a dead link does not change how the page looks.
• Color space issues: Without defined color profiles, a document's colors may render differently on different devices or future display technologies.
• Proprietary metadata: Some PDFs include metadata in formats tied to specific software versions, which may not be interpretable by future systems.

Concrete example: Imagine a legal firm that stored signed contracts as standard PDFs in 2008. The documents used a custom proprietary font and included JavaScript-based signature validation. By 2020, the font was discontinued and the validation script no longer ran in modern PDF viewers. The files looked corrupted even though they were technically intact. Had those files been saved as PDF/A, all fonts would have been embedded and JavaScript would have been prohibited - the documents would still be perfectly readable today.

PDF/A Standards Explained: PDF/A-1 to PDF/A-4

The ISO 19005 PDF standard has evolved through four major versions, each building on the last. Understanding which version fits your use case matters before you convert or create archived documents.

PDF/A-1, PDF/A-2 and PDF/A-3 use letters for their conformance levels. Level b (basic) guarantees that the page looks the same. Level u adds Unicode mapping so text can be reliably searched and copied. Level a adds a tagged logical structure and reading order on top of that, which also helps assistive technologies.

PDF/A-1 (ISO 19005-1, published 2005)

The original standard. It has two conformance levels:

• PDF/A-1a (Level A): Tagged structure and Unicode mapping. Best for documents that need reliable text extraction and a defined reading order.
• PDF/A-1b (Level B): Basic compliance. Ensures visual reproducibility but doesn't require full tagging. Suitable for scanned documents or files where accessibility isn't the primary concern.

PDF/A-2 (ISO 19005-2, published 2011)

Based on PDF 1.7, this version added support for JPEG 2000 compression, digital signatures (using PAdES), transparency, and optional content (layers). It also introduced Level U, so PDF/A-2 comes in 2a, 2b and 2u. Embedded files are allowed only if they are PDF/A files themselves.

PDF/A-2 is a strong choice for modern archiving workflows that involve complex graphics or need to support digital signatures.

PDF/A-3 (ISO 19005-3, published 2012)

The most flexible version. It allows embedding of arbitrary file formats (XML, spreadsheets, source files) as attachments within the PDF/A container. This is particularly useful in industries like manufacturing or finance, where the source data (an XML invoice, for example) needs to travel with the rendered document. Note that the embedded files themselves are not required to be PDF/A compliant.

PDF/A-4 (ISO 19005-4, published 2020)

The newest version is based on PDF 2.0. It drops the a/b/u letters and uses one base level plus two variants: PDF/A-4f, which allows embedded files of any type, and PDF/A-4e, which is meant for engineering documents and supports 3D content. Support in archives and software is still catching up, so use it only when your archive and tools explicitly support PDF 2.0.

Who Uses PDF/A?

PDF/A compliance is not just a technical preference - in many industries, it's a regulatory requirement or a contractual obligation.

• Government agencies: National archives and public records offices in the US, EU, and elsewhere mandate PDF/A for long-term document storage. The US National Archives, for instance, accepts PDF/A as a preferred format for electronic records.
• Legal sector: Some courts and electronic filing systems require or recommend PDF/A for filings, because case records can need to stay readable for decades.
• Healthcare: Patient records, clinical trial documentation, and regulatory submissions often need to be stored for 10-30 years. PDF/A ensures those records remain intact and accessible.
• Finance: Banks, auditors, and financial institutions often store transaction records, audit trails, and compliance reports in PDF/A to keep them readable over long retention periods. E-invoicing formats such as Factur-X and ZUGFeRD are built on PDF/A-3.
• Operations teams: Internal process documentation, quality management records, and supplier contracts benefit from PDF/A when long-term traceability is required.

PDF/A vs Standard PDF - Key Technical Differences

When comparing PDF/A vs PDF, the differences aren't just cosmetic. They reflect a fundamental shift in design philosophy from "works now" to "works forever."

The restrictions in PDF/A are intentional. Every prohibited feature is something that could prevent a document from rendering correctly in the future. The standard trades flexibility for permanence.

How to Check If a PDF Is PDF/A Compliant

Not every PDF labeled as "PDF/A" actually meets the standard. Here's how to verify PDF/A compliance properly:

1. Look for the PDF/A notice bar: When Adobe Acrobat opens a file that declares PDF/A conformance, it shows a notice bar at the top of the document. This is a quick first check, but it only tells you what the file claims to be.
2. Use a dedicated validator: The veraPDF (an open-source validator) or the PDF/A profiles in Acrobat Pro's Preflight can run a full conformance check and report specific violations.
3. Look for the PDF/A identifier in the file: A valid PDF/A file contains an XMP metadata block that declares its conformance level (e.g., PDF/A-1b or PDF/A-2a). If this block is missing or malformed, the file is not compliant.
4. Use an online converter/checker: Some online tools can both validate and convert in one step, which is the most efficient approach for operations teams handling large volumes of documents.

If you're also archiving scanned documents, add a searchable text layer with OCR before or during PDF/A conversion. The ocrmypdf method in the next section does both in one step.

How to Convert a PDF to PDF/A

Use software that writes PDF/A directly. If you're unsure which level to pick, PDF/A-2b is a safe default for most business documents. Embedded video, audio, JavaScript and external content are removed or flagged during conversion, but ordinary hyperlinks can stay. LooPDF doesn't create PDF/A files yet, so use one of these methods:

1. Remove password protection first: PDF/A prohibits encryption, so an encrypted file must be unlocked before conversion. If you have the password, you can do this with Remove Password Protection.
2. Microsoft Word: When saving a document as PDF, open Options and tick "PDF/A compliant".
3. LibreOffice: Use File, Export as PDF, tick the "Archive (PDF/A)" option and choose the PDF/A version.
4. Adobe Acrobat Pro: Open Preflight, pick a PDF/A conversion profile such as PDF/A-2b and run it. Preflight reports anything it could not fix.
5. Ghostscript for batch work: The -dPDFA option (for example -dPDFA=2) converts files from the command line, which suits large batches. It needs an ICC profile for the output intent, so test the settings on a few files first.
6. ocrmypdf for scans: ocrmypdf adds an OCR text layer to scanned PDFs and writes PDF/A output by default.
7. Validate with veraPDF: Whatever tool you use, check the result with veraPDF, because a conversion that silently drops features can still produce a file that fails the standard.

For those concerned about uploading sensitive documents to online tools, we've addressed this directly in our post on whether online PDF tools are safe to use.

Conclusion

PDF/A isn't just a technical checkbox - it's a practical commitment to document longevity. For operations teams, legal departments, and compliance officers, choosing the right archiving format today prevents costly retrieval failures years from now. The standard removes the features most likely to break a document over time, and a validator can confirm that a file actually meets it. Whether you're dealing with a handful of contracts or thousands of records, converting to PDF/A is a straightforward step with long-term payoff. Start with your most critical documents and work outward from there.

Frequently Asked Questions