Kindle Upload Errors: Common Formatting Rejections & How to Fix Them (2026)

Nothing deflates launch-day excitement like a red error banner on your KDP dashboard. You uploaded your EPUB or DOCX, clicked Launch Previewer, and instead of your beautifully formatted book, Amazon hands you a cryptic rejection: the file could not be processed, the table of contents is missing, or the cover does not meet requirements. The good news: almost every kindle upload error traces back to a small set of formatting mistakes, each with a precise, repeatable fix. This 2026 guide covers the seven most common formatting rejections on KDP, what each message means, and exactly how to resolve it — and if you have not formatted your manuscript yet, start with our complete guide to formatting a book for Amazon KDP, because a clean source file prevents most of these errors before they exist.

By the end, you will read any KDP error message like a translator, fix problems at the source-file level instead of re-uploading the same broken file, and run a twelve-point pre-upload checklist that catches most issues before Amazon sees them. First, the distinction that changes everything: not every KDP warning is an actual error.

Two Kinds of Kindle Errors: Hard Rejections vs Quality Warnings

KDP shows you two different layers of problems, and authors waste hours treating them the same. The first is upload-time validation: hard failures where the file is rejected outright and you cannot proceed. A corrupt file, an unsupported format, or a cover that violates the rules stops you cold — these are the true blockers.

The second layer is the Online Previewer’s quality panel, opened after your file is accepted: spelling flags, low-quality image warnings, language mismatch alerts, and layout notices. These do not block publishing — KDP offers an “Ignore All” option. But ignoring a warning does not erase it: Amazon’s review team still evaluates your book, and unresolved issues can surface in the Quality Notifications Dashboard, where real readers’ complaints land. Treat hard failures as blockers, and read every warning before you ignore any of them.

Error 1: “Your File Could Not Be Processed”

This is KDP’s bluntest message: Amazon could not read your file at all. The usual cause is a damaged file — an interrupted export, or a manuscript pulled from cloud storage mid-sync. The other cause is an unsupported format: as of 2026, EPUB is the recommended upload, DOCX works with less control, KPF comes from Kindle Create, and MOBI is no longer supported for new uploads. An old MOBI or a password-protected, DRM-restricted file triggers the same dead end.

Fix it at the source: open the file yourself — if Word, Calibre, or Kindle Previewer cannot open it either, the file itself is the problem, not KDP. Re-export from the original manuscript, strip any DRM or password protection, download to local disk instead of uploading from a syncing cloud folder, and prefer a fresh EPUB export. One clean rebuild beats ten identical re-uploads.

Error 2: Missing or Broken Table of Contents

A missing or non-functional table of contents is the single most common reason KDP rejects an eBook. Amazon requires a working, hyperlinked logical TOC: every chapter must be clickable and navigate to the right place. A visible list of chapter titles typed at the front does not count — the underlying navigation map inside the EPUB is what KDP validates. Hand-typed lists, entries linking to the wrong location, and TOCs never rebuilt after chapters were rearranged all fail this check.

The fix starts in your manuscript. Apply true Heading styles (Heading 1, Heading 2) to every chapter title in Word instead of just making the text big and bold, then regenerate the TOC from those styles so links rebuild automatically. In Kindle Create, use the automatic TOC builder. Before uploading, open the file in Kindle Previewer and click every entry on two device profiles — phone and tablet — since navigation bugs often hide on one screen size. Our complete Kindle eBook formatting guide shows the full heading-style workflow.

Error 3: Cover Image Rejections

Cover rejections are brutally specific because Amazon publishes exact numbers: at least 625 x 1000 pixels, with 2560 x 1600 recommended for crisp display on every device. It must be a TIFF or JPEG — and, the detail most authors miss, the cover must be the first element in your eBook file. The classic failures: a cover screenshotted from Word at a few hundred pixels wide, the wrong aspect ratio stretching the art, unreadable title text at thumbnail size, or a uploader cover mismatching the cover inside the manuscript.

Fix it with pixels, not hope. Export your final cover at exactly 2560 x 1600 as a high-quality JPEG, place it as the very first page of the manuscript, and upload that same file through KDP’s cover uploader so both copies match. Then zoom out: check the cover at thumbnail size — how readers actually see it in search results — and confirm the title stays readable. A gorgeous full-size cover that becomes an unreadable smudge at thumbnail size is still a rejection waiting to happen.

Error 4: Font Embedding and Typography Problems

Fonts cause a special KDP headache: the “fonts cannot be embedded” warning. Many commercial fonts carry licensing restrictions that legally prevent embedding, so KDP either strips them or throws an error. Decorative display fonts are the usual suspects — authors fall in love with a swirly script for chapter headings, only to learn its license forbids embedding. The irony: Kindle devices override your font choices with the reader’s preferred typeface anyway, so elaborate typography buys risk without reward.

The fix is restraint. Limit yourself to two font families at most, choosing fonts with embedding-friendly licenses: open-licensed workhorses or standard system fonts. In Word, check a font’s embedding permissions in its properties before committing. If KDP flags a font, replace it rather than fighting the warning — swap the decorative heading font for a clean serif or sans-serif. Readers will never miss the original, and your file sails through validation. Kindle’s job is reflowable reading, not print design: clean, readable typography always wins.

Error 5: Image Quality and File Size Problems

Images trigger two KDP complaints. The first is quality: the Previewer’s image check flags low-resolution pictures that will look blurry on devices — upscaling a tiny web image just makes a bigger blurry image. The second is file size: Amazon enforces a 650MB ceiling, but the practical limit is much lower. Keep your file under 50MB for fast downloads, and because authors on the 70% royalty option pay a per-megabyte delivery fee on every sale. A bloated file literally costs you money per copy.

Fix both with one compression workflow: size every image to its actual display dimensions instead of shrinking giant originals with HTML, compress to a sensible quality level, and strip out unused images. Never upscale a small original — if the source is too small, replace it. A final check with our pre-publish formatting checklist catches the stray 12MB PNG hiding in chapter seven.

Error 6: Reflowable vs Fixed-Layout Mismatch on Revisions

This is the sneakiest error because it only appears on revisions. An author publishes a fixed-layout eBook, later rebuilds it as reflowable (or vice versa), and KDP answers: “This content is a reflowable eBook. Updating a fixed format eBook with a reflowable eBook is not supported.” Once published, your layout type is locked — you cannot switch it with an update, however minor the revision. Authors trip over this by redesigning in Kindle Create without noticing the layout setting changed.

Choose correctly from the start: reflowable layout — text adapting to any screen — suits novels, memoirs, and almost all nonfiction. Fixed layout is only for picture books, cookbooks, comics, and heavily illustrated titles where the design must never change. If you hit the mismatch error, re-export the revision in the original layout. To truly change layouts, unpublish and publish the book fresh as a new edition. Our EPUB vs MOBI vs PDF comparison explains how each format maps to Kindle’s layout options.

Error 7: Metadata and Description Errors

Not every kindle upload error lives in the manuscript — some live in the details form. The classic is “Description may not contain invisible characters” or “Please fix the highlighted issue,” appearing when you paste your book description straight from Word. Word carries hidden formatting and unsupported characters that KDP’s description field rejects, and the same habit breaks bolding, creates phantom line breaks, and leaves unclosed HTML tags scrambling your listing.

The fix is boring and effective: type the description directly into KDP, or paste as plain text first and reapply formatting with only KDP-supported HTML. Then check the other metadata traps: the title and subtitle in your dashboard must match the manuscript’s title page exactly, and confirm you are uploading your latest version — not last month’s draft. Metadata mismatches are the easiest rejections to fix and the most embarrassing to get twice.

Quick-Reference Table: Error, Cause, and Fix

Match the message you see to the likely cause, apply the fix at the source, and re-export once.

The 12-Point Pre-Upload Checklist

Run through this list before every upload — it takes ten minutes and prevents the vast majority of kindle upload errors.

• Clean EPUB (or DOCX/KPF) that opens correctly in Kindle Previewer on your own computer.
• Working table of contents: every chapter clickable, every link landing in the right place.
• Cover is 2560 x 1600 pixels, JPEG or TIFF, and is the first element in the eBook file.
• Cover title text is still readable at thumbnail size, and matches the KDP uploader cover.
• No more than two font families, all with embedding-friendly licenses; no DRM or password protection.
• All images sized to display dimensions and compressed; total file under 50MB.
• Revisions use the same layout (reflowable or fixed) as the originally published file.
• Chapter titles use true Heading styles, not manually enlarged bold text.
• Book description entered as plain text with only KDP-supported HTML; no invisible characters.
• Dashboard title and subtitle match the manuscript’s title page exactly.
• Online Previewer quality panel reviewed on phone and tablet profiles before publishing.
• You are uploading the latest manuscript version — not last month’s draft from a synced folder.

Conclusion: Fix the Source, Not the Symptom

Every kindle upload error in this guide shares one cure: fix the source file, not the upload. A corrupt export, a hand-typed TOC, an undersized cover, a licensed font, a bloated image set, a switched layout, or a pasted-from-Word description — all are formatting decisions made long before KDP sees the file. Read Amazon’s messages, correct the cause in your manuscript, re-export one clean EPUB, and the red banners disappear. Or skip the troubleshooting entirely: hand the formatting to someone who has already made every mistake on this list — so you do not have to.