Tunmire Publishing and Media

How to Validate EPUB Files Before You Publish Your Book

How to Validate EPUB Files Before You Publish Your Book

To validate an EPUB before publishing, you need to test the actual file your reader will open, not just confirm it exported without an error message. A clean-looking ebook on your desktop can still have broken navigation, missing images, invalid code, or styling that fails inside a retailer's app. Those problems can delay distribution, trigger a platform rejection, or leave a paying reader with a book that feels unfinished.

EPUB validation belongs in your production checklist alongside proofreading, cover review, and print-ready PDF checks. It is the last technical inspection before your formatted manuscript goes out to readers.

Why a validated EPUB protects your release

An EPUB is not one fixed page. It is a packaged set of content files, style rules, images, metadata, and navigation instructions that a reading system interprets on its own terms. Kindle apps, Apple Books, Kobo devices, library platforms, and browser readers do not all render that package the same way.

That flexibility lets ebooks adapt to different screens, but it also means a file that looks fine in one app can fail in another. A chapter heading might lose its spacing, an image may overflow a narrow screen, a footnote link can lead nowhere, or the table of contents may skip a section entirely.

Technical validation catches structural problems. Reading the book on real devices catches presentation problems. You need both, because passing one does not guarantee the other.

A validated file also gives you a clean production record. If a retailer flags an issue after launch, it's much harder to figure out whether the problem started in the manuscript, the conversion, or a last-minute file swap. A defined validation step makes your final EPUB a deliberate release, not a hopeful export.

A two-part check to validate your EPUB

The most reliable workflow has two separate passes: standards validation, then reader-facing review. Treat them as different jobs with different questions.

1. Run a standards validation first

Use an EPUB validation tool that checks the file against current EPUB specifications. It examines the package structure, markup, metadata, image references, navigation documents, and other technical requirements, then reports errors, warnings, or deprecated elements.

Fix errors immediately. They often point to conditions that cause rejection or unreliable rendering, such as a referenced image that isn't included in the package, malformed code, invalid identifiers, or a broken table of contents file.

Warnings need judgment. Some are harmless leftovers from conversion; others signal code that works now but causes trouble in a specific storefront or a future reader update. Don't dismiss a warning just because the file technically passes. Check what it actually means for your book.

If you revise the EPUB after fixing something, validate the new export again. It sounds obvious, but it's common to confirm one version and then upload a different one after a late metadata, cover, or copyright-page change.

2. Review the book the way a reader will

A validator can't tell you whether a scene break is obvious, whether an image is too small to read, or whether your opening pages make the professional first impression your book deserves. Open the final EPUB in more than one reading environment.

At minimum, check it on a phone-sized screen and on a larger tablet or desktop reader. If your readers use a particular storefront heavily, prioritize that storefront's preview or app. Reflowable EPUBs respond to screen size, font, line spacing, and margins, so test with a larger type size as well as the default.

Start at the cover, then move through the book in order. Confirm that the title page, copyright page, dedication, epigraph, and table of contents appear where they should. Jump from the contents to a few chapters and back to the beginning. Search for a recurring term. Open every internal link, web link, footnote, and linked resource that matters.

Then look closely at the sections most likely to expose formatting problems: chapter openings, block quotes, lists, poetry, tables, captions, image-heavy pages, appendices, and back matter. A straightforward novel usually needs a faster visual pass; a cookbook, textbook, poetry collection, or reference guide needs much more device testing because its layout depends on elements that reflow less predictably.

Details that commonly fail in EPUB production

The same defects show up again and again in self-published ebooks, usually because they're easy to miss in an editing view.

Navigation comes first. Readers expect the table of contents to list the right chapters, use clear labels, and jump to the correct spot. A table of contents with duplicate entries, placeholder headings, or links to the wrong chapter tells the reader something is off before they've read a page.

Check metadata next. Title, subtitle, author name, language, publisher, publication date, and identifier should match both your distribution record and the visible title page. Inconsistent metadata creates confusing listings and makes version management harder, especially across a series or backlist.

Images need close review. Confirm every image is present, sharp enough for its purpose, correctly positioned, and has useful alternative text when it conveys information. Decorative images can use brief or empty alternative text; informational charts, diagrams, and photos need real descriptions, not filenames.

Styling problems are often subtler. Avoid using repeated blank paragraphs or spaces to force visual gaps; those shortcuts can collapse or behave oddly in another reader. Use consistent style rules for paragraph spacing, scene breaks, headings, indents, and page breaks, so the book adapts gracefully when a reader changes font size instead of clinging to a layout trick built for one screen.

Finally, check the cover and opening sample. Retailers may generate their own thumbnails, but the embedded cover still needs to display correctly inside the book itself. The opening pages shouldn't contain accidental blank screens, leftover placeholders, or internal production notes. A reader downloading a sample is judging your standards as much as your writing.

Build validation into your workflow

Validation works best when it isn't the first time anyone sees the formatted ebook. Start with a clean manuscript whose headings and paragraph styles carry real structural meaning. That produces a far more stable export than manually formatted text full of one-off overrides.

Once editorial changes are done, build the ebook layout, export the EPUB, and run the technical validator. Fix issues at the source whenever you can, repairing the heading style or image reference in the production file rather than patching a single exported EPUB you'll have to recreate later.

After the file passes, do the reader-facing review. Keep a short release checklist: navigation, metadata, cover, links, special formatting, images, and the final back-matter call to action. Series authors should add series naming and links to the next book. Nonfiction authors should check tables, notes, citations, and index behavior.

When the review is done, freeze the approved version. Name it clearly with the title, edition, and date or version number, and store it with the matching cover files and print-ready PDF. This matters when you revise a book years later, issue a new edition, or need to trace which file went to which retailer.

Tunmire's Forge lays out your manuscript and exports both a print-ready PDF and a validated EPUB, so you can move from interior layout to a file ready for distribution without handing formatting off to a separate tool.

Retailer acceptance is not the same as quality assurance

A retailer may accept an EPUB that still has reader-facing defects. Acceptance means the platform processed the file under its current rules, not that every link, image, screen size, and detail got the attention your book deserves.

The reverse happens too: a file can pass a general validator and still need a storefront-specific adjustment, because a retailer has extra delivery rules or handles a feature differently. That's not a reason to skip validation. It's a reason to treat validation as the baseline, then complete whatever retailer-specific review your chosen channels require.

Your ebook is a finished reading experience, not a converted document. Give the final file the same care you'd give a print proof: inspect it, test it, approve it on purpose, and publish only the version you're ready to put your name behind.

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