EPUB Validation Quick Check
A fast EPUB QA pass before upload prevents distributor rejection and reader-facing problems. Validate structure, navigation, and metadata in one repeatable loop, then ship one clean release candidate.
Start with one known release candidate
Always validate the latest export, not a stale file from an earlier draft.
If chapter order, heading hierarchy, front/back matter, or metadata changed, treat the EPUB as a new candidate and rerun all checks.
Use versioned file names (`book-title-epub-rc05.epub`) so validation evidence maps to exactly one file.
Run structure and navigation checks before styling polish
Open the EPUB in at least one reader and click through TOC entries from start to finish.
Verify chapter sequencing, chapter-open boundaries, and back matter position before addressing cosmetic warnings.
Structural defects compound quickly, so clear them first.
Validate metadata in the same pass
Confirm title, author naming, language code, and identifier strategy are final for this edition.
Metadata drift can break storefront quality even when typography looks clean.
If metadata changes, rerun both validator and navigation checks on the new export.
Triage findings by release impact
Blockers (invalid nav, broken links, missing required metadata) should stop release.
Structural warnings should be fixed before upload unless a documented exception is approved.
Advisory warnings can proceed only with explicit sign-off and reader-device verification notes.
Fix source content, re-export, and validate again
Apply fixes in source manuscript or export settings and generate a fresh EPUB.
Avoid direct ZIP/package patching as your primary workflow; it creates divergence from source.
Repeat validator plus click-through checks until one candidate passes with intended warning posture.
Numbers and Reference Tables
EPUB Validation Triage Matrix
Issue class
Example signal
Source-first action
Release decision
Navigation/TOC error
TOC jump lands on wrong chapter or missing anchor
Normalize heading hierarchy and anchor-producing headings in source
Block release until fixed
Broken internal link
Back matter link or chapter cross-reference fails
Repair link targets in source and re-export
Block release until fixed
Metadata defect
Missing/invalid language or identifier field
Correct package metadata fields and regenerate EPUB
Block release until fixed
Rendering warning
Unsupported CSS affects readability
Simplify style usage and verify in multiple readers
Fix before upload when reader-visible
Advisory-only warning
Non-critical best-practice notice
Document rationale and run extra device QA
Proceed only with explicit sign-off
Publish Checklist
Export one EPUB candidate from the latest manuscript source.
Verify chapter sequence and front/back matter order in a reader.
Click every TOC entry and confirm destination accuracy.
Confirm title, author naming, language, and identifier metadata.
Run EPUB validation on the exact candidate file.
Classify findings into blockers, structural warnings, rendering warnings, or advisories.
Fix blockers and structural warnings in source content/settings.
Re-export and rerun validation on the new file version.
Run click-through TOC and internal-link checks again after fixes.
Test in at least two reading environments before upload.
Archive one final validated EPUB and upload that exact file only.
Warning-to-Fix Map
Warning pattern: navigation document missing or invalid
Fix: Rebuild chapter heading structure in source and regenerate EPUB with a complete nav document.
Verify: Validator confirms nav document present and valid.
Warning pattern: TOC entry lands on wrong chapter
Fix: Remove duplicate heading anchors and normalize chapter heading hierarchy.
Verify: Every TOC link lands on the intended chapter heading.
Warning pattern: duplicate id or anchor target
Fix: Ensure each chapter and major section heading has a unique target in source content.
Verify: Validator no longer reports duplicate identifiers.
Warning pattern: broken internal hyperlink
Fix: Correct link targets in source front/back matter and chapter references.
Verify: All internal links resolve in reader click-through checks.
Warning pattern: malformed metadata field
Fix: Normalize title, author, language code, and identifier values before re-export.
Verify: Validator reports no required metadata field errors.
Warning pattern: unsupported CSS or rendering warning
Fix: Simplify source styles and remove unsupported properties that affect reader rendering.
Verify: Warning count drops and layout remains stable in at least two readers.
Warning pattern: chapter order appears correct but TOC is stale
Fix: Regenerate TOC from current heading structure before exporting again.
Verify: TOC order and chapter order both match the manuscript.
Warning pattern: issue remains after fix
Fix: Confirm validation run is against the newest export and remove stale local files.
Verify: Renamed latest EPUB passes the same validation step.
The Senswriter way (faster)
Use the same workflow in one workspace: draft, export, run checks, fix source, and publish one clean release-candidate file.
Write and reorganize chapters/scenes without switching between multiple tools.
Generate print-ready PDF, EPUB, and DOCX from the same manuscript source.
Re-export quickly after fixes so KDP and EPUB checks stay repeatable.
Use optional BYOK AI assist only if you want drafting support.
Open the Senswriter Workspace and see export examples .
Frequently Asked Questions
Is EPUB validation still needed if the file opens in a reader?
Yes. A file can open locally and still fail stricter distributor ingestion checks.
Should I edit EPUB files directly to fix warnings?
Avoid that workflow for normal releases. Fix source content and re-export so future updates stay consistent.
When should I rerun EPUB validation?
After any meaningful manuscript, structure, metadata, or front/back matter change before final upload.
What is the minimum pre-upload QA for EPUB?
Run validator checks, click every TOC link, and test the same file in at least two reading environments.
Can I treat metadata warnings as optional if reading looks fine?
No. Metadata defects can hurt distributor ingestion and storefront quality even when text rendering appears normal.
Why avoid direct EPUB package edits?
Direct package edits are fragile and drift from your manuscript source. Source-first fixes are more reliable for future revisions.