Ren Hollis

KDP “manuscript has errors”: the generic error, decoded

Short answer: “Manuscript has errors” is a bucket status, not a diagnosis: it means KDP’s checks failed your file on at least one of the 13 standard measured checks — page size, margins, bleed, fonts, page count, file structure — and the status itself never says which. The specifics live in two other places: the Print Previewer’s flags (with page numbers) and, after you publish, the review email. Work the checks in order and you will find it.

Here is the frustrating truth about this message: there is nothing to decode in the message itself. KDP shows the same generic label for a file that failed for one tiny reason and a file that failed for six. The label is the end of a pipeline, not a description of your problem — so stop reading the label and go read the two places where KDP actually itemizes what it found.

What KDP is actually saying

Your file is checked in two passes, and “manuscript has errors” can come from either:

  • Pass 1 — the automated scan. When you upload, the Print Previewer measures the file’s structure: page size against your chosen trim, margins and bleed, page count, embedded fonts, image resolution, cover dimensions. What it catches, it flags with page numbers — and it reads the file’s structure, not its appearance, which is why it can flag a page that looks perfect to you (a hidden text box, one italic word poking past its margin, counts as content in the wrong place).
  • Pass 2 — the human review. After you press Publish, a reviewer checks the files again. Books pass the Previewer and still get blocked here, and the findings arrive as an email listing the issues — sometimes with page references, sometimes with boilerplate you have to interpret.

Underneath the generic label, the actual defects are a known, finite list — the same checks our engines run and the ones this library documents one by one. In rough order of frequency:

The checkWhat it measuresThe guide
Page size ≠ trim sizeEvery PDF page vs the trim you selectedPage size mismatch
Margins / live elementsText inside the required margins for your page countMargin error
Bleed0.125″ past the trim on edge-to-edge pagesBleed error
Fonts embeddedEvery font carrying its embedded fileFonts not embedded
Page count in range24 minimum; maximum by trim, paper, inkPage count limits
Image resolution300 DPI effective, at placed sizeImages below 300 DPI
File structureSingle pages, flattened, unlocked, unencryptedSpreads · Password-protected PDFs

One variant worth separating out: “this file contains errors and cannot be processed” is a level below the generic status — the file couldn’t be read at all (corrupt export, damaged PDF, an exotic producer). That one is never about margins; it’s a broken file, and the fix is always a fresh export from the source document.

Check it yourself

  1. Open the Print Previewer and read every flag. Don’t skim the summary — open each flagged issue and note the page number it names. This is the closest thing to a diagnosis KDP gives you.
  2. Read the review email word for word. If you published and got blocked, the email lists the issues it found. Boilerplate about reviewing “your entire manuscript” means fix the pattern, not just the example page.
  3. Measure the file yourself. Page size in Acrobat (File > Properties), page count, fonts tab (every font should say Embedded). These three checks catch most of the list above in two minutes.
  4. Match file against setup. Trim size, bleed on/off, page count and paper in your title setup must describe the file you actually uploaded — a correct file against wrong setup answers fails exactly like a wrong file.

Want the itemized list instead of the bucket? Send us the actual files: the free check runs all 13 KDP and IngramSpark checks and returns the problems named, measured, and in plain English — free, within 48 hours. Get the free check →

How to fix it

There is no single fix because there is no single error — there is a discipline:

  1. Fix in the source file, never in the PDF. Go back to Word, InDesign, Canva — wherever the book lives — make the change there, and export a brand-new PDF. Patching a finished PDF produces files that pass the scan and print wrong.
  2. Export to a new file; don’t save over the old one. Saving over a previous export can carry corrupted data forward — a known cause of processing failures that survive several “fixes.”
  3. Fix everything flagged, then re-check the whole file. Reviewers sample; a fix that addresses only the example page often bounces on the same defect elsewhere.
  4. Change one thing at a time if you’re hunting. If the flags don’t identify the problem, bisect: upload a file with the suspect half of the book removed and see whether the error survives. Tedious, decisive.

The honest limit

KDP does not publish a definition of this status, and some of its causes are judgment calls made in the human pass — “unsatisfactory customer experience” is a real rejection phrase with no spec behind it. If the Previewer is clean, the email names nothing concrete, and a fresh export still fails, the remaining move is KDP Support (Contact Us in the footer) with your book’s ID and a precise description of what you’ve already checked. What we can promise on our side is narrower and real: the free check verifies your file against every published, measurable spec — if it passes all 13 and KDP still objects, the objection is in the judgment-call territory, not in your file’s measurements.

Or send us the files — the check is free

Email your interior and cover PDFs and we'll tell you exactly what's wrong — in plain English, free, within 48 hours. If it does need fixing, the by-hand fix is $19 and we redo it free if KDP rejects it for a formatting issue we were hired to fix. We rebuild files to be compliant with KDP's published spec — that's the promise we can keep.

Prefer the whole library in one file? The KDP Rejection Field Guide (free PDF) collects every guide, table, and the 13-point checklist.

Get my free rejection check

More from the Help Library