What Is PDF/A?

Overview

PDF/A is an ISO standard for PDFs that must remain readable and visually faithful for long periods—think records retention, legal filings, and institutional archives. Where ordinary PDF optimizes for flexible viewing and editing, PDF/A optimizes for self-containment and predictable rendering years later.

The core idea is that everything needed to display the document travels with the file: fonts are embedded, color is defined in an unambiguous way, and features that depend on external software behavior are restricted or banned. Encryption that would block future access, audio/video, and some forms of JavaScript or external linking are typically disallowed.

PDF/A comes in parts and conformance levels (for example PDF/A-1b for visual appearance, PDF/A-1a for tagged/structure accessibility, and later PDF/A-2/A-3 variants that allow JPEG2000, transparency, and file attachments under rules). Choose the level your records policy or receiving system specifies rather than the most feature-rich option by default.

Step-by-step

1. 1. Decide whether the job is archival or production

   Use PDF/A when the primary goal is long-term retention and reproducible appearance. Use PDF/X when the primary goal is exchange with a commercial printer. A single file is rarely the ideal choice for both missions without careful design.

   If a document must be both archived and printed, keep a clear source of truth and export purpose-specific derivatives rather than hoping one PDF satisfies every constraint.

2. 2. Embed fonts and avoid device-dependent color surprises

   Export with full font embedding. Substituted fonts years later are exactly what PDF/A is meant to prevent.

   Prefer ICC-based or clearly defined color. DeviceRGB/DeviceCMYK without profile context can look different on future viewers even if the pixels are intact.

3. 3. Strip or avoid features PDF/A forbids

   Remove encryption if your archive policy requires open access for future validators. Password protection conflicts with the idea that an archive can always open the file.

   Avoid reliance on external hyperlinks, embedded multimedia, and interactive forms unless your chosen PDF/A level explicitly allows a given construct. When in doubt, flatten the presentation into static page content.

4. 4. Validate with a PDF/A checker, then store the proven file

   Validation is part of the workflow, not an optional polish step. Many “Save as PDF/A” exports still fail validators because of fonts, transparency, or metadata.

   After a successful export, record checksums or retention metadata in your records system. Dockzio’s pdf-metadata tool can help you inspect titles, dates, and producer fields before you freeze a record copy.

5. 5. Plan for accessibility when level “a” is required

   Conformance level “a” expects logical structure (tags) and reading order, not only visual fidelity. Fixing tags after export is harder than authoring accessible structure in the source.

   If you only need visual preservation, level “b” is often the practical target—confirm with your compliance officer before choosing.

Common mistakes

• Equating PDF/A with “high quality PDF”. PDF/A is about archival predictability. It does not automatically improve image resolution, writing quality, or print geometry.
• Password-protecting an archival master. Encryption can make a file fail PDF/A validation and can block future access if keys are lost. Keep access control in the records system, not only in the PDF.
• Using PDF/A when the printer asked for PDF/X. Archival constraints and print-exchange constraints overlap but are not interchangeable. Send the standard the receiver named.