How to format a manuscript for Kindle

Most Kindle formatting problems come from treating an ebook like a printed page. A print page is fixed: you know its size, so you can position things on it. An ebook reflows — the reader chooses the font, the size, the margins and the screen — so anything positioned by hand will land somewhere you did not intend.

The fix is to stop describing appearance and start describing structure.

Four habits to unlearn

Manual indents

Tabs and rows of spaces at the start of paragraphs are absolute measurements pretending to be typography. Rendered on a small screen at large type, a tab can throw a line halfway across it. Set first-line indent in the paragraph style instead and delete every tab in the document.

Empty paragraphs for spacing

Pressing Enter repeatedly to push a chapter heading down the page produces blank lines that reflow with everything else, so the heading lands in a different place on every device. Use paragraph spacing and page breaks.

Direct formatting instead of styles

Selecting a chapter title and making it 18pt bold looks like a heading and is not one. It carries no structural meaning, so it cannot generate a table of contents, and the Kindle cannot treat it as a chapter start. Apply a real Heading 1 style and change what that style looks like.

Section breaks marked with blank lines

A scene break shown as an empty line disappears when the line falls at the bottom of a screen — the reader sees a paragraph break and loses the transition. Use a visible marker, centred: three asterisks, a small ornament, something the reader can see.

What to do instead

  1. Style everything. Heading 1 for chapter titles, a body style for prose, a separate style for the first paragraph of each chapter if it is unindented.
  2. Start chapters with a page break, applied through the style rather than typed in.
  3. Build the table of contents from headings so it links, rather than typing one out.
  4. Use paragraph spacing settings, not empty paragraphs.
  5. Insert images at a sensible width and let them scale; do not position them absolutely.

The table of contents

Kindle expects a linked, navigable contents list, and it is generated from your heading styles — which is the practical reason styles are not optional. If chapter titles are direct-formatted text, there is nothing to generate from.

A generated contents list also lets the device's chapter navigation work, which readers use constantly and notice immediately when it is missing.

Front and back matter

Keep the front matter short. On Kindle, the sample readers download is a fixed proportion of the file measured from the start — so six pages of front matter spend the sample on your copyright notice instead of your first chapter. Title page, copyright, and straight into the book.

Back matter is where the work pays off. An author's note, a link to your mailing list and a short list of your other books sit at the exact moment a reader has just finished and is most inclined to act.

Checking it

Amazon's Kindle Previewer renders your file the way real devices will and is the only check that counts. Look at it on the smallest phone size and the largest tablet size, and turn the type up two steps beyond what you would use yourself.

  • Does every chapter start on a new screen?
  • Do the contents links go where they say?
  • Are scene breaks visible when they fall at a screen edge?
  • Do images fit on a phone without horizontal scrolling?
  • Is there a stray tab anywhere?

When to hand it over

Plain narrative prose is genuinely a do-it-yourself job, and doing it once teaches you why the rules exist. It stops being one when the book has structure to preserve: tables that must hold their shape, footnotes, verse with meaningful line breaks, images with captions that must stay attached, or anything with two columns.

Reflowable text and fixed layout pull in opposite directions, and reconciling them is a specialist job rather than a patient afternoon.

Common questions

Can I just upload a Word document?
KDP accepts .docx and converts it, and for a cleanly styled prose manuscript the result is usually good. The conversion is only as good as the styling underneath, which is why the habits above matter more than the file format.
Do I need separate files for ebook and paperback?
Yes. The paperback is a fixed-layout PDF with real margins, gutters and page numbers; the ebook reflows. They are different documents built from the same text.
Will my fonts carry over?
Largely not, and that is by design — readers choose their own font and size on Kindle. Embedded fonts are possible in some formats but are overridden by reader settings in most reading modes.