PDF vs PDF/A: What's the Difference and When You Need It

PDF/A is an ISO standard (ISO 19005) built specifically for long-term archiving. A regular PDF is allowed to reference things outside itself — external fonts installed on the viewer's system, live JavaScript, encryption, links to other files — any of which can break or behave unpredictably years later on a different computer.

PDF/A closes those gaps. It requires every font to be embedded directly in the file (so text renders identically decades from now, even if that font is long discontinued), a defined color profile, and metadata describing the document — plus it prohibits things like encryption, embedded audio/video, and JavaScript, since none of those are reliably viewable indefinitely.

A regular PDF opened in 20 years might render with substitute fonts, missing colors, or broken links, depending on what software's available then. A PDF/A file is designed to be self-contained — everything needed to display it correctly is inside the file itself, so it doesn't depend on the world around it staying the same.

This is exactly why legal, medical, and government record-keeping systems frequently require it: a contract or medical record needs to look the same in 2050 as it does today, not "probably fine if the right font happens to still exist."

If nobody is explicitly asking for PDF/A compliance, you almost certainly don't need it for everyday use — it's a specialized format for a specific purpose (institutional archiving), not a general upgrade over a regular PDF. Convert to PDF/A when a system, court, or organization specifically requires it, not as a default habit.

One practical note: PDF/A doesn't allow encryption, so a password-protected PDF has to be unlocked before it can be converted.