PDF/A Compliance Guide: 1.4 vs 2.0 vs 3.0 for Long-Term Archiving

PDF/A (Portable Document Format for Archiving) is the ISO-standardized version of PDF specifically designed for long-term digital preservation. Unlike regular PDFs, which can rely on external fonts, execute JavaScript, reference external files, or use features that may not work in future software, a PDF/A document is entirely self-contained. Everything needed to render the document — fonts, color profiles, images, metadata — is embedded within the file. A PDF/A file created today should render identically when opened in 2050, regardless of what software exists then.

The PDF/A standard has evolved through several versions. PDF/A-1 (ISO 19005-1:2005) was based on PDF 1.4 and is the most restrictive: it requires all fonts to be embedded, prohibits transparency and layers, forbids JavaScript and external references, and mandates that all colors be specified in a device-independent color space. PDF/A-1 is the safest choice for maximum compatibility with archival systems and is required by many government archives. The trade-off is that it cannot include JPEG2000 images or benefit from modern PDF compression features.

PDF/A-2 (ISO 19005-2:2011), based on PDF 1.7, adds support for JPEG2000 compression (producing smaller files for image-heavy documents), transparency (important for modern graphic design), and PDF layers (useful for multi-language documents where each language is on a separate layer). PDF/A-2 also allows embedding of other PDF/A files as attachments, which is useful for creating document collections. Most organizations that do not require PDF/A-1 specifically should default to PDF/A-2 — it offers better compression and more flexibility while still meeting strict archival requirements.

PDF/A-3 (ISO 19005-3:2012) is identical to PDF/A-2 in its PDF requirements but adds the ability to embed arbitrary file formats (not just PDF/A) as attachments. This means a PDF/A-3 file can contain the original source document — a Word file, an Excel spreadsheet, a CSV dataset — alongside the archival PDF rendering. This is particularly useful for scientific data, where the original data files are as important as the visualization in the PDF. PDF/A-3 is also used in electronic invoicing (ZUGFeRD and Factur-X standards), where the PDF contains machine-readable XML invoice data as an attachment.

PDF/A-4 (ISO 19005-4:2020), based on PDF 2.0, is the most modern and future-proof version. It removes the requirement for device-independent color spaces (acknowledging that modern color management is reliable enough), supports modern encryption for document security, and is designed to be simpler to validate than earlier versions. PDF/A-4 is recommended for new archival projects that do not need backward compatibility with older PDF/A validators. However, many government systems and archival platforms still require PDF/A-1 or PDF/A-2, so check the requirements of your specific use case before choosing.

Validating PDF/A compliance requires specialized tools. A document that 'looks correct' is not necessarily PDF/A compliant — compliance failures are often invisible: a font that is not fully embedded, a color in a non-standard color space, or metadata that is missing a required field. Tools like veraPDF (open-source, industry standard), Adobe Acrobat Pro's Preflight, and online validators can check a PDF against the PDF/A specification and report compliance issues. Always validate before submitting to an archival system or government agency.

Creating PDF/A documents from existing PDFs is straightforward with the right tools. The conversion process embeds missing fonts, removes prohibited features (JavaScript, external references, encryption), converts colors to device-independent color spaces as needed, and adds required metadata. The resulting file is often slightly larger than the original due to embedded fonts and color data, but it is guaranteed to render correctly decades from now. Use https://www.iamuu.com/pdf/ to batch convert regular PDFs to PDF/A format, selecting the appropriate conformance level (A-1b for basic compliance, A-2u for Unicode text accessibility, etc.).

For most organizations, the practical recommendation is: use PDF/A-2 (level U for Unicode text accessibility) for new archival projects — it offers the best balance of modern features, file size efficiency, and broad compatibility with archival systems. Use PDF/A-1 only when specifically required by the receiving institution. Use PDF/A-3 when you need to attach source documents or data files. And use PDF/A-4 for cutting-edge projects where you control the entire toolchain. Regardless of which version you choose, validate every document before archiving, maintain the original non-PDF/A source files as a backup, and store archival copies in multiple locations following the 3-2-1 backup rule.