Document Management9 min readUpdated Sep 2, 2026

PDF/A Standard Explained: ISO Compliance, Conformance Levels & Long-Term Digital Archiving

Digital documents are often expected to remain accessible and visually identical decades into the future. However, standard PDF files frequently rely on external system fonts, device-dependent color spaces, and dynamic scripts that degrade over time. The ISO 19005 standard (PDF/A) guarantees long-term electronic document preservation. This guide breaks down conformance levels (1b, 2b, 2u, 3), prohibited features, and best practices for creating bulletproof digital archives.

PDFDock Engineering Team

Document Systems & Security Specialists

Key Technical Takeaways

PDF/A is an ISO-standardized subset of PDF specifically designed for preserving digital records over decades.
Standard PDFs allow external font links, encryption, audio, and JavaScript—all of which are strictly forbidden in PDF/A.
PDF/A-1 is based on PDF 1.4, PDF/A-2 adds JPEG 2000 and transparency support, and PDF/A-3 allows embedding arbitrary file attachments (e.g. XML invoices).
Conformance levels 'b' (basic visual), 'a' (accessible structured text), and 'u' (Unicode mapped) define the depth of machine readability.

1. What is PDF/A and Why Standard PDFs Fail Over Time

Standard PDF documents (defined by ISO 32000) are designed for dynamic document display across modern software environments. However, standard PDFs are not guaranteed to display consistently ten, twenty, or fifty years into the future. The primary reasons standard PDFs fail long-term preservation tests include: 1. **Unembedded System Fonts**: Standard PDFs can reference external fonts (such as Helvetica, Times New Roman, or system-installed typefaces) instead of embedding glyph outlines. When rendered on an operating system without those exact fonts installed, fallback fonts distort text layout, causing overflow and unreadable characters. 2. **Device-Dependent Color Spaces**: Colors defined in simple RGB or CMYK values without embedded ICC color profiles render unpredictably across different monitor calibrations and printing press hardware. 3. **External Hyperlinks and Dynamic Scripts**: Embedded JavaScript, audio/video streams, and links to external internet resources deteriorate as external servers vanish and runtime interpreters evolve. 4. **Encryption and Password Locks**: If an encrypted PDF is locked with a legacy cipher or forgotten passphrase, the archival record becomes permanently irretrievable. PDF/A (ISO 19005) resolves this by enforcing **Self-Containment**: every font glyph, vector outline, image raster, and color profile required to render the document must be physically embedded within the file itself.

The fundamental philosophy of PDF/A is 'visual preservation': a PDF/A compliant document opened fifty years from now must render identically on screen and in print, regardless of the software or hardware used.

2. PDF/A Parts and Conformance Levels (1b, 2b, 3b, etc.)

The PDF/A standard has evolved across three major ISO releases, each offering specific conformance levels tailored to document needs: ### PDF/A Parts - **PDF/A-1 (ISO 19005-1:2005)**: Based on PDF 1.4. Prohibits transparency, layers, and JPEG 2000 compression. - **PDF/A-2 (ISO 19005-2:2011)**: Based on PDF 1.7 (ISO 32000-1). Adds support for transparent elements, PDF layers, JPEG 2000 compression, and embedded PDF/A attachments. - **PDF/A-3 (ISO 19005-3:2012)**: Extends PDF/A-2 by permitting arbitrary file formats (such as XML, CSV, CAD drawings, or raw text) to be embedded inside the PDF container. ### Conformance Levels: b, u, and a Each part of the PDF/A specification supports distinct conformance levels:

Conformance Level	Focus	Unicode Requirement	Structural Tagging Requirement
Level B (Basic)	Visual Appearance Fidelity	No (Visual rendering only)	No structural tags required
Level U (Unicode)	Visual + Searchability	Yes (All glyphs mapped to Unicode)	No structural tags required
Level A (Accessible)	Full Accessibility & Structure	Yes (Mandatory Unicode mapping)	Yes (Full logical document tree & tags)

3. Prohibited Features: Fonts, Encryption & Color Profiles

To achieve genuine PDF/A compliance, documents must pass automated strict syntax validation against several technical constraints: 1. **Mandatory Font Embedding**: Every font used must be 100% embedded or subset-embedded with character width metrics. No external font substitution is tolerated. 2. **Strict Ban on Encryption**: Passwords and encryption dictionaries are illegal in PDF/A. Archival repositories must never be locked behind proprietary decryption keys. 3. **Prohibition of Dynamic Content**: Embedded JavaScript, Flash animations, audio tracks, and executable actions are forbidden because runtime environments change over time. 4. **Device-Independent Color**: All colors must either be defined in device-independent color spaces (such as CIELab or calibrated RGB) or include an embedded ICC Output Intent profile (e.g. sRGB or ISO Coated v2). 5. **Standardized XMP Metadata**: The document must include an Extensible Metadata Platform (XMP) packet containing title, author, creation date, and explicit PDF/A conformance declaration headers.

If you need to encrypt a sensitive document during transit, keep it as standard PDF. Once securely delivered to an archival repository, the encryption should be removed and converted to PDF/A.

4. E-Invoicing & Hybrid Archives: PDF/A-3 and ZUGFeRD / Factur-X

PDF/A-3 introduced a groundbreaking feature: the ability to embed non-PDF files inside the archival container. This gave birth to modern electronic invoicing standards across Europe and global trade: - **ZUGFeRD & Factur-X**: Widely mandated across Germany, France, and the European Union, these standards package human-readable invoice documents (PDF/A-3) with an embedded machine-readable XML schema (CrossIndustryInvoice). - **Hybrid Benefit**: An accountant or customer can open the PDF in any standard viewer and read the visual invoice, while automated enterprise resource planning (ERP) systems extract the embedded XML data directly for automated ledger accounting. - **Data Longevity**: Because the wrapper is PDF/A-3, the visual proof remains valid for statutory audit retention periods (typically 7 to 10 years).

5. Validating & Preparing Files for Long-Term Storage

When preparing records for legal archives, follow this technical checklist: 1. **Flatten Form Fields**: Interactive form inputs should be flattened into static vector text streams to prevent accidental editing or viewer rendering discrepancies. 2. **Combine Document Records**: Use [Merge PDF](/tools/merge-pdf/) to bundle supporting receipts, contracts, and addenda into a single coherent document rather than managing fragmented files. 3. **Verify Text Searchability**: Ensure scanned pages have been processed with OCR so characters map to valid Unicode values. 4. **Run an Open-Source Validator**: Utilize VeraPDF (the official open-source PDF/A validation library supported by the PDF Association) to verify syntax conformance before archiving.

Frequently Asked Questions

What is the difference between PDF/A and standard PDF?▼

Standard PDF allows external fonts, encryption, audio, and JavaScript. PDF/A strictly forbids these features to ensure the document can be opened and displayed identically decades in the future without external dependencies.

Which PDF/A version should I choose for general archiving?▼

PDF/A-2b is the most widely adopted standard today because it supports modern compression (JPEG 2000), transparency, and embedded vector graphics while ensuring universal compatibility.

Can a PDF/A document be password protected?▼

No. ISO 19005 explicitly prohibits encryption and passwords in PDF/A documents, as password protection compromises the long-term accessibility of archived records.

Can I convert regular scanned documents to PDF/A?▼

Yes. Scanned documents can be converted to PDF/A-1b or PDF/A-2b by embedding the scanned images alongside an ICC color profile and ensuring valid XMP metadata.