PDF/A Explained: Why Archival PDF Is a Different Format Than You Think

PDF/A is a constrained subset of PDF built for long-term preservation: everything needed to paint the page travels inside the file. An ordinary PDF that opens today can still fail an archive check tomorrow if it depends on system fonts, external resources, or interactive features a future viewer will not have.

What "archival" actually constrains

PDF/A requires fonts to be embedded and disallows external dependencies and certain dynamic content (scripts, some multimedia, live form behaviors that need outside data). The point is reproducibility: open the file in ten or thirty years and get the same glyphs and layout, without hoping the original machine's font folder still exists.

That is a different job from "looks fine in Preview." Everyday PDFs optimize for editing convenience and small downloads. PDF/A optimizes for self-containment.

Conformance levels are not marketing tiers

ISO PDF/A comes in generations (1, 2, 3) and conformance classes. The "b" variants (for example PDF/A-2b and PDF/A-3b) focus on visual fidelity; stricter classes add requirements around structure and tagged content. Courts, government portals, and records systems usually name an exact level. Guessing wrong means rejection even when the file "looks archival."

On PDF123, PDF to PDF/A exposes an outputFormat selector covering pdfa, pdfa-1, pdfa-2, pdfa-2b, pdfa-3, pdfa-3b, and pdfx. Pick what the receiving system documents. The convert path runs Ghostscript toward PDF/A (PDFA level 1 when the format name contains 1, otherwise level 2)—treat menu labels as inputs to that path, not as a guarantee of every ISO class or a press RIP profile.

PDF/A vs PDF/X

PDF/A targets long-term reading and records retention. PDF/X targets print production: color spaces, bleed, and prepress constraints so a press RIP gets a predictable job. They are related ISO PDF subsets with different failure modes. This product's convert tool is the archival (PDF/A) path; when a printer asks for PDF/X, use a prepress workflow that actually emits PDF/X, not an archival convert alone.

What conversion does not fix

Converting to PDF/A does not invent missing fonts you never embedded, repair a broken xref, or turn a scan into a tagged accessible document. It rewrites the file toward a conformance profile. If the source already violates hard rules (unembeddable fonts, forbidden content), conversion may fail or strip features you still need for day-to-day editing.

Use PDF to PDF/A when a checklist names a level. For automation against the same endpoint (POST /api/v1/convert/pdf/pdfa), see Developers.