What is PDF/X-1a? (And why IngramSpark demands it)

By Tracy Atkins, founder of BookDesigner.ai and BookDesignTemplates.com · 15+ years of print files, 70,000+ authors · Updated July 13, 2026

The standard, in one paragraph

PDF/X-1a is defined by the ISO 15930-1 standard. The "X" family of PDF standards exists for one purpose: to make a file that a commercial press can print with no guesswork and no last-minute repair. The "1a" flavor is the most locked-down and the most widely trusted for print, which is why it turns up so often in vendor requirements. It is built on the PDF 1.3 era feature set, deliberately, because that older, simpler feature set behaves the same on nearly every print system in the world.

The four rules it enforces

Each of those rules maps to a real failure that has ruined real books, which is the more useful way to understand them.

What each rule protects against on a real press

Embedded fonts stop font substitution

If a font is only referenced, not embedded, the press system reaches for whatever font it thinks is closest. Line lengths change, letters shift, and in the worst case text renders blank. Embedding puts the actual letterforms inside the file, so the press prints your type, not a stand-in for it. This is the single most common reason a file gets kicked back.

Flattened transparency stops the transparency surprise

Live transparency (a soft shadow behind a title, a semi-transparent overlay) can render one way on your screen and another way through a press RIP. Sometimes a faint box appears around the effect; sometimes the blend shifts. Flattening bakes the final appearance into the file so what you approved is exactly what prints.

CMYK color stops the color shift

Screens show color in RGB; presses lay down CMYK ink. If you hand a press an RGB file, something has to convert it, and that something is not you. Bright screen blues and greens can print duller or shift in hue. By converting to CMYK yourself and declaring an output intent, you decide how the color lands instead of leaving it to chance at the press.

Where IngramSpark and KDP differ

This is the practical heart of it. IngramSpark prints through a large distribution and print network, and it asks for PDF/X-1a (or the closely related PDF/X-3) on covers and prefers conformant interiors. Amazon KDP is more forgiving: it accepts an ordinary, well-made PDF and does much of the conversion on its own end. That difference is why a file can sail through KDP and then get rejected by IngramSpark. It is not that your book is wrong; it is that IngramSpark is checking against a stricter contract.

Why "Save as PDF" is not enough

When Microsoft Word saves a PDF, it produces a general-purpose document. It typically stays in RGB, it can keep live transparency, and it does not declare a print output intent. That file is genuinely fine for email and screen reading, and it may pass at KDP. It simply is not a PDF/X-1a file, and no amount of renaming makes it one.

To produce true PDF/X-1a you need a tool built for it. Adobe Acrobat Pro ships a PDF/X-1a preset that will embed fonts, flatten transparency, convert to CMYK, and write the output intent in one pass. Professional layout and prepress tools export to the standard directly. A generic PDF printer or a browser's "print to PDF" will not, because they are not aware of the conformance rules at all.

How to check what you have

• Open the PDF in Acrobat and look at the document properties for fonts: each should read as embedded or embedded subset.
• Confirm the color mode. If you see RGB anywhere in a file bound for IngramSpark, it is not conformant yet.
• If the tool that made the file never mentioned PDF/X, output intents, or CMYK, assume it did not produce X-1a and convert with a proper preset before you upload.

Source: ISO 15930-1 (PDF/X-1a:2001) and current IngramSpark and Amazon KDP file specifications, as of July 2026. Related: KDP vs IngramSpark: what each wants · IngramSpark cover rejections, decoded · All author guides