EPUB FixerKDP upload error scanner

EPUB validation explainer

Why an EPUB opens locally but fails KDP.

A reader can open an EPUB while KDP, Kindle Previewer, or EPUBCheck still rejects the file. The difference is usually strict package validation, not whether the chapters are visible on your computer.

Why it happens

Local reading and publishing validation are different checks.

What to do next

Use the failed EPUB to find the strict blocker.

  1. 1

    Save the exact KDP, Kindle Previewer, or EPUBCheck wording before re-exporting.

  2. 2

    Check whether the message names a missing file, anchor, OPF field, manifest item, navigation file, container.xml, or mimetype rule.

  3. 3

    Upload the same exported EPUB when you need the affected path and repairability decision.

  4. 4

    Return to the source tool when the issue depends on missing content, chapter order, fixed-layout design, cover artwork, or visual formatting.

Route the error

Pick the guide that matches the wording you have.

Common questions

Do not treat a local preview as publishing approval.

Does opening in Calibre mean the EPUB is valid?

No. A local reader can be tolerant. KDP, Kindle Previewer, and EPUBCheck are stricter about package paths, metadata, navigation, anchors, manifest entries, and ZIP packaging.

Should I re-export before scanning?

If you still have the EPUB that failed, scan that file first. The report can show whether the problem is a small package fix or a source export issue.

Can EPUB Fixer repair every file that opens locally but fails KDP?

No. It can help when there is one clear structural fix and the repaired EPUB passes EPUBCheck again. Missing content, ambiguous anchors, fixed-layout files, DRM, conversion, and visual formatting still need another workflow.