How to translate an EPUB novel into English and export a file you can read
Upload your EPUB to NovelVerba, approve the character-name table, translate in batches with a quote shown before you are charged, then export an EPUB for your e-reader. The translation is written back into your original book, so images, links, and most of the formatting stay intact. Vertical text, furigana, and drop caps are relaxed to fit English (see the limits section).
On this page
- What are the steps to translate an EPUB?
- Why is translating an EPUB harder than a TXT?
- What happens at each step?
- Write-back: why does the export keep its formatting?
- How do I export a bilingual EPUB to compare with the original?
- How do I check the EPUB I just exported?
- What does it cost, and how long is my data kept?
- What limits should I know before I start?

What are the steps to translate an EPUB?
| Step | What you do | Result |
|---|---|---|
| 1. Upload the EPUB | Pick your novel's EPUB file | Chapters split in the book's own reading order |
| 2. Scan proper names | Review character names, place names, and terms | The name table is used in every run |
| 3. Pick a batch | Choose a chapter range and see the quote | Priced by source characters, no hidden fees |
| 4. Translate and review | Read the finished chapter, fix flagged lines | Finished chapters are saved right away |
| 5. Export the EPUB | Download the EPUB or the bilingual EPUB | Images, links, and most formatting kept |
When the translation is done and you open it on your e-reader, tapping the table of contents takes you to the right chapter, the illustrations from the original are still in the book, and most of the formatting is kept. The table above is the five steps to that result.
Having an EPUB does not establish permission to copy and translate its contents. If the permitted uses are unclear, read Novel translation and copyright: three questions before uploading before sending the file to a service.
Why is translating an EPUB harder than a TXT?
An EPUB is not a plain text file. It is a zip package holding many HTML files (usually one per chapter), plus images, CSS, and a table of contents. Copying the text out, translating, and pasting it back by hand is the fastest way to ruin the book: lost bold and italics, broken table-of-contents links, shifted layouts, character names drifting chapter by chapter.
NovelVerba takes a different route: it reads the zip structure (container → OPF → spine), treats every document in the spine as a chapter in the book's original reading order, translates only the text inside text nodes, and writes the translation back into the exact same positions in your original file.
How to translate a whole web novel with AI: a 5-step workflowWhat happens at each step?
A long novel is not translated in one go but in batches, as in the steps below; how to split those batches so names and forms of address stay consistent from one batch to the next is covered in Translating a long novel in batches: where the next session picks up, and whether the names still match. Why a general chat window usually cannot translate a full EPUB and preserve its table of contents in one pass is examined in Can ChatGPT read and translate a full EPUB novel? Output limits and how to keep the table of contents.
- Upload the EPUB file. The system splits chapters by the book's spine. Each HTML document is one chapter, in the original document order.
- Scan proper names before translating. The AI lists character names, place names, and terms in the chapter range you choose; you decide each one: keep as-is, translate, or switch to the form you are used to. This name table travels into every translation run so characters do not change names halfway.
- Pick the batch range and see the price quote before pressing start. Cost is by source characters of the chapters in the batch, the number is shown for you to approve; no hidden fees.
- Translate chapter by chapter, watching progress live. Finished chapters are saved on the server right away. You can read and review immediately: flagged lines are marked, and you fix them line by line or retranslate the whole chapter. Close the tab mid-run and the run stops, but finished chapters are not lost: reopen the app and the system asks whether to continue with the rest. A chapter that was mid-translation when the tab closed may need to be translated and charged again.
- Export the EPUB. The translation is written back into the original EPUB: images, links, bold and italics, and most CSS are preserved; only the text is replaced, except three specific layouts that are loosened to fit English (listed under Limits). The exported file reads on an e-reader like the original book.
Write-back: why does the export keep its formatting?
Instead of building a new EPUB from translated text, NovelVerba reopens the exact zip package you uploaded, finds each paragraph by the positions recorded at split time, and replaces the text-node content with the translation. Inline tags (bold, links, line breaks) are preserved; leading and trailing whitespace follows the source; images and non-text assets are copied byte for byte.
Before export, every chapter passes a checkpoint: the source content must match the translated version exactly, and the translated line count must be complete. A chapter that fails (source tampered with mid-run, translation incomplete) triggers an error and the export is refused, rather than producing a "successful" file with raw source-language chapters inside. To resolve it, retranslate the chapter while its source text is still stored, or recreate the project from your original file if the source no longer matches what was translated.
An EPUB export rebuilds the book from your original EPUB file, so it needs that file still stored on the server. Once the original has been cleaned up under the storage policy, the download menu no longer shows the EPUB options; if the file is still stored but can no longer be read, the EPUB download reports an error. TXT, Markdown, and SRT exports do not depend on this file.
The book's metadata language (dc:language) is set to your project's target language (English in this walkthrough) so e-readers shelve the translation under the right language.
How do I export a bilingual EPUB to compare with the original?
If you want to compare while reading, choose the bilingual export: each source paragraph is inserted right before its translation in the same book, marked by a gray left border, smaller type, and a dimmer color, styling attached to each paragraph directly, so it renders even on readers that ignore the book's CSS files.
Besides EPUB and bilingual EPUB, the translation can also be exported as TXT, Markdown, or SRT. In the download menu, the bilingual form is available for TXT and EPUB; Markdown and SRT export the translation only. The two bilingual routes take the original text from different places. Bilingual TXT pairs each chapter with the source copy stored in the app: once a chapter's source text has been cleaned up under the storage policy, its original text is missing from the bilingual TXT, so the file still downloads but is no longer a complete bilingual version.
Bilingual EPUB takes the original text from your original EPUB file itself. That file is kept on the server specifically so EPUB export stays possible, which is why a bilingual EPUB still carries the full original even when a chapter's stored source text has been cleaned up. Once the original file is removed after 30 days without activity (see the data section below), EPUB and bilingual EPUB exports are no longer available.
How do I check the EPUB I just exported?
The steps below are a visual check. To check the file's package structure, metadata and table-of-contents links, use Check your EPUB before reading or translating. If the text is too small or the margins are off on your e-reader, Optimize EPUBs for your e-reader screen re-lays out the book for that screen size; see EPUB for e-readers: choose an export format, check for errors, and fit the screen for preset choices by device. Both tools run in your browser; the file is not uploaded to a server. How to keep the book title and chapter titles aligned with the table of contents is in Translating web novel book and chapter titles: keeping names aligned with the table of contents, and how to send the exported EPUB to a Kindle is in How to send a translated EPUB novel to Kindle and check for file errors before sending.
- Open the file right after downloading: chapters should follow the book's original reading order from start to finish.
- Flip through a few chapters in the middle: translated text sits where the original used to be; once every chapter has been translated, no source-language chapters remain (untranslated ones are kept in the source language, see below). In a bilingual EPUB, each translated paragraph has its original right above it behind a gray left border.
- The app warns you before downloading about chapters where translation failed and no translation is available. Check for chapters you have not translated yet yourself, since this warning does not count them. TXT, Markdown, and SRT leave chapters without translations out of the file, while EPUB keeps their original text. You can translate them first or download the file as it is.
- Try the table of contents and look at a few images: TOC links should land on the right chapters (TOC labels may stay in the source language) and illustrations should still display.
- Check the book's language information on your e-reader: it records your project's target language so the device shelves the book correctly. A download is generated fresh from the current translation, so after fixing lines in the app, export again to get an updated file.
What does it cost, and how long is my data kept?
Pricing is per source character: you pay for the characters of the chapters you translate, not a monthly subscription. Before every translation batch or name-scan run, the system shows a quote for you to approve before credits are deducted.
Chapter source text and the uploaded EPUB follow different deletion rules. Once the whole novel is translated, the app deletes the source text of chapters that are no longer marked for review. Source text for chapters still marked for review is kept so you can fix lines, but that retained source is still subject to the 30-day limit without translation or editing activity. Once the whole novel is translated, the chapter’s source text is deleted as soon as you save the change that clears its review flag. The original EPUB file is kept separately just so EPUB exports remain possible, and cleaned up after 30 days without any translation or editing activity. The 30 days count inactivity, not the age of the file.
This cleanup does not delete your project: the title, your name table, translation settings, and the full translation all remain. You can still read the translation and download translation-only TXT, Markdown, or SRT files. EPUB export requires the original EPUB file to still be stored. Asking to retranslate a chapter whose source is gone is refused; the app states that the original was deleted under the storage policy and points you to starting a new project from your original file.
The translation belongs to your project and does not expire on its own; to keep it outside the service, download a copy to your own device.
Privacy Policy: the lifecycle of content you uploadWhat limits should I know before I start?
Three layout specifics of Chinese/Japanese books are deliberately loosened when exporting to fit English: vertical text layout (CSS writing-mode: vertical-rl) is removed because the translation reads horizontally; furigana annotations (ruby) are unwrapped, keeping the translated base characters. English readers do not read kana; decorative drop caps keep their shell only when the translation lands on exactly one character, otherwise the shell is opened so the whole word is not blown up. Outside these three cases, the book's CSS and assets are untouched.
NovelVerba translates from Chinese, Japanese, and Korean into Vietnamese, English, Indonesian, Thai, Spanish, Arabic, Brazilian Portuguese, or German; this page follows an English-target project. The translation is AI-generated: proper names and style depend on the setup you lock at the name-scan step, and chapters are long, so review before treating a translation as final.
Books using UTF-16 encoding (some older EPUBs) are currently refused at write-back export to avoid character corruption, in that case, convert to a UTF-8 EPUB or use the TXT route.
Only use content you own or have the right to translate.
Questions about this page: [email protected]