How to Format a Book for Kindle: The Guide I Wish Existed When I Was Swearing at My Preview File

Let me paint you a picture. You’ve written a book. Months — maybe years — of work. You export it, upload it to KDP, hit the preview button, and your beautifully crafted manuscript looks like it was attacked by a formatting gremlin. Chapter titles have migrated to the middle of pages. Your paragraph spacing has developed a mind of its own. The table of contents links to absolutely nothing. Welcome to Kindle formatting, where the gap between what you see in Word and what readers see on their devices is roughly the size of the Grand Canyon.

Kindle formatting doesn’t have to be this painful. But it requires understanding a fundamental principle that most authors miss: Kindle books don’t have pages. They have a continuous flow of content that the reader’s device breaks into screens based on font size, screen dimensions, and display settings. You’re not designing a fixed layout. You’re defining structural rules that the device interprets on the fly. Once you internalize this, everything else gets easier.

Step 1: Choose the Right File Format

KDP accepts several file formats, but they are not created equal. According to KDP’s submission guidelines, the recommended format for ebooks is EPUB. You can also upload a .doc or .docx file, but KDP will convert it — and that conversion process is where most formatting disasters originate.

Word documents carry an enormous amount of hidden formatting: inline styles, font overrides, spacing anomalies, section break artifacts. When KDP’s automated conversion encounters these, it makes its best guess at what you intended, and that guess is often wrong. The result: inconsistent spacing, broken navigation, and visual artifacts that didn’t exist in your original file.

If you’re using book formatting software like Storyloft, Vellum, or Atticus, the tool generates a clean EPUB file directly — no conversion step, no guessing, no formatting gremlins. If you’re working from Word, I strongly recommend using a dedicated formatting tool for the export rather than uploading the .docx directly to KDP. The 30 minutes you spend on that step will save you hours of debugging.

Step 2: Structure Your Content Semantically

This is where most Kindle formatting guides lose people, so I’ll keep it simple. “Semantic structure” means using heading styles (H1 for chapter titles, H2 for sections) instead of just making text bigger and bold. It means using paragraph styles instead of hitting Enter twice for spacing. It means using first-line indent settings instead of pressing Tab at the start of every paragraph.

Why does this matter? Because Kindle devices use your content structure to build navigation. The table of contents is generated from your heading hierarchy. The “chapters” in the Kindle app’s chapter-skip feature come from your structural markers. If you formatted your chapter titles by manually changing the font size and bolding them — without using heading styles — the Kindle device has no idea they’re chapter titles. Your navigation breaks. Your TOC is empty or wrong. And your readers are stuck scrolling through a featureless text blob.

Ebook formatting software handles semantic structure automatically. When you designate something as a chapter in your project, the tool applies the correct heading level in the output file. If you’re doing this manually in Word, make sure you’re using the built-in Heading 1 style for chapter titles, not just visual formatting.

Step 3: Build a Working Table of Contents

Every Kindle book needs two types of table of contents:

The HTML table of contents. This is a page within your ebook that readers can navigate to. It lists your chapters as clickable links. It’s what you see when you tap “Table of Contents” in the Kindle app’s menu.

The logical (NCX/NAV) table of contents. This is metadata embedded in the ebook file that the Kindle device uses for its own navigation features — the chapter-skip arrows, the “Go to” menu, the progress indicator. If this is missing, KDP will accept your file but warn you, and your readers will have a degraded navigation experience.

Good ebook formatting tools generate both automatically from your chapter structure. If you’re building your EPUB manually, you’ll need to create both — the HTML TOC as a content page and the NCX/NAV as a metadata file. It’s one of the more fiddly parts of manual ebook creation, and it’s one of the strongest arguments for using formatting software instead.

Step 4: Handle Typography for Reflowable Text

Print book typography is about absolute control. Kindle typography is about graceful defaults. Readers can change the font, the size, the line spacing, and the margins on their device. Your formatting has to look good regardless of what settings they choose.

This means:

Don’t specify absolute font sizes. Use relative sizing (percentages or ems) so your text scales proportionally with the reader’s chosen font size. A chapter title set at “24px” might look great at one font size and absurdly large at another.

Don’t rely on specific fonts. Kindle devices may or may not have the font you embedded. Use standard web-safe fonts or embed fonts properly, but design your formatting to look good even if the device substitutes a different font.

Use paragraph spacing, not blank lines. Pressing Enter to create space between paragraphs works in print. On Kindle, it creates inconsistent gaps that vary by device and font size. Set paragraph spacing through styles instead.

Set first-line indents through styles, not tabs. Tab characters behave unpredictably in ebooks. A style-based first-line indent is consistent and clean.

Step 5: Handle Images Correctly

If your book includes images — cover images, illustrations, charts, photographs — they need to be sized and inserted correctly for Kindle.

Your cover image should be at least 1,600 pixels on the longest side (Amazon recommends 2,560 x 1,600 pixels). Interior images should be high-resolution but file-size-conscious — large images increase your ebook’s delivery cost (which Amazon deducts from your royalties on the 70% royalty option).

Images should be set to scale responsively within the text flow. An image that’s 800 pixels wide looks fine on a tablet but overflows the screen on a phone if it’s not set to scale with the container. CSS max-width settings prevent this, and good formatting software handles it automatically.

Step 6: Preview on Multiple Devices

KDP provides a preview tool called Kindle Previewer (downloadable for Windows and Mac) that simulates how your ebook will look on different devices. Use it. Then use it again. Then use it a third time specifically looking for these things:

Chapter transitions — does each chapter start cleanly on a new screen? Table of contents — do all links go to the right places? Images — do they display at a reasonable size and not overflow or pixelate? Typography — is the spacing consistent? Are there any visual artifacts from your source formatting?

The preview step is where you catch the problems that your formatting environment hid from you. The 20 minutes you spend previewing will prevent the one-star review that says “formatting was terrible, couldn’t read it.”

Step 7: Upload and Validate

When you upload to KDP, the platform runs its own validation. Common warnings include: missing logical TOC, images below recommended resolution, file size concerns, and metadata issues. Warnings don’t prevent publication, but they indicate problems that will affect the reading experience.

Errors — incorrect file format, corrupted EPUB structure, missing required elements — will prevent publication and require fixing before you can proceed.

If you’re using dedicated formatting software, most of these issues are caught before you ever upload to KDP. The tool validates the output file against known requirements and flags problems during the formatting stage rather than the upload stage. This is one of the core advantages of using purpose-built tools over manual formatting. Check the complete KDP formatting requirements guide for the full specification breakdown.

The Integration Advantage

I’ve formatted Kindle books the hard way (Word → manual EPUB conversion → debugging → prayer) and the easy way (writing and formatting in an integrated platform like Storyloft, where ebook export is a single step from the same manuscript). The difference isn’t just time saved — it’s errors prevented.

When your writing environment and your formatting environment share the same manuscript, structural decisions made during writing (chapter hierarchy, heading levels, image placement) carry directly into the Kindle output. No conversion artifacts. No lost structure. No rebuilding navigation that already existed in your project.

Combined with print formatting from the same source, you get a complete set of distribution-ready files — Kindle, EPUB, and print PDF — from a single workflow. That’s the end-to-end publishing model, and it turns Kindle formatting from a dreaded chore into a checkbox you click on the way to publishing. Which, frankly, is what it always should have been.

Frequently Asked Questions

What file format should I use for Kindle?

EPUB is recommended. While KDP accepts .doc and .docx, the conversion process frequently introduces errors. Formatting software that generates EPUB directly produces much cleaner results.

Can I format a Kindle book in Microsoft Word?

Technically yes, but it’s not recommended. Word embeds hidden formatting that causes issues during KDP’s conversion process. Dedicated formatting tools produce cleaner Kindle output with fewer errors.

What size should my Kindle cover image be?

Amazon recommends 2,560 x 1,600 pixels. The minimum is 1,000 pixels on the shortest side, but higher resolution produces better display quality across all Kindle devices.

Why does my Kindle book look different from my Word document?

Kindle ebooks use reflowable text that adapts to reader device settings. Font sizes, spacing, and page breaks are interpreted by the device, not fixed by the author. Using heading styles and paragraph styles instead of visual formatting ensures consistent results.