An Ebook Formatting Checklist You Can Run Before Upload

Your book passed beta reads, edits, and proof passes, and now the file itself stands between you and publication. Roughly ninety minutes of checklist work separates a professional-looking ebook from one that opens with a wall of unstyled text.

An ebook file needs four things: every heading tagged with an actual style, a clickable table of contents, zero manual spacing hacks, and a test run on a real reading device. Get those right and most remaining issues are cosmetic.

What You Are Actually Formatting

An ebook is not a fixed layout. Readers pick their font, size, margins, and line spacing, so your job is not to make pages look pretty. Your job is to give the reading app clean structure it can restyle however the reader wants.

That changes what matters:

Fixed print concern	Ebook equivalent
Page breaks between chapters	Chapter headings the reader can navigate to
Headers, footers, page numbers	Nothing. They get stripped anyway
Exact font choices	True italics and bold only, nothing else styled manually
Visual table of contents	A linked table of contents with no page numbers
Decorative dividers	Simple centered scene breaks

Everything on your checklist flows from this principle: structure over appearance.

The Pre-Upload Checklist

Run through each row before you convert anything.

#	Check	Why it matters	How to verify
1	Chapter titles use a real Heading 1 style	Navigation and the auto-generated TOC depend on it	Click into a title. The style box should say Heading 1, not Normal with bold applied
2	Subheadings use Heading 2	Keeps hierarchy intact across devices	Scroll and spot-check any chapter with subsections
3	Chapters end with a single insert, not empty paragraphs	Empty lines create gaps that resize on different screens	Turn on formatting marks and delete runs of blank paragraphs
4	Paragraph indents come from styles, not tabs or spaces	Tabs render inconsistently, first-line space sometimes collapses	Search for tab characters and leading spaces
5	Italics are true italics	Fake styling breaks when converted	Spot-check internal thoughts and emphasized dialogue
6	Scene breaks are simple centered marks	Fancy graphics convert badly	Standardize on asterisks or a similar plain mark
7	Table of contents is hyperlinked, no page numbers	This is what readers actually tap	Confirm every entry jumps to the right chapter
8	Front matter is ordered: title page, copyright, dedication, TOC	Reading apps display this sequence	Read the file from the top once
9	Metadata title matches your title page	Mismatches confuse store listings	Compare the file properties to the visible title
10	You tested the final file on a device	Conversion quirks only show up in a reader	See the test procedure below

Item ten is the one authors skip, and skipping it causes the most reuploads.

Fixing the Most Common Failure: Headings

Most DIY formatting problems trace back to one habit, typing a chapter title, hitting enter twice, and making the text bigger and bolder by hand.

Here is what conversion sees in each case.

Before, manually styled:

CHAPTER FOUR

(large bold regular paragraph, followed by two blank lines)

She hadn't expected him to still be standing there.

After, properly structured:

CHAPTER FOUR

(one Heading 1 paragraph, followed by one blank line)

She hadn't expected him to still be standing there.

To a human eye these look nearly identical. To a converter, the first version is unlabeled text with invisible gaps. The second version declares a chapter. When you generate a table of contents automatically, or when a reading app builds its navigation menu, only the second version gets found.

The fix takes one pass: open your Styles panel, select every chapter title, apply Heading 1, then search for consecutive blank paragraphs and collapse them to one. If your document has fifty chapters, use your editor's outline view, which lists only heading-styled paragraphs, to confirm nothing was missed.

Building the Table of Contents Last

Do not hand-type your TOC. Once your headings carry real styles, every major tool can generate a linked contents list from your heading styles, and a generated list stays correct even after you reorder or rename chapters.

Three details to check on the generated result:

1. Every entry navigates. Click through all of them in the source document.
2. No page numbers exist. Ebooks reflow, so page references are meaningless noise.
3. Back matter entries appear too, including your author note and any series links, because readers navigate backward as often as forward.

Order the linked TOC early in the book where store previews stop. Physical placement matters less than completeness, since every reader app also builds its own menu from your heading tags, but a visible TOC near the front keeps detail-oriented readers happy.

The Ten-Minute Device Test

Conversion hides mistakes until they reach a screen, so finish with a dry run.

The test: Load your final file onto whatever reader you own, plus at least one other environment such as a phone app, then page through the entire book at speed.

Check five things per chapter: the chapter title appears in the navigation menu, the first paragraph starts correctly with no orphan gap, scene breaks sit centered and alone, italic passages render italic, and the linked TOC lands on the right chapter.

Anything that looks off here will look worse on hardware you don't control, so fix and reconvert until a full skim comes back clean.

At minimum, preview on a small phone screen. Narrow viewports expose spacing hacks and wide tables immediately.

Cleaning Up Manuscripts From Other Workflows

Files drafted elsewhere usually arrive carrying baggage: tracked changes nobody accepted, comment bubbles, pasted-in web content with hidden formatting, inconsistent chapter labels. Strip that before you touch styles. Save a copy, clear all comments and revision marks, paste any externally sourced text back in using a plain-text intermediate step, and normalize every chapter label to the same pattern.

If you draft or revise inside WriteWithPaige, the manuscript comes out cleaner to begin with because the platform's EPUB export produces a structured file from your project directly, so revisions stay finished inside the tool instead of drifting back through word processors before export. The manuscript import feature lets you bring existing drafts into that pipeline when you would rather clean once than fight formatting flags repeatedly. Whichever route you take, the uploaded file still deserves the same ten-minute device test. For the fuller release process beyond formatting, the Kindle self-publishing walkthrough covers what happens after your file is clean.

Formatting is the least creative hour of publishing. Do it once, deliberately, and every future release speeds up, because the template and style set you built today becomes tomorrow's starting point.