What Is PDF/A? Archiving Guide (2026)

If you have ever wondered what is PDF/A format, here is the one-sentence answer: PDF/A is a restricted flavor of PDF designed so a document looks exactly the same in fifty years as it does today. It achieves this by forbidding everything that could break over time — external font references, encryption, JavaScript, embedded video — and requiring everything the document needs to be packed inside the file itself.

This guide explains in plain English what PDF/A forbids and why, decodes the version alphabet soup (A-1 through A-4), tells you when archiving is worth it — and when it is not — and gives the honest conversion warning most vendor guides bury. Our free PDF to PDF/A converter runs in your browser.

Table of Contents

What Is PDF/A Format, in Plain English

A normal PDF is a presentation format: it says “draw this text in that font at this position.” But it is allowed to be lazy about it — it can say “draw this in Helvetica” without including Helvetica, trusting that whatever computer opens the file will have Helvetica installed. In 2026 that works. In 2076, on some archive workstation, it may not — and your document silently reflows into a substitute font.

PDF/A (the “A” stands for Archive) eliminates that trust. It is defined by the ISO 19005 family of standards and maintained with input from the PDF Association. The core principle: a PDF/A file must be completely self-contained and self-describing. Every font embedded. No encryption (an archive no one can open is not an archive). No audio, video, or JavaScript (executable content rots fastest). No references to external files. Color defined in a device-independent way so the reds still look red on future displays.

The result is a file that any compliant reader renders identically, forever — or at least as close to forever as digital preservation gets. Governments, courts, libraries, and universities mandate it for exactly this reason: a thesis archived as PDF/A-1b in 2010 opens perfectly today, while plenty of 2010-era Word files do not.

PDF/A vs PDF: What Gets Forbidden

The difference between PDF/A vs PDF is not what PDF/A adds — it is what it takes away. Here is the forbidden list, with the reasoning:

  • Non-embedded fonts — forbidden. Every glyph used must be embedded in the file. This is the big one: it guarantees the text renders identically without relying on the reader’s system fonts.
  • Encryption — forbidden. A password-protected file is a file that becomes unreadable the moment the password is lost. Archives forbid it categorically.
  • JavaScript and executable actions — forbidden. Scripts break, get blocked by security policies, and depend on reader features that change. A document that needs code to display correctly is not archivable.
  • Audio and video — forbidden (except in PDF/A-4, which permits them under strict embedding rules). Embedded media depends on codecs that go obsolete.
  • External references — forbidden. No “fetch this image from a URL,” no external font files. Everything must be inside the single file.
  • Transparency effects — restricted in A-1 (flattened), allowed in A-2 and later. Early PDF/A played it safe with features that rendered inconsistently.
  • Device-dependent color — restricted. Colors must be defined in device-independent color spaces (or carry output-intent profiles) so rendering does not drift across devices.
  • Missing metadata — forbidden. PDF/A requires XMP metadata identifying the conformance level, so future software knows what rules the file follows.

Notice what is not forbidden: images, vector graphics, hyperlinks, bookmarks, form fields (in some levels), and digital signatures (in A-2+). PDF/A is not a dumbed-down PDF — it is a disciplined one.

PDF/A Versions Decoded: A-1 to A-4

The version history confuses everyone, so here is the decoder:

  • PDF/A-1 (2005, ISO 19005-1). Based on PDF 1.4. The strictest and simplest: no transparency, no layers, no JPEG 2000, no embedded files. The PDF/A-1b conformance level (the “b” means basic) guarantees visual preservation — the document looks right. PDF/A-1a (“accessible”) additionally requires tagged structure for screen readers. If a university thesis office says “submit PDF/A,” they almost always mean 1b.
  • PDF/A-2 (2011, ISO 19005-2). Based on PDF 1.7. Adds JPEG 2000 compression, transparency, layers, and embedded PDF/A files. The practical upgrade for documents with modern graphics.
  • PDF/A-3 (2012, ISO 19005-3). Identical to A-2 except it allows embedding any file format (spreadsheets, CAD files, XML data). Built for invoices-with-data workflows like ZUGFeRD/Factur-X, where the PDF carries machine-readable XML inside.
  • PDF/A-4 (2020, ISO 19005-4). Based on PDF 2.0. Consolidates everything, drops the a/b/u conformance levels in favor of simpler ones, and permits rich media under strict rules. The future-facing choice — but check that your recipient’s systems accept it before committing.

Which should you use? For maximum compatibility — theses, court filings, government submissions — PDF/A-1b or A-2b remain the safest bets, because every validator and archive system on earth understands them. Choose A-3 only if you need to embed source data files; choose A-4 only if your archive explicitly supports PDF 2.0 features. Newer is not automatically better in archiving — widely supported is better.

How to Convert PDF to PDF/A

To convert PDF to PDF/A with our free tool:

  1. Prepare the source. Remove password protection first — encrypted files cannot convert. If the document is a scan, run OCR before converting so the text layer is preserved properly.
  2. Open our PDF to PDF/A converter. Everything runs locally in your browser.
  3. Choose the conformance level. PDF/A-2b is the sensible default for most documents; use 1b if your institution specifically requires it.
  4. Convert and validate. Download the result and check that fonts render correctly and no content shifted — especially documents with unusual fonts or transparency effects.

Before converting a multi-part document, merge the parts into one file first — archiving ten fragments is worse than archiving one complete document. And check the document’s metadata afterward: PDF/A requires proper XMP metadata, and a converter worth using writes it correctly.

When NOT to Archive as PDF/A

PDF/A is the wrong choice more often than vendors admit:

  • Working documents. Drafts you will keep editing should stay in their editable format (Word, InDesign). PDF/A is a final format — archive the finished version, not the work in progress.
  • Documents needing encryption. If the file must be password-protected, it cannot be PDF/A. Choose security or archivability — you cannot have both in one file.
  • Interactive forms in active use. A form people still fill out should stay a normal PDF. Convert to PDF/A only when the filled form becomes a record.
  • When the recipient can’t open it. Some older systems choke on PDF/A-4 or misrender embedded-font subsets. Match the version to the least capable system in the chain.
  • As a “backup policy.” Converting to PDF/A is not backing up. A single PDF/A on a single hard drive is one spilled coffee away from oblivion. Archiving is about format longevity; backup is about redundancy. You need both.

The Honest Conversion Warning

Now the warning most converter vendors bury at the bottom of their pages, if they mention it at all:

Converting a normal PDF to PDF/A adds limited value and can lose data. Conversion cannot retroactively embed a font the original never included — if the source PDF references Helvetica without embedding it, the converter must substitute something, and that substitution is a guess. Transparency effects get flattened, which can subtly alter appearance. JavaScript-driven content (calculated form fields, dynamic elements) is stripped, potentially leaving blank spaces where live content was.

The uncomfortable truth: a PDF/A converted from a sloppy source is a sloppy PDF/A. The format guarantees that what is in the file renders consistently — it cannot guarantee that what is in the file is what you intended. The highest-quality PDF/A comes from exporting directly to PDF/A from the authoring application (Word, InDesign, and LibreOffice all offer it), not from converting afterward.

So treat conversion as a practical fallback, not a magic wand. One more disclosure about our own tool: our PDF to PDF/A converter is a best-effort converter, not an ISO-certified validator — always check its output against the recipient’s own validator (the checklist above) before a formal submission. If anything shifted, fix the source and re-export rather than patching the converted file.

What Is PDF/A Format? The Submission Checklist

Theory is one thing; getting a thesis or court filing accepted is another — run this checklist before you submit:

  • Right version. Confirm which conformance level the institution requires — usually PDF/A-1b or A-2b. “PDF/A” alone is not a complete specification.
  • Fonts embedded. Open the converted file on a different computer or phone and check that nothing substituted. A missing-font substitution is the classic silent failure.
  • Metadata complete. Title, Author, and the PDF/A conformance identifier must be present — our PDF Metadata Editor verifies this in seconds. The XMP conformance tag is mandatory, not decorative.
  • No encryption. A password-protected file cannot be PDF/A. If you protected a draft earlier, remove it before converting.
  • Visual page-by-page check. Flip through the converted file against the original. Transparency flattening and font substitution show up here if anywhere.
  • File size sane. Embedded fonts inflate size; 2–5x growth is normal, 20x suggests a problem.

Archivists reject files for boring reasons — wrong version, missing metadata, leftover encryption. Knowing what is PDF/A format technically matters less than matching the recipient’s checklist. When in doubt, ask the thesis office or court clerk which level they validate against; what is PDF/A format to you matters less than what their validator expects.

Convert with our PDF to PDF/A converter, then walk this list. Anyone who can explain what is PDF/A format but skips validation learns the lesson via a rejected submission. The people who never get rejections are not the ones who best understand what is PDF/A format — they are the ones who check. Make what is PDF/A format compliance a checklist, not a hope, and submissions go through first time. That practical discipline is what is PDF/A format mastery in the real world.

Try It: PDF to PDF/A

Our free PDF to PDF/A converter converts your documents to archival PDF/A in the browser — no upload, no account. Preparing a thesis or legal archive? Check the metadata for completeness first, merge multi-part documents into one file, then convert as the final step.

Frequently Asked Questions

What is PDF/A format used for?

PDF/A is used for long-term archiving of electronic documents — theses, court records, government filings, corporate records. It is an ISO standard (ISO 19005) that restricts PDF to self-contained, future-proof features so documents render identically decades from now.

What’s the difference between PDF and PDF/A?

PDF/A is a restricted subset of PDF. It forbids encryption, JavaScript, audio/video, external references, and non-embedded fonts, and requires embedded XMP metadata. A normal PDF allows all of these. Every PDF/A file is a valid PDF, but most PDFs are not valid PDF/A.

Which PDF/A version should I use?

PDF/A-1b or A-2b for maximum compatibility — they are accepted by virtually every archive, university, and court system. Use A-3 only if you need to embed data files (like invoice XML), and A-4 only if your recipient’s systems explicitly support PDF 2.0-based archiving.

Can I convert a normal PDF to PDF/A?

Yes, but with caveats: conversion cannot embed fonts the original never included (it substitutes them), flattens transparency, and strips JavaScript. Always validate the converted output visually against the original. Exporting directly to PDF/A from Word or InDesign produces better results than converting afterward.

Is PDF/A a backup?

No. PDF/A ensures format longevity — the file remains readable and renders consistently over time. Backup ensures survival — copies in multiple locations. Archiving without backup is still a single point of failure.