Down2PDF

You send a PDF to a government agency and receive a rejection: "Document must be in PDF/A format." You're preparing legal discovery and your compliance officer asks for PDF/A conversion. You're archiving company records and need to ensure they'll be readable in 50 years.

PDF and PDF/A look nearly identical—open one of each and you might not notice any difference. But under the surface, PDF/A imposes strict requirements that guarantee long-term preservation and accessibility. Understanding these differences is essential for anyone dealing with legal compliance, government submissions, or institutional archives.

What Is PDF/A?

PDF/A is a specialized version of PDF designed specifically for long-term archiving. The "A" stands for "Archive." Unlike regular PDF, which prioritizes flexibility, PDF/A prioritizes self-containment and reproducibility.

The core principle: a PDF/A file must contain everything needed to display itself identically, forever, without relying on external resources.

The ISO Standard

PDF/A is defined by ISO 19005, first published in 2005. It's not a separate file format—it's a constrained subset of the PDF specification with additional requirements. A PDF/A file is still a PDF file; it just follows stricter rules.

Why Regular PDF Isn't Enough for Archiving

Regular PDFs can include features that create long-term preservation risks:

External Dependencies

• Font references: A PDF might reference fonts installed on your system rather than embedding them. If that font disappears in 20 years, the document displays incorrectly.
• External links: Hyperlinks to websites, embedded videos from URLs, or linked images break when destinations change.
• JavaScript: Scripts might execute differently (or not at all) in future PDF readers.

Proprietary and Transient Features

• Encryption: Password-protected PDFs become unreadable if passwords are lost. Encryption algorithms may become deprecated.
• Multimedia: Embedded audio/video may use codecs that future systems don't support.
• Transparency and layers: Complex rendering features may not reproduce identically in future software.

Incomplete Metadata

Regular PDFs often lack proper metadata about creation date, authorship, and document properties—information critical for archives and legal proceedings.

What PDF/A Requires (and Prohibits)

Feature	Regular PDF	PDF/A
Font embedding	Optional	Required (all fonts must be embedded)
JavaScript	Allowed	Prohibited
Encryption	Allowed	Prohibited
External content references	Allowed	Prohibited
Audio/video	Allowed	Prohibited (PDF/A-1, A-2b) or restricted
Transparency	Allowed	Prohibited (PDF/A-1) or standardized (A-2, A-3)
XMP metadata	Optional	Required
Color profiles	Optional	Required for device-dependent colors
LZW compression	Allowed	Prohibited (patent concerns)

PDF/A Versions Explained

PDF/A has evolved through several versions, each adding capabilities while maintaining archival integrity:

PDF/A-1 (ISO 19005-1:2005)

The original standard, based on PDF 1.4. Most restrictive:

• PDF/A-1a: Full compliance including accessibility features (tagged PDF, Unicode mapping)
• PDF/A-1b: "Basic" compliance focused on visual appearance preservation

Use when: Maximum compatibility needed, or when regulations specifically require PDF/A-1.

PDF/A-2 (ISO 19005-2:2011)

Based on PDF 1.7. Adds modern features while maintaining archive quality:

• JPEG 2000 compression allowed
• Transparency support (flattened for A-1 compatibility)
• PDF/A files can embed other PDF/A files
• Digital signatures with PAdES (PDF Advanced Electronic Signatures)

Conformance levels:

• PDF/A-2a: Full accessibility compliance
• PDF/A-2b: Visual appearance preservation
• PDF/A-2u: 2b plus Unicode text mapping

Use when: Modern PDF features needed (transparency, JPEG 2000) while maintaining archival standards.

PDF/A-3 (ISO 19005-3:2012)

Same as PDF/A-2, but allows embedding any file type—spreadsheets, XML data, CAD files, original Word documents:

• Source files can travel with the PDF
• Machine-readable data (XML, JSON) can be included
• Useful for invoices (PDF + structured data) or contracts (PDF + source document)

Use when: You need to bundle original source files or structured data with the archived PDF.

PDF/A-4 (ISO 19005-4:2020)

The newest version, based on PDF 2.0:

• Simplified conformance levels (a, b, u, e, f)
• Better support for engineering documents (PDF/A-4e)
• Aligned with PDF 2.0's improved semantics

Use when: Working with PDF 2.0 features or engineering documents requiring 3D content.

Industries That Require PDF/A

Legal and Courts

Many court systems now require or prefer PDF/A for electronic filings:

• US Federal Courts: CM/ECF system accepts PDF/A
• European courts: Many mandate PDF/A for submissions
• E-discovery: PDF/A preserves document integrity for litigation

Government and Regulatory

• US National Archives: Recommends PDF/A for federal records
• FDA: Accepts PDF/A for pharmaceutical submissions
• SEC: EDGAR system accepts PDF/A
• European Union: Various directives mandate PDF/A for public sector documents

Financial Services

• Banking: Account statements, loan documents archived as PDF/A
• Insurance: Policy documents, claims records
• Audit: Financial statements requiring long-term preservation

Healthcare

• Medical records: Patient histories that must be preserved for decades
• Clinical trials: Documentation requiring regulatory retention
• HIPAA compliance: Secure, self-contained format for PHI

Creating PDF/A Documents

From Microsoft Office

1. File → Save As → Choose location
2. Save as type: PDF
3. Click "Options"
4. Check "ISO 19005-1 compliant (PDF/A)"
5. Save

Note: Office typically produces PDF/A-1b. For higher conformance levels, use specialized tools.

Using Adobe Acrobat

For converting existing PDFs:

1. Open PDF in Acrobat Pro
2. Tools → Standards → PDF/A Conversion
3. Select PDF/A version and conformance level
4. View and resolve any compliance issues reported
5. Save as PDF/A

Open-Source Options

LibreOffice:

• Export as PDF → Check "Archive (PDF/A, ISO 19005)"
• Select PDF/A version

Ghostscript:

gs -dPDFA -dBATCH -dNOPAUSE -sProcessColorModel=DeviceRGB -sDEVICE=pdfwrite -sPDFACompatibilityPolicy=1 -sOutputFile=output.pdf input.pdf

Validating PDF/A Compliance

Creating a PDF/A file doesn't guarantee compliance—validation is essential:

veraPDF (Free, Open Source)

The industry-standard validator, developed by the PDF Association:

• Validates all PDF/A versions (1a through 4)
• Detailed error reporting
• Command-line and GUI versions
• Integration with document management systems

Adobe Acrobat Preflight

Built into Acrobat Pro DC:

• PDF/A compliance checking
• Automatic fixing of some issues
• Detailed reports

Online Validators

For quick checks (consider privacy for sensitive documents):

• PDF/A Validator by 3-Heights
• Soda PDF Checker

Common PDF/A Conversion Challenges

Font Issues

The most common failure: fonts not embedded or not embeddable. Solutions:

• Use fonts that permit embedding (check license)
• Convert text to outlines (loses searchability)
• Substitute with similar embeddable fonts

Transparency

PDF/A-1 doesn't support transparency. Conversion flattens transparent elements, potentially changing appearance. Review carefully or use PDF/A-2 if transparency is important.

Form Fields

Interactive forms with JavaScript validation fail PDF/A compliance. Options:

• Flatten forms (convert to static content)
• Remove JavaScript, keep basic form fields
• Use PDF/A-3 to embed original interactive form

Color Spaces

Device-dependent colors (RGB without profile) violate PDF/A. Solutions:

• Embed ICC color profiles
• Convert to device-independent color spaces
• Use sRGB as default output intent

PDF/A in Document Management

Workflow Integration

For organizations processing high volumes:

• Automate conversion at document ingestion
• Validate on receipt and flag non-compliant files
• Maintain original + PDF/A copy where needed
• Track conversion failures for manual review

Storage Considerations

PDF/A files are often larger than optimized regular PDFs because:

• All fonts must be fully embedded
• Images can't use certain compression methods
• Metadata requirements add overhead

Plan storage accordingly—archival quality comes at a size cost.

When NOT to Use PDF/A

PDF/A isn't always the right choice:

• Interactive documents: Forms requiring JavaScript, multimedia presentations
• Temporary files: Drafts, working documents not intended for archiving
• Size-constrained: When file size is critical (email attachments, web delivery)
• Encrypted content: When document security requires password protection
• External resources intended: Documents meant to link to updating web content

Conclusion: Choosing the Right Format

Scenario	Recommendation
Legal/court submissions	PDF/A-1b or PDF/A-2b (check jurisdiction requirements)
Government archives	PDF/A-1a for accessibility, PDF/A-2b minimum
Financial records	PDF/A-2b for modern features, PDF/A-3 if source data needed
Medical records	PDF/A-2a for accessibility compliance
Engineering documents	PDF/A-4e for 3D content
Invoices with data	PDF/A-3 (ZUGFeRD, Factur-X standards)
Day-to-day sharing	Regular PDF is fine

PDF/A exists because documents matter beyond the moment of their creation. Contracts need to be enforceable in court years later. Medical histories must be readable decades from now. Government records must survive administration changes. When the stakes are high and time horizons are long, PDF/A provides the certainty that regular PDF cannot guarantee.