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.
EPUB error guide
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.
Scan the EPUB to check file paths and see what can be repaired or needs manual review. Your original EPUB stays unchanged.
Need fixed-layout, DRM, or source-file help? Check unsupported or review-first EPUB cases.
Match these report titles
Start here
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.
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.
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.
Upload the .epub file exported by Atticus.
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.
1. Example report output
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
The next step depends on whether the exported EPUB already contains the file or anchor the package points to.
Scan result
Move to Kindle Previewer or KDP upload for final platform checks.
Checked repair
Use repair only when the OPF, manifest, nav, image path, cover, media type, or ZIP change is unambiguous and revalidates.
Source fix
Return to Atticus when headings, notes, TOC order, missing images, or layout choices need source-level work.
3. Concrete path example
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
This check starts after Atticus has already exported the EPUB. It does not edit Atticus projects or decide book design.
Good fit
The scanner can inspect generated navigation, OPF metadata, chapter links, anchors, image paths, cover wiring, manifest entries, and ZIP packaging.
Manual fit
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
Visual layout, source editing, pricing, categories, DRM choice, review status, and KDP listing work are outside this scan.
Common situations
Start from the exported EPUB file and the validation message you see.
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.
Atticus headings can produce navigation files that still need matching OPF manifest and spine wiring.
Check the navigation layer before changing chapter headings.
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.
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.
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
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
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.
Why validators 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.
Repair 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 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 scanFAQ
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.
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.
No. It checks EPUB structure after export. Typography, visual layout, source editing, and paperback output belong in Atticus or another source workflow.
No. It checks supported EPUB structure blockers and revalidates checked repairs. Kindle Previewer, KDP upload, review, and account workflows remain separate.