KDP File Rejection Reasons: Diagnose the Stage and Fix the Source File
KDP file problems happen at different stages.
KDP file problems fall into several different stages: the file can fail to upload or convert, Print Previewer can block submission, Amazon’s review can flag formatting or content quality, or a book can go live and later receive a quality notification. Calling all of these a ‘file rejection’ hides the fastest route to the fix.
Start by identifying which stage failed and whether the problem belongs to the interior, cover, metadata, or content itself. Then fix the source file rather than repeatedly exporting the same broken version.
Ebook Problems: Use the Supported Formats and Preview the Conversion
KDP currently supports several ebook manuscript formats, including DOC/DOCX, KPF, and EPUB. EPUB must meet Kindle publishing specifications, while Kindle Create can produce KPF and EPUB for supported reflowable workflows. MOBI guidance in old tutorials is increasingly obsolete and should not be your default production route.
If conversion fails, first open the source in its native application, save a fresh copy, and test again in Kindle Previewer. Complex Word formatting, broken styles, unsupported layout techniques, bad image placement, and malformed EPUB structure are common causes of conversion trouble.
Broken Navigation and TOC Errors
Kindle books need working logical navigation. Manually typed page-number TOCs, fake headings, stale chapter links, and malformed EPUB navigation can create a book that opens but fails quality review or produces a poor customer experience.
Fix the heading hierarchy and regenerate the navigation from the source. Then test both the Go To menu and any visible HTML TOC in Kindle Previewer before re-uploading.
Print Interior Errors: Margins, Bleed, Fonts, and Page Geometry
Print Previewer automatically checks issues such as margins, cover size, and fonts. Bleed is one of the most common causes of print-review problems. If interior elements extend to the page edge, KDP requires the manuscript to be uploaded as PDF with the correct bleed dimensions.
Print Previewer may attempt to scale or reflow some content, but do not rely on automatic correction for a production book. Fix margins, trim size, bleed, and page geometry in the source application, create a fresh PDF, and upload that version.
Font Errors Can Hide in Places You Cannot See
KDP can reject print files when fonts cannot be printed successfully. Font problems may sit in visible text, spaces, punctuation, headers, footers, line breaks, or style definitions. Faux bold or faux italic styling can also create failures when the actual font face is missing.
Embed fonts correctly and use font families with real bold and italic variants where the design calls for them. If Previewer identifies a font error, inspect document styles as well as visible pages before exporting again.
Cover File Problems
Print covers fail when dimensions, spine width, bleed, barcode area, image quality, or fonts do not match the final book specifications. The full wraparound depends on trim size, page count, paper, and format, so a cover built before the interior is final can become wrong even without a design change.
Use KDP’s Cover Calculator/template for the final specification and export a new cover from the original design file. Do not stretch an old PDF to fit a new spine width.
Files Can Pass Upload and Still Fail Quality Review
KDP’s Kindle quality guidance includes typos, blurry images, unsupported formatting, inline page numbering, forced text colors, unreadable scans, and wrong content among the issues that can trigger action. A technically valid file is not automatically a high-quality ebook.
Wrong-content problems are particularly serious because the customer receives something different from what the listing promises. Before every upload, open the exact file and confirm title, edition, front matter, manuscript version, and cover belong together.
Some ‘File’ Problems Are Actually Content or Metadata Problems
A manuscript can be structurally perfect and still be rejected because of rights, misleading metadata, prohibited content, public-domain rules, AI disclosure, or a product that is unsuitable for Kindle reading. Do not keep rebuilding the PDF when Amazon’s message points to a content-policy issue.
Read the notification literally and follow the linked policy. If the reason remains unclear, contact KDP support with the exact message and title details rather than guessing which technical setting caused it.
A Faster Rejection-Repair Workflow
Save the rejection message, identify the affected format, reproduce the problem in Previewer where possible, and return to the source project. Fix one category of error at a time and name the new export clearly so you do not upload yesterday’s rejected file again.
After the fix, run the entire preview rather than checking only the reported page. Margin, style, font, or conversion errors often repeat throughout a manuscript even when the tool shows one example.
Read the Rejection Message for the Noun, Not the Tone
KDP notifications can sound generic, but the important words usually identify the layer: margin, bleed, font, cover, metadata, rights, quality, navigation, wrong content, or unsupported formatting. Copy the exact wording into your repair notes before changing anything.
If the message includes page numbers, inspect those pages and several nearby examples. A single flagged page can be the first place an automated check detected a document-wide style or margin problem.
Version Control Prevents Repeat Rejections
Many resubmission failures are versioning failures rather than formatting failures. The author fixes the manuscript, exports a new PDF, then uploads the old file from Downloads because both are called final.pdf. The technical problem was solved, but the rejected file returned.
Use deliberate filenames such as book-title-print-v7-bleed-fixed.pdf and archive superseded versions. Keep the editable source, exported file, cover, and upload notes together so the next update begins from the known published version.
A five-minute rejection check
- Confirm you edited the source file that produced the rejected upload
- Export to a new clearly named file
- Open that exact file from start to finish
- Run Kindle Previewer or Print Previewer as appropriate
- Check the cover against the final interior page count
- Upload the new file and keep the rejection message until the title is approved
Frequently Asked Questions
What ebook file types does KDP accept?
KDP currently supports multiple formats including DOC/DOCX, KPF, and EPUB. Use the current supported-formats page for the full list.
Should I still upload MOBI?
MOBI is no longer the normal recommended KDP production format. Use current DOCX, KPF, or EPUB workflows instead.
Why does Print Previewer reject my interior?
Common causes include margins, bleed, fonts, page geometry, and elements outside the printable area.
Does a print book with bleed have to be PDF?
Yes. KDP currently requires PDF when interior content bleeds to the page edge.
Can a technically valid ebook still have a quality problem?
Yes. Typos, unreadable scans, broken navigation, poor images, forced formatting, and wrong content can still trigger quality action.
Should I fix the PDF directly?
Usually fix the original Word, layout, or cover project, then create a fresh export. That preserves a reliable source for future updates.
Fix the Source of the Error, Not Just the Error Message
KDP’s tools usually tell you which layer is failing. Once you stop treating every problem as a generic rejection, the path from notification to clean resubmission becomes much shorter.
