Back to All Guides
Compliance12 min readUpdated 2026-10-18

Understanding PDF/A Archiving Standards: PDF/A-1b, PDF/A-2b, PDF/A-3, and PDF/X

The Authoritative Reference for Legal Filings, IRS E-File, and Long-Term Digital Preservation

I
IMON Khan
Lead Systems Architect at AmarPDF
Executive Summary & Key Takeaways
  • Standard PDFs allow external font references, dynamic JavaScript, and unmanaged device-dependent colors—all of which can cause the document to render incorrectly or fail to open 20 years from now.
  • PDF/A (ISO 19005) is an internationally standardized electronic archiving format that guarantees identical visual reproduction across future hardware and operating systems.
  • Core PDF/A mandates require 100% embedded fonts, standardized XMP metadata, and device-independent color profiles (ICC OutputIntents).
  • Dynamic interactive elements such as audio/video embeds, JavaScript triggers, encryption passwords, and external hyperlinks are strictly prohibited in PDF/A.

The Digital Preservation Problem: Why Regular PDFs Fail Over Time

Standard PDF files (ISO 32000-1 and 32000-2) are designed primarily for dynamic workplace interchange. To maximize flexibility and minimize file size, typical PDF creators frequently omit full font files, relying instead on 'system fonts' installed on the viewing device (such as Arial, Times New Roman, or Helvetica). If a user opens that PDF fifteen years later on an operating system where the original font is unavailable or has altered licensing metrics, the PDF reader substitutes an alternative typeface. This shifts line wraps, causes table text to spill over margins, and alters numeric data alignments in financial statements. Furthermore, standard PDFs frequently contain: - Dynamic JavaScript scripts that can cease functioning when browser runtime sandboxes evolve. - Device-dependent color codes (raw RGB or CMYK values without an embedded ICC color profile) that appear dramatically shifted on future display technologies. - Audio/video streams and interactive forms (Adobe XFA) that modern non-Adobe PDF viewers refuse to execute. To establish absolute permanence for records of enduring value, the International Organization for Standardization developed **ISO 19005**, colloquially known as **PDF/A**.

The Conformance Hierarchy: PDF/A-1, PDF/A-2, PDF/A-3, and Conformance Levels (a, b, u)

PDF/A is organized into four major chronological parts, each tailored to specific technological capabilities and archiving requirements: 1. **PDF/A-1 (ISO 19005-1:2005 - Based on PDF 1.4):** - The initial archiving benchmark. Strictly forbids transparency effects (drop shadows, opacity layers) and JPEG 2000 image compression. - **Level 1b (Basic):** Mandates visual preservation over time. The document must render identically on any viewer. - **Level 1a (Accessible):** Enforces 1b visual rules PLUS a fully tagged document structure tree (logical heading hierarchies, reading orders, alternative text for images) for assistive technology and screen readers. 2. **PDF/A-2 (ISO 19005-2:2011 - Based on PDF 1.7):** - Adds native support for alpha transparency, JPEG 2000 image streams, embedded PDF/A collections, and OpenType fonts. - **Level 2u (Unicode):** Requires that all text contains unambiguous Unicode mappings, ensuring that searching and copy-pasting extract precise text characters rather than gibberish symbols. 3. **PDF/A-3 (ISO 19005-3:2012):** - Introduces a revolutionary feature: the ability to embed arbitrary third-party file formats (XML, CSV, CAD drawings, raw Excel spreadsheets) directly inside the PDF container. - Extensively used across Europe for standardized e-invoicing frameworks (such as ZUGFeRD and Factur-X), where a human-readable PDF invoice contains an identical machine-readable XML invoice embedded inside its attachment dictionary. 4. **PDF/X vs PDF/A (Pre-press vs Archiving):** - While PDF/A targets long-term document archiving, **PDF/X (ISO 15930)** targets commercial high-end offset printing. PDF/X mandates CMYK color spaces, bleed boxes, trim boxes, and trapped annotations, but is not designed for electronic legal storage.
Comprehensive PDF/A Conformance Comparison Matrix
StandardBase SpecKey FeatureTransparency SupportEmbedded File SupportPrimary Regulatory Usage
PDF/A-1bPDF 1.4Visual permanenceForbiddenForbiddenState court filings, basic legal briefs
PDF/A-1aPDF 1.4Visual + Tagged AccessibilityForbiddenForbiddenFederal government filings (Section 508)
PDF/A-2bPDF 1.7Visual + Modern graphicsPermittedPermitted (PDF/A only)National Archives, institutional repositories
PDF/A-2uPDF 1.7Visual + Unicode searchablePermittedPermitted (PDF/A only)Corporate contracts, searchable audit archives
PDF/A-3bPDF 1.7Arbitrary file attachmentsPermittedPermitted (XML/CSV/DWG/etc.)Electronic Invoicing (ZUGFeRD, Factur-X)
PDF/X-4PDF 1.6Commercial pre-press colorPermittedN/AHigh-volume print publications & packaging

Technical Checklist: What Makes a PDF Compliant with PDF/A?

A PDF document cannot achieve verified PDF/A validation unless its binary object tree conforms to the following strict criteria: 1. **Complete Font Embedding (/FontDescriptor):** Every font referenced in the document must be 100% embedded in its entirety or as a valid subset font with glyph widths, encodings, and Unicode CMap tables. 2. **Standardized Device-Independent Color (OutputIntents):** The PDF catalog dictionary (`/Root`) must include an `/OutputIntents` array containing a recognized ICC profile (such as `sRGB IEC61966-2.1` for RGB documents or `U.S. Web Coated (SWOP) v2` for CMYK). 3. **Extensible Metadata Platform (XMP):** The document must contain valid XML metadata conformant to ISO 16684-1, explicitly stating the PDF/A part number and conformance level (e.g., `pdfaid:part="2"` and `pdfaid:conformance="B"`). 4. **Zero Encryption:** Passwords and document permissions (Owner/User security handlers) are explicitly barred. An archived historical record cannot be locked behind proprietary encryption algorithms that may be abandoned or unrecoverable centuries later.
Court & Federal Mandates
The US Federal Court Case Management/Electronic Case Files (CM/ECF) system, the US Patent and Trademark Office (USPTO), and the IRS strictly enforce PDF/A conformance. Uploading standard PDFs with un-flattened forms or missing fonts will trigger automated rejections.
In-Depth FAQ

Frequently Asked Technical Questions

Can I convert a regular PDF to PDF/A using AmarPDF?

Yes. AmarPDF's compliance tools inspect your document, embed missing font metrics, embed standard sRGB ICC color profiles, flatten dynamic XFA forms, and generate certified XMP metadata compliant with ISO 19005-2.

Why does converting to PDF/A increase my file size?

PDF/A requires embedding the complete binary font subsets and an ICC color profile (which alone can add 100KB to 500KB of color lookup tables). However, AmarPDF applies FlateDecode stream compression to minimize this footprint.

Can a PDF/A document have a password?

No. ISO 19005 strictly forbids password protection or encryption keys. The core philosophy of digital archiving requires that documents remain accessible to future generations without requiring proprietary cryptographic keys.

I
Written by IMON Khan
Lead Systems Architect at AmarPDF

Systems engineer specializing in high-performance document compilers, stream compression algorithms, and client-side WebAssembly execution.