EPUB FixerKDP upload error scanner

EPUB error guide

Check EPUB after Scrivener export

Scan a Scrivener-compiled EPUB to check generated chapters, anchors, front matter, TOC targets, OPF metadata, manifest entries, cover wiring, and ZIP packaging.

You see

The message matches this guide.

Choose this guide when your KDP, Kindle Previewer, or EPUBCheck wording matches "Check EPUB after Scrivener 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 Scrivener export
  • Scrivener EPUB failed KDP upload
  • Scrivener EPUB validation issue
  • Scrivener EPUB TOC, anchor, link, OPF, manifest, or ZIP blocker
  • Validate Scrivener EPUB before Kindle upload

Use this guide when

Your message matches "Check EPUB after Scrivener 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 Scrivener 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 Scrivener export report should show.

A useful report should connect the validation problem to the generated file Scrivener produced.

Compile output

The Scrivener-generated .epub file.

Generated files

Chapter XHTML, front/back matter, nav.xhtml, toc.ncx, content.opf, images, CSS, and ZIP entries.

Common blocker

Missing generated anchor, broken TOC target, spine mismatch, missing resource, OPF metadata, manifest, or ZIP packaging.

Decision

Checked repair, Scrivener compile fix, manual review, unsupported, or no supported blocker found.

The report should tell you whether one generated EPUB path is wrong or whether Scrivener compile settings need the fix.

2. Next step

Choose package repair or Scrivener compile fix.

Scrivener issues often depend on whether the generated structure already shows the intended book order.

Inspect

Use the generated path from the report.

Start with the named XHTML, nav, NCX, OPF, CSS, image, anchor, or ZIP path.

Checked repair

One package target is clear.

Repair may be safe for path case, manifest, media type, OPF identifier, navigation declaration, anchor, or ZIP wrapper alignment.

Compile fix

The book structure is wrong or incomplete.

Return to the Scrivener source when manual decisions about compile settings, chapter order, front matter, notes, or missing assets decide the right output.

3. Concrete path example

A Scrivener EPUB can fail because a TOC link points to a generated id that does not exist.

Compile settings can change generated anchors between exports.

Report:
Source file: OEBPS/nav.xhtml
Target file: OEBPS/body/chapter-04.xhtml
Missing anchor: #doc5
Candidate anchors: chapter-4
Decision: manual review unless one candidate is clearly the same chapter target

If generated ids keep changing between compiles, adjust Scrivener compile settings or headings instead of hand-patching every export.

Quick decision

Decide whether this is a Scrivener compile structure issue.

Use this for the compiled EPUB file. It does not edit the Scrivener project or choose compile settings.

Good fit

You have a compiled reflowable EPUB.

The scanner can inspect generated chapter files, navigation, OPF metadata, links, anchors, images, CSS, manifest entries, and ZIP packaging.

Manual fit

The issue touches generated reading order or anchors.

Use the report path to adjust Scrivener compile settings or source structure before compiling again.

Not this tool

You need source editing or layout design.

Scrivener project structure, compile presets, prose, typography, PDF output, and KDP account tasks are outside this scan.

Start here

Check the compiled Scrivener EPUB before changing compile settings.

Upload the .epub produced by Scrivener compile. The scan checks the generated output KDP sees, including chapter XHTML, front/back matter, nav.xhtml, toc.ncx, OPF entries, anchors, resources, and ZIP structure.

Matched

What it means

Scrivener compile turns binder items into an EPUB package. Validators check that generated package, not the Scrivener project.

Matched

Can it be fixed automatically?

A checked repair is possible when the compiled EPUB has one clear structural mismatch that can be changed and checked again, such as OPF, manifest, media type, navigation, path, anchor, or ZIP wiring.

Matched

What to check next

Upload the .epub compiled from Scrivener.

Matched

What not to assume

It cannot edit the Scrivener project, choose compile settings, decide chapter order, restore missing assets, improve formatting, convert source files, or decide KDP review outcomes.

Common situations

Common Scrivener EPUB export cases.

Start from the compiled EPUB that failed or is ready for upload.

Matched

Internal links or footnotes break after compile.

Scrivener can regenerate section ids when binder items, notes, or headings become XHTML.

Scan the EPUB and compare source file, target file, and missing fragment.

Matched

TOC or front matter does not validate.

Compile settings can create nav, NCX, or spine output that does not match the intended front matter and reading order.

Check navigation wiring before changing chapter text.

Matched

Images or stylesheets are missing after compile.

A compiled EPUB can reference an asset that was not packaged or declared in the manifest.

Repair only when the target exists clearly; otherwise fix the Scrivener project and compile again.

Scrivener export phrases to check

Check EPUB after Scrivener export: scan the compiled Scrivener EPUB for KDP, Kindle Previewer, EPUBCheck, generated TOC, OPF, links, anchors, images, CSS, manifest, media-type, container, and ZIP blockers.

Where Scrivener EPUB blockers usually appear

An author compiles an EPUB from Scrivener and KDP, Kindle Previewer, EPUBCheck, or another validator reports a structure problem on the compiled output.

What it means

Compile output can change chapter paths, ids, and reading order.

Scrivener compile turns binder items into an EPUB package. Validators check that generated package, not the Scrivener project.

Scrivener blockers often involve regenerated anchors, TOC targets outside the spine, front matter order, missing resources, undeclared manifest items, OPF identifiers, disconnected navigation, media types, or ZIP packaging.

Before you edit

Check generated anchors and reading-order wiring before another compile.

If the error comes back after each compile, first find the generated path. The report can show whether nav.xhtml, toc.ncx, chapter XHTML, OPF, manifest, or an anchor id is the failing part.

  1. 1Upload the .epub compiled from Scrivener.
  2. 2Keep the Scrivener project so you can adjust compile settings if needed.
  3. 3Check whether the report names generated XHTML, nav.xhtml, toc.ncx, OPF, CSS, images, anchors, manifest entries, media types, container.xml, or ZIP packaging.
  4. 4Use checked repair only when one generated-package change is clear and EPUBCheck passes again.
  5. 5Return to Scrivener when reading order, front matter, notes, headings, missing images, or compile settings are involved.
  6. 6Do not use this scanner for DOCX/PDF conversion, fixed-layout design, KPF/KCB, or KDP account tasks.

Why validators check it

Why Scrivener EPUB output still needs package validation.

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 Scrivener EPUB issue can be repaired here.

When automatic repair is safe

A checked repair is possible when the compiled EPUB has one clear structural mismatch that can be changed and checked again, such as OPF, manifest, media type, navigation, path, anchor, or ZIP wiring.

When you need manual review

It cannot edit the Scrivener project, choose compile settings, decide chapter order, restore missing assets, improve formatting, convert source files, or decide KDP review outcomes.

Before / after example

Before: nav.xhtml links to a generated id that no longer exists. After: a repair may be possible only when one replacement anchor clearly points to the same location. Before: the intended heading is unclear; fix the Scrivener source and compile again.

Ready to retry?

Upload the compiled Scrivener EPUB for a structure scan.

Use the .epub produced by Scrivener compile. The report separates a package repair from compile settings, source binder structure, or manual review.

Upload EPUB to scan

FAQ

Questions authors ask after Scrivener EPUB export.

Can EPUB Fixer validate a Scrivener EPUB export?

Yes. Upload the compiled reflowable .epub. The report can identify supported package, navigation, OPF, link, anchor, manifest, media-type, or ZIP blockers.

Should I change Scrivener compile settings first?

Scan the compiled EPUB first when you already have the failing output. Change compile settings when the report points to reading order, generated anchors, front matter, image handling, or TOC output.

Can it fix Scrivener project structure?

No. It does not edit the Scrivener project. It checks the compiled EPUB package and offers a checked repair only when one structural change is safe.

What if the same error returns after every compile?

Keep one report and compare the affected path after each compile. If generated ids or TOC structure keep changing, fix the compile settings rather than patching every output file.

Related EPUB error guides