PDF/A Explained: Why Archival PDFs Matter for Compliance

Most PDFs are built to be read today, on whatever device you have. PDF/A is built for a different job: making sure a document opens correctly in 20 years, on software that doesn't exist yet. If you've ever been asked to submit a "PDF/A compliant" file for a legal filing, a government archive, or a corporate records system, this guide explains what that actually means and why it's not just a regular PDF with a different name.

What makes PDF/A different from a regular PDF

PDF/A is an ISO-standardized (ISO 19005) subset of the PDF format, designed specifically for long-term preservation. A normal PDF is allowed to reference things outside itself — external fonts installed on the viewer's computer, links to other files, audio or video, JavaScript, and encryption. Any of those can silently break the document years later if the referenced resource disappears or the software that plays it stops existing.

PDF/A closes those doors. To be valid PDF/A, a file must:

• Embed every font it uses. The document carries its own fonts rather than relying on the viewer having them installed — no reflowed text or missing glyphs decades from now.
• Avoid encryption and passwords. An archived file must be openable without a key that might get lost.
• Avoid JavaScript and executable content. Anything that could run code or change behavior over time is excluded.
• Use only self-contained color profiles. Colors are defined in a way that doesn't depend on a specific device or external profile.
• Include an XMP metadata block. Structured metadata (title, author, creation date) is embedded in a standard, machine-readable format.

The result is a file that looks the same and behaves the same no matter when or where it's opened — which is the entire point of an archive format.

Who actually needs PDF/A

Not every document needs to be PDF/A, and forcing it on files that don't need it just adds friction. PDF/A compliance typically comes up in:

• Legal filings. Many courts require electronically filed documents to be PDF/A so records remain readable for the life of a case, which can span decades.
• Government and regulatory submissions. Tax authorities, patent offices, and regulatory bodies in many countries mandate PDF/A for permanent records.
• Corporate records retention. Contracts, financial statements, and compliance documents that must be retrievable and legible years after signing.
• Libraries, universities, and archives. Institutions preserving digital scholarship or historical documents rely on PDF/A specifically because it doesn't depend on any particular software surviving.
• Healthcare records. Patient records often need to remain accessible for the patient's lifetime plus additional years required by local regulation.

If you're not in one of these situations, a standard PDF is fine. If a form, court, or compliance policy specifically asks for PDF/A, that requirement usually isn't optional.

The different PDF/A levels

PDF/A isn't one single spec — it has parts and conformance levels that matter for stricter use cases:

• PDF/A-1 is the original 2005 standard, based on PDF 1.4. It's the strictest and most widely accepted for legal purposes.
• PDF/A-2 (2011) allows some modern PDF features like transparency and JPEG2000 compression while keeping the archival guarantees.
• PDF/A-3 (2012) additionally allows embedding non-PDF files (like the original spreadsheet behind a report) inside the archival PDF — used heavily in e-invoicing standards.

Within each part, conformance level B (Basic) guarantees visual reproducibility, while level A (Accessible) additionally requires proper document structure for screen readers and accessibility. Level U (Unicode) sits in between, guaranteeing text can be extracted correctly.

For most compliance requirements, PDF/A-1b or PDF/A-2b is sufficient. Check the exact requirement before assuming — some government portals reject anything but a specific part and level.

How to convert a PDF to PDF/A

Converting an existing PDF to PDF/A isn't just a "save as" operation — the tool needs to actively embed fonts, strip disallowed content, and validate the result against the spec. With PDFlexa's PDF to PDF/A tool:

1. Upload your PDF. The tool works with existing documents — no need to recreate them from source.
2. Let it process. Fonts get embedded, incompatible elements are removed or flagged, and metadata is normalized.
3. Download the PDF/A file. The result keeps the same visual appearance while meeting the archival standard.

Because this runs in your browser, the conversion doesn't require installing Adobe Acrobat Pro or any desktop archiving suite.

Common problems when converting to PDF/A

A few things trip people up during PDF/A conversion:

• Scanned documents without embedded fonts usually convert cleanly since there's no font issue — the image itself just needs proper color handling.
• Documents built with unusual fonts (especially older Asian-language fonts or custom icon fonts) can fail embedding if the font is not embeddable by license — check the font's embedding permissions if conversion fails.
• Password-protected PDFs must be unlocked before conversion, since PDF/A prohibits encryption entirely.
• Interactive forms need special handling — PDF/A-1 has restrictions on certain form field types that later parts relaxed.

If a converted file fails validation against a specific portal's checker, it's worth checking which exact PDF/A part and level that portal requires rather than assuming any PDF/A output will be accepted.

Frequently Asked Questions

Is PDF/A the same as a regular PDF with password protection removed? No. Removing a password is one requirement, but PDF/A also requires embedded fonts, restricted color profiles, no JavaScript, and structured metadata. A password-free PDF can still fail PDF/A validation for other reasons.

Will converting to PDF/A change how my document looks? Visually, no — the goal of PDF/A is to preserve the exact appearance of the original. What changes is what's happening under the hood: fonts get embedded and certain features get stripped out.

Can I edit a PDF/A file after creating it? Yes, but editing it with a tool that reintroduces disallowed features (like adding a password or a form with a restricted field type) can invalidate its PDF/A compliance. Re-validate after any edit if compliance matters.

Do I need special software to open a PDF/A file? No — any standard PDF reader, including browsers, can open a PDF/A file normally. PDF/A only restricts what can go into the file during creation, not how it's read.

How do I check if a PDF is actually valid PDF/A? Dedicated validators (like veraPDF, an open-source tool used by many archives) check a file against the exact ISO spec. A file that merely "looks like" it should be compliant can still fail strict validation on metadata details.

The bottom line

PDF/A exists to solve one problem: making sure a document stays exactly as readable in 20 years as it is today, regardless of what software or fonts exist by then. If a court, regulator, or records policy specifically requires it, treat that requirement as a hard constraint — a normal PDF, even a very clean one, doesn't meet it. For everything else, PDF/A adds restrictions you probably don't need.

Need to convert a file? Try the PDFlexa PDF to PDF/A tool — it's free and runs right in your browser.

Archiving records as part of your work? See our PDF tools for government agencies or PDF tools for researchers for related workflows.