How to Format an Ebook That Works Across Kindle, Apple Books, and Kobo

Laptop, e-reader, and smartphone displaying the same ebook chapter beside a manuscript and formatting checklist.

An ebook can look polished in a word processor and still break after conversion. Chapter titles disappear from navigation, scene breaks collapse, images become unreadable, and carefully chosen spacing behaves differently on a phone, tablet, and e-reader. The reason is simple: most ebooks are designed to reflow. Readers can change the font, text size, margins, orientation, and screen.

The safest production goal is therefore not to reproduce a printed page. It is to build a clean, structured file that reading systems can interpret consistently. Here is a practical workflow for authors preparing a text-heavy novel, memoir, or nonfiction book.

Choose reflowable unless the page itself carries meaning

A reflowable ebook lets text adapt to the reader’s screen and preferences. It is the right choice for most prose. Fixed layout preserves exact positioning and is usually reserved for picture books, comics, art books, and other projects in which words and images must stay in a precise relationship.

Apple Books currently supports EPUB 3.3 for both flowing and fixed-layout books. The W3C EPUB 3.3 specification explains that EPUB publications reflow by default and use a navigation document for the table of contents. Authors do not need to hand-code that structure, but their source document must identify headings and other elements correctly so conversion software can build it.

Clean the source before you style it

Start from a final, edited manuscript and save a separate formatting copy. Turn on nonprinting characters in your word processor so you can see paragraph marks, tabs, spaces, and manual line breaks. Replace repeated spaces and tabs with proper paragraph settings. Remove headers, footers, print page numbers, text boxes, and blank paragraphs used to push text onto a new page.

Use a page or section break before each chapter instead of pressing Enter until the next chapter moves down. For scene breaks, use one consistent marker, such as three centered asterisks, and give it its own paragraph style. Consistency makes global corrections possible and prevents a converter from guessing what a visual gap means.

Build structure with styles

Apply the word processor’s actual Heading 1 style to every chapter title. Use Heading 2 only for true subsections. Apply a body-text paragraph style to ordinary prose, and use built-in list tools for bullets and numbered lists. Changing font size or adding bold may make text look like a heading to you, but it does not give the file the structure a reading system needs.

Kobo’s Word conversion guidance, updated July 22, 2026, specifically recommends Heading 1 for chapter titles so they appear in device navigation. Kobo also warns that combining heading styles with numbered-list formatting can create validation errors.

Keep the number of styles small. A typical prose ebook may need only chapter title, body text, first paragraph, block quotation, scene break, and perhaps two levels of subheading. Control indents and spacing inside those styles. Avoid manual tabs, multiple returns, and dozens of nearly identical style variations.

Let readers control typography

Decorative fonts and rigid measurements often work against the strengths of a reflowable ebook. Readers expect to choose a comfortable font and text size. Use emphasis sparingly, reserve bold and italics for meaning, and avoid forcing body text into a particular color or size. Check that ornamental chapter elements still make sense when the font grows or the screen narrows.

Images should be large enough to remain clear but compressed so they do not bloat the file. Add concise alternative text when an image carries information. Kobo’s accessibility guidance recommends true heading and list styles, consistent formatting, descriptive links, and alt text for meaningful images. Those choices help screen-reader users and also create a better-organized file for everyone.

Export one clean EPUB and validate it

When your source is stable, export or convert it to EPUB. Amazon KDP accepts EPUB and recommends checking it with Kindle Previewer before upload. If you distribute widely, a clean EPUB is easier to test and maintain than several separately edited retailer files.

Run the file through EPUBCheck, the W3C project that checks an EPUB against the official specifications. Fix errors in the source or EPUB, regenerate the file, and validate again. A successful validation confirms the package follows the standard; it does not replace visual inspection.

Preview the places where problems hide

Do not read only the first chapter on one device. Test the beginning, middle, and end, then inspect every recurring element. Change font sizes and orientations. Preview on a phone-sized screen, a tablet, and an e-ink view when the tool provides one. Amazon’s Previewer can switch among device types, orientations, fonts, and sizes, and can isolate elements such as images, lists, and tables.

  • Open every table-of-contents link and confirm it lands on the correct heading.
  • Check chapter openings, scene breaks, block quotations, lists, footnotes, and hyperlinks.
  • Enlarge the text and watch for clipped images, overlapping elements, or stranded headings.
  • Confirm italics, special characters, em dashes, and accented letters survived conversion.
  • Inspect the final pages, including acknowledgments, author bio, newsletter link, and other books.

Use a release checklist for every retailer

Before publishing, record the EPUB version, validation date, tools used, and any retailer-specific changes. Upload the same approved content file where possible, then use each retailer’s own preview before pressing Publish. Confirm that the title, author name, language, cover, and table of contents match the listing metadata.

A reliable ebook is built through structure, validation, and deliberate testing. Clean styles give converters better instructions. Accessibility choices improve navigation. Device previews reveal problems a word processor cannot show. That process protects the reading experience long after the manuscript leaves your desk.

Leave a Reply

Your email address will not be published. Required fields are marked *