PDF Formats Explained: PDF/A vs PDF/X vs PDF/UA

When you "Save as PDF" from Word, Chrome, or your phone, you get a plain ISO 32000 PDF. It can do almost anything: embed video, link to external URLs, run scripts, pull in fonts by reference instead of bundling them, and combine RGB, CMYK, and spot colors in one file. For sending a quote, a contract draft, or a report that someone will read once and discard, this is exactly right.

The trouble starts when a file has to survive a constraint the base format never promised to honor. A standard PDF that references the Helvetica installed on your laptop may render with a substitute font on a machine that lacks it. One that links to a web page is useless once that page dies. One built in RGB can shift color badly on a CMYK press. None of that is a bug; the standard simply does not care about those scenarios. The sub-standards exist precisely to close those gaps, each for a different use case.

PDF/A (ISO 19005) is the archiving standard. Its single design goal is that the file renders identically far into the future, with zero dependence on anything outside the file itself. Records managers, courts, and national archives lean on it because a document you must keep for a decade cannot rely on fonts, plugins, or websites that may not exist later.

To deliver that guarantee, PDF/A forbids the things that break long-term reproduction. All fonts must be embedded, so there is no substitution. JavaScript and executable launch actions are not allowed. Audio, video, and external file references are out. Encryption is prohibited. Transparency is restricted in the stricter levels, and color must be described in a device-independent way using embedded ICC profiles or an OutputIntent, so a red stays the same red on any viewer.

There are flavors. PDF/A-1 is the strictest and oldest. PDF/A-2 adds JPEG2000 compression, transparency, and layers. PDF/A-3 additionally lets you embed any attachment, such as the original spreadsheet behind an invoice. Within each, the b conformance level guarantees visual reproduction, while the a level additionally requires a tagged structure for accessibility. For most business archiving, PDF/A-2b is the sensible default.

PDF/X (ISO 15930) is the prepress standard. It exists because a file that looks fine on your screen can be unprintable on a commercial press: missing fonts, low-resolution images, an RGB color space the press cannot reproduce, or no bleed where the design runs to the paper edge. PDF/X removes the ambiguity so the printer gets a file they can run without guesswork.

It enforces print-readiness from the other direction than PDF/A. Every font must be embedded. Color must be unambiguous, typically CMYK plus named spot colors, with a defined output intent that names the target printing condition such as a specific paper and ink standard. Hyperlinks, JavaScript, and other interactive elements are stripped because they mean nothing on paper. Crucially, PDF/X expects proper handling of bleed and trim boxes so the artwork extends past the cut line.

The common variants tell the printer how color is handled. PDF/X-1a allows only CMYK and spot colors, fully flattened, which is the safest choice when you are unsure. PDF/X-3 permits color-managed RGB with ICC profiles. PDF/X-4 adds live transparency and layers so the press RIP flattens them rather than you doing it manually. If a print shop hands you a spec sheet, it will almost always name one of these.

PDF/UA (ISO 14289, where UA stands for Universal Accessibility) makes a PDF usable by people relying on assistive technology such as screen readers. This is increasingly not optional. Public-sector bodies in the US (Section 508), the EU (the Web Accessibility Directive and the European Accessibility Act), and many large enterprises require accessible documents, and an audit will fail a PDF that ignores these rules.

PDF/UA is about structure, not appearance. The document must be fully tagged so its logical reading order is explicit: headings marked as headings, lists as lists, tables with real header cells, and content in the order a person would actually read it rather than the order it happens to sit on the page. Every meaningful image needs alternative text. Purely decorative graphics must be marked as artifacts so a screen reader skips them. The document language must be declared, and the title set, so assistive tech announces it correctly.

An important nuance: tagging alone does not equal compliance. A file can be tagged yet still fail because the reading order is scrambled or alt text is missing. PDF/UA is the rulebook that defines what "done properly" means, and dedicated accessibility checkers test against it.

The differences come down to what each standard guarantees and what it sacrifices to get there. PDF/A trades away interactivity for permanence. PDF/X trades away anything irrelevant to paper for press reliability. PDF/UA layers a strict structural requirement on top regardless of the others. They are not mutually exclusive in spirit, but a single file rarely needs to satisfy more than one at once.

Most viewers surface the conformance level if you go looking. In Adobe Acrobat, the Standards or Document Properties panel will state PDF/A, PDF/X, or PDF/UA conformance and the exact version. Many readers also show a blue notification bar reading something like "This file claims compliance with the PDF/A standard" when you open an archived file, because PDF/A viewers are expected to switch to a faithful, non-editing mode.

Under the hood, the claim lives in the file's XMP metadata. A PDF/A file carries a pdfaid part and conformance entry; PDF/X and PDF/UA declare themselves similarly. That metadata is only a claim, though. A file can assert PDF/A conformance and still violate the rules if it was produced carelessly, which is why true compliance is established by a validator (PDF/A and PDF/UA are commonly checked with the open-source veraPDF) rather than by trusting the label.

If you are not sure what you have and no banner appears, assume it is a standard PDF. The sub-standards require a deliberate export step; nothing turns a plain PDF into a conformant one by accident.

You produce a conformant PDF at export time, not by renaming a file. In most authoring tools the choice appears in the Save As or Export dialog. Microsoft Word offers a "PDF/A compliant" checkbox under PDF options. Adobe InDesign and Illustrator expose PDF/X presets built for press. LibreOffice has a direct PDF/A export. For accessibility, you typically build a properly tagged document first, then validate and remediate against PDF/UA, since tagging quality is the hard part.

Conversion has real consequences, so expect trade-offs. Converting to PDF/A will strip out any JavaScript, external links, and embedded media, and may rasterize transparency in the strictest levels. Converting to PDF/X flattens interactivity and pins down color. Going the other way, you can always open a conformant PDF in a general editor, but heavy editing often breaks the conformance and you will need to re-export. Keep your source document, not just the exported PDF, whenever you can.

For routine prep work before any standards export, lightweight web utilities are handy. An all-in-one suite like our PDF tools lets you reorder, split, and clean up pages first so the document you eventually export to PDF/A or PDF/X is already correct. If a file is bloated with oversized images, shrinking it before archiving keeps storage sane without touching the standard itself.

You almost never need to think about this for day-to-day documents. A plain PDF is fine for the overwhelming majority of files you send and receive. Reach for a sub-standard only when an external requirement forces your hand, and let that requirement pick the format for you.

The shortcuts are simple. If someone says the file must be retained for years or accepted by an archive, court, or compliance system, that is PDF/A. If you are handing artwork to a commercial printer, ask them for their exact spec and they will name a PDF/X variant. If you are publishing for a government body, a large enterprise, or anyone who mentions Section 508, WCAG, or the European Accessibility Act, that is PDF/UA. When more than one applies, such as an accessible archived record, you target the overlap, for instance PDF/A-2a, which bundles the tagged structure into the archival format.