Match the report title.
Look for "Fix EPUB for Kindle upload" or the closest title above. Keep the original EPUBCheck, KDP, or Kindle Previewer wording if it differs.
EPUB error guide
Upload the EPUB that Kindle Previewer or KDP rejected. The report finds the affected path and offers a checked repair when one safe EPUB structure fix passes EPUBCheck again.
You see
Upload the same reflowable .epub when Kindle Previewer or KDP reports a validation, conversion, TOC, link, metadata, or package problem.
You get
The report names the affected path and separates a checked structural repair from manual review or a Kindle workflow issue.
Not covered
Send to Kindle conversion, KPF/KCB creation, account, listing, pricing, DRM, and final acceptance stay outside this EPUB structure scan.
Scan when the message does not name the affected path. The report shows affected paths and repair decisions, not manuscript text.
Need fixed-layout, DRM, or source-file help? Check unsupported or review-first EPUB cases.
Match these report titles
Use this guide when
Your message matches "Fix EPUB for Kindle upload" or one of the report titles above.
Upload if
You have the exported reflowable .epub and need the affected path, file, field, or repair decision before editing.
Handle outside this tool
Use the source tool or publishing workflow for DOCX, PDF, KPF, KCB, fixed-layout, comics, image-first books, DRM, visual design, or KDP listing and approval problems.
Read the scan report
Use the report label, affected file, and repair decision together. A matching title alone is not enough if the file path or EPUB structure points to a different problem.
A useful report does not stop at the error name. It connects the message to an internal file and a next action.
Look for "Fix EPUB for Kindle upload" or the closest title above. Keep the original EPUBCheck, KDP, or Kindle Previewer wording if it differs.
Use the Affected area, Source file, Target file, or Problem type rows before editing OPF, nav, XHTML, CSS, or image paths.
Repairable means one clear structural change. Needs review or Not supported means use the named file, source project, or platform step.
Copy these fields from the report instead of rebuilding the fix from memory.
1. Example report output
A useful report should map the Kindle message to one EPUB package area and one next action.
Kindle-facing file
The final .epub manuscript file, not the DOCX, PDF, KPF, or KCB source.
Navigation layer
nav.xhtml, toc.ncx, OPF manifest, and spine wiring for Kindle table of contents behavior.
Reference layer
Chapter XHTML, CSS, images, anchors, and internal links that Kindle Previewer may validate strictly.
Package layer
content.opf, manifest entries, media types, cover-image property, container.xml, and ZIP wrapper.
Decision
Retry-ready, checked repair, manual review, or outside EPUB Fixer scope.
The report should tell you where to look before you open Kindle Previewer again.
2. Next step
The scan result should decide whether you retry, repair, or return to the source export.
Retry upload
Use Kindle Previewer and KDP's upload screen as the final checks for the platform workflow.
Repair package
Use checked repair when OPF, manifest, media type, navigation, cover property, path, or ZIP wrapper data can be aligned safely.
Fix source
Use the source tool when the report points to missing content, no reliable TOC, ambiguous anchors, or layout-sensitive fixes.
3. Concrete path example
Kindle tools can care about navigation files even when the chapters open.
Before Kindle upload: Previewer target file: final.epub Report: Navigation file: OEBPS/nav.xhtml Legacy NCX: OEBPS/toc.ncx OPF spine toc: points to old-toc Decision: manual review if nav and NCX disagree; checked repair only when one intended navigation target is clear
Do not delete nav.xhtml or toc.ncx just because one looks older. Check how the OPF manifest and spine connect them first.
Quick decision
This path is for a finished EPUB manuscript. Kindle device import, Send to Kindle conversion, KDP account, listing, DRM, pricing, review, and approval tasks stay outside it.
Good fit
The scanner can inspect the package parts that Kindle Previewer and EPUBCheck usually complain about.
Manual fit
Use the report as a checklist, then decide the final TOC, spine, anchor, or missing-content fix in the source workflow.
Not this tool
KDP account setup, listing metadata, cover upload, pricing, DRM, review status, and content policy need the Kindle or KDP workflow.
Start here
Upload the same EPUB that Kindle Previewer or KDP will inspect. The report shows whether the error is a clear package problem that can be checked after repair or a source and platform workflow issue.
A Kindle upload uses the finished EPUB package. The visible book can look fine while OPF metadata, navigation, links, resources, cover wiring, or ZIP packaging still disagree.
A checked repair is possible when one package correction is clear and can be validated again, such as OPF manifest, navigation declaration, media type, cover-image property, path, anchor, or ZIP wrapper alignment.
Use the same .epub file you would send to Kindle Previewer or KDP.
It does not repair personal Kindle or Send to Kindle device import, create KPF files, choose DRM, approve listing metadata, fix pricing, judge content policy, redesign the book, or decide whether Kindle accepts the upload.
Common situations
Start with the exact Kindle or KDP message and the EPUB file it names.
A targeted repair may be safer when the exported EPUB has one clear package blocker.
Scan the EPUB first and use the affected path as your Previewer checklist.
TOC failures often involve nav.xhtml, toc.ncx, OPF manifest, and spine wiring rather than visible chapter headings alone.
Check navigation wiring before rebuilding the book.
Manual EPUB edits can leave stale resource paths or anchors that strict validators reject.
Use the scan to trace source file and target path before retrying.
The Kindle manuscript cover depends on OPF cover metadata, manifest item, cover-image property, and the packaged image file.
Scan cover wiring; handle KDP marketing cover upload separately.
Fix EPUB for Kindle or KDP upload: scan OPF, nav.xhtml, toc.ncx, links, anchors, cover wiring, manifest, media type, container.xml, and ZIP package structure before retrying.
An author, formatter, or small publisher wants to fix a Kindle or KDP upload error in the exported EPUB before retrying Kindle Previewer or KDP.
What it means
A Kindle upload uses the finished EPUB package. The visible book can look fine while OPF metadata, navigation, links, resources, cover wiring, or ZIP packaging still disagree.
Common causes include disconnected nav.xhtml or toc.ncx, stale OPF spine references, missing resources, missing anchors, wrong media types, cover metadata mismatches, missing manifest entries, container.xml path mistakes, and bad ZIP packaging.
Before you edit
When the EPUB is already exported, the fastest useful check is usually OPF, nav.xhtml, toc.ncx, links, anchors, images, manifest entries, cover wiring, and ZIP packaging.
Why Kindle tools check it
KDP supports EPUB files that meet Kindle Publishing Guidelines and recommends checking the file with Kindle Previewer before upload.
EPUBCheck checks EPUB 2 and EPUB 3 files against the official rules and reports package, markup, link, and file-reference problems.
The OPF file is the EPUB's map: metadata, file list, reading order, and navigation wiring. KDP and EPUBCheck use it to decide whether the book package is coherent.
Can this be fixed safely?
A checked repair is possible when one package correction is clear and can be validated again, such as OPF manifest, navigation declaration, media type, cover-image property, path, anchor, or ZIP wrapper alignment.
It does not repair personal Kindle or Send to Kindle device import, create KPF files, choose DRM, approve listing metadata, fix pricing, judge content policy, redesign the book, or decide whether Kindle accepts the upload.
Before: the OPF spine points to an old NCX id or the manifest misses the navigation property. After: align the wiring only when the intended navigation file is clear and EPUBCheck passes again.
Ready to retry?
Upload the file you would send through Kindle Previewer or KDP. The report tells you whether a supported structural repair is possible and checks the repaired EPUB again before download.
Upload EPUB to scanFAQ
Sometimes. If Kindle or KDP is rejecting a supported EPUB structure problem, the report can offer a checked repair after the repaired file passes EPUBCheck again. Device import, Send to Kindle conversion, KPF/KCB, layout, account, and listing problems need another workflow.
Check the final EPUB package: OPF metadata, manifest, spine, nav.xhtml, toc.ncx, links, anchors, images, cover wiring, container.xml, and ZIP packaging. EPUB Fixer reports affected paths and a next-step decision.
For this page, Kindle upload means the EPUB manuscript file going through Kindle Previewer or KDP. Account, listing, pricing, and review workflow are separate from the EPUB structure check.
Only when Previewer fails because of a supported EPUB structure issue. KPF creation, visual layout, complex conversion, fixed-layout books, and source formatting still belong in the Kindle or source workflow.
No. Upload a real .epub file here. KPF, KCB, DOCX, PDF, and source projects are outside this scanner.