Why This Guide Exists

PDF/A is a legal requirement in many contexts, yet most explanations either oversimplify it into a checkbox or bury it in ISO committee language. This guide covers what actually changes when a PDF becomes PDF/A, the real differences between versions, and the questions people most commonly ask before relying on it for archival or compliance work.

🎯 What is PDF/A? The Foundation

The Evolution Timeline

PDF/A was created to solve a critical problem: digital documents decay. As software versions change, fonts disappear, and systems become obsolete, regular PDFs degrade over time. PDF/A locks documents in a preservation capsule.

📅 PDF/A-1 (2005)

First standard - Snapshot format based on PDF 1.4. Substandards: 1a (Tagged content) & 1b (Visual appearance)

📅 PDF/A-2 (2011)

Enhanced version - Based on PDF 1.7, supports transparency, JPEG2000, and PDF-1.7 Extensions

📅 PDF/A-3 (2012)

Most recent - Can embed non-PDF files (Excel, Word, XML), maximum flexibility

📅 PDF/A-4 (2020)

Modern standard - Based on PDF 2.0, includes digital signatures, 3D objects, and advanced compression

⚙️ What Actually Happens During PDF/A Conversion

PDFTEQ's converter is built on Ghostscript, the widely-used open-source PDF/PostScript engine that also powers many other PDF/A tools. Here is what it actually changes in your file to bring it into ISO 19005 compliance — no invented steps, just what the standard requires.

1
Font Embedding & Subsetting

The Core Issue: Regular PDFs contain font references that point to fonts on your computer. In 50 years, when your OS changes, those fonts disappear → text becomes unreadable.

The PDF/A Solution: We embed the entire font file inside the PDF. This "font container" approach means:

  • Font data is binary-encoded into the PDF stream
  • File size increases (~20-50KB per font) but document is standalone
  • Standard fonts (Helvetica, Times, Courier) are subset to used characters only
  • Custom fonts are fully embedded with all variants
  • Text remains perfectly readable across any future device
Regular PDF:
/FontName /Helvetica
/BaseFont (external reference)
PDF/A:
/FontFile <binary data>
/FontDescriptor (embedded)
2
Color Space & Output Intent

The Problem: A regular PDF can reference device-dependent color (plain RGB or CMYK numbers with no defined meaning) or fonts/images tied to a color profile that isn't embedded. Displayed on a different device decades later, colors can shift unpredictably.

The PDF/A Requirement: The file must declare an output intent — an embedded ICC color profile that fixes exactly how color values should be interpreted, independent of any specific screen or printer.

  • An ICC profile is embedded so color numbers have one unambiguous meaning
  • This is a genuine trade-off, not a free upgrade: converting between color models can shift how colors render, especially for documents originally authored in CMYK
  • Worth checking visually on color-critical documents (design proofs, branded materials) after conversion
3
XMP Metadata Injection (The Digital Passport)

This is the MOST CRITICAL step. Without this metadata packet, validation software will reject the file as non-compliant.

We inject a raw XML packet containing PDF/A conformance information:

<?xpacket begin='' id='W5M0MpCehiHzreSzNTczkc9d'?> <x:xmpmeta xmlns:x='adobe:ns:meta/'> <rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'> <rdf:Description rdf:about='' xmlns:pdfaid='http://www.aiim.org/pdfa/ns/id/'> <pdfaid:part>2</pdfaid:part> <pdfaid:conformance>B</pdfaid:conformance> </rdf:Description> </rdf:RDF> </x:xmpmeta>

What this means:

  • pdfaid:part = PDF/A version (1, 2, 3, or 4)
  • pdfaid:conformance = Conformance level:
    • A = Accessible (tagged content, structure)
    • B = Basic (visual appearance only)
4
Independent Validation

A conversion engine reporting "no errors" is not the same as a file being verified PDF/A-compliant — Ghostscript can, under some settings, produce output that isn't fully compliant without raising an error. To close that gap, every converted file is additionally checked with veraPDF, the open-source validator built for exactly this purpose, before it's returned to you. If a file doesn't pass, it isn't served labeled as compliant.

📊 Complete PDF vs PDF/A Comparison Table

Feature Regular PDF PDF/A (ISO 19005)
Font Management ❌ External references (system fonts) ✅ Fully embedded in document
Interactive Forms ✅ Fully editable fields & buttons ❌ Flattened (static only)
JavaScript/Scripting ✅ Supported ❌ Strictly Not allowed
Audio/Video Content ✅ Can embed media ❌ Not permitted
Transparency Effects ✅ Full support ⚠️ Limited (PDF/A-2+ only)
JPEG2000 Images ❌ Not supported ✅ Supported (PDF/A-2+)
External Links ✅ Full external linking ⚠️ Links must be relative
Embedded Files ✅ Can attach anything ⚠️ PDF/A-2 and earlier: PDF/A files only. PDF/A-3 removed that restriction and allows any file type
Digital Signatures ✅ Supported ✅ Fully supported
XMP Metadata ⚠️ Optional ✅ Required & validated
File Size ✅ Smaller (fonts external) ❌ Larger (+20-50% due to fonts)
50-Year Preservation ❌ Fonts may degrade ✅ Guaranteed readable
Legal/Government Use ⚠️ Often not accepted ✅ Mandated by law
Compliance Validation ⚠️ No validation needed ✅ Strict ISO 19005 validation

🔍 PDF/A Versions & Conformance Levels Explained

The Two Conformance Levels

PDF/A-1a, 2a, 3a (Level A)

A = Accessible (Tagged PDF)

  • ✅ Complete logical structure (tags, hierarchy)
  • ✅ Accessibility data for screen readers
  • ✅ Semantic meaning preserved
  • ✅ Government mandate for official documents
  • ❌ More complex to create
  • ❌ Larger file sizes
PDF/A-1b, 2b, 3b (Level B)

B = Basic (Visual Appearance Only)

  • ✅ Preserves visual appearance only
  • ✅ Simpler to create (most common)
  • ✅ Smaller file sizes
  • ✅ The most common choice for general archival
  • ❌ No logical structure
  • ❌ Limited accessibility

Version Comparison Matrix

Aspect PDF/A-1 (2005) PDF/A-2 (2011) PDF/A-3 (2012) PDF/A-4 (2020)
Base PDF Version PDF 1.4 PDF 1.7 PDF 1.7 PDF 2.0
Transparency ❌ Not allowed ✅ Supported ✅ Supported ✅ Supported
JPEG2000 ❌ No ✅ Yes ✅ Yes ✅ Yes
Embedded Files ❌ Not allowed ❌ Not allowed ✅ Any file type (its defining feature) ⚠️ Via the PDF/A-4f profile
Digital Sigs ✅ Basic ✅ Full ✅ Full ✅ Advanced
3D Objects ❌ No ❌ No ❌ No ✅ Yes
Accessibility ⚠️ Limited ✅ Full ✅ Full ✅ Full
Industry Adoption ⭐⭐⭐⭐ Highest ⭐⭐⭐⭐⭐ Most common ⭐⭐⭐ Growing ⭐⭐ Emerging

❓ 52 Research-Backed FAQs: The Complete Knowledge Base

We have compiled and answered exactly 52 unique, highly-searched questions about the PDF/A format from our research data to provide you with the most exhaustive resource on the internet.

Use regular PDF for temporary documents and interactive forms. Use PDF/A for long-term archival, legal compliance, and government submissions.

No. Every PDF/A is a PDF, but not every PDF is a valid PDF/A. PDF/A has strict ISO 19005 compliance rules (no JavaScript, embedded fonts).

You can use PDFTEQ's browser-based converter, Adobe Acrobat Pro (Save As > PDF/A), Foxit Reader, or LibreOffice export options.

No content editing is allowed as it breaks the archival integrity. You can only add annotations or digital signatures.

Larger file sizes, inability to edit content, no multimedia (video/audio) support, and no JavaScript functionality.

PDF/A is typically 20-50% larger because it must embed all font data and color profiles to remain self-contained.

Adobe Acrobat, Foxit, PDFTEQ, and Calibre fully support it. Browsers like Chrome and Edge offer partial (viewing) support.

Open it in Adobe Acrobat — compliant files show a blue ribbon stating it claims PDF/A compliance. For a definitive check, run it through an independent validator like veraPDF, since a file can claim compliance without actually passing validation.

Regular PDFs can execute malicious JavaScript. PDF/A is much safer because it strictly forbids executable scripts.

If the document must be kept for 5+ years or submitted to a government entity, use PDF/A. Otherwise, use regular PDF.

There is no "PDF B" format. 'A' and 'B' refer to conformance levels within PDF/A (e.g., Level A = Accessible, Level B = Basic).

Portable Document Format / Archive.

To guarantee that an electronic document will render exactly the same way 50 to 100 years in the future.

PDF/A-2b is a reasonable default for most general archival use — it balances modern features (like transparency support) with wide compatibility. If accessibility (screen reader support) matters for your document, use the "a" conformance level instead (e.g. PDF/A-2a).

Yes, especially if it is a PDF/A, as it disables macros and JavaScript. However, always download from trusted sources.

In Acrobat, go to Preferences > Documents > "View documents in PDF/A mode" and select "Never".

Do not use PDF when you need real-time collaboration, database management, or highly responsive web-fluid content.

No. PDF remains the global standard for fixed-layout documents and legal records, constantly evolving with standards like PDF/A-4.

Save as PDF for documents with text to maintain vector scalability. Save as JPEG for photographs.

To preserve exact formatting, layout, and fonts across different devices and operating systems.

1) Searchable PDFs (with a text layer) and 2) Image-only PDFs (scanned documents without OCR).

Generally safe. However, standard PDFs can harbor malicious scripts. Use PDF/A or trusted viewers like PDFTEQ for maximum safety.

Word is for drafting and editing. PDF is for publishing and sharing finished documents securely.

PDF/Engineering. An ISO standard (ISO 24517) built specifically to handle complex 3D technical drawings and CAD blueprints.

Standard PDFs support Launch Actions, embedded executables, and JavaScript APIs which can be exploited by hackers.

PDF/eXchange. A strict format (ISO 15930) used by the professional printing industry to ensure CMYK color accuracy.

Use the preflight tools in Acrobat Pro, or run the file through an independent validator like veraPDF, the open-source tool built specifically for checking PDF/A conformance.

Standard PDF prioritizes features (forms, encryption, media). PDF/A prioritizes longevity by forcing all data to be embedded.

Yes. Cryptographic digital signatures are fully supported and will not break the ISO 19005 compliance.

No. A PDF must be specifically converted and injected with proper XMP metadata to become a valid PDF/A.

To meet government regulations for electronic records and prevent data loss from format obsolescence.

Go to File > Export > Create PDF, click 'Options', and check the box that says "ISO 19005-1 compliant (PDF/A)".

Convert Word to standard PDF first using our Word to PDF tool, then run it through our PDF to PDF/A converter.

1a requires semantic structure tags (paragraphs, tables) for screen readers. 1b only guarantees visual appearance.

Both support transparency (unlike v1). 2a is accessible (tagged), while 2b is basic.

It depends on the institution. PDF/A is commonly required or strongly preferred by government archives, many e-filing systems, and some universities for permanent submissions — but the exact rules (including which PDF/A version) vary and can change. Check the specific submission guidelines of the institution you're dealing with rather than assuming one blanket rule applies everywhere.

The ISO standard sets no strict limit. PDFTEQ handles conversions up to local RAM limits (typically 1GB+).

Yes. In fact, standard XMP metadata is mandatory to declare the file's conformance level.

Use PDFTEQ's Metadata Editor tool to wipe the Info Dictionary before converting to PDF/A.

No. Encryption fundamentally violates the archival standard, as passwords can be lost over 50 years.

Extensible Metadata Platform is an XML-based language that embeds the document's ISO conformance details directly into the file.

Yes. TrueType, OpenType, and custom fonts are fully supported as long as their binary data is completely embedded.

Regular PDFs may degrade within 10-20 years. PDF/A is mathematically designed to be readable for 50 to 100+ years.

In regular PDFs, the system substitutes a fake font (breaking formatting). In PDF/A, this is impossible as fonts are embedded.

It varies by agency and record type. In the US, for example, NARA's guidance for transferring permanent electronic records references PDF/A among accepted formats, but the specific requirements are set out across several CFR parts and bulletins and depend on the type of record — it isn't one single blanket rule. If you're submitting to a specific agency, that agency's current published requirements are the reliable source, since these details do get updated.

Yes. It is the preferred format for archiving HIPAA-compliant patient medical records over long periods.

X-1a restricts files to CMYK only and flattens transparency. X-4 allows transparency and color-managed RGB for modern printing.

Using parsing tools that check the byte stream against a 100+ point ISO 19005 checklist (checking fonts, colors, XMP).

Yes. Lossless compression (ZIP/Flate) is standard. Lossy compression (JPEG) is allowed but degrades archival quality.

For desktop: Adobe Acrobat Pro. For a free, browser-based option: PDFTEQ's converter.

Yes. Document outlines (bookmarks) are fully supported and highly recommended for large archives.

Yes. However, it is strongly recommended to run them through an OCR tool first to create a searchable text layer.

🔒 Why Hybrid Processing Matters

Server-Based Processing (Others)
  • Your file uploaded to company servers
  • Unknown data retention policies
  • Privacy risks for sensitive legal docs
Hybrid Processing (PDFTEQ)
  • Files processed via encrypted tunnels
  • Complete privacy protection
  • Instant server deletion (0% Retention)

Execute ISO 19005 Protocol

Start your conversion — fonts embedded, metadata injected, and independently verified with veraPDF.

Convert PDF to PDF/A (Free)