How to Format a Table of Contents for Print & eBook (2026)

Your table of contents is the first thing readers judge and the last thing most authors finish. It is the map readers use to judge your book, the navigation backbone every eBook retailer requires, and in print, one of the pages where amateur formatting shows instantly. Get it right and nobody notices; get it wrong and reviewers call your book “unprofessional” before they finish chapter one. This 2026 guide shows how to format a table of contents for print and eBook: what goes in, what stays out, how dot leaders and page numbers work in print, why eBooks need two separate TOCs, and the Kindle rules that trigger KDP rejections. It builds on our guide to chapter headings, page numbers, and running heads, applied to the TOC page and the hidden navigation files behind it.

By the end, you will know how to build a print TOC like a traditional publisher, an eBook TOC page that links to every chapter with no page numbers, and the invisible NCX or EPUB3 navigation file behind the Kindle menu — plus a Word workflow that builds all three.

Print TOC vs eBook TOC: Two Different Jobs

The single biggest source of TOC confusion is treating the print and eBook versions as the same page. They are not. A print TOC is a reference aid on paper: readers scan it, find the page number for “Chapter 7,” and flip there. An eBook TOC is a navigation system: readers tap a chapter name and teleport to it, because there are no fixed pages. Force print conventions onto an eBook — page numbers, dot leaders stretching across the line — and you create clutter that breaks on small screens.

In print, the TOC lives in your front matter, typically after the dedication and before the preface, and uses lowercase Roman numerals for its own page numbers (vii, viii) since it appears before page 1 of the body. It lists chapter and section titles exactly as they appear in the body, connected by dot leaders to right-aligned page numbers. It never lists itself, the half-title, or the copyright page, and carries no page number or running head of its own — it opens on a fresh right-hand page. Our front matter and back matter guide maps the full front-matter order if you need it.

In eBooks, the visible TOC page sits near the front and contains hyperlinked chapter titles with no page numbers whatsoever. Behind it sits an invisible navigation file — the NCX in EPUB2, or the EPUB3 navigation document — that eReaders use to build their menus. Kindle’s “Go to > Table of Contents” reads that hidden file, not your HTML page. If the hidden file is missing or broken, the reader gets a dead menu — and KDP rejects the book.

What to Include (and Exclude) in Your TOC

A good TOC is a curated map, not a dump of every heading. Always include every numbered or titled chapter, exactly as titled in the text. For nonfiction, include first-level subheadings if they genuinely help navigation. Include substantial front matter that follows the TOC itself — foreword, preface, introduction — and major back matter: appendices, notes, glossary, bibliography, index. Part divisions belong in the TOC for longer works, with chapters nested beneath.

Leave out the dedication, copyright, half-title, and title pages — readers never navigate to those — and never list the table of contents itself. Resist listing every minor subsection: four levels of nesting is harder to use than two, and eReaders flatten deep nesting into visual noise. For fiction with untitled chapters, bare “Chapter 1, Chapter 2” entries are fine, though short subtitles orient readers better. Wording must match the body text character for character: if the body says “Chapter 1: The Big Dog,” the TOC must not say “The Large Dog.”

Formatting a Print TOC: Leaders, Page Numbers, and Layout

Print TOC formatting is a small typographic craft with firm rules. The classic layout: chapter title on the left, a row of dot leaders guiding the eye across the page, page number flush right. Dot leaders are not decoration — they give the eye a path from title to number across white space. Use true tab-stop leaders (a right-aligned tab with dot leaders in Word or InDesign), never manually typed periods; hand-typed dots drift out of alignment the moment anything reflows, and the ragged result is the most common visual tell of DIY formatting.

Page numbers refer to the body’s Arabic-numbered pages, and the TOC must be rebuilt after final pagination — every late edit that shifts pages invalidates the numbers. That is why the TOC is one of the last pages you finalize. Set it in the body font, usually one point smaller than body text, and differentiate hierarchy with weight and indentation: part titles bold, subheadings indented. The comparison below summarizes print vs eBook differences at a glance.

Formatting the eBook TOC Page: Linked, Not Paginated

The visible eBook TOC page is simple in concept and unforgiving in execution. Every entry is a hyperlink to its chapter; there are no page numbers, no dot leaders, no right-aligned columns — all of which look broken on a phone screen. List chapters in reading order, keep wording identical to the chapter headings, and make the full title tappable.

One level of hierarchy is ideal; two is the practical maximum. Deep nesting that looked elegant in print becomes an unreadable thicket on a 6-inch screen, and some converters flatten nested navigation silently. Keep the page lightweight — no heavy images, no fancy tables — and test it on the smallest screen you own. And remember: the visible page is only the half readers see. The half that matters to retailers is the navigation file — no amount of beautiful HTML compensates for a missing or broken one.

The Invisible TOC: NCX and EPUB3 Navigation Documents

Every eBook carries a second, invisible table of contents that readers never see directly but use constantly. When a Kindle reader taps “Go to > Table of Contents,” the device reads this hidden navigation file — not your HTML TOC page. Two formats exist. The NCX is the EPUB2 standard: an XML file with a navMap of navPoints, each pointing to a chapter in playOrder sequence. Amazon’s KDP documentation calls this the “Kindle Interactive TOC” — entries must be in chronological order, include every chapter and section, contain no duplicates, and have no typos. The EPUB3 navigation document is the modern replacement: an XHTML file with a nav element marked epub:type=“toc”, declared in the OPF manifest with properties=“nav”.

Either format satisfies Kindle conversion; having neither is not an option. Amazon’s conversion documentation states there is no synthesized TOC fallback — upload an EPUB with no navigation and the converter cannot invent one. You rarely hand-write these files: Kindle Create generates both TOCs from a Word manuscript when chapter titles use real Heading 1 styles, as do Vellum, Atticus, Draft2Digital, and Calibre. What you must do is verify: the “broken NCX view” — a Kindle menu that lists chapters but jumps nowhere — almost always traces to manually typed TOC entries, duplicated anchors, or chapters styled as bold text instead of true headings.

Kindle TOC Rules and KDP’s Navigation Checks

Amazon treats a working table of contents as a quality gate, and books fail its navigation checks regularly. First, your eBook must contain both TOCs: the hyperlinked HTML page near the front and the logical TOC (NCX or EPUB3 nav) the device menu reads, with every chapter in reading order, no duplicates, no typos. Second, every link must resolve — the converter rejects books with unresolved link targets, duplicate anchors, or entries pointing at content outside the spine. A chapter that exists in the HTML TOC but was deleted from the manuscript is a rejection waiting to happen.

Third, build from styles, not formatting. In MS Word, chapter titles must use the Heading 1 style. Manually bolded, enlarged text looks like a heading to you and like body text to every converter — your chapters silently vanish from the generated navigation. Subheadings in the hierarchy get Heading 2 and Heading 3. Fourth, mind the basics: DRM-free reflowable EPUB is the expected input, MOBI is no longer accepted for new uploads, and the cover must be the first element in the file. Our complete Kindle eBook formatting guide covers the full upload checklist beyond navigation. Preview every upload in Kindle Previewer and click through the TOC on e-ink, tablet, and phone layouts.

From Word to Finished Book: A TOC Workflow That Works

Here is the workflow professional formatters use to produce both TOCs from a single Word manuscript. Start with styles, applied from chapter one: every chapter title gets Heading 1 — real Heading 1 from the Styles gallery, not lookalike formatting. Subheadings that belong in the TOC get Heading 2. Front matter (Foreword, Preface, Introduction) and back matter (Appendix, Notes) get Heading 1 too. Do this as you write; retrofitting styles onto a finished 90,000-word manuscript is where most TOC disasters begin.

For print, generate the TOC with Word’s automatic table of contents (References > Table of Contents) after final pagination — never before. Word builds it from your Heading styles with proper tab-stop dot leaders and correct page numbers in one click. Review entries against the body text, fix mismatches at the source heading, regenerate, and repeat after any edit that shifts pagination. Export to PDF only when the TOC is final.

For the eBook, forget page numbers entirely. Import the styled Word file into Kindle Create, which builds the HTML TOC page and the Kindle Interactive TOC from your Heading 1 styles automatically — Draft2Digital, Atticus, and Vellum do the same. Then verify both: click every link on the HTML TOC page, and open the book in Kindle Previewer to confirm “Go to Table of Contents” lists every chapter in order and jumps correctly. Fix problems in the Word source — never by hand-editing generated files — and regenerate.

7 TOC Mistakes to Avoid

Check your book against this list before you upload or send anything to print. For the wider pre-publish sweep, pair it with our book formatting mistakes roundup.

• Page numbers in an eBook TOC — eBooks have no fixed pages; numbers are meaningless and mark the book amateur instantly.
• Dot leaders in an eBook TOC — with no page numbers to point at, they are noise on small screens.
• TOC titles that differ from the chapter headings — small mismatches break navigation checks.
• Listing the TOC itself, the dedication, or the copyright page — clutter no reader ever needs.
• Hand-typed dots instead of tab-stop leaders in print — they drift on reflow and look DIY.
• Finalizing the print TOC before final pagination — always build it last.
• A missing or broken NCX/nav document — the Kindle menu dies or KDP rejects the upload; generate from Heading styles and verify in Kindle Previewer.

Conclusion: Your TOC Is a Promise

Your table of contents is a promise: this book is organized, this author is professional, and you will always know where you are. In print, keep that promise with tab-stop dot leaders, page numbers rebuilt after final pagination, and a curated list matching the body text exactly. In eBooks, keep it with a clean hyperlinked TOC page and a verified navigation file. Build both from real heading styles in one source manuscript, verify every link in Kindle Previewer, and finalize the print TOC last. Do that, and the page everyone judges first needs no second thought.