PDF/X Explained: The Print Industry Standard for Reliable Output

If you have ever sent a PDF to a commercial printer and received a frantic email about missing fonts, low-resolution images, or the wrong color space, you have already met the problem PDF/X was created to solve. PDF/X is a family of ISO standards that strips away every variable that could surprise a printing press and turns a PDF into a reliable, self-contained print-ready file.

This guide walks through what PDF/X is, the most common flavors you will encounter, and when you should actually use it.

What PDF/X is, and what it is not

PDF/X is not a different file format. A PDF/X file is still a regular PDF that opens in any reader. The "/X" suffix simply means the file complies with a strict subset of the PDF specification designed for print production. Think of it as a checklist: certain features are required (embedded fonts, defined color spaces, output intent), and others are forbidden (transparency in older variants, JavaScript, audio, video, encryption).

A file that passes PDF/X validation is guaranteed to render the same way on any compliant device, which is exactly what a printer needs when the alternative is a phone call at midnight asking which font you meant.

The most common PDF/X variants

ISO has published several versions over the years. The ones you will actually encounter in 2026 are:

• PDF/X-1a, The oldest widely-used variant, based on PDF 1.3. CMYK and spot colors only, no transparency, no layers. Still demanded by some traditional offset shops.
• PDF/X-3, Adds support for color-managed RGB and Lab through ICC profiles. Useful when your printer can manage color conversion on their side.
• PDF/X-4, Based on PDF 1.6. Allows live transparency and layers, which is enormous for modern designers. This is the default request from most reasonable commercial printers today.
• PDF/X-5, Extensions of PDF/X-4 for partial files (referenced external graphics or color profiles).
• PDF/X-6, The newest variant, based on PDF 2.0, with cleaner handling of color and metadata.

If a printer simply says "send a PDF/X", and you are not sure which one, ask. The answer is almost always PDF/X-4 in 2026.

What PDF/X actually requires

Every PDF/X file must satisfy roughly the same core rules:

1. All fonts are embedded. No exceptions. If the press cannot find the font, layout breaks.
2. All images are within a defined color space. That usually means CMYK, but PDF/X-3 and later allow ICC-tagged RGB or Lab.
3. An output intent is declared. This is an ICC profile that says, in effect, "this file was designed to be printed on this kind of paper with this kind of ink." It is the difference between a Sunday newspaper and a luxury magazine.
4. No encryption. A press needs to read every object directly.
5. No interactive content. Forms, JavaScript, audio, and video are all stripped or forbidden.
6. Trim box, bleed box, and media box are defined. The press needs to know where the page ends, where the bleed goes, and where to trim.

For more on color spaces in PDF, see CMYK vs RGB in PDF and color management in PDF.

How to create a PDF/X file

Most professional design tools can export directly to PDF/X. In Adobe InDesign, choose File → Export → PDF (Print) and pick a PDF/X preset such as "PDF/X-4:2008". In Affinity Publisher, the same option appears in the export dialog. In Microsoft Word, you cannot export PDF/X directly, you need a post-processing step using Acrobat Pro, Ghostscript, or callas pdfToolbox.

A typical Ghostscript command to convert a regular PDF into a PDF/X-4 file looks like this:

gs -dPDFX -dBATCH -dNOPAUSE -sDEVICE=pdfwrite \
   -sColorConversionStrategy=CMYK \
   -dPDFSETTINGS=/prepress \
   -sOutputFile=output_x4.pdf input.pdf

You usually need to supply a PDF/X definition file that declares the output intent. Most printers can email one over for the press and stock you are using. For an overview of the broader Ghostscript ecosystem, see our Ghostscript introduction.

Validating a PDF/X file

Saying a file is PDF/X does not make it so. Run a preflight check before you send anything to the press. Common tools:

• Adobe Acrobat Pro, built-in preflight profiles for every PDF/X version.
• callas pdfToolbox, the industry-standard preflight engine, used inside many printers' own workflows.
• veraPDF, open-source validator for PDF/A and PDF/X.

A clean preflight report saves you from the late-night reprint email.

When you actually need PDF/X

If you are uploading a flyer to an online print-on-demand service, the answer is usually nothing special, they accept a normal PDF and convert it themselves. PDF/X matters when:

• You are working with a commercial offset, flexo, or large-format printer.
• The job is brand-critical and color has to match a sample.
• You are exchanging files between agencies and pre-press houses.
• The stock or process requires a specific output intent (newsprint, uncoated, coated, packaging).

For everyday office printing, like printing a contract you just signed at Docento.app, a regular PDF is perfect. PDF/X exists for situations where "looks fine in Acrobat" is not a strong enough guarantee.

Common gotchas

• Spot colors not converted. If your design uses a Pantone swatch but you export to PDF/X-1a with CMYK only, the spot may get flattened to a process build that looks dull. Either keep the spot or pick a closer Pantone Bridge equivalent.
• Mismatched output intent. Sending a file tagged for "Coated FOGRA39" to a shop running an uncoated job will give muddy results.
• Hidden transparency in PDF/X-1a. Older versions do not allow live transparency. Your design tool will flatten it on export, which can sometimes produce visible artifacts.
• Bleed missing. If your design ends exactly at the trim, any tiny misregistration will show a white edge. Add at least 3 mm of bleed.

Takeaway

PDF/X is a contract between you and the press. It removes ambiguity by demanding embedded fonts, defined colors, and clean structure, so the file you send is the file that prints. For most modern jobs you want PDF/X-4. Validate before you send, talk to your printer about output intent, and the rest of the workflow becomes boring, which, when you are paying for a print run, is exactly what you want.