Match the report title.
Look for "Apple Books EPUB rejected" or the closest title above. Keep the original EPUBCheck, KDP, or Kindle Previewer wording if it differs.
EPUB error guide
Apple Books or Google Play rejected EPUB
Use this when Apple Books, Google Play Books, Draft2Digital, or another store rejects an EPUB that may still open locally or pass a looser upload workflow.
Scan when the message does not name the affected path. The report shows affected paths and repair decisions, not manuscript text.
Fixed-layout, DRM, or source-workflow issue? Check unsupported or review-first EPUB cases.
Match these report titles
- 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 "Apple Books EPUB rejected" 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.
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 store-rejection report should show.
A useful report should translate the platform rejection into standard EPUB evidence where possible.
Store
Apple Books, Google Play Books, Draft2Digital, Kobo, or another EPUB-ingestion workflow.
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 standard EPUB repair or store workflow review.
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
Decide whether the store rejected EPUB structure or something else.
This page should catch platform rejection searches while keeping the product focused on EPUB structure.
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
Check the EPUB standard issue before chasing store-specific fixes.
Apple Books and Google Play Books can reject EPUB files that seem fine elsewhere. Start by checking EPUBCheck-style blockers: duplicate ids, metadata, links, anchors, navigation, manifest entries, and package structure.
What it means
Different stores can enforce EPUB rules differently. A rejection can still be a standard EPUB structure issue inside the file.
Can it be fixed automatically?
EPUB Fixer can help when the store rejection maps to one clear EPUB structure issue that can be checked with EPUBCheck again.
What to check next
Save the exact store rejection message and platform name.
What not to assume
It does not handle 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 and Google Play EPUB rejection cases.
Start by asking whether the rejection has a standard EPUB validation clue.
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.
Metadata or identifier mismatch.
The OPF package can point to missing or inconsistent metadata fields.
Check content.opf before changing store listing metadata.
Broken links, anchors, or missing resources.
A store can reject stale chapter links, missing images, or anchors that local readers ignore.
Scan source and target paths before re-exporting blindly.
Store rejection phrases this page can help with
Apple Books or Google Play EPUB rejected: store upload rejection caused by EPUBCheck, duplicate id, metadata, link, anchor, navigation, manifest, media-type, package, or ZIP validation blockers.
Where Apple Books or Google Play EPUB rejection appears
Apple Books, Google Play Books, Draft2Digital, Kobo, or another EPUB store rejects a file that may still open locally or may have behaved differently on KDP.
What it means
A store rejection often points back to strict EPUB validation.
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
Check the EPUB package before rebuilding the whole book.
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.
- 1Save the exact store rejection message and platform name.
- 2Run or scan against EPUBCheck-style structure checks first.
- 3Look for duplicate ids, broken links, missing anchors, missing resources, OPF metadata, manifest, media type, navigation, container, and ZIP issues.
- 4Use the affected internal file path to decide whether a checked repair is possible.
- 5Return to the source tool or formatter when the fix depends on notes, headings, layout, or missing content.
- 6Use the store dashboard or support workflow for policy, rights, account, listing, pricing, or cover requirements.
Why KDP checks it
Why stores can disagree on the same EPUB.
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 store rejection can be repaired here.
When automatic repair is safe
EPUB Fixer can help 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 handle 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?
Scan the EPUB rejected by the store.
Upload the same EPUB that Apple Books, Google Play Books, Draft2Digital, or another store rejected. The report can show whether the issue maps to a supported EPUB structure check.
Upload EPUB to scanFAQ
Questions authors ask about store EPUB rejections.
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 guarantee 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.