Why EPUB to Kindle Formatting Breaks in 2026

Sending an EPUB to your Kindle is supposed to be simple — email the file, it lands on your device, you start reading. But anyone who has actually done this knows that simple and looks right are two different things. The margins are too wide. The images look washed out. The table of contents is missing. Your carefully crafted EPUB arrived as something that vaguely resembles a book.

This guide covers the five most common EPUB-to-Kindle formatting problems in 2026, explains exactly why each one happens, and gives you concrete steps to fix them — whether you are using Calibre, Send-to-Kindle, or Kindle Previewer.

---

Problem 1: Margins and Whitespace Get Wrecked

Symptom: Your EPUB looks fine in Calibre, Adobe Digital Editions, or Apple Books. On Kindle the margins are huge, text feels stretched, and the whole layout looks differently spaced.

Root cause: Amazon's Send-to-Kindle conversion engine strips or overrides user-defined CSS margins. Many EPUBs rely on rules like body { margin: 0; } or p { margin: 0; } for tight text layout. When Amazon converts the EPUB to KFX (Kindle's native format), it applies its own margin defaults — and your carefully tuned CSS gets bulldozed.

How to fix it:

• Instead of setting margins on body or html, wrap your body content in a <div class="main-content"> and apply margins there. Kindle's renderer is less aggressive about stripping margins from inner divs.
• Use p { margin: 0; text-indent: 1.5em; } for paragraph spacing — Kindles respect text-indent more reliably than top/bottom margins on paragraphs.
• Avoid margin: 0 auto on body-level elements. Use max-width constraints on inner containers instead.
• For the most predictable results, use Calibre's EPUB-to-AZW3 conversion with the "Remove paragraph spacing between block elements" heuristic turned on, then side-load the resulting file via USB instead of Send-to-Kindle.

Problem 2: Images Look Blurry or Get Cropped

Symptom: Sharp images in your EPUB appear fuzzy, pixelated, or oddly sized on Kindle Paperwhite or Oasis screens.

Root cause: Kindle e-ink screens have a native resolution of 300 PPI (Paperwhite, Oasis) or 212 PPI (Basic model). Many EPUBs embed images at 72 DPI without setting max-width or height: auto in CSS. When Amazon's pipeline or Calibre converts the file, oversized images are downsampled, while undersized ones get stretched. The result is blur at any size.

How to fix it:

• Ensure all images are at least 1500 pixels wide — this covers the 300 PPI target for most Kindle screens.
• Add this CSS to your EPUB stylesheet: img { max-width: 100%; height: auto; }. This prevents the renderer from arbitrarily scaling images beyond their container.
• For cover images, use 1600 x 2560 pixels, JPEG format, RGB color profile, under 2 MB file size. Amazon's guidelines explicitly recommend these dimensions.
• Use PNG for screenshots or diagrams that need sharp text, JPEG for photographs. The OPF manifest should declare the correct media-type for each image.
• In Calibre's conversion dialog (Look & Feel tab), check "Preserve cover aspect ratio" and "Use SVG cover if available."

Problem 3: Tables Get Mangled or Turn Into Lists

Symptom: A comparison table, pricing chart, or data grid in your EPUB arrives on Kindle as a single-column list with no borders. Rows merge, columns disappear.

Root cause: Kindle's legacy MOBI and AZW3 formats have extremely limited CSS table support. The KFX format is better but still incomplete. Properties like border-collapse, colspan, rowspan, and percentage-based column widths are handled inconsistently. Amazon's Send-to-Kindle often flattens complex tables into plain text.

How to fix it:

• Best option: Convert your EPUB to KFX directly using Calibre's KFX Output plugin (version 2.22+). This generates the format Kindle natively renders best and preserves table structure far more reliably than MOBI or AZW3.
• Second best: Replace complex tables with simpler two-column layouts using <dl> (definition list) or nested <div> elements with display: inline-block. This sacrifices visual table formatting but keeps the data readable.
• If you must use HTML tables, keep them simple: <table> with <tr> and <td> only. Avoid colspan, rowspan, and percentage-based widths. Use border: 1px solid #333 without border-collapse.

Problem 4: Table of Contents Won't Navigate

Symptom: The EPUB you sent to Kindle has the chapters in the right order when you tap through, but the "Go To" menu shows nothing. You cannot jump between chapters using Kindle's navigation.

Root cause: Kindle reads the EPUB's NCX file (toc.ncx) or the <nav> element with epub:type="toc" to build its navigation menu. Many EPUBs either have a malformed NCX or rely on an inline HTML table of contents that looks correct to humans but is invisible to Amazon's parser. If the NCX is missing entries or the <nav> is not placed in the spine, Kindle's "Go To" menu stays empty.

How to fix it:

• Open your EPUB in Calibre and go to the "Table of Contents" tab. Click "Generate Table of Contents from headings" and ensure the detected heading levels (usually h1/h2) capture all chapters.
• In the same dialog, check "Use auto-generated TOC" and "Add to EPUB as inline TOC." This ensures both the NCX and the inline TOC are populated correctly.
• If you are hand-editing the EPUB, verify the spine includes <spine toc="ncx"> and that toc.ncx exists in the EPUB root with proper <navPoint> entries for every chapter.
• For Send-to-Kindle, include a <nav epub:type="toc"> element inside the EPUB's <body> with links to each chapter page. Amazon's parser also looks for this landmark directly.
• After fixing, re-send the EPUB to Kindle and check the "Go To" menu on your device. If empty, the NCX is still malformed — open the file in Sigil to inspect the TOC structure visually.

Problem 5: Fixed-Layout EPUBs Don't Render Correctly

Symptom: Children's picture books, comics, or cookbooks with fixed-layout positioning look scrambled on Kindle. Text floats off the page, spreads don't align, and the reading experience is unusable.

Root cause: Amazon's KFX renderer has never fully supported EPUB's fixed-layout properties like -epub-viewport and -epub-page-spread. When a fixed-layout EPUB hits Amazon's conversion pipeline, it falls back to reflowable layout — which breaks the entire design intent. Kindle firmware updates through 5.16.x have not addressed this gap.

How to fix it:

• The most reliable route is to use Kindle Previewer to convert your fixed-layout EPUB to KF8 (Kindle Fixed Layout). Open the EPUB in Kindle Previewer, go to File > Save as, and choose KF8 format. Side-load the resulting file onto your Kindle via USB.
• For comics and heavily illustrated books, consider reflowing the EPUB with full-page <img> tags at 100% width and no text overlays. This trades fixed-layout precision for reliable rendering.
• Amazon's official guideline still recommends using MOBI or KF8 for fixed-layout content — EPUB fixed-layout via Send-to-Kindle will break.

---

The 2026 Workflow That Actually Works

After troubleshooting dozens of formatting issues, here is the pipeline that produces the most reliable Kindle output from an EPUB in 2026:

1. Clean your EPUB source first. Run it through converter-epub.com to strip problematic CSS, normalize HTML structure, and embed fonts properly. A clean source prevents 80% of formatting issues before they start.
2. Open in Calibre. Use Calibre 9.9 or later (the KFX output profile in 9.9 is significantly better than earlier versions). Add the KFX Output plugin for direct KFX generation.
3. Configure conversion: In Look & Feel, check "Preserve cover aspect ratio." In Table of Contents, generate from headings. In Page Setup, select "Kindle" as output device.
4. Convert to KFX. This produces a file that Kindle natively renders — no intermediate MOBI step that could strip formatting.
5. Side-load via USB. Send-to-Kindle is convenient but applies its own conversion pass that can undo your fixes. USB side-loading preserves the KFX exactly as generated.

Common CSS Mistakes That Break Kindle Rendering

Even if you fix the five problems above, these CSS patterns cause trouble on Kindle almost every time:

CSS Pattern	Why It Breaks	Alternative
body { margin: 0; }	Kindle pipeline strips it	Margins on inner container
text-align: justify	Overridden on some Kindle fonts	Accept Kindle's default alignment
font-display: swap	Kindle ignores entirely	Remove — does nothing
hyphens: auto	Partially ignored on KFX	Accept — Kindle handles its own
column-count	Not supported on Kindle e-ink	Use single-column layout
position: absolute	Not supported in reflowable	Relative positioning only
border-collapse	Unpredictable on KFX/AZW3	Simple border: 1px solid

What About Kindle Firmware Updates in 2026?

Amazon shipped firmware 5.16.x throughout 2025 and into 2026. The release notes (available on Amazon's Kindle help page) show incremental improvements to the KFX renderer — better footnote handling, faster page turns, improved dictionary lookup — but no changes to the underlying EPUB CSS support. The five problems above have not been addressed by any 2026 firmware update.

Amazon still accepts EPUB as a primary format through Send-to-Kindle and KDP. The MOBI format was originally supposed to sunset in 2022 (then pushed to 2023), but Send-to-Kindle still accepts it as of mid-2026. There is no indication Amazon will drop EPUB support — in fact, Kindle Create now directly imports EPUB files.

---

Frequently Asked Questions

---

Summary

EPUB to Kindle formatting problems are frustrating, but nearly all of them come down to five root causes: CSS margin stripping, image scaling, table format incompatibility, TOC navigation structure, and fixed-layout fallback. Each has a concrete fix that involves either adjusting your EPUB source CSS, choosing the right conversion tool (Calibre with KFX Output is the best 2026 option), or side-loading instead of relying on Send-to-Kindle.

If you are converting a single EPUB and want to check whether it has these issues before sending to Kindle, run it through converter-epub.com first — clean up the HTML and CSS, then apply the fixes above. A clean source file is the single best investment you can make for Kindle formatting fidelity. All processing is done locally in your browser, so your content stays private. For more on the safety of online conversion, see the EPUB converter privacy guide.

For the reverse process — converting Kindle books to EPUB for use on other devices — see our guide on how to convert Kindle books to EPUB.