Amazon’s KDP rejection emails are famously vague. You get “manuscript does not meet content guidelines” or “file does not meet our specifications” with no page number, no flagged element, no actual reason. You’re left to guess.
IngramSpark is slightly better — they at least mention dimensions or fonts — but their error language is still cryptic enough that a first-time author can stare at it for an hour without understanding what to fix.
This guide decodes every common KDP and IngramSpark rejection message into plain English: what triggered it, what to actually check, and how to fix it.
The big idea: KDP rejects for 5 root causes
Despite the variety of rejection emails Amazon sends, almost every rejection traces back to one of these five issues:
- Embedded font problem (~40% of rejections)
- Trim size or bleed mismatch (~25%)
- Image DPI too low (~15%)
- PDF metadata or version issue (~10%)
- Actual content concern (~10% — rare, usually unique cases)
Once you know which bucket the rejection is in, the fix path is clear. Let’s decode the messages.
KDP rejection messages decoded
“Your file does not meet our specifications”
This is Amazon’s most generic message. It means a technical issue, not a content issue. Almost always one of:
- An embedded font that isn’t properly embedded (see our embedded fonts guide)
- A trim size mismatch between what you selected and what your PDF actually is
- A page that has artwork extending past the safe zone without bleed
Fix path: Run your PDF through BookReady’s free scanner first — it tells you which of these three is the actual cause. Then fix that specific issue and re-upload.
“Manuscript does not meet our content guidelines”
This sounds like a content rejection but in 80% of cases it’s still a formatting issue. KDP’s automated review confused a layout artifact for prohibited content. Most common triggers:
- Strange characters in your file’s metadata (hidden Unicode characters, often pasted from Word)
- A reused ISBN (you accidentally re-submitted with an ISBN already in use)
- A file too similar to one Amazon already has in the catalog (your test upload or a draft)
Fix path: Re-save the PDF from scratch (don’t edit-and-resave). Verify the ISBN. If you’ve previously test-uploaded with the same book, change the title slightly and re-try. If that fails, email KDP support — they almost always release the file after a manual review.
“Cover file dimensions do not match”
This one’s literal. Your cover PDF dimensions don’t match what KDP expects for your selected trim size + page count.
KDP’s expected dimensions are: (2 × trim_width) + spine_width + 2 × bleed, on the width axis; trim_height + 2 × bleed on height.
For a 6x9 paperback with 300 pages on KDP white paper: width = 12 + 0.6750 + 0.25 = 12.925, height = 9 + 0.25 = 9.25.
Fix path: Use KDP’s cover calculator (or BookReady’s) to get the exact dimensions for your book, then re-export the cover at that exact size. Most rejections here are because authors guessed at spine width.
“Interior file does not meet our specifications”
The interior PDF has a technical issue — almost always one of three:
- Trim size doesn’t match what you selected in KDP
- Margins inside the gutter are too tight (must be at least 0.375” for paperback)
- Page count doesn’t match the spine
Fix path: Re-check the trim size by opening File → Properties in Acrobat. Compare to the trim size you selected in KDP. If they don’t match, re-export at the right size. Then check your gutter margin.
“Bleed area does not match”
The bleed in your interior or cover PDF is missing, partial, or too large.
KDP expects bleed = 0.125 inches on any side where artwork extends to the edge. Cover always needs bleed on all four sides; interior only needs it on pages with full-bleed images.
Fix path: Re-export from your source file with bleed enabled in the export settings. Don’t try to fix this in the PDF.
“The image resolution does not meet our specifications”
At least one image in your interior or cover is under 300 DPI at print size. KDP requires 300 DPI minimum.
Fix path: Find the offending image (BookReady’s scanner tells you which page it’s on). Replace it with a higher-resolution version. If you only have the low-res file, you’ll need to commission new artwork or re-shoot the photo — no software can truly upscale beyond what’s there.
“File cannot be opened or contains errors”
Your PDF is corrupted, password-protected, or in a version Amazon’s parser can’t read.
Fix path: Re-export from the source file. Don’t use “Print to PDF” — that often produces files Amazon can’t parse. Use a real export function (Affinity Publisher’s PDF/X-1a is the gold standard).
IngramSpark rejection messages decoded
IngramSpark uses slightly different language and is generally more specific.
“The trim size of the file does not match the trim size of the title”
Same as KDP’s interior file rejection. Your PDF trim doesn’t match what you selected in the title setup.
Fix path: Re-export at the correct trim. Don’t try to fix in PDF — re-export from source.
“Fonts are not embedded”
One or more fonts in your PDF are referenced but not embedded. The most common Ingram rejection.
Fix path: Check via Acrobat → File → Properties → Fonts. Every font must say “Embedded” or “Embedded Subset.” If any don’t, replace those fonts with embed-friendly equivalents (Cardo, EB Garamond, Source Sans Pro all embed cleanly and are free).
“Bleed area is missing or insufficient”
Your bleed is less than 0.125” on at least one edge. IngramSpark is stricter than KDP about this — they reject for partial bleed where KDP might not.
Fix path: Re-export with bleed set to exactly 0.125” on all four sides. Verify in BookReady’s scanner before re-uploading.
“The color space is not CMYK”
IngramSpark only accepts CMYK PDFs for print interiors and covers. KDP also prefers CMYK but is more lenient. If your file is RGB, IngramSpark rejects.
Fix path: In your design tool, change the document color profile to CMYK before exporting. In Photoshop: Image → Mode → CMYK Color. In Affinity: Document → Convert Format. Then re-export. For Word users, this requires a separate conversion step in a real layout tool.
“Image resolution is below 300 DPI”
Same root cause as KDP’s image rejection. At least one image is too low-res.
Fix path: Find and replace the offending image. The scanner tells you which page.
“The cover spine width does not match the page count”
You uploaded a wraparound cover, but the spine width in your design doesn’t match what IngramSpark calculates for your book’s page count + paper type.
Fix path: Use IngramSpark’s spine calculator (or BookReady’s) and re-design the cover with the correct spine width. This usually means resizing the back cover and re-positioning spine text.
“PDF version is not supported”
IngramSpark requires PDF version 1.3 to 1.7. PDF 2.0 (the newest) is not yet supported on their side.
Fix path: Re-export with PDF 1.4 or 1.5 selected (in Affinity: Export → PDF → Compatibility → PDF 1.4). This is the most overlooked Ingram-specific issue.
Common fixes that solve most rejections
If you only have time to do a few things, these solve about 85% of all rejections across both platforms:
- Re-export your PDF using PDF/X-1a:2003 as the preset. This single setting forces font embedding, CMYK color, proper bleed handling, and a supported PDF version.
- Verify trim size in Acrobat’s File → Properties. It should exactly match what you selected at upload.
- Run the file through BookReady’s free scanner before uploading. Catches the top 5 rejection causes in under 30 seconds, with the actual page numbers.
- Use embedded-friendly fonts. Cardo, EB Garamond, Lato, Source Sans Pro all embed cleanly and are free. Avoid free downloaded fonts of unknown license — those are the most common embed failures.
- Don’t edit and re-save the rejected PDF. Open your source file (Word, Affinity, InDesign) and re-export. Editing the PDF directly usually adds more issues than it fixes.
When to email KDP / Ingram support directly
If you’ve fixed the technical issue and re-uploaded, and the file is still rejected with the same vague message, it’s usually a stuck record on their side. Email support with:
- Your KDP or Ingram order ID
- The exact rejection message you received
- A short description of what you changed
- A statement that the file passed BookReady’s pre-flight check (or whatever scanner you used)
Support usually releases the file within 24-48 hours.
Final thoughts
KDP and IngramSpark reject for boring, technical reasons 95% of the time. Bleed. Fonts. DPI. Trim size. None of them are about your writing.
The fastest way to never see another rejection email is to run your PDF through a checker that catches all five common issues before you upload. Ten seconds of scanning saves three days of re-submission cycles.
Catch it before they do. BookReady’s PDF scanner is free at bookready.net.
FAQs
Q: KDP rejected my file once but accepted it the second time without me changing anything. Why?
A: Their automated review pipeline occasionally false-positives. If you suspect this, re-upload exactly the same file — about 30% of the time it goes through. If it rejects again, the issue is real.
Q: Why does IngramSpark accept a file KDP rejected (or vice versa)?
A: Their review pipelines have different sensitivity thresholds. Ingram is stricter on bleed and CMYK; KDP is stricter on trim-size matching. A file can pass one and fail the other.
Q: Can I appeal a content-guidelines rejection?
A: Yes. Email KDP support with the rejection notice, your book details, and a statement explaining why the rejection is a misclassification (often it is — the automated content review false-positives on certain words or formatting). They usually respond within 5 business days.
Q: What if my book has nudity, profanity, or violence — will it be rejected?
A: Not automatically. KDP allows adult content if properly marked as such during upload. The rejection only triggers when content guidelines are actually violated (CSAM, hate speech, illegal content). For everything else, mark the book as 18+ during setup and you should be fine.
Q: Does BookReady’s scanner check for content issues?
A: No — only technical issues. Content rejections are rare (under 10% of all rejections) and the scanner can’t predict what KDP’s content algorithm will flag. The scanner catches the technical 90%.