How to Test a Translated EPUB on Kindle, Kobo, and Apple Books

A translated EPUB is not ready because it opens in one desktop app. Validate the package first, then test the exact final file in every reading system that matters to the release. Kindle conversion, Kobo processing, and Apple Books can expose different failures in navigation, fonts, reflow, images, notes, metadata, and right-to-left text.

Download the cross-reader EPUB test matrix and create one row per check, platform, device class, and final file build. The matrix deliberately has no prefilled pass results: a generic screenshot is not evidence for your edition.

Start With Validation, Not Visual Inspection

An EPUB is a ZIP-based publication package, not a single page. The W3C EPUB 3.3 specification defines a container, package document, manifest, spine, navigation document, and content resources. A reader may recover from a malformed link or missing declaration, so “it opened” does not prove conformance.

Run the current production release of EPUBCheck against the translated file before platform testing. Resolve errors first. Review warnings and usage messages against your target EPUB version and release requirements instead of automatically ignoring or promoting all of them.

Validation and reader testing answer different questions:

Keep the validation report with the build it describes. If you change the EPUB after validation, create a new build identifier and rerun the check.

Build a Small but Defensible Test Matrix

Testing every device is impossible. Testing one convenient app is weak. Choose environments from the actual distribution plan and the risks in the book.

At minimum, record:

• exact EPUB filename or hash;
• build date;
• platform, app or device, version, and operating system;
• viewport, orientation, theme, and font setting where relevant;
• chapter or feature tested;
• expected behavior;
• actual result and severity;
• screenshot, video, log, or written evidence; and
• fix and retest status.

Select representative locations before opening the first reader:

1. the cover, title page, and metadata;
2. the first table-of-contents entry and a deeply nested entry;
3. an opening, middle, and final chapter;
4. the longest translated heading and paragraph;
5. a footnote with its return link;
6. an image, caption, list, and table if present;
7. mixed scripts, uncommon characters, or RTL passages;
8. search, text selection, and text-to-speech where required; and
9. the end of the book, so truncation cannot hide behind a good opening.

Use the same locations on every platform. That turns three casual reading sessions into comparable evidence.

Test the Kindle Edition After Conversion

Amazon recommends using Kindle Previewer while formatting an ebook. Its documented controls include device type, orientation, font choices, feature filters, and auto-advance. Amazon's content-quality guide also identifies common problems such as typos, unreadable image text, missing or poor covers, and formatting that limits reader customization.

For a translated EPUB:

1. Open the exact candidate file in the current Kindle Previewer.
2. Record any conversion or import messages.
3. Test phone, tablet, and e-reader views relevant to the audience.
4. Increase and decrease font size; change orientation when available.
5. Open the interactive TOC, notes, internal links, and external links.
6. Use feature filters to inspect images, lists, and tables where available.
7. Run auto-advance as a completeness sweep, then manually inspect high-risk locations.
8. If publishing through KDP, repeat the checks in the Online Previewer after upload because the uploaded pipeline is part of the delivery path.

Do not label a source EPUB “Kindle tested” when only an unrelated MOBI, KPF, or earlier build was inspected. Record the conversion input and the platform output being approved.

Test the Kobo-Processed File

Kobo's official validation and testing guidance says an uploaded file is converted to a Kobo-formatted EPUB and provides a “Download and preview this eBook” path. It also states that viewing the book on a Kobo eReader or Kobo app is the way to see the Kobo reader experience.

That makes the processed file—not only the file on your computer—the relevant artifact.

1. Upload the release candidate through the normal Kobo workflow.
2. Download the preview file produced for the title.
3. Open it in at least one Kobo environment used by the audience.
4. Test the same TOC, note, image, typography, and completeness locations used for Kindle.
5. Check bookmarks, highlights, search, and annotation behavior if they are acceptance requirements.
6. Record whether the result came from Kobo Desktop, a mobile app, or a specific eReader.

If the uploaded file changes, repeat the Kobo processing and tests. Evidence for yesterday's processed file does not approve today's source.

Proof the File in Apple Books

Apple states that EPUB books must pass validation at import and documents package failures such as invalid URI characters, resources missing from the manifest, and unsupported encodings in its book-validation guide. Apple Books supports EPUB 3.3 and earlier EPUB 3 versions, with different behavior for reflowable and fixed-layout books, as described in its digital-books overview.

Use Apple Books' proof workflow for the final candidate:

1. Add the EPUB as a proof using the current Apple Books publishing instructions.
2. Test it on the Mac and, when iPhone or iPad readers are in scope, on those device classes.
3. Change text size, orientation, theme, and window size for a reflowable book.
4. Test navigation, notes, images, language changes, search, selection, and read-aloud behavior required by the project.
5. Inspect fixed-layout pages at the smallest supported viewport rather than approving only a large tablet view.
6. Record import or validation failures separately from visible rendering defects.

Apple's formatting and content guidelines also call out incomplete books, missing referenced material, overlapping content, and scanned body text. Those are useful release checks even when the translated file passes structural validation.

Test Translation-Specific Failure Modes

The same source EPUB can fail only after translation because the target language changes text length, script, direction, or font requirements.

Reflow and clipping

Test the longest headings, captions, table cells, buttons, and notes at large font sizes and narrow viewports. Fixed heights, forced line breaks, and positioned boxes that tolerated the source language can clip the translation.

Fonts and character coverage

Search for tofu boxes, missing combining marks, incorrect joining, substituted weights, and characters falling back to a visibly different font. Check regular, bold, italic, and emphasized text separately. A successful English view says nothing about Arabic shaping or CJK coverage.

Navigation and notes

Open every TOC entry at least once with an automated link report or manual sweep. Manually test representative footnote and endnote links in both directions. Translated labels can look correct while the underlying fragment target is missing.

Search, copy, and text-to-speech

Confirm translated body text remains real text where the reading system supports these actions. Test a distinctive target-language phrase in the opening, middle, and final chapter. If text-to-speech is in scope, check that language metadata and mixed-language passages produce acceptable behavior in the actual supported system.

Metadata and bookshelves

Inspect the title, author, translator credit, cover, publication language, reading direction, and series information as displayed by the reader. Package metadata and retailer metadata are separate inputs; record which one you are reviewing.

Use Severity to Decide Whether to Release

Retest the exact final build. If a shared CSS or package fix resolves a Kobo defect, rerun the related Kindle and Apple Books checks because the same change can create a regression elsewhere.

Final Cross-Reader Release Gate

Approve the translated EPUB only when:

• the final file passes the chosen EPUBCheck gate;
• the source and translated edition inventories match;
• TOC, spine order, notes, images, and metadata pass;
• target-language fonts, direction, and reflow pass at risky settings;
• the retailer-processed or previewed artifacts correspond to the final build;
• every required Kindle, Kobo, and Apple Books environment has recorded evidence;
• all blockers and majors are fixed and retested; and
• a qualified target-language reviewer has approved representative content.

If you still need to produce the translated file, BookTranslator's EPUB translator can create a complete-file draft for review. If the edition contains both source and target text, use the bilingual EPUB workflow before applying this cross-reader release matrix.