What is PDF/A? Complete Guide to the Archival PDF Format (2026)

PDF/A is an ISO-standardized version of PDF designed for long-term archival storage. Unlike a regular PDF — which can reference fonts installed on your computer, contain JavaScript, link to external resources, and be encrypted — a PDF/A file is fully self-contained, with every font embedded inside the document and every feature that depends on external resources stripped out. The result is a document guaranteed to render the same way decades from now, regardless of what fonts are installed or what software is available.

If you've been asked to submit a "PDF/A compliant" document, or you're trying to decide between PDF and PDF/A for archiving important records, this guide covers everything you need to know.

What Does PDF/A Stand For?

PDF/A stands for "Portable Document Format for Archiving." It's defined by the ISO 19005 standard, originally published in 2005 and updated several times since. The "/A" suffix distinguishes it from standard PDF (ISO 32000) and from other PDF variants like PDF/X (for print production) and PDF/E (for engineering).

Why PDF/A Exists

Regular PDFs were never designed for long-term preservation. They can:

• Reference external fonts — if the font isn't on your computer, the PDF substitutes another, sometimes badly
• Contain JavaScript — which may not work in 30 years when the PDF spec evolves
• Link to external resources — images, multimedia, hyperlinks that break when the linked content moves
• Be encrypted — making it impossible to render without the password (which may be lost)
• Use compression schemes — that future readers may not support

For a contract that needs to be readable in 50 years, an academic thesis that goes into a library archive, a court filing that becomes part of permanent legal record, or government records that have retention requirements — these dependencies are unacceptable risk.

PDF/A fixes all of this by embedding everything the document needs to render directly inside the file, and forbidding any feature that requires external dependencies.

PDF vs PDF/A — The Core Differences

Feature	Regular PDF	PDF/A
Fonts	Can reference system fonts	Must embed all fonts
JavaScript	Allowed	Forbidden
Encryption	Allowed	Forbidden
External links	Allowed	Forbidden
Audio/video	Allowed	Forbidden
Transparency	Allowed (PDF 1.4+)	Allowed in PDF/A-2 and 3, forbidden in PDF/A-1
Color management	Optional	Required (device-independent color)
XMP metadata	Optional	Required, with PDF/A identifier

Visually, a PDF and its PDF/A equivalent look identical. The difference is entirely in what the file contains under the hood.

PDF/A Variants Explained

There are three main PDF/A standards, and each has sub-levels.

PDF/A-1 (2005)

The original variant. The most restrictive — no transparency, no JPEG 2000 compression, no layers. Based on PDF 1.4.

• PDF/A-1a: Accessible (requires tagged structure for screen readers)
• PDF/A-1b: Basic (visual reproduction guaranteed, but not necessarily accessible)

PDF/A-2 (2011)

Added support for transparency, JPEG 2000, OpenType fonts, and embedded PDF/A files. Based on PDF 1.7. This is the most common choice for new archival projects today.

• PDF/A-2a: Accessible
• PDF/A-2b: Basic
• PDF/A-2u: Unicode (text must be mapped to Unicode)

PDF/A-3 (2012)

Same as PDF/A-2 but allows embedded files of any format (like the original Word document, an XML invoice, or source data). This is the variant used for German ZUGFeRD e-invoices.

For most archival use cases, PDF/A-2b is the right choice — modern features, good tool support, no accessibility burden.

When You Need PDF/A

You generally need PDF/A when:

• Government submissions: Many e-filing systems (US Courts PACER, EU TED, various tax authorities) require PDF/A
• Legal records: Court filings, evidence preservation, contract archives with multi-decade retention
• Academic archives: Theses, dissertations, library digital collections
• Healthcare records: Long-term patient record retention (HIPAA-compliant archival)
• Compliance frameworks: ISO 9001 document control, SOX retention, GDPR record-keeping
• Corporate records: 7+ year financial documents, audit trails

If you're just sharing a document by email or storing it on a personal drive for the next few years, you don't need PDF/A — regular PDF is fine.

How to Convert PDF to PDF/A

There are three main paths:

Browser-Based Conversion (Free, Private)

PDF Zone's PDF to PDF/A converter runs entirely in your browser. It:

1. Strips disallowed features (JavaScript, encryption, embedded actions)
2. Embeds the required XMP metadata identifying the file as PDF/A-2b
3. Cleans up the document structure

This is the fast path when you have a sensitive document and don't want it uploaded to a third-party server. For mission-critical certified archival, validate the output with veraPDF, the open-source PDF/A validator.

Adobe Acrobat Pro

The gold standard for certified PDF/A conversion. File → Save As Other → Archivable PDF. Adobe handles all the edge cases — font embedding, color management, accessibility tagging — and produces validated PDF/A output. Costs about $25/month.

Command-Line Tools

For batch processing or automation:

• Ghostscript: gs -dPDFA=2 -sProcessColorModel=DeviceRGB -sDEVICE=pdfwrite -sPDFACompatibilityPolicy=1 -sOutputFile=out.pdf in.pdf
• veraPDF + qpdf: A free pipeline for conversion and validation

How to Verify PDF/A Compliance

After converting, you should validate. The reference validator is veraPDF — an open-source tool maintained by the PDF Association. Drop your PDF in, and it'll report whether the file conforms to the claimed PDF/A standard, plus any specific rules it violates.

If you need certified compliance (government, legal), validate before submission. If you're doing best-effort archival, the browser-based conversion is usually good enough.

Common Misconceptions

"PDF/A is just a renamed PDF." No — it's a strict subset with specific requirements. Renaming a .pdf file to look like PDF/A doesn't make it compliant. The XMP metadata and the actual file contents must match the standard.

"PDF/A is required by law." Not generally — it's required by specific systems and frameworks. Check the actual requirement of whoever is asking.

"PDF/A files are larger." Often yes, because embedded fonts add size. The tradeoff is portability and longevity.

"You need Adobe to make PDF/A." Not anymore. Free open-source tools and browser-based converters produce valid PDF/A output for most documents.

Bottom Line

If you're archiving a document for long-term preservation, court filing, regulatory compliance, or library collection, convert it to PDF/A. For everyday sharing, regular PDF is fine. When in doubt, PDF/A-2b is the right modern default — broadly supported, no accessibility burden, captures all the archival guarantees.

Try PDF Zone's free PDF to PDF/A converter →