What is PDF/A? Standard Explained for Ordinary Document Workflows

Have you ever tried to open a 15-year-old digital file, only to be greeted by missing font warnings, broken layouts, or an error stating that the software format is no longer supported?

Standard PDF files are versatile, but they are not immortal. Standard PDFs can reference external system fonts, include executable JavaScript code, link to third-party web assets, and use proprietary color spaces. If you open a standard PDF 20 years from now on a computer that lacks your fonts or operating system, the document can render as unreadable gibberish.

To solve this digital obsolescence problem, the International Organization for Standardization created PDF/A (ISO 19005).

In this guide, we demystify what is PDF/A in plain language, explain what it guarantees (and what it does not), breakdown the differences between PDF/A-1, 2, and 3, and help you determine when a normal PDF is completely sufficient.

Important Preservation Warning: A conversion badge or file extension alone does not prove long-term archival quality. If a source document has unreadable scanned text or corrupted vector streams, wrapping it in a PDF/A container will not fix underlying legibility problems.

What Makes PDF/A Different from Standard PDF?

The core idea of PDF/A is to make the document more self-contained for long-term preservation.

The format restricts external dependencies and requires key resources, such as fonts and color profiles, to be embedded. It improves portability, but does not guarantee that a document will display identically on every future device.

graph TD
    A["PDF/A Standard (ISO 19005)"] --> B["Mandatory Requirements:"]
    B --> B1["100% Embedded Font Glyphs"]
    B --> B2["Standardized Device-Independent Color (ICC Profiles)"]
    B --> B3["Standard Dublin Core XMP Metadata"]
    A --> C["Strict Prohibitions:"]
    C --> C1["No Password Locks or Encryption"]
    C --> C2["No Executable JavaScript or Dynamic Scripts"]
    C --> C3["No External Font or Image Hyperlinks"]
    C --> C4["No Audio or Video Codec Streams"]

What PDF/A Mandates:

• 100% Embedded Fonts: Every font character used must be physically embedded inside the file. Even standard fonts like Arial or Times New Roman cannot rely on the operating system.
• Device-Independent Color: Must embed standardized ICC color profiles to ensure colors look identical across future displays and printers.
• Standardized XMP Metadata: Machine-readable Dublin Core metadata describing author, title, and creation history.
• Logical Reading Order: For compliance level A, structural tags define paragraph flows for screen readers and accessibility tools.

What PDF/A Strictly Prohibits:

• No Encryption or Passwords: An encrypted file cannot be safely archived because passwords get lost and cipher algorithms become deprecated.
• No Executable JavaScript: Prevents security vulnerabilities and software dependency failures.
• No External Resource Links: Cannot stream images or fonts from external web servers.
• No Audio or Video: Avoids dependency on obsolete proprietary multimedia codecs.

Detailed Comparison: Standard PDF vs. PDF/A

Understanding the PDF/A Family: 1, 2, and 3 Explained Simply

The PDF/A standard has evolved through three distinct ISO iterations, each adding modernized capabilities:

PDF/A-1 (ISO 19005-1, Released in 2005)

• Based on PDF 1.4 (Acrobat 5).
• Does not support transparency (drop shadows or opacity).
• Widely mandated by early government electronic filing portals.

PDF/A-2 (ISO 19005-2, Released in 2011)

• Based on PDF 1.7 (ISO 32000-1).
• Adds support for transparent graphics, layers, and JPEG 2000 image compression.
• Allows embedding of other PDF/A documents as attachments.

PDF/A-3 (ISO 19005-3, Released in 2012)

• Identical to PDF/A-2, with one revolutionary addition: allows embedding of non-PDF files (such as raw XML, CSV spreadsheets, CAD drawings, or source code) directly inside the container.
• Real-World Impact: PDF/A-3 is the technological foundation for mandatory European electronic invoicing standards, such as Factur-X (France) and ZUGFeRD (Germany), where a human-readable PDF invoice contains machine-readable XML embedded directly inside.

Compliance Levels: What Do 'a', 'b', and 'u' Mean?

When saving a file as PDF/A, you will see suffixes like PDF/A-2b or PDF/A-1a:

• Level B (Basic Visual Compliance): Focuses on reliable visual reproduction. It does not guarantee identical rendering on all future screens or printers.
• Level U (Unicode Compliance): Adds Unicode mapping for text in addition to the visual requirements of Level B.
• Level A (Accessible / Structural Compliance): Adds structural information, such as document tags, to support logical reading order and accessibility workflows.

When Do You Actually Need PDF/A?

For ordinary office work, standard PDF is often sufficient. Some organizations and submission workflows specify PDF/A, but requirements vary and must be checked with the receiving institution:

1. Court electronic filing: Check the specific court and portal instructions for accepted file formats; requirements can differ.
2. Patent and government submissions: Check the receiving office's current rules for the document and submission method.
3. Institutional repositories: Ask the archive or university which PDF/A profile, if any, it accepts.

Converting to PDF/A: Key Considerations

If you need to generate a PDF/A compliant file:

1. Generate from the Source Application: Whenever possible, export directly to PDF/A from Microsoft Word, LibreOffice, or Google Docs using the built-in "Export as PDF/A" option. This ensures fonts are embedded at generation time.
2. Do Not Rely on Conversion Alone: Converting an existing standard PDF to PDF/A using automated software can sometimes fail if the source file was missing fonts. Always validate the converted file using an ISO compliance validator.

Archival Document Preparation Checklist

Before submitting an official archive file:

• [ ] Compliance level verified: Did you select the required version (e.g., PDF/A-2b for standard legal filing)?
• [ ] No passwords applied: Ensure the document is unlocked and unencrypted.
• [ ] Searchable text confirmed: If the document contains scanned pages, was OCR performed so text is selectable?
• [ ] Visual fidelity spot-checked: Do all diagrams, signatures, and stamps appear intact?
• [ ] Metadata standardized: Does the Dublin Core title and author represent the official document record?

Last reviewed: September 2026 by UtilityKit Technical Document Standards Team.