How do you format an ebook for Kindle?

Start from a clean manuscript file

Most Kindle formatting disasters are pasted-in formatting: Google Docs exports, web copy with inline styles, and double-spaced Word files from 2019. Strip the manuscript to plain semantic structure first — real Heading 1/Heading 2 styles, body text, lists — before you style anything.

One font, one body size, chapter breaks as real breaks rather than stacked empty paragraphs. The converter rewards boring files and punishes clever ones.

Build navigation that actually navigates

Kindle readers jump — between chapters, back to a checklist, forward to the resources page. That only works when your TOC is generated from heading styles, not typed by hand. Verify every chapter starts on its heading and appears in the logical TOC after conversion.

Front matter order matters too: cover, title page, copyright, contents, then chapter one. Our format comparison explains why the DOCX stays your source file even when you also ship PDF.

Cover and images that survive compression

Upload the largest cover Amazon allows — a 2560-pixel JPEG at 1.6:1 ratio — with title text readable at thumbnail size, because thumbnails are where covers sell. Inside the book, keep images simple, captioned, and centered; complex floating layouts reflow unpredictably on e-ink.

Test every image at the smallest preview size, not full screen. If a diagram is unreadable small, split it or cut it — Kindle readers won't pinch-to-zoom your workbook.

The pre-upload checklist

Preview on KDP's own online previewer across phone, tablet, and e-ink views. Click every TOC entry. Check chapter openings, image placement, and that no stray blank pages survived. Then answer the AI disclosure questions honestly — our disclosure explainer walks through them.

Honest-scope note: this checklist covers standard reflowable nonfiction — guides, lead magnets, workbooks. Fixed-layout books, translations, and audiobook production are separate crafts this post doesn't cover.

• Convert and click-test the full TOC on all three preview devices.
• Confirm cover renders legibly at thumbnail size.
• Complete disclosure answers before submitting.

Prepare a source that can reflow cleanly

Kindle readers use screens of different sizes and can change the font. Prepare a manuscript whose structure survives that reflow. Use real heading styles for chapter titles, ordinary paragraphs for body text, and simple lists or tables when they remain readable on a phone. Avoid aligning text with repeated spaces or tabs, inserting manual line breaks to make a page look right in one editor, or placing essential text inside an image. Those shortcuts can look fine in a desktop document and collapse after conversion.

Start with a clean editable source and keep a copy before changing the layout for Kindle. Review the manuscript for duplicate title pages, empty headings, inconsistent scene breaks, and page-number references that will be meaningless in a reflowable edition. If a chart is important, test whether its labels remain legible at the smallest screen size or rewrite the insight in surrounding prose. A reader should be able to understand the argument even when an image is reduced or unavailable.

Amazon’s current manuscript guidance lists accepted upload formats and describes its conversion and preview tools. Use those instructions for the format you are submitting now rather than assuming a PDF, DOCX, or EPUB will behave identically. A PDF that preserves every pixel may be right for a fixed-layout workbook, but that property can make an ordinary text book uncomfortable on a small screen. A DOCX can be convenient when its styles are clean; an EPUB can be useful when you have already validated the package. The file extension is only the beginning of QA.

Create the table of contents from headings or the appropriate authoring tool, not by typing page numbers into a list. Check that every chapter link goes to the right heading and that the back link or reading navigation makes sense. Use descriptive link text inside the book; a raw URL may be ugly or unusable on an e-ink device. Keep external resources on a maintained page when they change often, and explain what the reader will find there rather than sending them away without context.

Run the preview as a reader, then as an editor

After upload or conversion, open the platform preview on more than one device class. First read the opening chapter without hunting for defects. Notice whether the book feels comfortable: paragraph length, chapter breaks, image size, and whether you can follow the argument. Then make a second technical pass. Jump through the table of contents, inspect the start and end of each chapter, and check places where lists, quotes, and tables meet page breaks. A file can pass conversion while still presenting a poor reading experience.

Search for artifacts that often survive spell-check: doubled spaces, broken characters, blank pages, headings stranded from their first paragraph, and captions separated from images. Inspect front matter and back matter separately. A rights note or author bio copied from an older edition can be more embarrassing than a small typographical error in chapter three. If you included a disclosure page, check that it matches the final content and that you answer KDP’s separate AI-content question accurately during publishing.

Ask one person to read the converted sample, not the source document. Give them three tasks: find a particular chapter, follow a resource link, and locate the next action after finishing the book. Their success shows whether the file works as a product. If they struggle, adjust the source and reconvert; do not patch only a screenshot or assume the retailer will fix the issue. Keep each upload version with a date so you can tell which file was inspected and which was eventually published.

Make the final metadata agree with the book. Title, subtitle, series, contributor name, description, and cover should describe the same edition. If you update the interior later, preview again and review any changed platform disclosures. A Kindle book is not complete when the file uploads; it is complete when the converted edition is navigable, honest, and ready for the reader who bought it.

Formatting cases to inspect by hand

Image-heavy pages need special attention. A chart that is clear at desktop width may become illegible on a phone or e-ink screen. Put the conclusion in adjacent text, use high-resolution source images, and avoid labels that depend on color alone. For a workbook or picture book, check whether the project belongs in a fixed-layout workflow and read the current KDP guidance for that format. Do not force a page design into a reflowable novel template simply because the upload accepts the file.

Tables can fail more subtly. A two-column comparison may look fine until the reader increases font size and cells wrap into narrow stacks. Simplify wide tables, split them into short lists, or present each option in a separate subsection. Keep column headers meaningful and repeat context in prose. When the reader changes orientation or font, the answer should remain findable. Preview the hardest table rather than assuming every table behaves like the easy one on page three.

Footnotes, endnotes, and links need purposeful navigation. A reader who taps a note should be able to understand the reference and return to the main text. External URLs may change, so record a checked date and use a stable source page where possible. Do not fill the book with raw links that a reader cannot interpret without leaving the chapter. A concise source note with the organization, page title, and reason it matters is more useful than a long unannotated list.

Front matter should be brief and accurate: title, author or organization, edition, rights note, and any process disclosure you choose to include. Avoid pages of marketing before the first useful chapter. Back matter can offer a resources list and one next action, but it should not make the buyer feel that the purchased book was only a funnel. Check that the retailer’s sample exposes enough of the real teaching to help a buyer decide fairly.

Finally, test updates as carefully as first publication. A corrected paragraph can shift a table, break a contents link, or leave a caption on the wrong page. Keep the prior source and export so you can compare versions. After a revised upload, inspect the new converted file rather than assuming the old preview remains valid. Formatting quality is a repeatable release process, not a one-time decoration pass.