You are submitting a document to a court, a government agency, or a university archive, and the instructions say: "PDF/A format required." What does that mean? And if nobody asked for PDF/A, does it matter? Here is the difference between a standard PDF (flexible, living, interactive) and PDF/A (self-contained, locked down, archival) — and when you actually need each one.
Short version: standard PDF is for documents you use today. PDF/A is a straitjacket that guarantees the document will look identical in 50 years — no external fonts, no JavaScript, no dynamic content. If a regulation demands PDF/A, use a PDF to PDF/A converter to make your PDF compliant. If no regulation demands it, stick with standard PDF — it is smaller, more flexible, and perfectly fine for everything else.
What PDF/A Actually Does — Self-Contained by Force
A standard PDF is like a web page — it can reference external resources. A font that lives on your operating system. An image loaded from a URL. A JavaScript that calculates form fields. These work today because the resources are available. In 2050, that external font server is gone, that JavaScript engine has changed, and the PDF looks broken.
PDF/A solves this by banning everything external:
- All fonts must be embedded inside the file. Even system fonts like Arial or Times New Roman — if the PDF uses them, the font data must be copied into the PDF. No "this font should be installed on the reader's computer."
- No JavaScript, no multimedia, no 3D. These are execution-dependent — they rely on the PDF reader's implementation, which changes over time. PDF/A strips them all.
- No external references. Images, stylesheets, data streams — everything must be inside the file. No URLs, no linked resources.
- No encryption. An encrypted PDF might become unopenable if the decryption method is lost or deprecated.
- Color profile required. An ICC color profile must be embedded so colors render identically on any screen or printer, now and in the future. The trade-off: the file gets slightly larger (font embedding adds 5-30% on a typical document), and you lose interactive features. What you gain: a guarantee that the document will render identically on any PDF reader, on any operating system, at any point in the future.
Standard PDF — Flexible, Interactive, Smaller
Standard PDF was designed for documents that live in the present. It is the universal format for sharing formatted documents — layouts, fonts, images, and vector graphics in a self-contained file. But unlike PDF/A, it allows shortcuts:
- External fonts — the PDF references "Arial" without embedding it, assuming the reader's system has it installed. Smaller file, works on most computers.
- JavaScript — form validation, calculations, dynamic content. A tax form PDF that calculates totals in real time. An interactive map with zoomable layers.
- Multimedia — embedded video, audio, 3D models. A product brochure with a rotating 3D view. A portfolio with embedded video clips.
- Transparency and layers — overlapping semi-transparent elements, optional content groups that can be toggled on/off.
- Encryption — password protection, DRM, digital rights management. For 99% of PDFs — invoices, reports, contracts, ebooks, presentations, forms — standard PDF is the right choice. It is more efficient, supports features users expect, and renders correctly on every current PDF reader. The risk (future incompatibility) only matters if the document must survive for decades.
When You Actually Need PDF/A
PDF/A is not "better PDF." It is a preservation format for a specific set of use cases:
Legal and court filings
Many courts — US federal courts, UK HM Courts, German courts — require PDF/A for electronic filings. The rationale: a PDF/A document submitted in 2026 will be readable and identical when the case is reviewed in 2046. Standard PDF submissions may be rejected outright if the court's system detects they are not PDF/A compliant.
Government archives and national libraries
National archives, libraries, and government record-keeping systems mandate PDF/A. The US Library of Congress, the UK National Archives, the European Commission — all require or strongly recommend PDF/A for document submission and preservation. These institutions think in centuries, not years.
ISO-compliant organizations
Organizations that follow ISO document management standards (ISO 19005 defines PDF/A) often require it as a matter of policy. If your contract, grant agreement, or regulatory filing says "documents must comply with ISO 19005" — that means PDF/A.
Long-term preservation (10+ years)
If a document must be readable and identical in 2036, 2056, or beyond — scientific papers, historical records, architectural plans, legal contracts — PDF/A is the safe choice. Standard PDF might still work in 2056, but there is no guarantee. PDF/A guarantees it.
When PDF/A Is Overkill
Most PDFs do not need PDF/A. Converting to PDF/A adds size, strips interactive features, and provides no benefit if nobody is going to open the file in 20 years:
- Email attachments and link sharing — the recipient opens it now, not in 2050. Standard PDF is smaller and works perfectly.
- Invoices, receipts, bank statements — keep them as standard PDF. If you need to archive them long-term, converting to PDF/A when you archive is easier than maintaining PDF/A for every outgoing document.
- PDFs with fillable forms — converting to PDF/A removes the form interactivity. The recipient cannot type into fields. For forms, standard PDF is the only practical choice.
- PDFs with multimedia or 3D — PDF/A strips it all. If the multimedia is essential to the document, PDF/A cannot be used.
- Ebooks, brochures, marketing materials — these are ephemeral by nature. Nobody will read a 2026 brochure in 2056. Standard PDF is fine.
PDF/A Versions — A-1 Through A-4
PDF/A has evolved through four versions. Each is more permissive than the last. If you are converting to PDF/A and the regulation does not specify a version, here is what to pick:
| Version | Year | Based on | Key feature | Pick when |
|---|---|---|---|---|
| PDF/A-1 | 2005 | PDF 1.4 | Strictest — no transparency, no layers, no JPEG2000 | Maximum compatibility required |
| PDF/A-2 | 2011 | PDF 1.7 | Adds transparency, JPEG2000, PDF/A attachments | Best general choice for new archives |
| PDF/A-3 | 2012 | PDF 1.7 | Any file as attachment (DOCX, CSV, XML) | Need to embed source files alongside |
| PDF/A-4 | 2020 | PDF 2.0 | Fewest restrictions, no conformance levels | Cutting-edge, modern PDF 2.0 features |
| Each version also has conformance levels (except A-4, which removed them): "b" (basic) guarantees visual appearance — the document looks right; "a" (accessible) adds tagging and structure for screen readers and accessibility tools; "u" (unicode) guarantees text can be extracted as Unicode — useful for search and text mining. |
For most users, PDF/A-2b is the practical sweet spot — modern enough to handle typical documents (including transparency), compatible enough for almost all archiving requirements, and widely accepted by courts and government agencies. PDF/A-1b is still requested for maximum compatibility with older systems.
How to Convert a Standard PDF to PDF/A
Converting to PDF/A is automated — you do not manually embed fonts or strip JavaScript. The PDF to PDF/A converter does it:
- Upload your standard PDF.
- Choose the PDF/A version — A-1 for maximum compatibility, A-2 for modern archives, A-3 to embed source files.
- The converter validates the PDF against the chosen standard, embeds missing fonts, strips forbidden content, and adds the required metadata and color profile.
- Download the compliant PDF/A. The file is now marked with a conformance indicator that validation tools can verify. What gets removed during conversion: JavaScript, multimedia, 3D content, external font references (fonts are embedded instead), encryption, and — depending on the PDF/A version — transparency and layers (flattened instead of removed in A-2 and later). The visual appearance of text, images, and vector graphics is preserved.
Related Tools
If you need to submit a PDF/A but your source is a Word document, convert directly to PDF/A with the Word to PDF converter — choose PDF/A as the output format to skip the intermediate standard PDF step. To verify a PDF/A is compliant before submission, check that the file metadata contains a PDF/A conformance marker (most PDF readers show this in Properties). To reduce the size of a PDF/A after conversion (font embedding adds weight), use the PDF compressor — compression does not break PDF/A compliance if it only optimizes internal structures.
Quick Summary
- Standard PDF is for living documents — flexible, interactive, supports forms, JavaScript, external fonts. Use it for everything that does not need to survive decades.
- PDF/A is a preservation format — self-contained, all fonts embedded, no external deps, no JavaScript. Guarantees identical rendering in 50 years.
- Use PDF/A when regulation demands it — courts, government archives, ISO-compliant organizations, long-term preservation beyond 10 years.
- PDF/A-2b is the practical default — modern enough for typical documents, compatible enough for most archiving requirements.
- Converting to PDF/A is automated — font embedding, JS stripping, metadata insertion are all handled by the converter. You upload a PDF, get a compliant PDF/A.