PDF/A vs. PDF/X vs. PDF 2.0: Which PDF Standard Does Your Workflow Actually Need?
If you have ever been told that your organization needs to produce "compliant PDFs" without being told which standard applies, or why, you are not alone. PDF/A, PDF/X, and PDF 2.0 are three distinct standards that serve three distinct purposes. Applying the wrong one to your workflow, or attempting to apply all three at once, creates unnecessary complexity without improving compliance.
This post explains what each standard actually requires, what problems each one was designed to solve, and how to determine which one your workflow needs.
PDF/A: The Archival Standard
PDF/A is an ISO standard (ISO 19005) designed for long-term document preservation. The core requirement is self-containment: a PDF/A document must include everything needed to render it identically on any compliant viewer, at any point in the future, without relying on external resources.
In practice, this means fonts must be fully embedded, color spaces must be explicit, encryption and password protection are prohibited, JavaScript and executable content are not allowed, and XFA (XML Forms Architecture) forms are prohibited. The document must render consistently regardless of the software or hardware used to view it.
PDF/A comes in several conformance levels. PDF/A-1b is the most basic and most widely supported: it requires visual reproducibility but does not mandate Unicode text mapping. PDF/A-2b adds support for JPEG 2000 compression, optional content groups, and embedded files. PDF/A-3u, which is supported by PDF Optimizer, requires Unicode character mapping for all text and allows any file type to be embedded as an attachment, making it the right choice for workflows where machine-readable text extraction will be required later.
PDF/A is used in healthcare, financial services, government, and legal environments where documents must be retained for years or decades and reproduced reliably without dependency on any particular software version. If your compliance requirement is long-term retention, PDF/A is typically the standard required for long-term retention workflows.
PDF/X: The Print Exchange Standard
PDF/X is an ISO standard (ISO 15930) designed for the reliable exchange of print-ready files between content creators and print production environments. Where PDF/A is about future readability, PDF/X is about present-tense production accuracy.
PDF/X requirements focus on color precision and rendering predictability. Transparency must be flattened, because many prepress raster image processors cannot handle live transparency. All fonts must be embedded. Color spaces must be defined in a way that ensures consistent reproduction on the target output device. External content and references are not permitted.
PDF/X is used in commercial printing, packaging production, magazine and catalog publishing, and any workflow where a PDF is being handed off to a press or service bureau. If your requirement is print accuracy rather than archival retention, PDF/X is the standard that applies.
Note that PDF/A and PDF/X can coexist in the same document in certain combinations, most commonly PDF/A-1b and PDF/X-1a, but this is unusual outside of publishing workflows that require both archival storage and print production.
PDF 2.0: The Current Specification
PDF 2.0 (ISO 32000-2) is the current version of the core PDF specification, released in 2017. It is not a compliance standard in the same sense as PDF/A or PDF/X. Rather, it is the baseline specification that all PDF-compliant software is expected to follow.
The most significant change in PDF 2.0 is the deprecation of XFA forms. XFA, which was a proprietary Adobe technology for dynamic form rendering, is explicitly excluded from the PDF 2.0 specification. Organizations still using XFA-based forms need to be aware that PDF 2.0 compliant viewers are not required to render them, and that PDF/A-3u does not support XFA either.
PDF 2.0 also standardizes several features that were previously ambiguous or vendor-specific, including digital signatures, encryption, optional content groups, and associated file attachments. For most organizations, moving to PDF 2.0 is less about meeting an external compliance requirement and more about ensuring long-term compatibility with the direction the specification is heading.
Choosing the Right Standard for Your Workflow
The decision comes down to the purpose of the documents you are producing. If you are building an archival system for regulated documents that must be retained for years and reproduced accurately on future systems, you need PDF/A. PDF/A-1b is the right starting point for most organizations. If you need machine-readable text extraction from archived documents, move to PDF/A-3u.
If you are producing documents for print production, whether commercial printing, packaging, or prepress workflows, you need PDF/X. The specific variant depends on your print environment and the requirements of whoever is receiving the files.
If you are building new document workflows from scratch and have flexibility in your format choices, targeting PDF 2.0 compatibility is a sound approach, particularly if you need to ensure that any XFA-based forms in your existing inventory are addressed.
For many enterprise workflows, the practical answer is PDF/A because it is the standard most commonly required by regulatory, legal, and government retention mandates.
Automating Compliance Conversion with PDF Optimizer
PDF Optimizer supports PDF/A-1b and PDF/A-3u conversion as part of an automated optimization workflow. You configure the target standard in your JSON profile, and PDF Optimizer converts documents to compliance in a single processing pass that also handles compression, image optimization, and any other optimization operations you have defined.
This means you do not need separate tools for optimization and compliance conversion. A single CLI command, using a single profile, can reduce file size and produce ISO-compliant output simultaneously.
Getting Started
Get a free trial of PDF Optimizer