Formatting a Kindle eBook
Turn a finished manuscript into a reflowable, navigable, accessible ebook that survives real screens.
Seven rules · An eight-part scorecard · A 90-minute preflight
The one-star review says the formatting is broken. The author checks the file, and on their laptop it looks perfect.
It was perfect, on that one screen. Then a reader enlarged the font, and the hand-built chapter openings drifted into blank screens. Another opened the book on a phone, and the seven-column table cropped mid-word. A third asked their Kindle for the table of contents and got nothing, because the headings were only bold text. A reflowable ebook is read on hundreds of different screens under settings the author never sees, and formatting that works on one of them can still be broken on the rest.
The fix is not pixel control, because ebooks do not offer any. The fix is semantics: mark what every element is, once, and let each device compose the page. This guide is that workflow, from manuscript cleanup through the style map, navigation, accessibility, and the preview protocol that catches failures before readers write reviews about them.
What Kindle formatting must accomplish
Good ebook formatting is almost invisible. Readers notice it only when they move without friction, change their settings, understand the hierarchy, and trust that nothing is missing or broken. The formatted file has five jobs.
Preserve meaning
A chapter stays a chapter when the font enlarges. A list stays a list when a sentence wraps. Formatting communicates structure, not a printed page.
Support reflow
Font, size, spacing, margins, orientation, and theme all change across phones, tablets, and E Ink readers. Text must reorganize without overlaps, cropping, or gaps.
Provide navigation
Readers open the Kindle menu, see the hierarchy, and move to the intended chapter. Most nonfiction also needs a visible, linked contents page.
Preserve content integrity
Conversion must not lose italics, reorder chapters, corrupt characters, drop images, flatten lists, or insert an old draft. A handsome chapter opener cannot compensate for a missing paragraph.
Remain accessible
Headings expose structure, meaningful images need text alternatives, links need understandable labels, and content must make sense read linearly.
Keep editing and formatting separate. Editing asks whether the book is accurate, complete, clear, and worth reading. Formatting asks whether every reader can navigate and consume that finished content reliably, so freeze one approved source manuscript before conversion. The governing principle: format by meaning once. Let the reader choose how it looks.
Choose reflowable or fixed layout
This decision controls the rest of the workflow, and for most nonfiction it has a default answer.
Text adapts to the reader's device and settings, and apparent page count changes with them. Right for nonfiction guides, business, self-help, education, novels, memoirs, text-led books with occasional images, and any book that must work on phones and E Ink devices.
Each element is anchored to a designed page. Justified only when the spatial relationship between words and images is essential: picture books, comics, highly visual textbooks, art and photography books where composition carries meaning.
If the text becomes 40 percent larger and moves onto more screens, does the book still make sense?
If yes, choose reflowable. If no, because the exact page composition is part of the meaning, investigate fixed layout. And remember that a reflowable ebook has no stable page count: do not pad it with double spacing or blank screens, and say in Chapter 6, never on page 84.
Clean the manuscript before styling it
Many conversion problems begin as invisible debris in the source document. Work in a clearly named duplicate, keep the editorial master untouched, turn on formatting marks, and search for hidden trouble.
- Repeated spaces used for alignment.
- Tabs used for indents.
- Empty paragraphs before chapters.
- Manual line breaks inside paragraphs.
- Headers, footers, and page numbers.
- Text boxes and floating objects.
- Typed bullets or numbers instead of real lists.
- Bold-only fake headings.
- Tracked changes and comments.
- Duplicate or pasted passages.
Triage each finding: keep it when the structure is already sound, such as a genuine numbered list; convert it when the content belongs but the construction is fragile, such as a text-box sidebar becoming a headed subsection; remove it when it exists only to imitate a print page. Then lock a content manifest before conversion: exact title and subtitle, contributors, front matter, a numbered list of chapters and subsections, expected images, tables, notes, and links, back matter, and the approved source filename and date. The converted ebook gets compared against it during review.
Build the Semantic Style Map
A semantic style tells the conversion system what an element is. Manual formatting only tells it how the element looks in one file. Map every element the book uses to a named style, and note the Kindle behavior each one must produce.
Two rules keep the map honest. Use headings in order: Heading 1 is a chapter, Heading 2 a major section, Heading 3 a subsection, and if a level looks wrong, change the style's appearance rather than falsifying the hierarchy. And use real chapter breaks: insert a page break before each major chapter rather than pressing Enter repeatedly, because blank paragraphs expand, collapse, or become empty screens.
Structure front matter, body, and back matter
The ebook should begin quickly, identify itself accurately, and move readers into the promised content. Front matter should not become a wall between the purchaser and the book.
Title page, copyright and edition notice, a brief disclaimer when needed, the linked contents page, an optional short introduction, then the main content. Title, subtitle, author, and series must match KDP metadata, and the retail cover does not belong inside the manuscript.
Every chapter begins at a defined chapter break, uses the same heading level for its title, appears in the correct sequence, nests section headings consistently, and ends without accidental blank paragraphs or isolated ornaments.
Conclusion, notes and references, acknowledgments, glossary, genuinely connected resources, about the author, and a restrained invitation to continue. Do not make essential content available only through an external link.
Format the elements readers actually see
The goal is controlled consistency without blocking reader preferences. Choose one paragraph-separation system, set indents through the style, and design emphasis through structure before decoration.
Forced full justification. Fixed black or white text colors. Colored backgrounds behind body text. Unusual body fonts that must be embedded. Underlines that are not links. Double spacing and empty screens before chapters.
Lists, built with real list controls and never typed symbols. Block quotes, in a dedicated style with a moderate indent and attached attribution. Scene breaks, as a robust centered marker rather than empty paragraphs. Special characters, checked in the converted file.
Create working Kindle navigation
There are two related but different contents systems, and a nonfiction book usually needs both. The logical TOC powers the Kindle Go To menu, and Amazon requires it; it should expose the book's meaningful hierarchy in reading order. The HTML TOC is the visible, linked contents page inside the book, and Amazon strongly recommends it; for a structured nonfiction guide, include it unless there is a compelling reason not to.
Build both from heading styles, then test them after conversion, entry by entry: select each entry and confirm it opens at the correct heading, confirm the entry order matches the book, confirm the displayed wording matches the destination, and test that the defined Beginning location opens at an appropriate point.
Handle images, tables, callouts, and notes
Special elements fail more often than ordinary paragraphs. Design them for narrow screens first.
Insert the file rather than pasting it, keep it inline, use a high-quality source, check legibility in color and grayscale, keep captions close, add meaningful alt text, and confirm placement after conversion. Avoid screenshots of long paragraphs and diagrams with tiny labels.
Use tables only for genuinely tabular relationships, never as invisible layout grids. If a table needs horizontal panning or crops when enlarged, simplify it, split it, or convert it into repeated labeled records that reflow reliably.
Floating text boxes convert badly. Turn them into inline sections with a descriptive heading, placed between complete paragraphs, never mid-sentence.
Amazon requires footnotes to use bidirectional links; test every one. Use descriptive link text rather than click here, check every URL before upload, and follow KDP hyperlink rules.
Build accessibility into the file
Accessibility is not a final plugin. It is the result of correct structure, language, descriptions, and reading order. Six practices carry most of it: write meaningful headings, descriptive rather than decorative; give every meaningful image alternative text that communicates its purpose in context; set the correct language so the KDP entry, the book, and the file metadata agree; preserve a reading order that makes sense read linearly; make links understandable, because screen-reader users navigate by link list; and keep words as selectable text rather than images of text. Record the accessibility features you actually tested.
Chart.
Bar chart showing newsletter sign-ups rising from 120 in January to 310 in March after the landing-page revision.
Choose an export workflow
Three workflows cover most reflowable nonfiction, and one rule covers all of them: do not convert a paperback PDF into your reflowable ebook, because it encodes fixed pages, headers, footers, and print geometry.
Best for a straightforward text-led book with simple headings, lists, links, and occasional images. Few production steps, but complex Word formatting may not convert predictably.
Best for authors who want a guided visual workflow without editing EPUB code. Kindle Create manages reflowable typesetting, themes, navigation, and the KPF file, though imported tables, notes, and lists may have editing limits.
Best for publishers using a dedicated ebook application or a professional formatter. Portable, inspectable structure with more control, but a valid EPUB can still read poorly; validation is not review.
Match the workflow to the manuscript's condition. A simple, clean, text-led file suits DOCX or Kindle Create. Complex navigation or professional production suits EPUB. A manuscript full of wide tables, text boxes, or print layouts needs redesign first, because no format choice will repair it. And if page geometry is essential to meaning, assess fixed layout with a specialist.
A worked manuscript conversion
A practical nonfiction manuscript arrives for conversion. The chapter opener looks acceptable on the author's laptop and is structurally fragile everywhere else.
Six blank paragraphs before the title. CHAPTER THREE typed in 18-point bold. A rule made from underscore characters. Body paragraphs indented with tabs. A checklist made from typed hyphens. A two-column warning text box. A spreadsheet screenshot with tiny labels. See the meeting template on page 112.
The chapter label and name become one Heading 1. Genuine sections become Heading 2. The checklist becomes a real bulleted list. The warning becomes a headed inline subsection. The spreadsheet becomes an accessible table. Six blank paragraphs become one chapter break. Tab indents move into the body style. The page reference becomes a linked chapter reference.
The final ebook does not reproduce the exact paperback page. It preserves the paperback's content hierarchy while letting every reader's device compose a usable reading experience. That is successful Kindle formatting.
The Kindle Resilience Scorecard
Score each dimension from 0 to 2. Zero is broken or absent, one is present but inconsistent or insufficiently tested, two is complete, consistent, and verified.
Semantic structure
Manual appearance only
Styles used inconsistently
Complete, logical style hierarchy
Navigation
Missing or broken
Partial or cluttered
Logical TOC plus a useful linked contents page
Reflow behavior
Fixed-page habits remain
Mostly reflows with weak spots
Clean across sizes and orientations
Typographic consistency
Competing local formatting
Minor inconsistencies
Restrained, consistent, reader-friendly
Media resilience
Cropped, tiny, or floating
Readable only in some views
Inline, legible, captioned, tested
Accessibility
Structure or descriptions absent
Some features implemented
Headings, alt text, language, order, links verified
Content integrity
Missing, duplicate, or wrong content
Manifest not fully checked
Converted file matches the approved source
Preview coverage
Spot-check only
Several views, incomplete book
Entire book and special elements stress-tested
13 to 16 means READY for the final KDP preflight. 9 to 12 means REPAIR before upload; the book may look acceptable in one view but remains vulnerable elsewhere. 0 to 8 means REBUILD from the source structure; do not patch isolated screens. No score can overrule a critical defect: a broken TOC, an unreadable table, a missing chapter, or the wrong manuscript file blocks publication on its own.
Take the preflight sprint with you.
This page has the workflow. The designed field guide has it in the form you actually use: twenty-nine pages built to be printed, with the Semantic Style Map, the full upload checklist, the device stress matrix, and the 90-minute sprint as working forms. Same content, better working copy.
The complete preview protocol
Preview is not a ceremonial last click. It is where the ebook becomes observable. Use the desktop Kindle Previewer and KDP's Online Previewer, in six passes.
Compare the ebook with the manifest and approved source: every front-matter item, every chapter in order, every image, table, note, and resource, no duplicated or missing passages, no old comments, no wrong version, no duplicate cover.
Test every visible TOC link, every logical navigation entry, the Beginning location, nested order, internal cross-links, footnote and return links, external links, and back navigation after following a link.
Inspect headings and first paragraphs, indents and spacing, italics and special characters, lists with wrapped lines, block quotations, chapter breaks, accidental blank screens, and stranded headings.
Inspect every image and table using the Previewer's element filters: cropping and resolution, text legibility, captions and alt text, grayscale comprehension, and tables at standard and enlarged font sizes.
Phone portrait and landscape at a large body font expose weak reflow and awkward openings. E Ink grayscale exposes contrast failures and color dependence. Tablet portrait and landscape expose hierarchy, image balance, and table behavior. A dark theme exposes forced colors and invisible text.
Use auto-advance if available, then perform a human skim from beginning to end. Automated warnings will not tell you that a chapter appears twice or a caption describes the wrong image. Keep a defect log, and retest each fix plus one chapter before and after it.
Common formatting failures and repairs
Matching the paperback page for page
Preserve hierarchy and emphasis, not page geometry. Remove print-only elements and rebuild as reflowable content.
Enlarging and bolding headings manually
Apply real heading styles and generate navigation from them.
Starting chapters with repeated blank lines
Insert a real chapter or page break. Blank paragraphs expand, collapse, or become empty screens.
Forcing justified body text
Keep reflowable body presentation flexible and inspect the converted default instead.
Leaving page numbers in the text or TOC
Remove inline numbers. Use chapter names, reader-system locations, and working links.
Using a table as a layout grid
Convert non-tabular content into linear headings, paragraphs, and lists.
Inserting the cover into the manuscript
Remove the retail cover from the content file and upload it in the cover section. KDP flags manuscript-inserted covers as a common error.
Uploading and assuming KDP will fix it
Treat the converted file as a new artifact requiring full acceptance testing.
The 90-minute Kindle preflight sprint
Run this after the production file is generated. It is a focused acceptance test, not a substitute for proper formatting; if it discovers a structural failure, stop the clock and fix the system.
Confirm the approved source filename and date, the title, subtitle, author, language, and edition. Open the manifest and defect log, and confirm the cover is separate.
Open every chapter from the logical TOC. Test the visible contents page and heading hierarchy. Confirm chapter order, the Beginning location, and first and last paragraphs.
Inspect all lists, images, and captions. Inspect tables at larger text sizes. Test footnotes, return links, and every internal and external link, and verify special characters.
Phone portrait at large type, phone landscape, E Ink grayscale, tablet portrait and landscape, and a dark theme if available. Inspect any rigid spacing.
Compare chapter and asset counts with the manifest. Search for XX, TK, TODO, and stray page references. Inspect copyright, references, and back matter.
Record every defect and classify blocking against nonblocking. Repair blockers in the source, regenerate, retest, and record the final filename and approval date.
The release gate
The full upload checklist covers six domains: source control, structure, front and back matter, body formatting, navigation and links, and media, accessibility, and preview integrity. It compresses into four statements. Publish only when all four are true.
- The file is structurally correct.
- The complete content matches the approved manuscript.
- Navigation and special elements work.
- The book remains readable under changed settings.
A Kindle book succeeds when its design survives change.
The preflight sprint takes 90 minutes, and a first pass through the full workflow takes an evening or two. That is the honest cost of a file that survives every reader's settings, and it is cheaper than the alternative, because formatting complaints arrive in public, as reviews. What the workflow cannot do is make an unvalidated book worth converting.
Galley runs the page-one checks and returns a verdict in about a minute. ENTER, CAUTION, or AVOID, with the numbers behind it. Validate the idea and plan the book first, and the chapter structure in the Blueprint becomes the semantic skeleton this guide formats: the styles, the manifest, and the navigation all inherit from a book that was planned rather than patched.
Free. No card.
Frequently asked questions
- What is the best file format for a Kindle eBook?
- There is no single best format for every workflow. KDP accepts common reflowable workflows including DOCX, Kindle Create's KPF, and standards-compliant EPUB. A simple text-led manuscript may convert well from DOCX, Kindle Create offers a guided path, and EPUB offers more control. The best file is the one your workflow can produce, validate, and fully test without losing structure or content.
- Should I upload a PDF for my Kindle eBook?
- Usually not for a text-led reflowable book. A print-ready PDF preserves fixed pages and print elements, while most Kindle books should adapt to the reader's screen and settings. Start from the editable manuscript and use a reflowable DOCX, KPF, or EPUB workflow instead.
- Do Kindle eBooks need page numbers?
- Do not type page numbers into the body or the contents list. The text changes position as readers alter font and screen settings, and KDP treats inline page numbering as a quality issue. Refer to chapters or sections and rely on working navigation.
- Should Kindle body text be justified?
- Do not force print-style justification. KDP's content-quality guidance identifies forced body alignment as a potential formatting problem, because readers should retain control of their reading experience. Inspect the platform's reflowable output instead of imposing a fixed page appearance.
- Does a Kindle eBook need a table of contents?
- Amazon requires a logical TOC, which appears through the Kindle navigation interface, and strongly recommends a visible linked contents page as well, especially for nonfiction. Both must link to the correct destinations and follow the book's order.
- Can I use custom fonts in a Kindle book?
- Custom typography can be appropriate for limited display elements, but avoid forcing a body font in a reflowable book, because readers rely on their own font and size preferences. Any embedded-font workflow also requires appropriate licensing and extensive device testing.
- How do I start each chapter on a new page in a Kindle book?
- Use a genuine page or chapter break in the source, or assign the appropriate chapter-title element in your ebook tool. Do not add repeated empty paragraphs; they expand or collapse unpredictably as settings change.
- How much previewing is enough before publishing?
- Preview the entire converted book, not a sample. Test multiple device classes, orientations, and text sizes, then inspect every high-risk element and link. The first chapters are not a representative sample of the whole file.
Your Kindle book is not a miniature paperback. It is a responsive reading system.
Structure the meaning. Let it reflow. Preview the whole book, until nothing essential depends on your own screen.
- Amazon KDP eBook Manuscript Formatting Guide
The core reflowable formatting instructions, including styles and breaks.
- Amazon KDP: Supported eBook Manuscript File Formats
Current accepted formats and their conversion behavior.
- Amazon KDP: Table of Contents with a Navigation Document
Logical and HTML table of contents requirements and recommendations.
- Amazon KDP: Guide to Kindle Content Quality
The quality issues KDP checks, including alignment, spacing, and page numbers.
- Amazon KDP: Accessibility Guidelines
Headings, alternative text, language metadata, and reading order.
- Amazon KDP: Kindle Previewer
The desktop preview tool, its device views, and element filters.
Platform requirements and tools change. Confirm current KDP instructions before production and upload.