PDF has been around since 1993. For most of that time, the world ran on PDF 1.7, the version standardized as ISO 32000-1 in 2008. In 2017, ISO published a substantial update: PDF 2.0 (ISO 32000-2). A revised PDF 2.0 came out in 2020, with another minor revision in 2024. Almost a decade in, PDF 2.0 is finally common enough that the choice between 1.7 and 2.0 starts to matter for real workflows.
This guide compares the two and explains when you should care.
A brief history
- PDF 1.0 (1993), the original.
- PDF 1.3 (2000), the version that PDF/X-1a is based on. Still the lowest common denominator.
- PDF 1.4 (2001), transparency. Yes, PDFs did not have transparency for the first eight years.
- PDF 1.5-1.6 (2003-2004), layers, embedded multimedia, 3D.
- PDF 1.7 (2006, ISO in 2008), the long-running plateau. Everything you have read or produced before roughly 2020 is probably PDF 1.7.
- PDF 2.0 (ISO 2017, revised 2020 and 2024), the modern baseline.
For nine years, PDF 2.0 sat unused while tools caught up. By 2026, most authoring and reading tools handle it, and several modern standards (PDF/X-6, PDF/UA-2, the upcoming PDF/A-5) require it.
What is actually new in PDF 2.0
The 2.0 spec is not a complete redesign, every PDF 1.7 file is still readable. PDF 2.0 cleans up ambiguities, adds features, and removes legacy baggage.
New features:
- AES-256 encryption as the modern default. PDF 1.7 supports it via an extension; 2.0 makes it standard. See PDF encryption explained.
- Improved digital signatures. Better algorithms (SHA-256+), better certificate validation, support for long-term validation (LTV) baked in.
- Better tagged-PDF support. The structure tree got cleaner, with new tag types and stricter requirements aligned with PDF/UA. See tagged PDF vs untagged PDF.
- Output intents in pages. PDF/X-style color intents can live at the page level, not just the document level. Useful for files that mix pages destined for different presses.
- Page-level metadata. Per-page XMP metadata enables fine-grained provenance and rights tracking.
- Soft masks in images and shadings are spec'd more rigorously, reducing the long tail of rendering bugs across viewers.
- MathML tagging. Mathematical content can be tagged for accessibility (a huge upgrade for technical publishing).
- Modern cryptography. Hash functions, key sizes, and signature algorithms are brought up to current best practice.
Things deprecated or removed:
- 40-bit and 128-bit RC4 encryption, historic, weak, gone.
- Several rarely-used color spaces and rendering tricks, cleaned up to reduce viewer disagreement.
- Some old, ambiguous syntax forms, only one canonical way to express things, less interpreter divergence.
Why this matters in 2026
Three reasons.
Security. If you produce signed or encrypted PDFs that need to stand up to modern threats, PDF 2.0 brings cryptography current. AES-256, SHA-256, and properly-specified LTV signatures are baseline expectations now, especially for legal and financial workflows. See digital signatures vs electronic signatures for the legal context.
Compliance. Modern accessibility (PDF/UA-2) and archival (PDF/A-4 and the upcoming PDF/A-5) standards build on PDF 2.0. If your industry mandates one of these, you are implicitly mandated to produce PDF 2.0 files.
Quality. PDF 2.0 reduces the long-running "but it renders differently in Chrome / Acrobat / Preview" problem. Stricter spec wording forces converging behavior across implementations. The era of "this works in Acrobat but breaks in everything else" is slowly ending.
Compatibility realities
Almost every modern viewer handles PDF 2.0 by 2026:
- Adobe Acrobat / Reader (DC and beyond)
- Foxit Reader
- PDF-XChange Editor
- macOS Preview (recent versions; some advanced features still partial)
- Browser-based viewers (Chrome's pdfium, Firefox's pdf.js, Edge's built-in)
- Mobile readers (most iOS PDF apps, most Android PDF apps)
The long tail of older viewers, embedded readers in old appliances, and conservative enterprise PDF stacks may still drop down to 1.7 rendering. Practical guidance: if your audience is general internet users on current hardware, 2.0 is safe. If your audience includes airline kiosks, hospital admin systems, or government legacy software, default to 1.7 for the next few years.
How to know which version a PDF is
Open the file's properties:
- Adobe Acrobat: File → Properties, look at the PDF Version field.
- Most readers expose this in a "Document Properties" or "About this PDF" dialog.
- Programmatically: open the file in any text editor and look at the first line.
%PDF-1.7versus%PDF-2.0is right there.
How to produce PDF 2.0
Most modern authoring tools default to 1.7 for compatibility, but expose 2.0 as an option:
- Adobe InDesign: Export → Adobe PDF (Print or Interactive) → Compatibility → "Acrobat 10 / PDF 2.0".
- LibreOffice: PDF export dialog → Version → "PDF 2.0".
- Ghostscript:
gs -sDEVICE=pdfwrite -dCompatibilityLevel=2.0 -dPDFSETTINGS=/prepress ... - qpdf:
qpdf --object-streams=generate input.pdf output.pdf --conformance-level=2.0. See qpdf introduction.
If a tool does not yet expose a 2.0 option, you can produce a 1.7 file and convert it. The structural changes are mostly additive; conversion is lossless in the common case.
Should you upgrade your existing files?
For files actively in use, being signed, distributed, edited, upgrading to PDF 2.0 when convenient is reasonable. The benefits (better signatures, cleaner tagging) compound.
For archival files, the situation is more nuanced. PDF/A-2 is based on PDF 1.7 and is mature. PDF/A-4 (PDF 2.0-based) is newer but still finds gaps in some archival workflows. If you are submitting to a national archive or regulator, ask what they accept before re-saving thousands of files.
Common gotchas
Signed files do not transparently upgrade. Re-saving a signed PDF as 2.0 invalidates the signature. Plan version choices before signing.
Validators can lag. Some preflight tools still flag perfectly-valid PDF 2.0 features as warnings because their rules predate the spec. Update your preflight toolchain.
Mixed-version pipelines. If your pipeline mixes PDF 2.0 producers and PDF 1.7-only consumers, errors do not show up at production; they show up months later when an archive system rejects an attachment. Standardize end to end.
Tag-tree migration. A PDF/UA-1 tagged file does not become PDF/UA-2 automatically. The tag-name set expanded; old tag names are still legal but may be remapped. Run a tagged-PDF accessibility checker after migration.
Takeaway
PDF 2.0 is the version PDF should have been a decade ago: tighter spec, modern cryptography, cleaner accessibility, page-level color and metadata, and removal of weak legacy features. By 2026 it is safe for most workflows. Use it for new files that benefit from modern signing or accessibility; default to 1.7 only when your audience is constrained by older systems. When you edit files in Docento.app, the version stays as authored, so you can pick the right starting point and not lose it on a round trip.
