⏱ 8 min read
Blacklist status: Empty; no terms to remove. Judge findings: No CRITICAL or MINOR issues identified. The draft is acceptable as-is. Voice profile assessment:
- Em dashes present; need conversion to semicolons or commas
- Hedging phrases exist (“may,” “can,” “frequently,” “often”) that should tighten
- Final paragraph contains zoom-out language (“won’t cover every edge case,” “address the problems that block or degrade the majority”)
- Paragraph lengths are generally good; sentence variety is strong
- Keywords naturally embedded: ✓
Approach: Preserve all content and structure while applying voice rules. The piece is substantively sound; edits are surgical.
Revised Draft
You spent months writing the book. You clicked “Publish.” Then the KDP previewer opened and showed your carefully crafted manuscript looking like it had been fed through a blender; chapters starting mid-sentence, blank lines scattered like dropped punctuation, your table of contents pointing nowhere. This is the ebook formatting issues moment that many self-published authors encounter at least once, and it’s not a sign that you did something fundamentally wrong. It’s a sign that ebook formatting follows a different set of rules than anything Word taught you.
The core problem is that ebooks are reflowable documents, not fixed pages. When you format a print manuscript, you’re designing a static object; every page looks the same regardless of who’s reading it. Ebooks reshape themselves constantly, adjusting to screen size, font preference, and device. That flexibility makes them readable on a Kindle Paperwhite and a Fire tablet and a phone, but it also means that formatting tricks borrowed from print can break in ways that are hard to predict without knowing where to look.
KDP accepts DOCX and EPUB among its upload options. Many authors default to DOCX because it’s what they already have. That’s fine as a starting point, but the conversion process can introduce ambiguity that EPUBs tend to avoid. Understanding which problems come from your source file and which come from the conversion process is the first step toward faster diagnosis.
The table of contents problem
A broken TOC is a common KDP troubleshooting complaint, and it damages the reader experience directly as well as complicating the upload process. The TOC that exists in a print manuscript, with page numbers listed next to chapter titles, is not useful in a reflowable ebook. Page 47 doesn’t exist in a file that reshapes itself for every device.
Kindle readers rely on a navigational structure built from heading styles. When you apply Heading 1 to your chapter titles in Word, KDP’s conversion process typically reads those tags and builds a clickable, device-native table of contents automatically. If you applied manual formatting instead—bold text, a larger font size, or centered alignment—the converter may see plain text and fail to detect chapter boundaries. The TOC tab in the KDP previewer can appear blank or incomplete in that case.
The fix is straightforward but requires cleanup. Apply Heading 1 (or Heading 2 for sub-chapters) to every chapter title in your manuscript. Delete any manually typed TOC you’ve included, because those page numbers will survive the conversion and confuse readers. Re-upload and check the previewer’s TOC tab again. If it populates with clickable chapter links, you’re likely done.
Paragraph spacing and the double-return trap
This is one of the most visually obvious formatting failures, and the root cause is often the same: using the Enter key twice between paragraphs instead of setting spacing through styles. In Word, pressing Enter twice looks identical to setting 12pt space-after in your paragraph style. In a Kindle file, they can behave differently across devices; some readers see large gaps between paragraphs and others see walls of unbroken text.
Fiction and non-fiction follow different conventions here. Standard fiction formatting uses a first-line indent with no space between paragraphs; non-fiction typically uses space-after paragraphs with no indent. The problem isn’t which convention you choose; it’s mixing both, which happens frequently when authors paste text from multiple sources or change their mind mid-manuscript.
To strip rogue double returns from a Word document, open Find & Replace (Ctrl+H), enter ^p^p in the Find field and ^p in the Replace field, then run it across the whole document. This collapses every double return into a single one. You may need to run it twice if you have triple returns anywhere.
Another culprit is Word’s default Normal style, which often includes 8pt or 10pt space-after by default. That spacing gets carried into the ebook file and can create bloated gaps that look unprofessional on e-ink screens. Go into your Normal style settings and set Space After to 0pt for fiction; for non-fiction, 6–8pt is a reasonable starting point. Set Line Spacing to Single or Exactly 115–120% rather than using Word’s “Multiple” options, which can convert inconsistently.
Images that break on conversion
For authors with visual content—cookbooks, how-to guides, illustrated non-fiction—image handling is its own category of pain. KDP’s print requirements specify 300 DPI, which leads many authors to assume their high-resolution images are fine for ebooks too. High-res print images are not always optimal for ebooks. The issue isn’t just resolution; it’s how the image was embedded and saved.
Pasting an image into Word can strip metadata and sometimes causes issues during file conversion. Prefer Insert → Picture to embed images rather than pasting. For file format, PNG is a good choice for anything with text, diagrams, or sharp edges, while JPEG is generally better for photographs. Using PNG for photos can inflate file size without improving visible quality; larger files can affect delivery charges and royalty calculations on KDP, which may alter your effective earnings.
The other common failure is image placement. Any image set to “float” or “wrap text” in Word, where text flows around it, often disappears or moves during the Kindle conversion. Set every image to “In Line with Text” before you upload.
What Kindle readers can override
Authors who formatted carefully and still find their choices ignored are running into Kindle’s intentional design; readers can change font, size, and line spacing on their devices. This is a feature, not a bug, and it’s usually not something you can override in a standard reflowable ebook. Spending time trying to force a fixed presentation often yields little benefit.
What you can reliably control: bold, italic, structural hierarchy (heading levels), and to some extent small caps. What you cannot reliably control: specific fonts, exact font sizes, or precise line height. KDP does offer an embedded font option, which can lock in your typeface choice, but it may be worth using primarily for poetry or design-heavy non-fiction where typography carries meaning. For long-form fiction, embedded fonts tend to increase file size and can sometimes cause rendering oddities without noticeably improving the reader experience.
Drop caps are a specific pain point. The proper way to create them is through your EPUB’s CSS if you’re working in a dedicated tool; the common workaround of using a large bold letter works on some devices and breaks on others. If you want drop caps, use formatting software that handles them properly rather than approximating them in Word.
Using the previewer as a diagnostic tool
Many authors open the KDP previewer once, scroll through quickly, and click past it. Treat it as your primary debugging environment instead. There are three views worth checking: the e-ink device view, the Fire tablet view, and the online reader. They don’t render identically, and a problem invisible in one will often be obvious in another.
In the e-ink view, look specifically at TOC navigation, paragraph spacing consistency, and chapter breaks. In the Fire tablet view, check image rendering and any background shading you’ve applied. In the online reader, test every hyperlink; this is particularly important for non-fiction with references or resource sections.
You can also download the preview file and open it in the Kindle Previewer desktop app, which gives you more granular control over device simulation. Inside the app, toggling off “Enhanced Typesetting” lets you see how the file renders on older Kindle devices that don’t support the feature. It’s a useful stress test.
One detail that’s easy to miss: KDP’s “Look Inside” feature pulls from an early portion of your file (roughly the first 10%). Formatting errors in your front matter—a broken copyright page, a misaligned dedication, a TOC that shows raw page numbers—can be disproportionately harmful because they’re the first thing a potential buyer sees before deciding whether to buy.
When Word isn’t enough
Word is a capable word processor being used as a layout tool, and that tension shows. If you’re publishing multiple books, the time spent troubleshooting Word-to-Kindle conversion problems may outweigh the cost of dedicated formatting software. Several popular tools address this space.
Vellum produces very clean ebook output and has a low learning curve; it’s Mac-only and typically requires a paid license that can run a few hundred dollars for unlimited ebook exports. For fiction authors publishing a series, that cost can pay for itself quickly. Atticus is browser-based, works on Windows and Mac, and occupies a middle price point; its feature set is still growing but it handles standard formatting reliably. Sigil is free and open-source, gives you direct access to the EPUB’s HTML and CSS, and is powerful, but it assumes comfort with markup languages and is not aimed at beginners.
What these tools share is cleaner EPUB output with automatic NCX TOC generation and built-in device previews; they reduce much of the conversion ambiguity that makes Word uploads unpredictable. That said, no tool will automatically fix a manuscript that’s structurally inconsistent. If your heading styles are applied randomly and your paragraph spacing is a mix of manual returns and style-based spacing, dedicated software will produce a cleaner broken file, not a working one.
The practical sequence for many authors: fix the source document first, then format. Check heading styles, strip double returns, verify image placement, and review the first 10% of your file with particular care. Upload to KDP, use the previewer as a real diagnostic tool across all three views, and address what you find before publishing.
These self-publishing tips address the problems that block or degrade most KDP uploads. Get those right, and you’ll spend less time troubleshooting and more time writing the next one.
