eBook Quality Checklist: Test Your EPUB Before Publishing

An eBook quality checklist should test what readers can do, not just whether the opening page looks attractive. Before publishing your EPUB, check chapter navigation, text resizing, images, links and the reading order. Test the actual exported file, then repeat the important checks after any correction.
A print PDF can look excellent while an eBook has broken navigation or awkward spacing. The two formats serve different reading environments. This guide is for a typical reflowable text-based eBook; an illustrated fixed-layout book needs checks suited to that format.
Start your eBook quality checklist with the right file
Give each export a clear version name and record the date. Keep the source manuscript, working exports and approved delivery in separate folders. When someone reports a problem, you should be able to identify exactly which file they opened.
Amazon’s reflowable-book guidance explains that text-heavy books adapt when readers change their text settings. A line moving to another screen is therefore expected behavior. Missing text, overlapping elements or an unusable link is a different matter.
Use Kindle Previewer when preparing for KDP. Its device, orientation and font-size options help expose problems hidden by one comfortable desktop view. If you publish elsewhere, also use that destination’s preview or recommended reading software. A successful check in one application does not prove every reading system behaves identically.
1. Test every route through the contents
Open the visible contents page and select each entry. Confirm that it reaches the correct heading, rather than the previous chapter, an empty screen or the middle of a paragraph. Then test the reading application’s navigation menu separately.
These are related but distinct navigation routes. KDP’s Kindle Create guidance describes both a linked contents page and a Kindle Interactive table of contents. An attractive list of chapter names is not enough if those routes do not work.
Check introductory material, numbered chapters, appendices and other intentional sections. Look for duplicate entries or missing parts. If you used subheadings, make sure the hierarchy helps readers rather than turning every small heading into an overwhelming menu.
2. Increase the text size and rotate the screen
Read several representative passages with larger text and in landscape orientation. Include the opening chapter, a long heading, a list and a passage with italics. Check that words remain visible and that paragraphs do not acquire enormous gaps.
Hypothetical test: a chapter heading looks neat at the default size but splits into six short lines on a phone with enlarged text. Ask whether the heading still reads naturally and whether the surrounding spacing remains sensible. Do not force the entire book into tiny text just to preserve the original page shape.
Reflowable pages will not match the print pagination. Judge the reading experience and sequence, not whether the same paragraph stays at the same vertical position on every device.
3. Inspect images, tables and captions together
Look at each meaningful image at phone size. Can the reader understand it without struggling to decipher tiny labels? Does its caption remain associated with the correct figure? Are image descriptions present where needed for accessibility, rather than a filename that conveys nothing?
For a complex chart, review whether its information should also be explained in nearby text. A caption saying “Chart 2” cannot replace the meaning of the chart. Decorative images and information-bearing diagrams need different treatment.
Amazon’s table guidance favors actual HTML tables over images of tables, with attention to readability and assistive technology. If a table is too wide, discuss restructuring it rather than shrinking an entire page into a photograph.
4. Follow the links and return paths
Test internal cross-references, footnotes and their return links. A note should not leave readers searching for the sentence they were reading. Review external links for spelling, relevance and destination restrictions set by the platform.
Use descriptive link wording when it helps someone understand the destination. “Download the practice worksheet” is more useful than a long unexplained URL, provided the destination genuinely supplies that worksheet.
Also check that no production-only link remains: a private file, an editor’s temporary document or a placeholder website. Do not click through a purchase or submit a form simply to check a destination; opening the intended public page is enough.
5. Read the beginning, transitions and ending
Automated conversion does not establish that the correct text was exported. Compare the title, author name, copyright details, first paragraphs, scene breaks and ending against the approved source. Confirm that comments, instructions and draft placeholders have not entered the reading copy.
Scan chapter boundaries for missing paragraphs or accidental repetition. Read the final sentence and back matter. A clean opening can conceal an incomplete ending when the wrong file was exported.
For broader quality expectations, refer to KDP’s content-quality guidance. Treat preview checks as part of quality assurance, not a guarantee of platform acceptance.
Use an issue log your formatter can act on
Record file version, application/device setting, location, observed problem and expected result. Add a screenshot when it makes the problem clearer. Use one row per issue and mark it open, fixed or retested.
Example: “EPUB v3; phone portrait; large font; contents entry ‘Chapter 6’ opens Chapter 5. Expected: Chapter 6 heading.” This is more useful than “the contents are wrong.”
Prioritize problems that prevent reading or change meaning. After a fix, retest the issue and the related section. If the contents were rebuilt, test all entries again. Retain the final approved filename so a working export is not uploaded by mistake.
Get help preparing the reader-ready file
Publishing Spot’s print and eBook formatting service includes EPUB output and a linked table of contents for the eBook work in your agreed package. Share your final manuscript, intended platforms and any complex tables or illustrations before choosing scope.
Bring your issue log if a file already exists. Discuss your eBook formatting project so the team can review what needs preparation or correction. Formatting supports the reading experience; it does not replace editorial review.
Official platform guidance checked October 27, 2026. The test sequence and example issue log are practical suggestions; adapt them to your book and destination.




Comments