PDF/A Compliance Guide: Archiving Standards

What is PDF/A and Why is it Necessary for Digital Preservation?

Digital obsolescence poses a serious risk to corporate, legal, and government records. If a PDF created in 2026 references a proprietary font installed only on Windows 11, opening that document in 2050 on a different operating system may result in missing text, incorrect character encoding, or complete rendering failure.

PDF/A (Portable Document Format for Archiving) solves this by enforcing a strict rule of 100% self-containment. A conforming PDF/A file contains every single visual component—including font glyphs, vector geometries, raster images, and color space profiles—directly within the binary envelope. PDF/A supports long-term reproducibility, but continued preservation also depends on valid files, maintained storage, and suitable reading software.

PDF/A Conformance Levels Explained: 1b, 2b, 3b, and PDF/A-4

The PDF/A standard has evolved through multiple parts and conformance profiles. Understanding which profile your organization or regulatory agency requires is essential:

1. PDF/A-1 (ISO 19005-1, based on PDF 1.4): The foundational archiving standard. Level 1b (Basic) guarantees visual preservation. Level 1a (Accessible) requires tagged PDF structure and logical reading order for screen readers.

2. PDF/A-2 (ISO 19005-2, based on PDF 1.7): Adds support for JPEG 2000 compression, transparency layers, embedded PDF/A attachments, and object streams.

3. PDF/A-3 (ISO 19005-3): Extends PDF/A-2 by permitting the embedding of non-PDF raw files (such as XML financial data, CSV spreadsheets, or CAD models) within the PDF wrapper—widely used for electronic invoicing (e.g., ZUGFeRD / Factur-X).

4. PDF/A-4 (ISO 19005-4, based on PDF 2.0): Modernized standard that simplifies conformance into PDF/A-4, PDF/A-4e (engineering/3D), and PDF/A-4f (embedded files).

Mandatory PDF/A Requirements and Prohibited Features

To achieve strict ISO compliance, a PDF document must satisfy rigid technical constraints:

1. 100% Font Embedding: Fonts needed to render the document must be embedded as required by the chosen profile; valid embedded subsets can contain only the glyphs used. External font linking or font substitution is strictly forbidden.

2. Device-Independent Color Spaces: Colors must be defined using standard ICC color profiles or calibrated RGB/CMYK spaces to prevent device-dependent hue shifts.

3. Zero Encryption & Passwords: Encrypted documents cannot be indexed or preserved by archival crawlers; PDF/A forbids all password protection and permissions restrictions.

4. Prohibition of Executable Code & Scripts: Embedded JavaScript, interactive launch actions, external URL file references, and audio/video media are prohibited because they cannot be guaranteed to execute safely in future software.

5. Standardized XMP Metadata: Documents must embed standardized Extensible Metadata Platform (XMP) metadata declaring the exact PDF/A conformance version.

Converting Standard PDFs to PDF/A In-Browser with FileTools

Commercial desktop tools like Adobe Acrobat Preflight often charge expensive ongoing licenses for PDF/A conversion. Online cloud converters require uploading confidential legal dossiers or financial statements across the internet.

FileTools uses pdf-lib JavaScript to write document properties and XMP profile identifiers, and removes the catalog Names, OpenAction, and AA entries when present. The current implementation does not embed missing fonts or ICC profiles, inspect every prohibited object, or validate PDF/A conformance. Removing Names may also remove access to named destinations or attachments; retain the original and inspect the output.

Step-by-Step Conversion Workflow for Archival Compliance

1. Confirm the exact PDF/A part and conformance level required by the receiving archive. Prepare fonts and other required resources in the original authoring software.

2. Keep the original PDF. FileTools offers PDF/A-1b and PDF/A-2b identifiers plus title, author, and subject fields; these settings identify the intended profile rather than proving compliance.

3. Process a copy locally. The current tool writes metadata and removes selected catalog entries; it does not repair all PDF/A violations.

4. Run the output through veraPDF or another appropriate independent preflight validator. Read the complete report for the selected profile and resolve failures in a capable authoring or conversion tool.

5. Submit only a file whose required checks pass, and separately follow the receiving archive’s document and accessibility rules.

Preflight Validation and Verifying Conformance with veraPDF

veraPDF validates PDF/A requirements against profile-specific rules. A viewer banner or pdfaid metadata entry identifies a claimed profile, not the result of a full conformance check.

Run validation for the exact profile required by the recipient and retain the report. Font properties and the absence of encryption are useful spot checks but are not a substitute for all applicable rules.

FileTools does not produce a certification or a veraPDF pass report. Image-only input can still violate color, metadata, transparency, or other requirements even when it has no text fonts.