EPUB FixerKDP upload error scanner

EPUB error guide

Invalid, corrupt, or damaged EPUB file

Scan when an EPUB is invalid, corrupt, unreadable, or contains duplicate ZIP entries. Check whether the wrapper can be repaired before replacing the whole export.

Scan EPUB structureSee an example report

Best fit

The EPUB opens poorly or is rejected as corrupt.

Upload when the file is still a reflowable .epub and you need to know whether the wrapper, container.xml, OPF path, or mimetype entry is blocking validation.

Report shows

Package map and duplicate entries first.

The scan checks ZIP readability, repeated paths, root mimetype, META-INF/container.xml, and the OPF rootfile before deeper link or chapter errors.

Stop when

The archive is encrypted, incomplete, or not an EPUB.

Use the source project or backup when the ZIP cannot be opened, core package files are gone, DRM is present, or several OPF targets compete.

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

  • Invalid EPUB file
  • Corrupt EPUB package
  • Corrupted ebook file
  • Damaged EPUB file
  • EPUB is not a valid ZIP package
  • EPUB ZIP contains duplicate entries
  • Duplicate ZIP entry in EPUB
  • Mimetype, container.xml, OPF rootfile, or package error

Use this guide when

Your message matches "Invalid EPUB file" 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 "Invalid EPUB file" 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 invalid EPUB report should show.

The first useful answer is whether the EPUB wrapper can be repaired or whether the file needs a clean export.

Wrapper check

Is this a readable ZIP package with the EPUB mimetype entry?

Duplicate paths

Does one internal path appear more than once, and are those copies identical or different?

Container map

Does META-INF/container.xml exist and point to a real OPF file?

OPF rootfile

Does the rootfile path match the actual package location?

Decision

Repair wrapper, inspect package path, re-export source, or unsupported.

If the package map is broken but one OPF target is obvious, repair may be safe. If the file is damaged or encrypted, use the source export instead.

2. Next step

Choose package repair or clean export.

Invalid EPUB messages are often package-level, but not every damaged file is repairable.

Package check

Use this when the file was manually zipped or renamed.

Mimetype order, compression, duplicate paths, and root folder layout are common causes after manual archive edits.

OPF check

Use this when container.xml points to the wrong package file.

A repair can be safe when one real OPF file exists and the rootfile path is just wrong.

Clean export

Use this when the ZIP is damaged, encrypted, or missing core files.

Return to the source project and export a fresh EPUB instead of inventing required package content.

3. Concrete path example

A corrupt-looking EPUB may only have a wrong rootfile path.

The file can contain the book, but container.xml points readers to the wrong OPF path.

Validator:
EPUB is invalid: OPF file could not be found.

Report:
container.xml rootfile path: OEBPS/package.opf
Actual OPF file: EPUB/content.opf
Decision: safe only if EPUB/content.opf is the single real package file

If several OPF files exist or the ZIP cannot be opened, stop and re-export from the source project.

Quick decision

Decide whether the file is broken or just packaged incorrectly.

Some invalid EPUB files only need a wrapper fix. Others are not safe to repair because required package files are missing.

Good fit

The EPUB is readable but has a package wrapper mistake.

Mimetype, container.xml, OPF rootfile, ZIP ordering, and identical duplicate entries can be checked and sometimes repaired.

Manual fit

The package has competing OPF files or unclear root layout.

The report can name the candidates, but a person should choose the intended package file.

Not this tool

The file is encrypted, DRM-protected, non-EPUB, or deeply damaged.

Use the original source export or a proper backup instead of trying to patch missing core files.

Start here

Check the EPUB wrapper before editing chapters.

Invalid EPUB often means the package wrapper cannot be opened correctly. Start with mimetype, ZIP structure, META-INF/container.xml, and the OPF rootfile path before touching book content.

Matched

What it means

An EPUB is a ZIP package with a required wrapper and a package map. If the wrapper or map is broken, validators may reject the file before checking chapters, images, or links.

Matched

Can it be fixed automatically?

A checked repair is possible when the wrapper mistake has one exact result, such as mimetype order, container.xml pointing to one OPF, a package-root mismatch, or duplicate ZIP entries whose bytes are identical.

Matched

What to check next

Confirm the file extension and source: it should be a real .epub exported by a publishing or formatting tool.

Matched

What not to assume

It cannot choose between duplicate entries with different content or repair a deeply corrupted archive, encrypted EPUB, DRM file, non-EPUB input, missing OPF package, missing book content, or several competing package targets.

Common situations

Common invalid EPUB cases.

Start with the first package layer that fails.

Matched

The mimetype file is missing, compressed, or not first.

Manual ZIP tools often package EPUB folders in the wrong order.

Rebuild the wrapper only when the rest of the EPUB package is intact.

Matched

container.xml is missing or points to the wrong OPF.

EPUB readers need container.xml to find the package document.

Repair the rootfile path only when one real OPF target is clear.

Matched

The EPUB ZIP contains the same path more than once.

The repeated entries may be identical copies or different versions of the same internal file.

Keep one copy only when the bytes are identical. If the copies differ, choose the correct source version manually and rebuild the EPUB.

Matched

The file is not a valid EPUB ZIP.

A renamed folder, damaged upload, encrypted file, or wrong source file can look like an EPUB but fail package checks.

Go back to the source tool and export a fresh EPUB.

Invalid EPUB phrases to check

Invalid EPUB file: corrupt EPUB, duplicate ZIP entry, damaged EPUB, invalid mimetype, container.xml, OPF rootfile, or ZIP package error.

Where invalid or corrupt EPUB messages appear

KDP, Kindle Previewer, EPUBCheck, Apple Books, Google Play Books, or a reader app says the EPUB is invalid, corrupt, damaged, a corrupted ebook, unreadable, not a valid EPUB, or cannot find the package file.

What it means

A file can be invalid because the package map is broken.

An EPUB is a ZIP package with a required wrapper and a package map. If the wrapper or map is broken, validators may reject the file before checking chapters, images, or links.

Common causes include zipping the parent folder, duplicate internal paths, compressing or misplacing mimetype, missing container.xml, a wrong OPF rootfile path, damaged ZIP data, encrypted content, or a file that is not really an EPUB.

Before you edit

Check whether the EPUB is packaged like a real EPUB.

A broken ZIP wrapper, duplicate path, missing mimetype, missing container.xml, or wrong OPF rootfile path can stop validation before deeper content errors are visible.

  1. 1Confirm the file extension and source: it should be a real .epub exported by a publishing or formatting tool.
  2. 2Check whether the EPUB can be opened as a ZIP package.
  3. 3Check whether any internal path appears more than once and whether those entry bytes are identical.
  4. 4Look for the root mimetype entry and whether it is first and uncompressed.
  5. 5Check META-INF/container.xml and the OPF rootfile path.
  6. 6Confirm there is one intended OPF package file before repairing container.xml.
  7. 7Re-export from the source project when required files are missing, encrypted, damaged, or ambiguous.

Why KDP checks it

Why readers and validators reject invalid EPUB packages.

EPUB ZIP container

The EPUB ZIP wrapper must point readers to the OPF file through META-INF/container.xml and keep packaged resources at the paths the book references.

EPUBCheck

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

KDP eBook file formats

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

Can this be fixed safely?

When an invalid EPUB package can be repaired safely.

When automatic repair is safe

A checked repair is possible when the wrapper mistake has one exact result, such as mimetype order, container.xml pointing to one OPF, a package-root mismatch, or duplicate ZIP entries whose bytes are identical.

When you need manual review

It cannot choose between duplicate entries with different content or repair a deeply corrupted archive, encrypted EPUB, DRM file, non-EPUB input, missing OPF package, missing book content, or several competing package targets.

Before / after example

Before: the ZIP contains two identical copies of OEBPS/nav.xhtml. After: repack with one copy and validate again. Before: two copies differ or the ZIP cannot be opened; choose the correct source file manually or export the EPUB again.

Ready to retry?

Scan the invalid EPUB package.

Upload the EPUB when it is not encrypted and still looks like a normal reflowable EPUB package. The report will stop early when the file is outside scope.

Upload EPUB to scan

FAQ

Questions authors ask about invalid EPUB files.

Why does my EPUB say invalid or corrupt?

Often the ZIP wrapper or package map is broken. Check mimetype, container.xml, and the OPF rootfile path before editing chapters.

Can a corrupt EPUB be repaired automatically?

Only when the package mistake is clear and the core files still exist. A damaged, encrypted, or incomplete archive should be exported again.

Can EPUB Fixer remove duplicate ZIP entries?

Only when every repeated entry at that path has identical content. If the copies differ, the report stops because choosing the correct file changes the book and requires the source project or an EPUB editor.

Is renaming a ZIP file to EPUB enough?

No. The ZIP has to follow EPUB packaging rules, including a correct mimetype entry and container.xml package map.

Should I use this for DRM or encrypted EPUB files?

No. DRM-protected or encrypted EPUBs are outside this scanner.

Related EPUB error guides