PDF/A, PDF/X, PDF/UA — what the letters after the slash mean
7 min read
Plain PDF guarantees one thing: it looks the same on every screen. The letters after the slash exist to guarantee more than that.
Why there are multiple standards
The base PDF specification is permissive. Fonts may or may not be embedded; content may reference external resources; files may contain JavaScript. That flexibility becomes a liability for specific purposes like archiving, printing, and accessibility.
So ISO defined restricted profiles, each narrowing what's allowed for one purpose: PDF/A (Archive), PDF/X (eXchange, for print), and PDF/UA (Universal Accessibility).
PDF/A — a document that still opens decades from now
PDF/A is the long-term preservation profile. Its core principle is self-containment: everything needed to display the document must be inside the file. Fonts must be embedded; encryption, JavaScript, audio/video, and content that depends on external links are forbidden.
That's why institutions with retention obligations require it: there's no guarantee today's installed fonts or software will exist in twenty years, so the file must stand alone. Word and most major programs offer a “PDF/A compliant” option in their PDF export settings.
PDF/X — a document that won't blow up at the print shop
PDF/X is the commercial printing profile. Screens make color with light (RGB); presses make it with ink (CMYK) — and plain PDF happily mixes the two. The result is the classic incident: “the printed colors don't match my monitor”.
PDF/X forces color to be defined against print standards and requires things like bleed areas beyond the trim line and embedded fonts. If a print shop asks for PDF/X for your flyer or booklet, your layout software's export presets (InDesign and the like) have it built in.
PDF/UA — a document a screen reader can actually read
PDF/UA is the accessibility profile. Screen readers don't read pixel positions — they follow the document's structural information. The problem, as the anatomy of PDF shows, is that base PDF has none.
PDF/UA requires tagging every piece of content with structure (this is a heading, this is a paragraph, this is a table header cell), alternative text for images, and a defined reading order. Documents published by public institutions increasingly must meet this level under accessibility law.
Where you'll meet each one
The typical situations where each standard is required:
- PDF/A: court e-filing, public records, thesis and journal submission, contracts kept long-term
- PDF/X: files delivered to print shops (business cards, flyers, booklets, packaging), ad placements
- PDF/UA: documents published by public bodies, organizations with accessibility obligations
- No requirement stated: plain PDF is fine — converting buys you nothing
Why “save as PDF/A” sometimes fails
Converting an existing PDF to PDF/A most often trips over fonts: ones that were never embedded, or ones whose license forbids embedding. The converter either fails or substitutes a different font, changing the document's appearance.
The reliable route is exporting to PDF/A from the source document (Word, etc.) in the first place. Converting a finished PDF after the fact is strictly the fallback.