archiving

Converting PDFs to PDF/A-1b & PDF/A-2b: The Complete Archival Guide

Learn how to convert standard PDFs into permanent ISO 19005 PDF/A records with embedded font subsets, color output intents, and zero external dependencies.

A
Alex VanceLead Document Security Engineer
Published
Updated 2026-10-25
3 min read

The assumption that any PDF file will remain readable decades into the future is a dangerous myth. Standard PDFs frequently rely on system fonts installed on the host operating system, external web hyperlinks, dynamic JavaScript runtimes, or uncalibrated color spaces. Over 10 or 20 years, as operating systems evolve and legacy fonts are deprecated, regular PDFs break. The International Organization for Standardization created the PDF/A format (ISO 19005) specifically to guarantee permanent digital preservation.

Understanding the PDF/A Hierarchy

  • PDF/A-1 (ISO 19005-1, based on PDF 1.4): The classic standard. Level 1b guarantees visual preservation across decades; Level 1a mandates structural tags and Unicode character mappings.
  • PDF/A-2 (ISO 19005-2, based on PDF 1.7): Adds support for modern JPEG 2000 compression, transparency layers, and embedded PDF/A file attachments.
  • PDF/A-3 (ISO 19005-3): Allows embedding arbitrary raw XML or CSV data payloads directly inside the PDF container (widely used in European ZUGFeRD / Factur-X electronic invoicing).

Mandatory Conversion Requirements Under ISO 19005

To qualify as an authentic PDF/A document, several strict modifications must occur: every font glyph used in the document must be 100% embedded in the binary payload, standardized ICC color profiles (/OutputIntents) must be attached, and all dynamic features—including JavaScript calculation macros, embedded audio/video, and encryption dictionaries—must be permanently stripped.

Anatomy of the PDF/A OutputIntent Color Profile Dictionary

ISO 19005-1 § 6.2.2 Output Intent Dictionary for PDF/A-1bpdf
% ISO 19005-1 Mandatory Output Intent Dictionary
12 0 obj
<<
  /Type /OutputIntent
  /S /GTS_PDFA1
  /OutputCondition (sRGB IEC61966-2.1)
  /OutputConditionIdentifier (sRGB IEC61966-2.1)
  /RegistryName (http://www.color.org)
  /Info (sRGB IEC61966-2.1)
  /DestOutputProfile 15 0 R
>>
endobj

Government & Judicial Mandate

Federal court systems, municipal land registries, and state archives across North America and Europe strictly mandate PDF/A compliance for all permanent official filings.

1

Load File into Archival Engine

Select your standard PDF in iKnowAPDF converter. Files are parsed inside local browser RAM.

2

Embed Output Intents and Font Glyphs

The engine embeds standardized sRGB color profiles, resolves font subsets, and strips dynamic JavaScript.

3

Export Archival PDF/A

Download your permanent, future-proof document verified for long-term storage across decades.

Recommended Client-Side Tool✓ 100% client-side privacy

Convert PDF Files Locally

Convert PDFs to Word, Excel, PowerPoint, images, or archival standards with zero cloud exposure.

100% Local RAM Execution (Zero Uploads)•No Watermarks or Sign-up
Open PDF Converter

Frequently Asked Questions

Can an encrypted PDF be compliant with PDF/A?

No. ISO 19005 explicitly bans password encryption to guarantee that future digital archivists can access public records without obsolete cryptographic key restrictions.

Why does PDF/A-1b require flattening transparency?

Because PDF 1.4 (on which PDF/A-1 is based) did not standardize blending modes and alpha channels. To ensure exact visual reproduction, transparencies are flattened into solid vector or raster elements.

How can I verify that my converted PDF is truly PDF/A compliant?

You can validate the output file using industry-standard open-source conformance validators such as VeraPDF or the Adobe Acrobat Preflight panel.

Does converting to PDF/A alter my document content or layout?

No. The visual layout, typography, and page numbers remain completely intact. The conversion only standardizes color profiles, font subsets, and container metadata.

A

Written by Alex Vance

Lead Document Security Engineer

Specialist in WebAssembly document processing, cryptographic privacy, and client-side browser architectures. Former browser security researcher with 12+ years optimizing high-throughput ISO 32000 document engines.

Credentials: M.Sc. in Computer Science, ISO 32000 & WebAssembly Security Specialist

Related Guides & Tutorials