Skip to main content

Sending your translated EPUB novel to Kindle: pick the right Send to Kindle channel, check package errors, and set screen margins

Tri Thu知秋

· Updated

On this page

According to official Amazon Send to Kindle documentation, you can send a DRM-free .epub file to your Kindle library via Web browser (up to 200 MB) or via an authorized @kindle.com email address (up to 50 MB). Before sending, run a quick browser check on the package structure, dc:language tag, and table-of-contents links with the EPUB Validator to prevent file rejection errors.

On an ancient stone terrace beneath green pine boughs overlooking a golden sea of clouds at sunset, a female swordswoman in celadon jade and cream classical robes leans against a stone balustrade, holding a flat bronze-rimmed jade tablet glowing softly with neat rows of text and a side chapter list beside an open wooden casket holding a cinnabar-sealed bamboo scroll and a white carrier pigeon perched on a stone post.
Inspecting the chapter package structure and setting comfortable page margins before sending a newly translated novel to your Kindle library.
Delivery channel or pre-send stepAmazon limits and requirementsWhat to check before sending
Send to Kindle on the Web (amazon.com/sendtokindle)Accepts DRM-free .epub files via drag-and-drop in the browser up to 200 MB per file and syncs to your account libraryDrop the file into the browser EPUB Validator (up to 50 MB) to check 12 package structure, dc:language, and TOC items
Send to Kindle by Email (@kindle.com)Accepts attached .epub files up to 50 MB total (up to 25 files per email) from an address on your Approved Personal Document E-mail ListVerify the file is under 50 MB, the sender address is approved under Manage Your Content and Devices, and toc.ncx links work
Pre-tune margins for 6-6.8 inch or 7-8 inch screens (optional)Run the browser EPUB Optimizer (up to 50 MB per file) before uploading via Web or attaching to EmailPick the 6-6.8 inch preset (16px margin, 1.55 line spacing) or 7-8 inch preset (22px margin, 1.6 line spacing); verified on Calibre 9.13.0 desktop

How does Kindle accept a translated EPUB novel through Amazon Send to Kindle?

Readers who finish exporting a translated web novel as an .epub file on a computer or phone often hit a roadblock when moving the book to a Kindle e-reader: copying a raw .epub over a USB cable into the device folder does not make it show up like on other e-readers, while sending an unverified file online sometimes triggers a delivery failure notice. According to Amazon's official documentation, the Kindle ecosystem accepts .epub files (without DRM) through Amazon Send to Kindle and syncs the book into your account library for reading across Kindle devices and Kindle apps.

The first and most convenient route for long multi-chapter novels with illustrations is the official Web uploader at amazon.com/sendtokindle. Once signed in to your Amazon account, you can drag and drop your .epub file directly in the browser with a maximum file size of 200 MB. The second route is emailing the .epub file as an attachment to your dedicated @kindle.com address. According to Amazon's official help page Learn How to Use Your Send to Kindle Email Address, email delivery supports up to 50 MB total (up to 25 attachments per email), provided you first add the sender address to your Approved Personal Document E-mail List under Manage Your Content and Devices.

Keep two strict boundaries in mind: both channels only accept personal DRM-free .epub files, and this guide covers only legitimate personal or translated files rather than bypassing DRM on commercial books. In addition, Amazon's Tier-1 documentation specifies that Send to Kindle accepts .epub files and syncs them to your library without detailing internal server conversion steps, so your sole task is preparing a well-formed .epub archive before uploading. For the full EPUB translation workflow from Chinese, Japanese, or Korean, see How to translate an EPUB novel into English and export a file you can read. If your source file is still in PDF or DOCX before uploading, check Translate a novel from a PDF file: which format should you convert it to before uploading?

Why does an EPUB open fine on a computer but fail or lose its table of contents in Send to Kindle?

A common frustration when reading translated novels is that an .epub file opens without complaint in a desktop reader app, yet fails processing when uploaded to Send to Kindle or arrives on your e-reader with a missing chapter menu. Desktop apps frequently ignore minor archive mistakes, whereas automated ingestion gateways processing .epub uploads are sensitive to 3 categories of structural flaws inside the zip container.

First are container shell and metadata errors: a compressed or misplaced mimetype entry, a missing or misrouted META-INF/container.xml file, or missing dc:title and dc:language declarations inside the .opf package document. Second are broken table-of-contents links: a toc.ncx or nav.xhtml file pointing to a chapter file renamed or dropped from the manifest when chapters were merged manually. Third are leftover traits from Chinese or Japanese source files, such as UTF-16 encoding or vertical typesetting rules (writing-mode: vertical-rl). This is also why copying chapters through a chat box and re-zipping them by hand often breaks the table of contents; read Can ChatGPT read and translate a full EPUB novel? Output limits and how to keep the table of contents.

Instead of uploading a book and waiting to see whether an error email comes back, drop your exported file into EPUB Validator: Check EPUB Files Before Reading or Translating. The tool runs in your browser (without uploading your book to a server, supporting files up to 50 MB) and checks 12 items across package structure, metadata, and table-of-contents links. I also want to state its limit clearly: this browser check inspects 12 common structural, metadata, and navigation points so you catch broken archives early, but it is not equivalent to EPUBCheck and does not guarantee that every file passing the check will never be rejected.

Check group in EPUB Validator (12 checks)Files and tags inspected in the browserWhy it matters before Send to Kindle
ZIP container shell and package rootChecks the leading mimetype entry, META-INF/container.xml, and the path to the .opf package fileEnsures the archive is a valid EPUB container from the first byte so the upload gateway can open it
Required metadata and spine reading orderChecks dc:title, dc:language, manifest resource declarations, and the sequential spine reading orderHelps the library recognize the target language and keeps chapters in the proper reading sequence
Table-of-contents links and internal resourcesCross-checks nav.xhtml and toc.ncx targets against XHTML chapter files and flags missing imagesPrevents unresponsive chapter menus or missing illustrations after the book syncs to your Kindle

How do a format-preserving (write-back) EPUB and a rebuilt EPUB from TXT display differently on Kindle?

When you translate a novel on NovelVerba and export an .epub file for your Kindle e-reader, the platform offers two export paths depending on what source file your project started from. Both exports automatically clean up the package traits that most often trip up Send to Kindle, while differing in whether they preserve the original layout or build a fresh one.

If your project started from an original .epub file, the format-preserving (write-back) EPUB reopens the original zip archive, preserves the container.xml -> OPF -> spine/manifest/toc structure along with illustrations, and writes translated paragraphs back into place. NovelVerba's writer automatically performs three adjustments: it updates dc:language in the .opf file to match your target language (vi, en, id, es, th, ar, pt-br, or de), strips vertical text rules (writing-mode: vertical-rl) from Chinese or Japanese books so lines read horizontally, and rejects UTF-16 source files up front.

By contrast, when you translate from a plain-text .txt file (or build a new EPUB from translated chapters), the builder outputs a newly constructed .epub package. On the browser TXT builder path, the exported book follows the EPUB 2.0 specification with a complete toc.ncx navigation file and a valid target dc:language tag. Because a rebuilt EPUB contains clean XHTML chapters without heavy publisher stylesheets, the file stays compact under the 50 MB limit for @kindle.com email delivery and takes screen-size margin presets cleanly.

How do you pre-set page margins and line spacing for a 6-6.8 inch or 7-8 inch Kindle screen?

Web novels feature rapid dialogue and short paragraphs; if you leave the raw stylesheet of a Chinese or Japanese source book untouched on a 6-inch to 8-inch screen, you may end up with cramped margins, tight line spacing, or double-indented paragraphs from full-width ideographic spaces stacking on CSS indentation. To tune the page layout before uploading to Send to Kindle, open EPUB Optimizer: Reformat EPUB Books for Your Kindle, Kobo or Xteink in your browser (supporting files up to 50 MB per file without server upload).

Inside the EPUB Optimizer, two presets target common Kindle screen classes: the Kindle 6-6.8″ preset (profile key paperwhite) sets page margins to 16px, line spacing to 1.55, paragraph indent to 1.2em, justified alignment (justify), and disables hyphenation (hyphens: none); meanwhile, the 7-8″ preset (profile key oasis) sets page margins to 22px, line spacing to 1.6, and paragraph indent to 1.3em with justify and hyphens: none for wider panels.

One hardware verification boundary I always state transparently: all current structural and layout checks in the system are verified on the Calibre 9.13.0 desktop reader alongside official manufacturer documentation, and have not been tested directly on physical Kindle e-reader hardware. Device firmware can still override file margins with its own reading menu settings. For a broader comparison of EPUB exports, font embedding, and presets for Kobo, Boox, and Xteink devices, read Reading translated novels on an e-reader: choosing the right EPUB export, checking errors, and fitting your screen.

  1. Step 1 - Export your translated EPUB from NovelVerba: Download either the format-preserving (write-back) EPUB or a rebuilt EPUB from TXT; the system sets dc:language to your target language (vi, en, id, es, th, ar, pt-br, or de), removes writing-mode: vertical-rl, and rejects UTF-16 archives.
  2. Step 2 - Validate and tune layout in your browser: Drop the .epub file (up to 50 MB) into the EPUB Validator to confirm all 12 package, metadata, and TOC checks pass (runs in the browser, does not upload to a server, and is not equivalent to EPUBCheck); optionally run the EPUB Optimizer with the 6-6.8″ preset (16px margin, 1.55 line spacing, 1.2em indent) or 7-8″ preset (22px margin, 1.6 line spacing, 1.3em indent).
  3. Step 3 - Send via Amazon Send to Kindle: Upload the DRM-free .epub file at amazon.com/sendtokindle (up to 200 MB) or email it to your @kindle.com address from an approved address on your Approved Personal Document E-mail List (up to 50 MB).
Check your EPUB file in the browser before sending to Kindle