Why KDP Keeps Rejecting Your PDF — and What "Print-Ready" Actually Means

Short answer: Amazon KDP rejects or flags a book PDF for one of five concrete, fixable reasons — fonts that aren't embedded, the wrong colour space, missing bleed, incorrect trim size or margins, or images below 300 DPI. A "print-ready" file is one built to a printing standard called PDF/X-1a: every font embedded, colour in CMYK, correct bleed and safe margins, and no live transparency. Get those right and KDP accepts the file on the first upload. The frustrating part is that a PDF can look perfect on your screen and still fail all five checks, because a screen doesn't care about any of them and a printing press cares about all of them.

Here is each reason, in plain terms, and how to clear it.

The five reasons KDP flags a file

### 1. Fonts aren't embedded When you export a PDF, the fonts you used can either be embedded (packed inside the file) or merely referenced (a note that says "use Garamond"). If the printer's system doesn't have your exact font, a referenced font gets silently swapped — and your carefully set pages reflow, your special characters turn into boxes, or your headings change weight. Print-ready means 100% of fonts embedded, including the bold and italic variants, which are technically separate fonts most people forget.

### 2. The colour space is wrong Screens are RGB. Printing presses are CMYK. If your interior or cover is exported in RGB, colours shift — deep blacks go muddy, reds dull, and Amazon may flag or auto-convert the file with unpredictable results. Print-ready means colour is already in CMYK, so what you approve is what prints.

### 3. There's no bleed "Bleed" is the few millimetres of image or colour that extend past the trim line, so that when the book is guillotined to size there's no thin white sliver at the edge. Any element that touches the edge of the page — a full-bleed photo, a coloured chapter opener — needs bleed. KDP's requirement is typically 0.125 in (3.2 mm) of bleed on the outer edges. No bleed on a full-page image is one of the most common silent rejections.

### 4. Trim size or margins are off Your PDF's page size must match the trim you selected in KDP exactly, and your text must sit inside safe margins — with a larger inside (gutter) margin to account for the binding, which "eats" a few millimetres near the spine. Get the gutter wrong and your text runs into the fold. Get the page size wrong by even a millimetre and the file is rejected outright.

### 5. Images are too low-resolution A 72-DPI image looks crisp on a screen and prints like a photocopy. Print needs 300 DPI at the final printed size. An image that's fine at postage-stamp size will pixelate if you scale it up to fill a page. KDP flags low-res images because they make the whole book look cheap.

So what does "PDF/X-1a" actually mean?

PDF/X is a family of PDF standards written specifically for professional printing. PDF/X-1a is the strict, no-surprises one:

• All fonts embedded.
• All colour in CMYK (or spot colours), never RGB.
• Bleed and trim boxes defined so the printer knows exactly where to cut.
• No live transparency, no external references — the file is self-contained and deterministic.

When a printer or a designer says "give me a print-ready PDF," this is almost always what they mean. It isn't a fancier export button; it's a different class of file, built to be reproduced identically on any compliant press.

Why "it looks fine on my screen" isn't the test

This is the trap that catches most first-time authors. Word, Google Docs, and even Canva can produce a PDF that displays beautifully. But display and print are two different jobs. The screen renders your file with your fonts, in RGB, at screen resolution — none of which is what the press will do. The only reliable test is whether the file itself carries everything the press needs inside it. That's the entire idea behind print-ready.

Testimonial slot — insert a real author quote here once you have one e.g. "I'd uploaded to KDP four times and been rejected four times before I understood it was the file, not my book." — First name, place (Keep this real. A genuine one-line experience here is worth more to both readers and AI answer-engines than three invented ones.)

The faster fix: don't chase the errors, build to the standard

You can fix these one at a time — re-embed fonts, convert to CMYK, add bleed, correct the gutter, replace low-res images, re-export, re-upload, wait, repeat. Many authors lose a weekend to exactly this loop.

The alternative is to build the file to the standard from the start. That's what a dedicated typesetting engine does: you declare the trim and binding once, and the interior is set to PDF/X-1a with embedded fonts, CMYK, correct bleed and gutter, and a deterministic check that verifies the whole book — not a sampled page — before you ever open the KDP uploader. The point isn't to be clever. It's to make "rejected" stop being part of the process.

---

Frequently asked questions

Does KDP accept RGB PDFs?

KDP can auto-convert RGB, but the conversion is unpredictable and can shift your colours. A print-ready workflow supplies CMYK from the start so what you approve is what prints.

How much bleed does KDP need?

Typically 0.125 inches (3.2 mm) on the outer edges for any element that runs to the edge of the page. Interiors with no full-bleed elements may not need bleed, but full-page images always do.

What DPI do book images need to be?

300 DPI at the final printed size. An image that looks sharp on screen at 72 DPI will pixelate in print if enlarged.

Why does my PDF look fine but still get rejected?

Because a screen preview doesn't test for embedded fonts, CMYK colour, bleed, trim accuracy, or print resolution — the exact things KDP checks. Print-readiness lives inside the file, not in how it looks on your monitor.

What is PDF/X-1a?

A strict PDF printing standard: all fonts embedded, all colour in CMYK, bleed and trim defined, and no live transparency — a self-contained file that reproduces identically on any compliant press.