How to Validate an EPUB File Before You Publish

A manuscript can look finished on screen and still fail as an ebook. A broken table of contents, a missing image reference, or invalid HTML may not appear until a retailer rejects the upload or a reader opens the book on a different device. Knowing how to validate an EPUB file is the production check that catches those problems before your release date does.

EPUB validation is not a cosmetic review. It tests whether the file follows the technical rules that allow ebook readers, retailer systems, and accessibility tools to interpret it consistently. A validated EPUB is not a guarantee that every retailer will accept every element without question, but it is the correct baseline for a distributable ebook.

What EPUB validation actually checks

An EPUB is a packaged publication, not a single document. Inside the `.epub` file are XHTML content files, CSS stylesheets, images, metadata, navigation documents, fonts when embedded, and a manifest that identifies the package contents. Each part must be present, correctly referenced, and structured according to the EPUB standard.

A validator inspects those components for technical compliance. It looks for issues such as missing files, malformed markup, invalid metadata, unsupported attributes, broken internal links, improper image declarations, and navigation errors. The most widely recognized validation engine is EPUBCheck, which is also the basis for many publishing tools and retailer-adjacent workflows.

Validation is different from proofreading and visual QA. A validator can confirm that an image file is declared correctly, but it cannot tell you that the image is blurry, poorly placed, or the wrong image for the chapter. It can detect a broken link in the navigation, but it cannot decide whether your chapter titles are clear. A production-ready ebook needs both technical validation and an intentional reader review.

How to validate an EPUB file step by step

Start with the final EPUB you intend to distribute. Do not validate an early export, make changes in a separate source file, and assume the final package remains clean. Each export is its own production artifact and should be checked accordingly.

1. Export a fresh EPUB from your source file

Export from the formatted manuscript or book-production environment you are using. Before validation, confirm that the file opens as an EPUB and that it has not been renamed with the wrong extension or compressed incorrectly.

If you are building an EPUB manually, do not treat it like an ordinary ZIP archive. EPUB packaging has specific requirements, including the placement and storage method of the `mimetype` file. A file can contain all the expected documents and still fail because the package itself was assembled incorrectly.

2. Run the file through an EPUB validator

Upload the file to a trusted validator that uses a current EPUBCheck engine, or run EPUBCheck locally if your production process supports command-line tools. Save the complete validation report, not just a pass or fail message. The report is your record of what the file contains and where a problem occurs.

Some publishing platforms generate a validated EPUB as part of export. For example, Tunmire Forge is designed to produce validated EPUB files from a structured manuscript workflow. Even when validation is built into your export process, open the final file and inspect it before distribution. Validation reduces technical risk; it does not replace editorial or design review.

3. Separate errors from warnings and informational messages

A validation report may return errors, warnings, and informational notices. Errors normally require correction because they indicate the EPUB does not meet the required specification. Warnings deserve review, but their effect depends on the message and your distribution plan. Informational messages may simply describe the validator version or a feature it encountered.

Do not ignore a warning merely because the file technically passes. A warning about deprecated markup, fallback behavior, or an unusual metadata value can become a retailer problem later, especially when a distribution channel updates its ingestion rules. At the same time, do not make random changes just to force a completely silent report. Read what the message identifies and determine whether it affects the actual package.

4. Locate the source of each issue

Validation messages usually identify a file name, line number, column number, and error code. An error such as a missing resource may point to an image listed in the package manifest but absent from the EPUB archive. A parsing error often indicates malformed XHTML, such as an unclosed tag, an unescaped ampersand, or invalid nesting.

If you are working from a source document rather than editing EPUB code directly, correct the issue in the source whenever possible and export again. Directly modifying the EPUB can be appropriate for experienced production teams, but it creates a maintenance problem: your source manuscript and your distributed file can drift apart. For most authors and small presses, the cleaner workflow is source correction, fresh export, fresh validation.

5. Revalidate after every fix

One correction can expose another issue or change the file package in unexpected ways. Re-run the validator after each round of changes until errors are resolved and remaining warnings have been assessed. Keep the final clean report with the EPUB, cover file, and release assets.

This is especially useful for series publishers. A repeatable folder structure with the final EPUB, validation report, cover export, and retailer upload notes makes later updates far less risky. When you revise a backlist title, you can verify exactly which file was previously distributed.

Common EPUB validation errors and what they mean

The wording in a report can feel technical, but most failures fall into a manageable set of production issues.

Missing or undeclared resources occur when a content file references an image, stylesheet, font, audio file, or other asset that is not properly included in the EPUB package. Check the file path, capitalization, and manifest entry. File names are case-sensitive in many EPUB-reading environments, even if your desktop operating system makes that easy to overlook.

Malformed XHTML or HTML is often caused by copied text, hand edits, or conversion artifacts. Look for unmatched tags, improperly nested elements, invalid characters, or HTML features that do not conform to the EPUB profile. Clean markup is easier to style, validate, and maintain than a file full of local formatting exceptions.

Navigation document errors can affect the table of contents and reader navigation. Confirm that every listed chapter or section exists, every target link works, and the reading order matches the book. For a nonfiction title, also check whether front matter and appendices are represented in a way that helps readers move through the book without cluttering navigation.

Metadata errors involve identifiers, language declarations, titles, contributor fields, or dates. Use accurate metadata from the beginning. A placeholder title, an incorrect language code, or a missing unique identifier may not change how the pages look, but it can complicate retailer ingestion and catalog management.

Accessibility-related issues frequently involve images without useful alternative text, poor heading structure, or content that depends entirely on visual formatting. Requirements vary by retailer and market, but accessible structure is sound publishing practice. If an image carries meaning, write concise alt text that communicates that meaning. If an image is purely decorative, handle it appropriately so a screen reader does not announce noise.

Validate the file, then test the reading experience

A technically valid EPUB can still produce a weak reader experience. After the validator passes, open the book in more than one EPUB reading environment if possible. Check the cover, table of contents, chapter starts, scene breaks, images, footnotes, endnotes, internal links, and any special typography.

Change the font size and switch to a different theme. Reflowable ebooks are designed to adapt to the reader's screen and preferences, so a layout that looks fine at one font size may reveal a spacing or heading problem at another. Test on a phone-sized screen as well as a larger reading application. Many buyers will encounter your book first on a small device.

Pay particular attention to elements that look like print layout. Text positioned in columns, elaborate drop caps, text wrapped around images, tables, and decorative chapter-opening treatments may require simpler ebook treatment. The trade-off is straightforward: preserving a print-like look can introduce fragile behavior across devices. In most trade ebooks, readable reflow matters more than reproducing every print design decision.

When a validator passes but a retailer still rejects the EPUB

Retailer acceptance is not identical to EPUB conformance. A retailer may apply additional rules for cover dimensions, embedded fonts, prohibited content, metadata consistency, image quality, or its own file-processing system. It may also convert your EPUB after upload, creating a preview issue that was not visible in your original file.

When that happens, read the retailer's rejection message first. Determine whether it identifies a file-standard problem, a metadata problem, or a platform-specific requirement. Do not rebuild the entire ebook without evidence. Make the targeted correction, export a new file, validate it again, and retain a versioned record of the change.

A validated EPUB is the point where your completed manuscript becomes a dependable digital book package. Treat the validation report like any other production checkpoint: keep it, review it, and let it protect the work you are about to put in readers' hands.