How to Format a Word Document for Kindle — 2026 Guide

Last updated: September 2026 — checked against KDP’s current file and image guidelines.

To format a Word document for Kindle, you need to set paragraph styles correctly, remove manual formatting, insert page breaks before each chapter, build an automatic table of contents, and prepare your images before uploading to KDP. This guide covers every step in order — from opening your manuscript to downloading your finished KPF file from KDP.

Most formatting problems on Kindle come from the source Word document — not the conversion step. Fix the document first and the conversion will be clean. Starting a new book? Our free Word manuscript templates have every style in this guide already set up.

What You Need Before You Start

Before you open your manuscript, confirm you have these in place:

Microsoft Word — any version from 2016 onwards. The steps in this guide use Word 2021 on Windows. Mac users follow the same steps with the same menus.

Your finished manuscript — formatting is the last step before conversion. Your text should be fully edited and proofread before you touch a single style setting.

Kindle Previewer — Amazon’s free desktop app. Download it from the KDP website. You will use it to check your converted file before uploading. The ideal final file format to upload to KDP is a validated ePub file — but this guide covers the Word document preparation that makes any conversion method produce a clean result.

1–2 hours — for a standard novel or non-fiction book with no images or complex formatting. Complex books with tables, footnotes, or many images take longer.

Step 1 — Set Up Your Page and Document Settings

Open your manuscript in Word. Go to Layout → Margins → set all margins to 1 inch on all sides. This has no effect on the final Kindle file — eBook margins are controlled by the reader’s device — but it keeps your working document readable.

Next, turn off widow and orphan control. Go to Home → Paragraph settings → Line and Page Breaks → uncheck Widow/Orphan control. Kindle pages reflow, so this print setting does nothing in an eBook — turning it off keeps your working document closer to how the text will actually flow.

Turn off hyphenation. Go to Layout → Hyphenation → None. If you have ever used manual hyphenation, search for stray hyphen characters too — they can survive conversion and appear mid-word on Kindle screens, where line breaks fall in different places. Kindle handles line breaks itself.

Remove all headers and footers. Go to Insert → Header → Remove Header. Repeat for Footer. Page numbers, chapter titles in the header, and running footers do not exist in reflowable eBooks. They add unwanted code to your converted file.

Step 2 — Remove All Manual Formatting

This is the step most authors skip. It is also the step that causes the most Kindle formatting problems.

Manual formatting includes using the Tab key for indents, using multiple spaces to centre text, or hitting Enter multiple times to create space between sections. Every one of these creates invisible characters in your file that convert into broken formatting on Kindle.

Remove all tab characters. Press Ctrl+H to open Find and Replace. In the Find field, type ^t (this is the code for a tab character). Leave the Replace field empty. Click Replace All. Word removes every tab from the document.

Remove double spaces. Then press Ctrl+H again. In the Find field, type two spaces. In the Replace field, type one space. Click Replace All. Repeat until Word reports zero replacements — this means no double spaces remain.

Remove multiple blank lines. After that, in Find, type ^p^p (two paragraph marks). In Replace, type ^p (one paragraph mark). Click Replace All repeatedly until no consecutive blank lines remain in the document. If you used blank lines to mark scene breaks, replace them with a centred scene-break marker such as * * * on its own line first — otherwise the breaks disappear.

Remove manual line breaks. Finally, in Find, type ^l (lowercase L — the code for a manual line break). In Replace, type ^p. Click Replace All. Manual line breaks (Shift+Enter) display incorrectly in reflowable eBooks.

Step 3 — Apply Paragraph Styles Correctly

Styles are the foundation of clean Kindle formatting. They tell the conversion process what every element in your book is — body text, chapter heading, block quote — and how it should display.

First, open the Styles panel. In Word on Windows, press Ctrl+Alt+Shift+S. On Mac, go to Format → Style.

Apply these styles throughout your manuscript:

Normal — every body text paragraph. Select all body text → click Normal in the Styles panel. This must be consistent throughout. A mix of Normal and Body Text styles — or Normal with manual font changes — is the single most common source of formatting inconsistencies in converted Kindle files.

Heading 1 — every chapter title. Select the chapter title text → click Heading 1. Do not use large bold text that looks like a heading. The Heading 1 style is what generates your table of contents entries.

Heading 2 — every section heading within a chapter. Select → click Heading 2.

No Indent — the first paragraph of each chapter (after the chapter title). The first paragraph following a heading should have no first-line indent. Create a No Indent style based on Normal: in the Styles panel click New Style → name it “No Indent” → set “Style based on” to Normal → Format → Paragraph → set Special to (none). Don’t modify Normal itself — that would remove the indent from every paragraph.

Block Quote — any quoted passage. Indent left 0.5 inches, italic, space before and after 6pt.

Step 4 — Set Paragraph Indentation Using Styles

Never use the Tab key or spacebar to indent paragraphs. Using Word styles helps you easily format your book for Kindle. The correct method is to set the indent inside the Normal style itself.

Right-click Normal in the Styles panel → Modify → Format → Paragraph. Set:

• First line indent: 0.3 inches
• Space before: 0pt
• Space after: 0pt
• Line spacing: 1.15

Click OK. Every paragraph using the Normal style now has a consistent first-line indent set inside the style — not as a tab character that will break during conversion.

Step 5 — Insert Page Breaks Before Every Chapter

To begin, place your cursor immediately before each chapter title. Press Ctrl+Enter to insert a page break. Do this for every chapter in the book.

Never use blank lines to push a chapter to a new page. Ten blank lines between chapters look correct in Word. In a converted Kindle file, they create a large blank space before the chapter heading — visible on every device and impossible to fix after conversion without going back to the source file.

Once inserted, confirm your page breaks are in the right place. Go to View → Draft to see your document in a simplified view where page breaks show as a dotted line across the page. Every chapter title should be immediately below a page break marker.

Step 6 — Build Your Table of Contents

Use Word’s automatic table of contents — not a manually typed list. A manually typed TOC does not generate clickable links in a converted Kindle file. Amazon’s validator will accept it but readers cannot tap the chapter names to navigate.

Place your cursor on a blank page near the front of the book — after the title page and before Chapter 1. Go to References → Table of Contents → Automatic Table 1.

Word builds the TOC from your Heading 1 and Heading 2 styles. Every chapter title you marked as Heading 1 appears as a clickable entry.

Update the TOC after any changes to the manuscript. Right-click the TOC → Update Field → Update Entire Table. Do this immediately before converting or uploading your file.

Step 7 — Prepare Your Images

Insert images — don’t copy and paste them. Go to Insert → Pictures → This Device and choose the file. Pasted images often lose quality or arrive in odd formats.

Set all images to In Line With Text. Select each image → click the layout icon that appears → choose In Line With Text. Images set to Square, Tight, or other text-wrapping options do not convert correctly to eBook format.

Make sure images are embedded, not linked. If you inserted any image using “Link to File”, go to File → Info → Edit Links to Files and click Break Link, so the image is stored inside the document.

Use images large enough to stay sharp. Modern Kindle screens are more than 1,200 pixels wide, and KDP adds a content quality warning to the Amazon detail page of eBooks with blurry images or illegible text in images. KDP recommends that photos fill at least 60% of the screen width, and images containing text — charts, maps, diagrams — at least 80%. Stop Word from shrinking them: File → Options → Advanced → Image Size and Quality → tick Do not compress images in file.

Keep file size sensible. On KDP’s 70% royalty plan, a delivery cost is deducted for every megabyte of every copy sold, so save photos as good-quality JPEGs rather than huge uncompressed files. Our KDP royalty calculator shows how file size affects your earnings.

Avoid formats Kindle doesn’t support. Kindle doesn’t support TIFF files, animated GIFs, or transparent backgrounds (transparent areas are converted to white). Use JPEG for photos and PNG for line art, in the sRGB colour space.

Add alt text. Right-click each image → View Alt Text and describe what the image shows. Kindle’s accessibility features read it aloud to readers who use screen readers.

Don’t put text inside images. Tables, captions, and headings should be real text, not pictures of text — they stay sharp, searchable, and resizable. See KDP’s image guidelines for reflowable eBooks for the full rules.

Step 8 — Final Document Checks Before Converting

Run through this checklist before saving your final file:

• All body text uses the Normal paragraph style — no mixed styles
• All chapter titles use Heading 1 — not manual bold formatting
• All section headings use Heading 2
• Page break before every chapter title
• TOC updated — all chapters present and linked
• No tab characters anywhere in the document (Find ^t returns zero results)
• No double spaces (Find two spaces returns zero results)
• No headers or footers
• All images set to In Line With Text, embedded, and with alt text
• Spell check complete
• File saved as .docx — not .doc

Want a printable version? Download our free Kindle Formatting Checklist.

Step 9 — Convert and Upload to KDP

Your Two Upload Options

Save your final file as .docx. You now have two options for converting and uploading to Amazon KDP.

Option A — Upload the .docx directly to KDP

To upload, log into KDP. On your Bookshelf, click + Create → Kindle eBook. On the Kindle eBook Content tab, under Manuscript, click Upload manuscript → select your .docx file. For every other field, follow our step-by-step guide on how to upload a book on Amazon Kindle.

KDP converts your Word document automatically using its own conversion engine. The result is functional but may have inconsistencies — particularly with footnotes, custom fonts, and complex formatting. KDP accepts other formats like DOCX but the ePub gives you the most control and provides the most reliable and professional result.

After uploading, check the output before publishing: open KDP’s online previewer, or download the preview file and open it in Kindle Previewer. Read through it carefully in every device view — Kindle e-reader, phone, and tablet.

Warning — What a .docx Upload to KDP Actually Produces

⚠️ What Uploading a .docx to KDP Actually Produces

Most authors do not realise this until after their book is live. Here is what a direct .docx upload to KDP frequently causes — and why it matters to your readers and your book’s credibility.

1. .docx is not a Kindle format.

Amazon KDP converts your Word file automatically using its own engine. You are not uploading a Kindle file. You are uploading a Word file and asking Amazon’s software to guess what your book should look like. The engine does its best — but it is not a specialist, and it does not know your book.

2. Automated conversion produces messy output.

Bloated code, inconsistent paragraph spacing, wrong heading sizes, and garbled special characters are all common results of automated .docx conversion. The book may look acceptable on a desktop preview but display incorrectly on a Kindle Paperwhite or Kindle app on older devices. Most authors only discover these problems after readers report them in reviews.

How Footnotes, Metadata and TOC Links Are Affected

3. Footnotes and endnotes break — or disappear entirely.

KDP’s automatic engine handles simple footnotes inconsistently. Pop-up notes — the correct Kindle format for footnotes — require specific HTML code that the automated engine does not always generate. Endnotes linked throughout the body text frequently lose their links completely. A reader tapping a footnote number on their Kindle sees nothing. That is a serious problem for academic texts, annotated editions, and any book where footnotes carry important content.

4. Internal links in the TOC may not work correctly.

A manually typed TOC has no clickable links at all. An automatic TOC from Word conversion may generate links that point to incorrect chapters — particularly if the book has been edited since the TOC was last built. Every link in your table of contents must be tested manually in Kindle Previewer before publishing.

5. Metadata does not display correctly from a .docx upload.

When KDP converts a .docx file, details such as title, author, and language are taken from your KDP dashboard fields and whatever Word stored in the document properties — and leftover properties (an old title, or the name of whoever created the template) can end up inside the file. A hand-coded conversion sets this metadata deliberately in the eBook’s package file, so every device shows the correct details.

The short version: uploading a .docx to KDP is the fastest route to publishing. It is not the best route. If your book has footnotes, endnotes, a linked TOC, custom styles, or content where metadata accuracy matters — use Option B.

Option B — Convert to KPF First, Then Upload

For a cleaner result — particularly if your book has footnotes, tables, special characters, or a non-standard layout — have your .docx converted to a KPF file first, then upload the KPF to KDP. KPF is Amazon’s own Kindle package format, produced with Amazon’s Kindle tools.

With our Kindle Conversion service, your book is hand-coded in clean HTML and CSS from your prepared Word document, then built into a KPF — typically a leaner file with more precise formatting than an automated conversion of the same document. The difference is visible in Kindle Previewer: consistent heading sizes, correctly linked footnotes, and a table of contents that links to the right place every time. You also receive the complete source files.

Common Word Formatting Problems and How to Fix Them

Problem 1: Chapter headings are different sizes throughout the book

Cause: Some chapter titles used Heading 1 style, others used manually bolded Normal text.

Fix: Find every chapter title → apply Heading 1 style consistently.

Problem 2: Table of contents links to the wrong pages

Cause: TOC was not updated after final edits to the manuscript.

Fix: Right-click TOC → Update Field → Update Entire Table → re-export.

Problem 3: Large blank space before chapter headings

Cause: Multiple blank lines used to push chapters to a new page instead of a page break.

Fix: Delete all blank lines before chapter titles. Insert Ctrl+Enter page break instead.

Problem 4: Paragraph spacing is inconsistent throughout

Cause: Mix of paragraph styles — some paragraphs using Normal, others using Body Text or Default.

Fix: Select all (Ctrl+A) → apply Normal style → re-apply Heading 1 to chapter titles.

Problem 5: Footnotes show as plain text numbers, not pop-up notes on Kindle

Cause: Footnotes were typed manually as superscript numbers rather than inserted using Word’s Insert Footnote function.

Fix: Delete manual footnote numbers. Reinsert footnotes using References → Insert Footnote in Word. The conversion engine reads Word footnote data and converts it to Kindle pop-up notes automatically.

When to Use a Professional Formatting Service

Overall, this guide covers the most common scenario — a standard fiction or non-fiction manuscript with minimal special formatting. Some books need more than a well-prepared Word document.

Consider a professional service if your book has:

• Footnotes or endnotes throughout (poetry, academic work, annotated editions)
• Tables, charts, or data that must display precisely
• Multiple languages or right-to-left scripts (Arabic, Hebrew, Persian, Urdu) — see our Arabic eBook conversion
• A fixed layout where text and images must stay in exact positions — see Fixed Layout Kindle
• Custom fonts that need embedding and licencing
• Complex front matter (multiple copyright pages, contributor lists, index)

A professional hand-coded conversion costs from $30 (up to 50 pages) to $125 (up to 350 pages) — see our full pricing. The result is a leaner file, a cleaner layout, and a book that previews cleanly in Kindle Previewer — compared to an automated conversion that may need several rounds of correction.

The time calculation matters, too. Following this guide for a 300-page book with footnotes and a complex structure can take 4–6 hours if you’re new to Word’s style system — time you could spend writing your next book.

Frequently Asked Questions

Can I upload a Word document directly to KDP without converting it first?

Yes. KDP accepts .docx files and converts them automatically. The result is usually acceptable for simple text-only books. For books with footnotes, tables, images, or custom styles, the automatic conversion often produces inconsistencies. Converting to a validated ePub or KPF file before uploading gives you more control over the final result.

My Word document looks correct on screen but the Kindle version looks wrong. Why?

Word and Kindle render text differently. Word displays a fixed page with your exact font and spacing choices. Kindle renders a reflowable document where the reader controls font size, line spacing, and typeface. Formatting that relies on fixed positions — text pushed to a specific place with blank lines or spaces — breaks in the reflowable Kindle environment. The fix is to use styles and page breaks rather than manual positioning.

Does the font I use in Word affect how the book looks on Kindle?

For most books, no. Kindle readers can change the typeface to their preference — your Word font is overridden by the reader’s device settings. The exception is if you embed a specific font in your converted file. Embedded fonts display on devices where the reader has not changed the default font settings.

What is the difference between uploading .docx and uploading a KPF file to KDP?

A .docx upload is converted by KDP’s automatic engine — you have no visibility into or control over the result until you preview it in Kindle Previewer. Footnotes may break, TOC links may point to the wrong chapters, and metadata may display incompletely in the book information panel on readers’ devices. A KPF file is the finished converted file — built by hand or a professional tool before upload. The file is already in its final form. Footnotes are correctly linked pop-up notes, all TOC links are tested and confirmed, metadata is set deliberately, and the file is usually leaner than an automated conversion of the same manuscript. Uploading a KPF gives you a predictable, consistent result every time.

How long does it take to format a Word document for Kindle?

A simple 50,000-word novel with no images or special formatting takes approximately 1–2 hours following this guide. A 300-page non-fiction book with footnotes, tables, and images takes 4–6 hours. A children’s picture book with full-page illustrations requires fixed layout formatting — a different process entirely from this guide. See our children’s book formatting service.

The Honest Comparison — .docx Upload vs Hand-Coded Conversion

Authors ask us this question regularly. Here is a straight answer with no sales pressure.

If your book is a simple text-only novel with no footnotes and you want to publish today — uploading the .docx is a reasonable choice. Check the output carefully in Kindle Previewer before going live.

If your book has footnotes, endnotes, a linked TOC, tables, images, special characters, or if metadata accuracy matters to you — a hand-coded conversion is the correct choice. Pricing starts at $30, and the source files you receive mean you are never locked out of your own book again.

Still writing? Read how to write an eBook and publish it, and check which eBook formats you need. New to the terms in this guide? See our eBook glossary.