Published
PDF/A: The Archival Format for Documents You Want to Still Open in Twenty Years
Most PDFs aren't built to last. PDF/A is a stricter, ISO-standardized version of the format — no audio, no JavaScript, no encryption, no fonts borrowed from the machine that made it — designed so a document opens the same way in 2046 as it does today. Here's what it locks down, where it came from, and whether you actually need it.
What It Is
PDF/A is a stricter version of PDF, standardized by ISO under ISO 19005. It has one job: make sure a document still opens correctly decades after it was created. A PDF/A file is still a valid PDF, but it's missing anything that could stop working later — no audio or video, no JavaScript or executable file launches, no encryption, no links out to fonts or resources living outside the file, no LZW compression (which carried patent baggage when the standard was first written).
Underneath all of that is one idea: embedding. A PDF/A file has to be self-contained — every font, every color profile, every piece of content packed inside the file itself, rather than borrowed from whatever computer happens to open it. That's part of why what a document's metadata actually contains matters more than most people assume. A PDF/A file carries its own description of itself, in a standardized form, so a machine reading it in 2046 doesn't have to guess.
Why It Matters
Open an ordinary PDF on a different computer, or open it again years later, and you've probably seen the small failures: a heading substitutes a different typeface, a table shifts, a character turns into a box. That happens because a regular PDF is allowed to reference a font installed on the machine that created it, instead of carrying a copy of the font itself. If that font isn't there anymore, the viewer improvises. It's the same root cause behind why a PDF looks different depending on what opens it — just stretched across years instead of across devices.
Twenty years isn't a marketing number here. It's close to the actual design brief. Every restriction in PDF/A traces back to it. Encryption is forbidden because a password-protected file is a file nobody can guarantee access to later. External references are forbidden because a linked resource can move, change, or vanish. JavaScript is forbidden because executable code is one more thing that has to keep working, on hardware and in runtimes nobody can predict. Strip all of that out, and what remains is a file with nothing left to go wrong.
Where You'll See It
PDF/A wasn't built for casual reading. The push for it started in 2002, led by the Association for Information and Image Management, the National Printing Equipment Association, and the Administrative Office of the U.S. Courts — the last of those because federal courts needed an electronic filing format that wouldn't depend on any single software vendor still being around by the time a case file needed to be pulled up again. That's roughly where PDF/A still lives: court filing systems, library and museum deposit requirements, bank and insurance records, academic thesis archives. Anywhere an institution is making a formal commitment to keep a document readable long after everyone who created it has moved on.
The standard has grown since then. PDF/A-1 (2005) covers PDF 1.4. PDF/A-2 (2011) moved to PDF 1.7 and added a Unicode text-mapping level. PDF/A-3 (2012) allows embedding the original source file alongside the archival copy. PDF/A-4 (2020) is built on PDF 2.0 and adds engineering-specific profiles for things like 3D content. Each version keeps the same promise, just extended to match whatever PDF itself could do by that point.
How Margina Handles It
None of this changes how a PDF/A file behaves on the reading side. Margina opens one the same way it opens any other PDF — the restrictions that make PDF/A useful for archiving are invisible once the file is finished. They only mattered to whoever produced it. The same self-contained-embedding idea that makes PDF/A reliable across decades is, at a smaller scale, a problem a local-first reader already has to solve for an ordinary PDF or EPUB you've sent yourself: no account, no server, nothing about the file that depends on a service still being around later.
If you're not sure whether a document you're holding is PDF/A, you almost certainly don't need it to be. The format exists for institutions making formal preservation commitments, not for a contract you're reading on your phone or a chapter someone emailed you.
Frequently Asked Questions
Is PDF/A the same as a regular PDF?
It's a restricted subset. A PDF/A file is still a valid PDF, but it's missing anything that could break over time — no audio or video, no JavaScript, no encryption, no links out to fonts or resources living outside the file. Everything a PDF/A needs to render is packed inside it.
How do I know if a PDF is already PDF/A?
Most PDF viewers that support the standard show it somewhere in the document properties. If nothing mentions it, assume it's a regular PDF — most PDFs you receive day to day are.
Do I need to convert my documents to PDF/A?
Almost certainly not, unless an institution is telling you to — a court's e-filing system, a library's deposit requirement, a records-retention policy at work. For a contract you're reading on your phone or a chapter you sent yourself, a regular PDF is fine.
Why do courts and archives specifically require it?
Because they're committing to keep a document readable for decades, sometimes without knowing what software will exist by then. PDF/A trades flexibility for that guarantee: nothing in the file depends on anything outside it.
Conclusion
PDF/A is what a file format looks like when it's designed for a reader who won't show up for twenty or thirty years, rather than one reading it in the next few seconds. Most of what actually crosses your phone — a contract, a syllabus, a chapter someone sent you — was never meant to last that long, and it doesn't need to. It's worth recognizing PDF/A mainly so you know what it is when you see it: a format built for institutions, not for the document sitting in your inbox right now.