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

PDF is the general-purpose format used everywhere. PDF/A is the archival variant defined by ISO 19005 — a stricter subset that guarantees the file will render identically in 50+ years. PDF/A requires all fonts to be embedded, forbids external dependencies (no JavaScript, no embedded video, no external image links), requires explicit color management, and mandates strict XMP metadata. Use PDF/A when you have an archival or regulatory requirement spanning years to decades; use regular PDF for everyday work.

When do I need PDF/A instead of regular PDF?

Three scenarios where PDF/A is required by spec: (1) government/court filings (many US federal courts, EU court systems, state archival agencies require it for filings longer than 1 year); (2) regulated industries (pharmaceutical 21 CFR Part 11, HIPAA archival, SEC 17a-4 financial recordkeeping); (3) long-term contracts and historical preservation (50-year easements, 99-year ground leases, museum/library archival).

What's the difference between PDF/A-1, PDF/A-2, PDF/A-3, and PDF/A-4?

Each newer sub-standard adds features while preserving the archival guarantee. PDF/A-1 (2005, based on PDF 1.4) is most restrictive. PDF/A-2 (2011, PDF 1.7) allows transparency, JPEG 2000, layers. PDF/A-3 (2012) allows embedding ANY file inside the PDF, used for invoicing standards like ZUGFeRD. PDF/A-4 (2020, based on PDF 2.0) is modernized. For maximum backwards compatibility pick PDF/A-1b; for modern features pick PDF/A-2b; for embedded attachments pick PDF/A-3.

How do I convert a regular PDF to PDF/A?

Three free options: (1) LibreOffice — File → Export As PDF, check the PDF/A-1a checkbox in the dialog; (2) PDF24 desktop tool on Windows — has built-in PDF/A export; (3) Adobe Acrobat Pro — File → Save As Other → Archivable PDF (paid). PDFFlare doesn't currently produce PDF/A directly (on the roadmap). After conversion, validate with veraPDF (free, open source) to confirm conformance.

Will compressing a PDF/A file break its conformance?

Possibly — aggressive compression can change embedded font structure or trigger PDF/A validator failures. Use mild compression on PDF/A files (PDFFlare's Compress PDF with the High Quality preset rather than Smallest), and re-validate with veraPDF after compression. For files where PDF/A conformance is mandatory, avoid compression entirely or run validation in your build pipeline to catch any breaks.

May 7, 20269 min read

PDF/A vs PDF: What's the Difference? (And When You Need Each)

You uploaded a PDF to a government portal and got back “file rejected — must be PDF/A.” Or you're archiving a contract and wondering if regular PDF is enough. Or your compliance team handed you a PDF/A-1b spec and you have no idea what the suffix means. So what's actually different between PDF/A vs PDF, and when do you need the archival variant?

In this guide you'll learn the PDF/A vs PDF differences in plain English — what each format guarantees, when you need PDF/A, and how to handle PDFs in long-term workflows using PDFFlare's Compress PDF, Merge PDF, and other tools. PDFFlare doesn't produce PDF/A directly (yet) — but understanding the format helps you decide whether you need it or whether regular PDF is enough.

What Is PDF/A?

PDF/A is the archival variant of PDF, defined by ISO 19005. The “A” stands for Archive. It's a stricter subset of regular PDF designed to guarantee the file will render identically in 10, 50, or 100 years — long after the software that created it has stopped existing.

The key restrictions vs regular PDF:

All fonts must be embedded. Regular PDF can reference system fonts; PDF/A bundles every font in the file itself, so it renders the same on any system.
No external dependencies. No JavaScript, no embedded video, no external image links, no encryption. Everything needed to view the file must be in the file.
Color managed explicitly. PDF/A requires either an embedded ICC color profile or a specified output intent — so colors render the same on every monitor and printer.
Strict metadata. XMP metadata is required and must follow specific schemas.
No transparency in older sub-standards. PDF/A-1 disallows transparent objects; PDF/A-2 and later allow it.

The PDF/A Sub-Standards

PDF/A has multiple sub-standards, each adding features while preserving the archival guarantee:

PDF/A-1 (2005) — based on PDF 1.4. Most restrictive. Two conformance levels: 1a (accessible, full structure / tagging) and 1b (basic, visual fidelity only).
PDF/A-2 (2011) — based on PDF 1.7. Allows JPEG 2000 compression, transparency, layers, and embedding other PDF/A files. Levels: 2a, 2b, 2u (b + Unicode mapping).
PDF/A-3 (2012) — based on PDF 1.7. Like PDF/A-2 but allows embedding ANY file (spreadsheets, source documents, XML data) inside the PDF. Useful for invoicing standards like ZUGFeRD and FacturaE.
PDF/A-4 (2020) — based on PDF 2.0. Modernized. Drops the 1a/1b/2a/2b distinction; instead has PDF/A-4, PDF/A-4f (with attachments), and PDF/A-4e (engineering with 3D).

PDF/A vs PDF — Key Differences in Practice

When to use PDF/A instead of regular PDF

Three scenarios where PDF/A is required by spec:

Government / court filings. Many US federal courts (PACER), EU court systems, and state archival agencies require PDF/A for filings longer than 1 year.
Regulated industries. Pharmaceutical (21 CFR Part 11), medical records (HIPAA-aligned archival), financial recordkeeping (SEC 17a-4), and other regulated industries often mandate PDF/A.
Long-term contracts. 50-year real-estate easements, 99-year ground leases, historical document preservation in libraries and museums — anything where rendering must be guaranteed for decades.

What's the difference between PDF/A-1, 2, 3, and 4?

Each newer sub-standard adds features while preserving the archival guarantee. Pick PDF/A-1b for maximum backwards compatibility (oldest readers handle it), PDF/A-2b for modern features (transparency, layers, JPEG 2000), PDF/A-3 if you need to embed other files, PDF/A-4 if you want PDF 2.0 features and don't need 1a/1b accessibility-vs-basic distinction. When in doubt, ask your compliance team which conformance level they require.

How to convert PDF to PDF/A

PDFFlare doesn't produce PDF/A directly yet — this is on the roadmap. Until it ships, the easiest paths are: (1) Adobe Acrobat Pro's Save As PDF/A option (paid); (2) free PDF24 desktop tool with PDF/A export; (3) LibreOffice's Export As PDF dialog with the PDF/A-1a checkbox enabled. After conversion, PDFFlare's Compress PDF and Merge PDF can still operate on PDF/A files (with the caveat that aggressive compression may invalidate PDF/A conformance — validate with veraPDF or similar after).

When Regular PDF Is Enough

For 95% of everyday use cases, regular PDF works fine. You don't need PDF/A for:

Email attachments. Sharing a document this week — PDF is universal, PDF/A adds no benefit.
Internal documents. Memos, proposals, shared notes within an organization. Use PDF.
Web publishing. Blog post PDFs, white papers, marketing material. Use PDF (often with PDF/UA tagging for accessibility, but not PDF/A).
Most contracts under 5 years. Standard PDFs are durable enough; PDF/A is overkill.

Common Mistakes

Producing PDF/A then signing it with embedded certificate. Some signing operations break PDF/A conformance. Always re-validate after signing.
Compressing PDF/A aggressively. Heavy lossy compression can change embedded font structure or trigger validator failures. For PDF/A files, use lighter compression and re-validate.
Converting scanned PDF/A without proper OCR. PDF/A-1a requires structure / tagging; scans need OCR text layer + structure tags. Run OCR PDF first to add text, then convert to tagged PDF/A.

How to Validate PDF/A Conformance

Use veraPDF(free, open source) — the canonical validator. Drop your file in, get a report showing which PDF/A profile it conforms to (or which validation rules it fails). Adobe Acrobat Pro also has a built-in Preflight tool that validates PDF/A. For ad-hoc checks, the file's document properties dialog usually shows “PDF/A-1b” (or whatever variant) in the Description tab.

Privacy: PDF/A Tools and Privacy

Most PDF/A converters run server-side because the conformance checks are expensive. For confidential documents, prefer desktop tools (LibreOffice, Adobe Acrobat Pro) over web converters. PDFFlare's companion tools (Compress, Merge, Edit, Sign) all preserve privacy — Compress runs in a sandboxed worker that never persists files; Merge / Edit / Sign run entirely client-side.

Related Tools

Compress PDF — shrink PDF/A files (use mild compression to preserve conformance).
Merge PDF — combine multiple PDF/A files into one archive.
OCR PDF — add a text layer to scanned PDF/A files for searchability.
Edit PDF — annotate PDF/A files (re-validate conformance after).

Wrapping Up

PDF/A vs PDF: regular PDF for everyday use, PDF/A when you have a regulatory or archival requirement spanning years to decades. PDF/A locks fonts, forbids external dependencies, and guarantees identical rendering forever. Use it when required; use regular PDF when not. PDFFlare's companion tools (Compress, Merge, OCR) work on PDF/A files but should be used with awareness — aggressive operations can invalidate conformance, so validate with veraPDF after.