How to Validate EPUB Files Before You Publish

A clean-looking ebook can still fail at upload. That is why learning how to validate EPUB files matters before your book reaches KDP, Apple Books, Kobo, or a distributor. Retailers do not judge the EPUB by its cover. They inspect the package, metadata, navigation, code structure, images, and accessibility details behind it.

Validation is not busywork. It is the final technical check between a finished manuscript and a rejection notice that forces you back into your files. For serious self-publishers, it is part of the production process, just like proofreading the manuscript or approving a cover proof.

What EPUB Validation Actually Checks

An EPUB is not one document. It is a compressed package containing HTML or XHTML content files, CSS stylesheets, images, fonts, metadata, a table of contents, and a set of instructions telling e-readers how those pieces fit together.

An EPUB validator checks whether that package follows the EPUB specification. In plain terms, it looks for structural problems that can break a book on an e-reader, create inconsistent formatting, or cause a retailer to refuse the upload.

A validator can identify issues such as missing files, invalid HTML, unsupported CSS, broken image references, duplicate identifiers, faulty navigation documents, and incomplete metadata. It may also flag warnings that do not stop an upload but could create a poor reading experience.

That distinction matters. A file can technically pass validation and still look wrong on a Kindle, phone, tablet, or larger e-reader. Validation confirms that the EPUB is built correctly. Quality control confirms that the reader experience is correct. You need both.

How to Validate EPUB Files Step by Step

Start with a finished, stable export

Do not validate an EPUB while the manuscript is still changing every hour. Finalize your text, chapter order, headings, front matter, back matter, and image placement first. Then export a fresh EPUB from your formatting tool.

Use a clear file name with a version number, such as `MyBook_EPUB_v3.epub`. This prevents a common production mistake: fixing one file, then accidentally uploading an older version later.

Run the file through an EPUB validator

The standard technical validator used across the publishing industry is EPUBCheck. Many publishing platforms and formatting tools rely on the same underlying EPUB rules, even if their reporting screens look different.

Upload or open your EPUB in a validation tool and review the report from top to bottom. Do not stop at the first message. One incorrect reference can trigger several related errors, and fixing the root issue often clears multiple alerts at once.

Errors need action. Warnings need judgment. If a validator reports an error, assume the file is not ready until you understand and resolve it. If it reports a warning, assess whether it affects retailer acceptance, accessibility, or the reader's experience.

Fix the source, not just the exported file

This is where many authors lose time. If you manually edit an EPUB file after export, the fix can disappear the next time you make a manuscript change and export again.

Whenever possible, correct the problem in the source document or the formatting project. For example, fix a broken image in the layout tool, update an incorrect heading in the manuscript, or replace unsupported styling in the book's formatting settings. Then export a new EPUB and validate it again.

Direct EPUB editing can make sense for an experienced formatter handling a small code-level fix. It is not the best default workflow for most authors. The more manual patches you apply, the harder it becomes to maintain a reliable master file.

Revalidate after every correction

Validation is iterative. Fix an issue, export a new version if needed, and run the check again. Continue until the report is clean or until every remaining warning has been deliberately reviewed.

Keep a short production log if you are working through several issues. Note the file version, the error, the correction, and the result. This is especially useful for books with tables, footnotes, images, complex front matter, or multiple contributors.

Common EPUB Errors and What They Mean

Most validation problems fall into a few predictable categories. The message itself may look technical, but the underlying cause is usually straightforward.

Broken links and missing resources

An EPUB may reference an image, stylesheet, font, or chapter file that is no longer included in the package. This often happens after replacing images, rearranging chapters, or importing content from another document.

Check that every image appears where expected and that internal links point to real destinations. A broken endnote link or table of contents entry may not always stop publication, but it makes the book feel unfinished.

Invalid or messy HTML

EPUB content is built with web-style markup. Copying text from word processors, websites, or older documents can introduce malformed tags, empty links, unclosed formatting, and invalid characters.

The solution is usually to clean the source formatting rather than paste more code on top of the problem. Strip unnecessary styling, apply consistent paragraph styles, and use real heading levels instead of manually enlarging or bolding text.

Navigation and table of contents problems

A functional table of contents is not optional in a professional ebook. EPUB navigation should reflect the book's real structure and take readers to the correct chapter or section.

Use consistent headings for chapter titles. If some chapters are styled as headings and others are simply bold text, automatic navigation can become incomplete or inaccurate. Also check the table of contents on an actual device or reading app after validation, because a technically valid menu can still be poorly organized.

Metadata errors

Metadata includes the title, author name, language, publication identifier, and other book information stored inside the file. Incomplete or conflicting metadata can create retailer warnings, display inconsistencies, or confusion when multiple editions exist.

Make sure the title and author information match the details you plan to enter on the retailer's dashboard. Small mismatches, such as a different subtitle or author middle initial, can create unnecessary questions during publication.

Image, font, and accessibility issues

Large images can make an EPUB slow to download or unstable on older devices. Missing alternative text can also reduce accessibility for readers using screen readers. Embedded fonts may cause licensing, display, or file-size issues depending on the retailer and reading device.

Use images only where they support the book, compress them appropriately, and include meaningful alternative text when an image carries information. Decorative images may not need detailed descriptions. Charts, diagrams, and instructional visuals do.

Validation Is Not the Same as Retailer Preflight

A generic EPUB validator checks EPUB standards. Retailers add their own rules. KDP may handle a formatting feature differently than Apple Books, Kobo, or an IngramSpark distribution workflow. A file that passes EPUBCheck is in good technical shape, but it is not automatically cleared for every sales channel.

That is why the strongest workflow uses two layers of checking. First, validate the EPUB structure. Second, run a retailer-specific preflight that checks the standards of the platform where you plan to submit.

Retailer preflight catches problems closer to the real upload environment: required metadata fields, file size limits, cover pairing issues, unsupported elements, and platform-specific formatting behavior. If you are distributing widely, test against each important destination rather than assuming one successful upload proves universal compatibility.

Tunmire's validation system is built around this practical reality: authors need more than a generic pass or fail. They need publishing files checked against KDP and IngramSpark requirements before submission, while the manuscript, layout, and export remain in the same workflow.

Test the Reading Experience After Validation

Once the EPUB passes technical checks, open it in more than one reading environment. A phone is useful for spotting cramped tables, oversized images, and awkward page breaks. A tablet helps you assess hierarchy and spacing. An e-reader view shows how the book holds up in the format many buyers will actually use.

Check the beginning, middle, and end of the book. Open every chapter from the table of contents. Test footnotes, endnotes, web links if included, image captions, scene breaks, and any special elements such as poetry, recipes, callout boxes, or tables.

Pay close attention to reflowable behavior. Readers can change font size, margins, line spacing, and screen orientation. A well-built EPUB should remain readable when those settings change. If the design only works at one font size, the formatting is too fragile.

Build Validation Into Your Publishing Workflow

The cheapest time to catch an EPUB error is before upload. The second-cheapest time is before readers buy the book. After publication, a formatting correction can mean replacing files, waiting for updates, managing reviews tied to a flawed edition, and explaining avoidable problems to readers.

Treat validation as a release gate. Your EPUB is ready to submit only when it passes technical validation, meets the retailer's requirements, and has been reviewed in real reading conditions. That discipline protects your launch, your time, and the professional standard your book deserves.

A reader should never have to notice the machinery behind your ebook. When your file is validated properly, they can focus on the story, the argument, or the work you put on the page.