What is PDF/A?
PDF/A (Portable Document Format / Archive) is an ISO-standardised subset of the PDF specification created specifically for the long-term archiving of electronic documents. The "A" stands for Archive. The standard was first published in 2005 as ISO 19005-1 and has since been revised and extended into multiple parts covering different use cases.
Unlike a regular PDF, which can contain content that depends on external resources, proprietary software, or time-limited elements such as digital rights management, a PDF/A file must be entirely self-contained. Every font, colour profile, and piece of content the viewer needs to render the document correctly must be embedded inside the file itself. This ensures that the document can be opened and displayed identically by any compliant viewer, whether today or a hundred years from now.
PDF/A is not a separate application — it is a specific configuration and validation standard for the PDF format. A valid PDF/A file is also a valid PDF file. The difference lies in what is permitted inside it.
Why Does PDF/A Exist?
When electronic document archiving became mainstream in the 1990s, organisations quickly realised that digital preservation is harder than it sounds. A document saved today might reference a font that is no longer licensed, link to a server that no longer exists, or use a feature deprecated in a newer PDF reader. Open the same file in twenty years and it could look completely different, or fail to open at all.
The PDF/A standard addresses this problem by being prescriptive. It defines exactly what a PDF file must and must not contain in order to qualify as a valid archive format. The standard was developed jointly by AIIM (Association for Information and Image Management), NPES (the Association for Suppliers of Printing), and Adobe Systems — the original creators of PDF. It was adopted by ISO in 2005.
PDF/A Versions Compared
The standard has grown considerably since 2005. There are now four main parts, each addressing slightly different archiving needs:
PDF/A-1 (ISO 19005-1, 2005)
The original archiving standard, based on PDF 1.4. It comes in two conformance levels: PDF/A-1a (accessible — requires tagged content and Unicode character maps) and PDF/A-1b (basic visual reproducibility). Most compliance requirements in older regulations reference PDF/A-1b. It is still widely used but lacks support for JPEG 2000 compression and embedded files.
PDF/A-2 (ISO 19005-2, 2011)
Based on PDF 1.7, PDF/A-2 added support for JPEG 2000 image compression, optional content groups (layers), digital signatures using PAdES, and the ability to embed other PDF/A files as attachments. It also has three conformance levels: a (accessible), b (basic), and u (Unicode). For new archiving projects, PDF/A-2b is often the recommended starting point.
PDF/A-3 (ISO 19005-3, 2012)
PDF/A-3 is identical to PDF/A-2 except that it allows embedding of arbitrary file types — not just PDF/A files — as attachments. This means you can embed a native XML, Excel, or CAD file alongside the rendered PDF representation. This is especially useful for machine-readable invoicing formats like ZUGFeRD and Factur-X, which embed structured XML data in a PDF/A-3 container.
PDF/A-4 (ISO 19005-4, 2020)
The most recent revision, based on PDF 2.0. PDF/A-4 removes the a/b/u conformance level structure in favour of just PDF/A-4, PDF/A-4e (for engineering documents), and PDF/A-4f (which allows embedded files, like PDF/A-3). It is still being adopted by the industry.
Technical Requirements of PDF/A
Understanding what PDF/A prohibits is as important as knowing what it allows. The standard bans a range of PDF features that could cause rendering inconsistencies over time:
- JavaScript: All JavaScript is prohibited. A PDF/A file cannot execute code.
- Encryption: PDF/A files cannot be password-protected or encrypted, since encrypted content may become inaccessible if the encryption scheme is deprecated or the password is lost.
- External content: No references to external URLs, fonts not embedded in the file, or other resources outside the document.
- Audio and video: Multimedia embeds are not permitted in PDF/A-1 or PDF/A-2.
- Transparent objects (PDF/A-1 only): Transparency is not supported in PDF/A-1 because it was not part of PDF 1.4.
- LZW compression: Prohibited in PDF/A-1 for historical patent reasons.
Conversely, PDF/A requires the following:
- All fonts used must be fully embedded in the file.
- Colour spaces must be fully specified using device-independent profiles (ICC profiles).
- The file must contain XMP metadata including the PDF/A conformance level identifier.
- Document structure must include the correct XMP schema for archiving metadata.
Who Needs PDF/A?
PDF/A is mandated or strongly recommended in several sectors:
Legal and courts: Many court systems worldwide require that submitted documents be in PDF/A format to ensure long-term readability of legal records. The European Court of Justice and many US federal courts accept or require PDF/A.
Government and public administration: Numerous EU member states and US federal agencies require PDF/A for official electronic records under long-term retention policies. Germany's eGovernment Act, for instance, specifies PDF/A for official electronic communications.
Healthcare: Medical records must often be retained for 10–30 years. PDF/A ensures that patient records remain intact and accessible over those timeframes.
Finance and accounting: Tax records, audit trails, and financial statements frequently require long-term storage in a format that cannot be altered and will remain readable.
Libraries and archives: National archives and digital libraries use PDF/A to preserve digitised historical documents, ensuring future researchers can access them.
How to Create or Convert to PDF/A
There are several ways to produce a PDF/A-compliant document:
Saving directly from applications
Microsoft Office 365 allows you to export directly to PDF/A-1a from the Save As dialog. LibreOffice offers PDF/A export options under File > Export as PDF. When saving directly from the source application, the result is usually better than post-conversion because all font embedding and colour profile information is applied cleanly at the point of creation.
Converting an existing PDF
If you already have a PDF that needs to be converted to PDF/A, tools such as Adobe Acrobat Pro can apply a "Preflight" process that embeds fonts, converts colour spaces, removes disallowed content, and writes the required XMP metadata. Open-source alternatives include Ghostscript (command-line) and tools built on the Apache PDFBox library.
Be aware that automatic conversion is not always lossless. If the original PDF contains JavaScript, transparency effects, or unembeddable fonts, the converter must make choices about how to handle them, and the visual output may differ slightly from the original.
PDF tools for basic PDF work
For everyday PDF tasks like merging, splitting, and compressing files before archiving, ToolMasta offers free browser-based tools. Use Merge PDF to combine multiple documents, Split PDF to extract specific pages, or Compress PDF to reduce file size before long-term storage.
How to Validate a PDF/A File
Simply renaming a file or having software claim it is PDF/A is not enough. You need to validate the file against the relevant ISO standard to confirm compliance. Several free and commercial validators exist:
- veraPDF: The industry-standard open-source PDF/A validator, available at verapdf.org. It checks conformance against PDF/A-1, 2, 3, and 4, and produces detailed reports of any non-conformances.
- Adobe Acrobat Pro: Includes a built-in preflight profile that checks PDF/A conformance and can fix many issues automatically.
- PDF Tools AG: Commercial tools widely used in enterprise archiving pipelines.
Validation is particularly important when receiving PDF/A files from third parties, since a file can claim to be PDF/A in its metadata while still containing prohibited content.
Reading the validation report
A typical validation report lists failures such as "Font not embedded", "Transparency detected", or "Colour space not device-independent". Each failure references the specific clause of the ISO standard it violates, making it straightforward to diagnose and fix issues before filing or submitting a document.
PDF/A may seem like a technical detail, but for organisations that depend on the long-term integrity of their records, it is foundational. Choosing the right conformance level at the point of creation is far cheaper and more reliable than trying to convert a large archive of non-compliant PDFs years later. When in doubt, PDF/A-2b remains the most practical and widely supported starting point for new archiving projects.