KDP Ebook Formatting: Build a Professional Kindle File That Reflows Correctly
Create a clean reflowable Kindle ebook using EPUB, KPF, or DOCX, with semantic styles, navigation, images, accessibility, validation, and device testing.
A Kindle ebook is not simply a document with a different file extension. It’s a structured digital publication that must behave correctly across a wide range of devices: from a Kindle Paperwhite with a small e-ink screen to the Kindle app on a 13-inch iPad to the Kindle Cloud Reader in a desktop browser. Each of these rendering environments has different screen dimensions, font rendering, and navigation behavior. A properly formatted ebook works well on all of them. A poorly formatted ebook: one built from a Word document with manual formatting, inconsistent styles, or leftover invisible characters: breaks in predictable and embarrassing ways across at least some of them.
This guide covers ebook formatting at the technical level: what KDP accepts, what it rejects, and what produces the cleanest output across devices. The starting point for all of this is a clean, finalized manuscript: if your text still has errors, inconsistencies, or structural problems, no amount of formatting expertise will rescue the reading experience. Book your manuscript proofreading with Vappingo before you open your formatting tool. Use this specialist guide after the complete KDP formatting guide. Keep the Kindle file-types guide, table of contents guide, and KDP images guide open for the technical details.
Choose a Current Kindle Source Format
For most reflowable books, EPUB, KPF, or a well-structured DOCX are practical current inputs. MOBI is legacy and is no longer accepted as a KDP upload format. KPF is produced by Kindle Create; EPUB is the strongest interoperable publishing format; DOCX can work well for straightforward books when the styles are clean.
The Kindle file-types guide explains the difference between author upload formats and formats such as KFX that Amazon may use in the delivery ecosystem. Do not waste time trying to manufacture KFX as your KDP upload file.
Build the Ebook With Styles, Not Manual Layout
Use semantic paragraph and heading styles for body text, chapter titles, subheadings, block quotes, captions, and other recurring elements. Avoid tabs, repeated spaces, manual line breaks, and stacks of blank paragraphs to force visual positions. Those tricks break when the reader changes font size or opens the book on a different device.
Keep body styling restrained. Readers can override font family, size, theme, and other display choices, so the file should remain usable when your preferred typography is not shown. Preserve intentional bold and italics, but remove accidental local formatting carried over from the writing document.
Create Both Visible and Interactive Navigation
A nonfiction book will often benefit from a visible contents page, while Kindle also needs functional navigation so readers can jump among major sections from the reading interface. Build the TOC from real heading structure and verify that every link lands on the correct chapter or section. Use the KDP table of contents guide for the difference between the visible HTML TOC and interactive Kindle navigation. Do not assume that applying a large font to chapter text creates navigation automatically.
Handle Images for Kindle, Not Print
Reflowable Kindle images should be high quality, sized responsively, and prepared in an appropriate screen color space such as sRGB. Do not reuse a blanket print rule such as “CMYK for everything.” Kindle guidance favors screen-appropriate images, and accessibility also matters: meaningful images should have useful alternative text.
Avoid rasterizing ordinary body text into images. Text rendered as text adapts to reader settings, remains sharper across resolutions, and is more accessible. Use images when the image itself carries information or design value. See the KDP images guide for a format-by-format treatment of print and ebook requirements.
Make Ebook-Specific Layout Decisions Carefully
Page numbers, fixed running heads, mirrored margins, and print-style blank recto pages do not belong in a normal reflowable ebook. Scene breaks, chapter starts, callouts, tables, footnotes, and lists need structures that can adapt to screen width. If a page must preserve exact spatial relationships, that may be a fixed-layout use case rather than a normal reflowable one.
Test edge cases: long chapter titles, nested lists, tables on narrow screens, image captions, poetry, code, footnotes, and links. A clean first chapter does not prove the whole book is resilient.
Validate the EPUB Before KDP Conversion
If you work in EPUB, run EPUBCheck or your production tool’s validator before upload. Then inspect the file in Kindle Previewer because formal validity and good Kindle rendering are different questions. A technically valid EPUB can still contain poor navigation, cramped tables, tiny images, or awkward spacing.
Resolve structural errors at source rather than patching the converted output repeatedly. When you regenerate the ebook from a clean project, every later update is easier and less risky.
Preview on More Than One Device Profile
Use Kindle Previewer to inspect phone, tablet, and Kindle-style layouts where available. Check chapter starts, TOC links, scene breaks, images, lists, block quotes, back-matter links, and the first pages readers are likely to sample. Also test font-size changes because reflow problems often appear only when the text becomes larger.
After publication, open the live Read Sample when it becomes available and check the customer-facing experience. KDP preview and retail sample updates can take time to propagate, so do not assume a just-uploaded revision is instantly visible everywhere.
Build Back Matter for the Next Reader Action
Useful ebook back matter can include an author note, other books, series order, newsletter signup, acknowledgments, and a clear path to the next relevant title. Use descriptive links and keep the page useful even if the retailer app changes how external links behave.
For a series, connect this with the series sell-through guide. Back matter is part of the reader journey, not a dumping ground for every promotion you run.
Common Ebook Formatting Mistakes to Avoid
The recurring problems are structural: manual tabs, repeated spaces, hard returns used as layout, inconsistent heading styles, broken TOC links, print page numbers left in the file, tiny images, inaccessible image-only text, and old MOBI workflows copied from outdated tutorials. Most can be prevented by starting from a clean styles-based manuscript and validating before upload.
If a conversion problem appears only after upload, return to the source file and fix the structure there. A stable source project is the best defense against formatting drift across future revisions.
Frequently Asked Questions
Does KDP still accept MOBI files?
No. KDP completed the transition away from MOBI uploads. Use current formats such as EPUB, KPF, or DOCX for normal reflowable books.
Is KFX the file I should upload to KDP?
No. KFX is part of Amazon’s Kindle delivery ecosystem, not the normal author upload format you need to create.
Do Kindle ebooks need page numbers?
Normal reflowable ebooks do not use fixed print page numbers as layout elements. Navigation and location behavior are handled differently from print.
Should Kindle images be CMYK?
No. Reflowable Kindle content is screen-based; use appropriate screen color such as sRGB and follow current Kindle image guidance.
How should I test a Kindle file before publishing?
Validate the source where relevant, open it in Kindle Previewer, test multiple device profiles and font sizes, and check navigation and image behavior throughout the book.
What to Do Next
Generate the ebook from a clean styles-based source, run validation, then review the entire book in Kindle Previewer at more than one screen size and font setting. Fix problems at source and regenerate rather than patching the converted file manually.
Finish the text before you lock the production files. Vappingo’s qualified native-English editors can proofread the manuscript and publication-facing copy so formatting and upload are built on a clean source.
