EPUB FixerKDP upload error scanner

EPUB error guide

Check EPUB after Reedsy export

Use this when you have the EPUB Reedsy exported and want to know whether the final file has a KDP, Kindle Previewer, or EPUBCheck blocker before you edit the book or export again.

You see

The message matches this guide.

Choose this guide when your KDP, Kindle Previewer, or EPUBCheck wording matches "Check EPUB after Reedsy export" or a close variant.

You get

An affected EPUB path and decision.

The report points to the package, OPF, nav, XHTML, resource, anchor, metadata, or ZIP area behind the message.

Do not upload

The issue is outside EPUB structure.

Use the source tool or publishing workflow for DOCX, PDF, KPF, fixed-layout, DRM, cover design, KDP listing, or review problems.

Scan EPUB structureSee an example report

Scan when the message does not name the affected path. The report shows affected paths and repair decisions, not manuscript text.

No signup before the scan report.Checks EPUB package paths, not manuscript text.Repair download only after EPUBCheck passes again.

Need fixed-layout, DRM, or source-file help? Check unsupported or review-first EPUB cases.

Match these report titles

  • Check EPUB after Reedsy export
  • Reedsy EPUB failed KDP upload
  • Reedsy EPUB validation issue
  • Reedsy EPUB TOC, OPF, link, cover, manifest, or ZIP blocker
  • Validate Reedsy EPUB before KDP upload

Use this guide when

Your message matches "Check EPUB after Reedsy export" 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

Decide if this report item matches.

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.

Error textAffected pathDecisionRepair, review, or stop

A useful report does not stop at the error name. It connects the message to an internal file and a next action.

Match the report title.

Look for "Check EPUB after Reedsy export" or the closest title above. Keep the original EPUBCheck, KDP, or Kindle Previewer wording if it differs.

Check the affected file first.

Use the Affected area, Source file, Target file, or Problem type rows before editing OPF, nav, XHTML, CSS, or image paths.

Follow the repair decision.

Repairable means one clear structural change. Needs review or Not supported means use the named file, source project, or platform step.

Keep with your repair note.

Copy these fields from the report instead of rebuilding the fix from memory.

Source file
Target path or field
Original error
Repair decision
Next step

1. Example report output

What a Reedsy export report should show.

A useful report should tell you whether to fix the EPUB package or return to the Reedsy project.

Export checked

The Reedsy .epub output, not the editing project or PDF.

Validation area

OPF metadata, nav.xhtml, toc.ncx, internal links, anchors, images, cover wiring, manifest, media type, container.xml, or ZIP packaging.

Affected path

The internal EPUB file to inspect before another upload or Reedsy export.

Decision

Retry, checked repair, Reedsy source change, manual review, or unsupported by this scanner.

The report should help you decide whether another Reedsy export is needed or whether the current EPUB has one fixable package issue.

2. Next step

Choose upload retry, repair, or Reedsy source change.

Use the scan result to decide whether the problem is in the package Reedsy exported or in the source project.

Retry

The scan does not find a supported blocker.

Continue with Kindle Previewer or KDP upload for platform checks.

Checked repair

One EPUB package issue is clear.

Use repair when OPF, manifest, navigation, media type, cover, path, or ZIP alignment is unambiguous.

Source change

The problem belongs in Reedsy.

Fix missing images, chapter structure, TOC source, or layout choices in Reedsy, then export again.

3. Concrete path example

A Reedsy EPUB can fail because a TOC entry points outside the spine.

The TOC can link to a real file that KDP still does not treat as part of the reading order.

Report:
Source file: OEBPS/nav.xhtml
TOC target: OEBPS/backmatter.xhtml
OPF spine: target not listed
Decision: manual review unless the reading-order role is clear

Adding a file to the spine changes reading order. Do that only when the source book structure makes the intended order clear.

Quick decision

Decide whether this is a Reedsy export structure issue.

Use this for the EPUB package Reedsy exported, not for book editing or publishing account work.

Good fit

You have the Reedsy .epub export.

The scanner can inspect OPF metadata, navigation, internal links, anchors, cover wiring, manifest entries, media types, and ZIP packaging.

Manual fit

The issue touches reading order or missing content.

Use the report path to decide what to fix in Reedsy before exporting again.

Not this tool

You need formatting, PDF, or KDP account help.

Source editing, visual layout, cover design, pricing, categories, and KDP review status are outside this scan.

Start here

Check the Reedsy-exported EPUB before another upload attempt.

Upload the .epub Reedsy exported. The scan checks the package KDP sees, including OPF metadata, nav.xhtml, toc.ncx, internal links, anchors, cover references, manifest entries, and ZIP structure.

Matched

What it means

KDP and EPUBCheck inspect the exported EPUB package, not the Reedsy editor. Metadata, manifest, navigation, resources, anchors, and ZIP files have to agree inside that package.

Matched

Can it be fixed automatically?

A checked repair is possible when the Reedsy export has one clear correction, such as OPF, manifest, media type, navigation, cover-image, path, anchor, or ZIP alignment.

Matched

What to check next

Upload the .epub exported from Reedsy.

Matched

What not to assume

It cannot edit the Reedsy project, choose chapter order, restore missing content, redesign formatting, fix PDF output, manage KDP listings, or decide whether a platform will accept the book.

Common situations

Common Reedsy EPUB export cases.

Start from the Reedsy EPUB you downloaded.

Matched

KDP rejects the Reedsy EPUB.

The upload blocker may be a package issue that is invisible in the Reedsy editor.

Scan the exported EPUB and compare the affected path with the KDP message.

Matched

TOC or navigation behaves differently in Kindle Previewer.

The Reedsy export still has to keep nav.xhtml, toc.ncx, OPF manifest entries, and spine order aligned.

Check navigation evidence before changing chapter headings.

Matched

The internal cover is not recognized.

The cover image file can exist while OPF metadata or the cover-image property is missing or points elsewhere.

Scan cover wiring before replacing artwork.

Reedsy export phrases to check

Check EPUB after Reedsy export: scan the exported Reedsy EPUB for KDP, Kindle Previewer, EPUBCheck, OPF, TOC, nav.xhtml, links, anchors, cover wiring, manifest, media-type, container, and ZIP blockers.

Where Reedsy EPUB blockers usually appear

An author downloads a Reedsy EPUB and wants to validate it before KDP upload, or needs a clearer path after KDP, Kindle Previewer, or EPUBCheck rejects it.

What it means

The exported EPUB can have a strict validation issue even when the manuscript looks finished.

KDP and EPUBCheck inspect the exported EPUB package, not the Reedsy editor. Metadata, manifest, navigation, resources, anchors, and ZIP files have to agree inside that package.

Reedsy export blockers often involve disconnected navigation, TOC targets outside the spine, missing anchors, stale image or stylesheet paths, cover metadata, undeclared manifest items, OPF identifiers, media types, or ZIP packaging.

Before you edit

Check navigation, links, and cover wiring before changing the source project.

A path-level report helps you avoid changing the whole book when the blocker is only an OPF field, nav target, anchor, cover declaration, manifest entry, or ZIP issue.

  1. 1Upload the .epub exported from Reedsy.
  2. 2Keep the Reedsy project available in case the report needs a source change.
  3. 3Check whether the report names OPF, nav.xhtml, toc.ncx, XHTML links, anchors, images, CSS, cover wiring, manifest entries, media types, container.xml, or ZIP packaging.
  4. 4Use checked repair only when one clear structural change is safe and EPUBCheck passes again.
  5. 5Return to Reedsy when the fix depends on chapter order, missing assets, TOC source, or visible formatting.
  6. 6Use KDP or the source workflow for account, listing, pricing, review, paperback, or cover-design tasks.

Why validators check it

Why Reedsy EPUB exports still need validation before upload.

KDP eBook file formats

KDP supports EPUB files that meet Kindle Publishing Guidelines and recommends checking the file with Kindle Previewer before upload.

EPUBCheck

EPUBCheck checks EPUB 2 and EPUB 3 files against the official rules and reports package, markup, link, and file-reference problems.

EPUB 3.3 package rules

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?

When a Reedsy EPUB issue can be repaired here.

When automatic repair is safe

A checked repair is possible when the Reedsy export has one clear correction, such as OPF, manifest, media type, navigation, cover-image, path, anchor, or ZIP alignment.

When you need manual review

It cannot edit the Reedsy project, choose chapter order, restore missing content, redesign formatting, fix PDF output, manage KDP listings, or decide whether a platform will accept the book.

Before / after example

Before: nav.xhtml points to a backmatter file that is not in the spine. After: this may be repairable only if the intended reading order is clear. Before: reading order is ambiguous; fix it in Reedsy and export again.

Ready to retry?

Upload the Reedsy EPUB for a structure scan.

Use the .epub file exported from Reedsy. The report can show whether to retry upload, use a checked repair, inspect a named path, or fix the source and export again.

Upload EPUB to scan

FAQ

Questions authors ask after Reedsy EPUB export.

Can I check a Reedsy EPUB before uploading to KDP?

Yes. Upload the exported .epub file. The report can identify supported package, navigation, OPF, link, cover, manifest, media-type, or ZIP blockers.

Should I fix the EPUB or export again from Reedsy?

Use the report decision. Clear package wiring may be repairable. Missing content, TOC source, chapter order, or visual formatting should be fixed in Reedsy and exported again.

Can this fix Reedsy formatting or PDF problems?

No. EPUB Fixer checks the EPUB package after export. Formatting, PDF output, cover design, and source editing stay in Reedsy or another workflow.

Does this mean KDP upload will pass?

No. It can find and sometimes repair supported EPUB structure blockers. KDP upload, content, listing, review, and account checks remain separate.

Related EPUB error guides