EPUB FixerKDP upload error scanner

EPUB error guide

Check EPUB after Atticus export

Use this when you have an Atticus EPUB and need to know whether the exported file has a KDP, Kindle Previewer, or EPUBCheck blocker before you change headings, images, notes, or export settings.

You see

The message matches this guide.

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

Use this guide when

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

A useful scan report points to the generated file that should be checked before you re-export.

Export checked

The Atticus .epub output that failed or will be uploaded.

Navigation layer

Whether nav.xhtml, toc.ncx, OPF spine entries, and TOC targets agree.

Reference layer

Chapter links, image paths, cover metadata, manifest items, media types, container.xml, and ZIP wrapper.

Decision

Retry, checked repair, Atticus re-export, manual review, unsupported, or no supported blocker found.

The report should tell you whether the exported package is fixable as-is or whether the Atticus source needs the change.

2. Next step

Choose scan result, repair, or Atticus source fix.

The next step depends on whether the exported EPUB already contains the file or anchor the package points to.

Scan result

No supported blocker is found.

Move to Kindle Previewer or KDP upload for final platform checks.

Checked repair

One package reference is clear.

Use repair only when the OPF, manifest, nav, image path, cover, media type, or ZIP change is unambiguous and revalidates.

Source fix

The issue depends on the book source.

Return to Atticus when headings, notes, TOC order, missing images, or layout choices need source-level work.

3. Concrete path example

An Atticus EPUB can fail because an image path changed during export.

The chapter file can reference a path that no longer exists in the ZIP package.

Report:
Source file: OEBPS/Text/chapter-03.xhtml
Referenced image: ../Images/scene.png
ZIP match: OEBPS/images/scene.png
Decision: checked repair only if this is the single clear packaged target

If the image is not packaged anywhere, restore it in Atticus and export again instead of inventing a file.

Quick decision

Decide whether this is an Atticus export structure problem.

This check starts after Atticus has already exported the EPUB. It does not edit Atticus projects or decide book design.

Good fit

You have the Atticus .epub file.

The scanner can inspect generated navigation, OPF metadata, chapter links, anchors, image paths, cover wiring, manifest entries, and ZIP packaging.

Manual fit

A path is named but the intended target is unclear.

Use the report to find the chapter, image, or TOC entry, then fix the Atticus source if the target choice needs judgment.

Not this tool

You need formatting or platform setup.

Visual layout, source editing, pricing, categories, DRM choice, review status, and KDP listing work are outside this scan.

Start here

Check the Atticus-exported EPUB before changing the manuscript.

Upload the .epub that Atticus exported. The scan checks the package KDP sees, including generated chapter paths, TOC targets, image references, OPF metadata, cover wiring, manifest entries, and ZIP structure.

Matched

What it means

Validators inspect the exported EPUB, not the Atticus editor. The package must keep generated chapters, navigation, resource paths, metadata, manifest entries, and ZIP files in sync.

Matched

Can it be fixed automatically?

A checked repair is possible when the exported package already contains enough evidence for one correction, such as a manifest item, media type, OPF identifier, nav declaration, cover-image property, path mismatch, or ZIP packaging rule.

Matched

What to check next

Upload the .epub file exported by Atticus.

Matched

What not to assume

It cannot edit Atticus source projects, design the book, choose chapter order, restore missing files, fix typography, handle paperback output, or decide KDP review outcomes.

Common situations

Common Atticus EPUB export cases.

Start from the exported EPUB file and the validation message you see.

Matched

KDP rejects the Atticus EPUB after upload.

The failure may come from a generated TOC target, missing manifest item, wrong media type, or cover reference inside the export.

Scan the same EPUB and use the affected path before re-exporting.

Matched

The Kindle TOC or Go To menu is wrong.

Atticus headings can produce navigation files that still need matching OPF manifest and spine wiring.

Check the navigation layer before changing chapter headings.

Matched

Images or CSS fail after export.

The EPUB may reference Images/photo.jpg while the package contains images/photo.jpg, or the image may be absent entirely.

Repair only when the report finds one clear packaged target.

Atticus export phrases to check

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

Where Atticus EPUB blockers usually appear

An author exports from Atticus and wants to check the EPUB before Kindle upload, or has a validation message on the Atticus output.

What it means

After export, a chapter, image, or TOC target can point to the wrong packaged path.

Validators inspect the exported EPUB, not the Atticus editor. The package must keep generated chapters, navigation, resource paths, metadata, manifest entries, and ZIP files in sync.

Atticus export blockers often involve image folder case, missing assets, TOC targets outside the spine, anchors generated from headings, cover wiring, undeclared manifest items, media types, or ZIP packaging.

Before you edit

Check TOC, links, anchors, and package metadata before another Atticus export.

If Atticus looks correct, do not start by rewriting source text. First check whether the exported EPUB has a stale image path, missing anchor, cover declaration, or manifest entry.

  1. 1Upload the .epub file exported by Atticus.
  2. 2Keep the Atticus project available for re-export if the report marks manual review.
  3. 3Check whether the report names OPF metadata, 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 the report shows one clear structural change and EPUBCheck passes again.
  5. 5Return to Atticus when the fix depends on chapter order, note behavior, missing assets, visual layout, or source headings.
  6. 6Do not use this scanner for DOCX, PDF, KPF, KCB, fixed-layout, comics, or KDP account tasks.

Why validators check it

Why Atticus EPUB output still goes through EPUBCheck-style 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 an Atticus EPUB issue can be repaired here.

When automatic repair is safe

A checked repair is possible when the exported package already contains enough evidence for one correction, such as a manifest item, media type, OPF identifier, nav declaration, cover-image property, path mismatch, or ZIP packaging rule.

When you need manual review

It cannot edit Atticus source projects, design the book, choose chapter order, restore missing files, fix typography, handle paperback output, or decide KDP review outcomes.

Before / after example

Before: chapter XHTML points to Images/photo.jpg but the EPUB contains images/photo.jpg with different case. After: the reference can be aligned when the target is unique and EPUBCheck passes again. Before: the image is absent; fix Atticus and export again.

Ready to retry?

Upload the Atticus EPUB for a package scan.

Upload the exact Atticus .epub you plan to send to KDP or Kindle Previewer. The report tells you whether to repair the package, return to Atticus, or stop because the issue is outside this scanner.

Upload EPUB to scan

FAQ

Questions authors ask after Atticus EPUB export.

Can EPUB Fixer validate an Atticus EPUB before KDP upload?

Yes. Upload the exported reflowable .epub. The report can identify the affected path and whether the next step is retry, checked repair, Atticus re-export, or unsupported.

Should I change Atticus settings first?

Not if you already have the failing EPUB. Scan that file first, then change Atticus settings only when the report points to TOC, heading, note, image, or layout work in the source.

Can this repair Atticus formatting problems?

No. It checks EPUB structure after export. Typography, visual layout, source editing, and paperback output belong in Atticus or another source workflow.

Does this mean Kindle upload will accept the book?

No. It checks supported EPUB structure blockers and revalidates checked repairs. Kindle Previewer, KDP upload, review, and account workflows remain separate.

Related EPUB error guides