EPUB FixerKDP upload error scanner

EPUB error guide

Fix EPUB for Apple Books or Google Play Rejection

Upload the EPUB that Apple Books rejected. The report separates a standard EPUB structure blocker from an Apple Books workflow issue and offers a checked repair only when the fix is clear.

Scan EPUB structureSee an example report

You see

Apple Books rejected the EPUB.

Upload the same file when the message mentions validation, import, a missing file, a bad URI, metadata, navigation, or package structure.

You get

An Apple Books EPUB fix decision.

The report names the affected path and separates a checked structural repair from manual review or an Apple Books workflow issue.

Not covered

Store, app, or device workflow.

Rights, pricing, account state, listing metadata, content review, cover delivery, Apple Books app/device problems, and final store decisions stay outside this scan.

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

  • Fix EPUB for Apple Books
  • Apple Books EPUB fix
  • Apple Books EPUB import error
  • Apple Books EPUB validation error
  • Apple Books EPUB rejected
  • Google Play Books EPUB rejected
  • Store rejected EPUB validation error
  • Duplicate IDs, metadata, link, anchor, or package blocker

Use this guide when

Your message matches "Fix EPUB for Apple Books" 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 "Fix EPUB for Apple Books" 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 Apple Books EPUB fix report should show.

A useful report should translate the platform rejection into standard EPUB evidence and one next action where possible.

Store

Apple Books or Google Play Books.

Likely validator family

RSC duplicate id, broken link, OPF metadata, navigation, manifest, media type, or package wrapper.

Affected path

The internal EPUB file or package field behind the rejection.

Decision

Checked repair, formatter handoff, source export fix, or unsupported.

The report should help you separate a standard EPUB blocker from a store policy or account issue.

2. Next step

Choose an Apple Books EPUB fix or store workflow.

Not every store rejection is the same kind of problem.

Upload scan

Use this when the store rejected an EPUB file.

Scan the EPUB to find whether it has strict validation blockers even if another platform accepted it.

Checked repair

Use this when the blocker is a clear EPUB structure mismatch.

Duplicate ids, metadata links, manifest entries, path mismatches, and ZIP wrapper problems may be actionable when the target is clear.

Store review

Use this when the rejection is policy, account, rights, pricing, or listing related.

Those problems belong in the store dashboard or publisher workflow, not the EPUB package scan.

3. Concrete path example

A stricter store rejection can be a duplicate-id EPUBCheck issue.

The same EPUB can behave differently across platforms when one store enforces stricter validation.

Store rejection:
Apple Books or Google Play rejects the EPUB after upload.

Report:
EPUBCheck family: RSC_005 duplicate ID
Affected file: OEBPS/Text/chapter-04.xhtml
Duplicate id: note-12
Decision: manual review if footnote/backlink targets depend on reader location

Do not delete duplicate ids blindly. Navigation, notes, and backlinks may depend on the intended target.

Quick decision

Is Apple Books rejecting the EPUB structure?

This path is for the finished EPUB file. Apple Books app/device behavior, store account, delivery, policy, and final acceptance tasks stay outside the structure scan.

Good fit

The rejection mentions EPUB validation or file structure.

Scan for duplicate ids, broken links, metadata, navigation, manifest, media type, package, and ZIP issues.

Manual fit

The store gives vague rejection wording.

The report can still find standard EPUB blockers, but a platform-specific issue may remain.

Not this tool

The rejection is about rights, pricing, account, listing, content policy, or cover requirements.

Use the store dashboard or publisher support workflow.

Start here

Fix the EPUB structure behind an Apple Books rejection.

Upload the same rejected EPUB. Apple Books and other stores can reject package rules that a local reader does not show; the report finds the affected path before you change store metadata or export again.

Matched

What it means

Different stores can enforce EPUB rules differently. A rejection can still be a standard EPUB structure issue inside the file.

Matched

Can it be fixed automatically?

A checked repair is possible when the store rejection maps to one clear EPUB structure issue that can be checked with EPUBCheck again.

Matched

What to check next

Save the exact store rejection message and platform name.

Matched

What not to assume

It does not fix Apple Books app or device import problems, store policy, rights, tax, account setup, pricing, categories, territories, cover requirements, content review, or final approval by Apple Books, Google Play Books, or any other store.

Common situations

Common Apple Books EPUB fix situations.

Start with the exact import or validation message and the EPUB file it names.

Matched

Apple Books rejects the EPUB after import.

The rejection may point to a standard package, manifest, URI, metadata, or link problem.

Scan the same EPUB and keep the Apple Books message with the report.

Matched

Duplicate ids after export.

Some source tools can generate repeated ids in XHTML, which stricter validators reject.

Locate the duplicate id and check whether notes, TOC links, or backlinks depend on it before editing.

Matched

Metadata or identifier mismatch.

The OPF package can point to missing or inconsistent metadata fields.

Check content.opf before changing store listing metadata.

Apple Books EPUB errors to check

Fix EPUB for Apple Books: store upload rejection caused by EPUBCheck, duplicate id, metadata, link, anchor, navigation, manifest, media-type, package, or ZIP validation blockers.

Where Apple Books EPUB import problems appear

An author, formatter, or small publisher wants to fix an Apple Books or Google Play rejection in an exported EPUB that may still open locally.

What it means

Apple Books can reject package rules that a reader does not show.

Different stores can enforce EPUB rules differently. A rejection can still be a standard EPUB structure issue inside the file.

Common causes include duplicate XHTML ids, missing anchors, broken resource paths, OPF identifier mismatches, missing language or modified metadata, media-type mismatches, disconnected navigation, manifest problems, and ZIP packaging mistakes.

Before you edit

Find the EPUB path before changing store metadata.

Do not assume the store is wrong or that KDP behavior proves the file is clean. Find the affected EPUB path and validation family first.

  1. 1Save the exact store rejection message and platform name.
  2. 2Run or scan against EPUBCheck-style structure checks first.
  3. 3Look for duplicate ids, broken links, missing anchors, missing resources, OPF metadata, manifest, media type, navigation, container, and ZIP issues.
  4. 4Use the affected internal file path to decide whether a checked repair is possible.
  5. 5Return to the source tool or formatter when the fix depends on notes, headings, layout, or missing content.
  6. 6Use the store dashboard or support workflow for policy, rights, account, listing, pricing, or cover requirements.

Why KDP checks it

Why Apple Books validation can reject an EPUB that opens elsewhere.

Apple Books book validation

Apple Books requires import validation and specifically calls out URI encoding and files missing from the OPF manifest as reasons an EPUB can fail import.

Google Play Books EPUB files

Google Play Books recommends running EPUBCheck before upload and shows file-processing errors in the Partner Center when an EPUB cannot be processed.

EPUBCheck

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

Can this be fixed safely?

When an Apple Books EPUB rejection can be fixed here.

When automatic repair is safe

A checked repair is possible when the store rejection maps to one clear EPUB structure issue that can be checked with EPUBCheck again.

When you need manual review

It does not fix Apple Books app or device import problems, store policy, rights, tax, account setup, pricing, categories, territories, cover requirements, content review, or final approval by Apple Books, Google Play Books, or any other store.

Before / after example

Before: Google Play rejects an EPUB and the scan finds duplicate id note-12 in one XHTML file. After: repair only when the intended note and backlink targets are clear, then validate again. Before: the store rejection is about rights or pricing; use the store workflow.

Ready to retry?

Find and fix the EPUB problem behind the Apple Books error.

Upload the same EPUB that Apple Books or Google Play Books rejected. The report shows whether the issue maps to a supported structure repair and checks the repaired file again before download.

Upload EPUB to scan

FAQ

Questions authors ask when Apple Books rejects an EPUB.

Can you fix an EPUB rejected by Apple Books?

Sometimes. If the rejection maps to a supported EPUB structure problem, the report can offer a checked repair after the repaired file passes EPUBCheck again. Store policy, account, delivery, app/device, and final acceptance problems need the Apple Books workflow.

Why would Apple Books or Google Play reject an EPUB that works elsewhere?

Different platforms can enforce EPUB rules differently. The file may still have duplicate ids, metadata, link, anchor, or package problems that another platform tolerates.

Can EPUB Fixer decide Apple Books or Google Play acceptance?

No. It can check and sometimes repair EPUB structure blockers, but final store acceptance includes policies and platform decisions outside this scanner.

Should I change KDP metadata if Apple Books rejects the EPUB?

No. First check the EPUB file itself. Store listing metadata and OPF package metadata are different places.

What if the rejection does not include an error code?

Scan the EPUB and look for standard EPUBCheck-style blockers. If the scan is clean, the rejection may be platform workflow or policy rather than file structure.

Related EPUB error guides