Tunmire Publishing and Media

How to Validate an EPUB Before You Publish Your Book

How to Validate an EPUB Before You Publish Your Book

A finished manuscript can look flawless in your editor and still fail as an ebook. A missing navigation document, an invalid image reference, or a broken table of contents can cause retailer upload errors or a poor reading experience after publication. Validating your EPUB is the final production check that confirms your ebook is packaged correctly before it reaches readers.

Validation is not busywork for an independent author. It is quality control. An EPUB is a structured package, not just a document saved with a different extension. It contains XHTML content files, CSS styling, metadata, images, navigation, and a manifest that tells reading systems how those pieces fit together. Validation checks whether that package follows the EPUB standard closely enough to open reliably across devices and storefronts.

What EPUB Validation Actually Checks

A validator examines the technical structure of the file. It looks for files listed in the package but missing from the archive, images used in a chapter but absent from the manifest, invalid markup, broken internal links, and metadata problems. It can also flag accessibility issues, including missing image descriptions or an incomplete navigation structure.

The most widely recognized technical validator is EPUBCheck. Many retailer systems run related checks during upload, even if they don't expose every rule the same way. Passing a validator doesn't guarantee every page looks perfect on every e-reader, but it does mean the EPUB is structurally sound enough to move into visual review with far less risk.

That distinction matters: validation finds code and packaging problems, while device testing finds presentation problems. A proper release process needs both.

How to Validate an EPUB, Step by Step

Start with the final EPUB export, not a working draft. If you change the manuscript, layout, chapter files, or cover after validation, export and validate again. Treat the validated EPUB as its own release artifact, the way you'd treat a print-ready PDF as the approved file for print production.

1. Export a Standard EPUB File

Use an EPUB export built for commercial distribution, preferably EPUB 3 unless a specific distributor requires another format. Avoid renaming a ZIP archive to .epub or assembling files manually unless you understand the package specification; EPUB files have strict internal requirements, including archive order and uncompressed files in particular locations.

Forge, Tunmire's layout tool, exports validated EPUBs to reduce this friction, but you should still keep a final review step of your own. Automation should remove repetitive formatting work, not your ownership of the finished reading experience.

2. Run the File Through EPUBCheck

Submit the exported file to EPUBCheck through a trusted implementation, or run the validator locally if you have a technical workflow. Save the results with your release files; a clean validation report is useful evidence that the exact ebook package you approved was checked before distribution.

Read every message carefully. Validators generally separate findings into errors, warnings, and informational notices. Errors need correcting. Warnings may not block retailer delivery, but don't dismiss them automatically. A warning about deprecated markup may be fine in a legacy backlist title; a warning tied to navigation, metadata, or accessibility deserves a closer look.

If the report gives a file path and line number, open that exact XHTML or CSS file in an EPUB editor or code editor. Don't make random formatting changes hoping the error disappears. Find the referenced element, fix the cause, export or repackage the EPUB, then validate again.

3. Confirm the Navigation and Table of Contents

A reliable table of contents is one of the first things readers notice when it fails. In EPUB 3, the navigation document should include the book's meaningful reading structure: front matter when appropriate, chapters, parts, endnotes, acknowledgments, and other major sections.

Check that every navigation entry opens the right location. A chapter title that links to the previous chapter is technically a working link, but it's still a production failure. For nonfiction, test links to notes, appendices, resources, and index entries. For fiction, make sure scene-break conventions, parts, and bonus chapters appear as intended without creating clutter.

Also inspect the reading order in the package document. A valid EPUB can contain all the right files but present them in the wrong sequence if the spine is misconfigured. Your title page shouldn't appear after Chapter 1, and an author's note shouldn't interrupt the final chapter unless that's a deliberate choice.

4. Review Metadata and Cover References

Metadata controls how the book identifies itself inside reading apps and, in some cases, during retailer ingestion. Confirm the title, contributor names, language, publisher information where applicable, publication date, and unique identifier. Pay close attention to subtitle punctuation and author bylines. Small inconsistencies between your cover, retailer listing, copyright page, and EPUB metadata create avoidable confusion.

Your cover image needs its own check. Verify it's included in the EPUB package, correctly identified as the cover, and sized clearly enough for thumbnail displays. An ebook cover doesn't need the same dimensions as a paperback or hardcover wrap, but it should be a polished front-cover image with no spine or back-cover elements.

5. Check Accessibility Before You Call It Finished

Validation and accessibility overlap, but they're not identical. An EPUB can pass a technical validator while still being difficult to use with assistive technology. Review headings, image descriptions, tables, language declarations, and reading order with real readers in mind.

Use heading levels to show hierarchy rather than styling ordinary paragraphs to look like headings. Give meaningful images concise alternative text when the image carries information. If an image is decorative, mark it as such so screen-reader users aren't interrupted by filenames or irrelevant descriptions.

Tables need special care. A simple table with labeled headers works well. A complex, visually designed table can become confusing on a small screen or with a screen reader. When the content allows it, consider a simpler structure. The goal isn't just to satisfy a rule; it's to preserve your meaning across reading modes.

Common EPUB Validation Errors and What They Mean

Some errors show up repeatedly in independent publishing workflows. Knowing the likely cause speeds up the fix.

A missing manifest item usually means the EPUB references a font, image, stylesheet, or chapter file that wasn't declared in the package. A broken hyperlink often comes from a renamed chapter file or an anchor ID that no longer exists. Invalid XHTML commonly results from unclosed tags, improperly nested elements, or special characters pasted from another application.

CSS errors can be more subtle. A validator may flag unsupported properties, malformed declarations, or values that don't meet the EPUB profile. Not every styling preference translates consistently to every e-reader anyway. When you have to choose between elaborate formatting and dependable rendering, dependable rendering is usually the stronger choice.

Font issues are another frequent source of trouble. Embedded fonts must be correctly licensed, declared, and included. Many narrative ebooks don't need them at all. Reader-selected fonts improve comfort and accessibility, while custom fonts may be justified for illustrated, poetry, or highly designed books. It depends on the book's purpose, not on whether the file can technically include a font.

Validate First, Then Test Like a Reader

Once the EPUB passes validation, open it in more than one reading environment. Test a phone app, a tablet, and an e-reader previewer if you can. Change the font size. Switch to dark mode. Move through the navigation. Search for a phrase. Follow footnotes and return to the text. Check that chapter openings, indents, scene breaks, images, and page-break behavior stay intentional.

This review is where you matter most. A validator can't tell you whether a memoir's photo captions feel detached from the images, whether a novel's ornamental scene break disappears in dark mode, or whether a nonfiction callout box becomes unreadable at a larger font size. Those are publishing decisions, not just technical defects.

If you produce titles regularly, build validation into your release checklist: approved manuscript, final cover, EPUB export, validator report, device review, retailer upload, archived release package. The process gets faster with repetition, because you're catching the same class of error before it reaches distribution.

A clean EPUB should be quiet. Readers shouldn't notice its package structure, navigation logic, metadata, or code, because each element simply supports the book. Validate the file, test the reading experience, and release an ebook that keeps the attention where it belongs: on your work.

Last updated November 15, 2026

Tunmire Publishing and Media

Tunmire builds software for independent authors — Apollo for writing, Iris for covers, and Forge for print-ready interior layout, export, and validation. Practical guides from the team that ships the tools.

← All posts