EPUB error reference

Turn EPUB error codes into a file, cause, and repair step.

Do not fix only the wording of an error. Identify the package layer—container, OPF metadata, navigation, XHTML, CSS, media, or accessibility—then validate the replacement file again.

Package-layer diagnosisPrivate first-pass checkOfficial validator linked
Private by default

Drop in the file you plan to publish

Choose a DOCX or EPUB. This first check runs in your browser; your manuscript is not uploaded.

Read the location before the message

A validator result usually identifies a severity, code, file path, line, and explanation. The path tells you whether the failure lives in package.opf, nav.xhtml, a chapter document, CSS, or a media asset. Repair the source that generates that file whenever possible; hand-editing the export can be overwritten on the next build.

Common error families
LayerTypical problemRepair direction
ContainerMissing or wrong package pathRepair META-INF/container.xml
OPF metadataMissing title, language, identifierComplete publication metadata
Manifest or spineMissing item or broken reading orderRebuild references and order
XHTMLInvalid nesting or duplicate IDsFix semantic document markup
NavigationBroken target or missing navRebuild table of contents links
MediaMissing file or wrong media typeAdd the asset and correct manifest type

Use the official validator as the final standards check

ShipMyBook's browser tool is a bounded structural preflight. EPUBCheck is the open, standards-complete reference used across the publishing ecosystem. Run the current release after every repair and proof the book in real reading systems; zero validator errors does not guarantee a good visual or accessible reading experience.

FAQ

Frequently asked questions

Is every warning a release blocker?

No. Severity and platform requirements matter. Understand the warning and document the decision instead of automatically suppressing it.

Why does an EPUB still look wrong after passing validation?

Validation checks standards and structure. CSS, image behavior, font fallback, device differences, and accessibility still require proofing.

Found the package layer? Repair and validate again.

A paid release can keep the repaired EPUB tied to its source, print file, cover, and metadata.

See repair pricing