PDF Standards
PDF/X standards and a practical guide for professional print production.
PDF/X standards and a practical guide for professional print production.
What is PDF/X?
PDF/X is a print-optimised PDF standard defined by ISO. Its differences from a regular PDF:
- All fonts embedded
- Colour profile defined
- Transparency rules specified
- Print-exchange constraints; image resolution still needs a separate profile check
PDF/X Versions
| Standard | Year | Feature |
|---|---|---|
| PDF/X-1a:2001 | 2001 | CMYK/spot, no live transparency |
| PDF/X-3:2002 | 2002 | RGB + CMYK |
| PDF/X-4:2008 | 2008 | Live transparency, layers |
| PDF/X-5:2010 | 2010 | External references |
| PDF/X-6:2020 | 2020 | PDF 2.0 production exchange |
PDF/X-1a:2001
Most Widely Used
A legacy exchange format for a producer who explicitly requires it:
CMYK or Spot colour only
All fonts embedded
Flattened content expected for legacy workflows
ICC profile required
No RGB
No live transparencyWhen to Use It
- Offset print
- Working with external print shops
- When maximum compatibility is required
PDF/X-4:2008
Modern Print Standard
Live transparency
Accepts CMYK and RGB
Layer support
OpenType fonts
ICC profileWhen to Use It
- Digital print
- Designs containing transparency
- Modern workflows
- A suitable modern producer profile; not a universal acceptance rule
Preserve-first policy
NowToPrint checks PDF/X, output intent, transparency, spot colour, and font evidence without silently converting RGB or spot colours to CMYK, flattening transparency, trapping, or outlining fonts. If a conversion is required, prepare and upload a corrected source PDF from a specialist prepress workflow.
Comparison
| Feature | PDF/X-1a | PDF/X-4 |
|---|---|---|
| Transparency | Flattened | Live |
| Colour | CMYK/Spot | CMYK/RGB/Spot |
| Layers | ||
| Compatibility | Very high | High |
| File size | Can be large | Generally smaller |
Exporting from Adobe InDesign
PDF/X-1a
File → Export → Adobe PDF (Print)
Preset: [PDF/X-1a:2001]
General:
Optimize for Fast Web View
Output:
Color: Convert to Destination
Destination: producer-approved target ICC (ISO Coated v2 only when appropriate)
Advanced:
Fonts: Subset 100% (embedded)PDF/X-4
File → Export → Adobe PDF (Print)
Preset: [PDF/X-4:2010]
General:
Create Acrobat Layers
Output:
Color: No Conversion + correct Output IntentExporting from Adobe Illustrator
File → Save As → Adobe PDF
Preset: PDF/X-1a:2001 or PDF/X-4:2010
Marks and Bleeds:
Trim Marks
Bleeds: product/profile requirement (3 mm is an example)PDF Validation
Adobe Acrobat Pro
Tools → Print Production → Preflight
→ Select PDF/X-1a or PDF/X-4 profile
→ AnalyseOnline Tools
NowToPrint Requirements
| Area | Current guardrail |
|---|---|
| PDF version | Acceptance depends on parser/profile support and measured coverage; a version label alone grants no print readiness. |
| Recommended format | PDF/X-4 |
| Legacy workflow | PDF/X-1a only when the producer requires it; validate flattening and colour conversion at source. |
| Design JSON export | Legacy creator/template/canvas feature flags are disabled. A historical 200-page / 15 MB generation guard is not an enabled export promise. |
| Batch generation | VDP bulk is disabled. Historical 500-row / 5 MB / 50 MB ZIP guards do not activate it. PDF preflight batches have separate document/queue limits. |
| Rust generation contract | Generation budgets are separate from PDF admission; a bounded internal generation contract does not enable a disabled editor or certify PDF/X output. |
| Large-file streaming | Streaming work is engine-safety and future-flow groundwork, not a public blanket upload-size promise. |
| Measured native runtime | Public measured-render claims require a current-source Linux manifest V3 bundle, real native smoke, direct PDFium FFI fuzz, ASan/LSan, and an independently signed isolation receipt. Local verifier tests are not runtime evidence. |
| Browser WASM release | Public browser-engine claims require all six WASM artifacts to share one exact source/provenance identity, source-scope v2, byte hashes, immutable asset versions, committed lineage, and a same-run signed current-HEAD receipt. A local contract test or hand-edited receipt is not release evidence. |
| Real-world corpus | A public corpus claim requires at least 50 distinct, sanitized, hash-only PDF admissions, independent human Ed25519 review, pinned reviewer keys, multiple source programs, and minimum coverage across five print-product classes. Synthetic fixtures and unsigned local review records do not count. |
| External oracle matrix | A public differential-oracle claim requires exact-current-HEAD signed receipts from veraPDF, qpdf/libqpdf, PDFium, and mutool over the same 50+ admitted corpus. Each receipt pins executable, lock, command, runner, result-set, log, and offline read-only execution policy, with zero unclassified false-negative or page-count divergence. A configured tool or green workflow alone is not evidence. |
| Passport report quality | A premium Passport report claim requires an exact-current-HEAD signed child artifact for ar, en, and tr: five pinned HTML/PDF security, visual, tagged-structure, Unicode, and ActualText lanes plus six human receipts across JAWS, NVDA, and VoiceOver on HTML and PDF surfaces. Unit tests, a single screenshot, or unsigned accessibility notes do not count, and this evidence is not PDF/UA certification. |
The release-evidence rows above describe claim gates, not evidence that those gates passed. Browser commercial/book profiles can supply full mapped diagnostic scope; packaging has a baseline with named omissions and unmapped profiles remain unknown. Canonical production decisions require the Rust PreflightReportV2 and a fresh, verified decision receipt bound to source/foundation/profile/registry; a preview, compatibility projection, score or PDF/X declaration is insufficient.
The shared limit profile defines Standard 200 MiB/500 pages and Extended 500 MiB/2000 pages for designated surfaces. The current multi-source workflow additionally caps combined source bytes at 200 MiB even with an extended grant; runtime and transport limits can be narrower than the general tier. Check the actual route and operation before upload. The contract versioning policy is docs/api/PDF_CONTRACT_VERSIONING_2026_TR.md: schema version, API major and private package version are separate identities. Channel contracts do not prove deployed parity or public availability.
PDF/X evidence in PDF Tools is a standards-readiness signal, not third-party certification. The report checks the available metadata, output intent, transparency, colour, font, geometry, and render evidence and routes uncertain jobs for review.
Common Errors
| Error | Consequence | Solution |
|---|---|---|
| Font not embedded | Font substitution | Embed fonts |
| RGB image | Colour shift | Prepare for print at source, or verify the RIP plan |
| Low resolution | Pixelation risk | Use effective PPI required by the chosen print profile |
| Missing bleed | White-edge risk | Supply bleed required by the product/finishing profile |
Previous: ← Resolution | Home: Technical Guides
Was this article helpful?