KDP Table of Contents: eBook Navigation and Print TOCs That Work

By the time you reach the table of contents, the manuscript is usually starting to feel like a finished book. The chapters are in order, the headings are styled, and the contents page can seem like a straightforward final step.

With KDP, there is one important distinction: Kindle and print need different things from a TOC. Kindle readers need working navigation, while a paperback or hardcover needs page numbers that match the final layout.

Fortunately, both versions can start from the same clean heading structure. Once that is in place, the job is much simpler: generate the right TOC for each format and check it before publication.

This guide shows you how to do that in Word, Kindle Create, and other formatting tools, including what to include and what to test before you publish.

What Table of Contents Does a Kindle eBook Actually Need?

Amazon currently distinguishes between two navigation layers in a Kindle eBook: the logical TOC and the HTML TOC. Understanding the difference removes much of the confusion created by older tutorials that use terms such as NCX, interactive TOC, navigation TOC, and in-book contents page almost interchangeably.

The logical TOC is the part that remains available from the Kindle reading interface as the reader moves through the book. It exposes the book’s navigable structure and helps readers understand where they are in relation to the surrounding chapters and sections.

Current KDP guidance recommends building this logical TOC with an EPUB navigation document. NCX navigation is still supported, which is why the term continues to appear in Amazon documentation and older publishing tutorials, but KDP says the navigation document is preferred when one is present.

The practical lesson is simple: do not assume that an attractive contents page inside the manuscript automatically creates working Kindle navigation. Both layers need to survive conversion.

Does Every Kindle eBook Need a Visible Contents Page?

The logical TOC is required. The visible HTML TOC is not described by Amazon as universally mandatory, but KDP currently strongly recommends including one near the beginning of the book.

That distinction matters for fiction. It is tempting to conclude that a novel with 25 numbered chapters gains little from displaying all 25 chapter numbers on a contents page. From a purely editorial perspective, that may be true. Amazon nevertheless recommends the visible TOC because readers expect it and because it provides another route through the book, including on devices where navigation support differs.

For nonfiction, textbooks, collections, reference books, workbooks, and books with titled chapters or major sections, the case for a visible contents page is even stronger. Readers often use those books nonlinearly and need to see the structure before deciding where to go.

When an HTML TOC is included, Amazon says the entries should be actual links rather than page-number references. Reflowable Kindle books do not have stable print-style pagination, so page numbers should not be added to the eBook contents page.

How Should Chapter Headings Be Set Up?

A reliable table of contents starts with the chapter headings, not with the contents page. If the manuscript does not identify its structure consistently, the formatting tool has to guess what counts as a chapter, section, or subheading.

In Microsoft’s Word-based KDP workflow, Amazon currently instructs authors to apply Heading 1 to chapter titles. That gives the chapter names a consistent structural role and allows Word to build an automatic table of contents from them.

Heading 1 is a Word workflow, not a universal Amazon rule for every formatting application. Kindle Create detects and tags chapter titles through its own structure, while EPUB editors, Atticus, Vellum, and other tools can establish navigation in different ways. The important principle is that the chapter structure is explicit and consistent before the TOC is generated.

Keep chapter names stable before final conversion as well. If “Chapter 7: Market Research” becomes “Finding Your Market” after the TOC has been generated, every navigation layer that still carries the old title needs updating.

This is one reason the KDP manuscript preparation checklist puts structural cleanup before final formatting.

How Do You Create a KDP Table of Contents in Word?

For a Word-based Kindle workflow, Amazon’s current instructions use Word’s automatic TOC rather than a manually typed chapter list. This gives the contents page real links and lets it update when chapter titles change.

For a straightforward chapter-based Kindle eBook, the current KDP Word workflow is:

That final step is the important one. A hyperlink working in Word proves that it works in Word. The published product is the converted Kindle file, so that is where navigation needs to be tested.

A print edition needs a different final treatment. Page numbers belong in a print TOC because the layout is fixed. If one Word manuscript is being used to produce both editions, create format-specific outputs rather than leaving print page numbers in the Kindle contents page or eBook-style links in the final printed design.

Kindle Create can automate more of this. It detects chapter titles, builds the Kindle Interactive TOC, and can insert a visible TOC page. In supported print workflows, Kindle Create can then remove the eBook links and add page numbers when the paperback is processed. That automation belongs to the Kindle Create workflow and should not be assumed to happen in every formatting application.

How Much Detail Should a Kindle TOC Include?

A useful TOC reveals structure. It does not reproduce every heading simply because the formatting software can find it.

For a novel, chapter-level navigation may be enough. A practical nonfiction book may need parts and chapters. A reference book may justify another layer when readers frequently jump to major subsections.

Amazon’s current navigation guidance supports two levels of nesting in Kindle devices and applications. That makes hierarchy particularly important. The highest level should represent the book’s major divisions, with the second used only where it genuinely helps the reader understand what sits inside them.

The logical navigation should still represent the meaningful navigable structure accurately. Do not shorten it by accidentally excluding a real chapter because one title was given the wrong style.

How Is a Print Table of Contents Different?

A print TOC answers a different reader question: Which physical page do I turn to? That makes page numbers useful in print and inappropriate in the visible TOC of a reflowable Kindle eBook.

Page numbers are only trustworthy once pagination is stable. Changing the trim size, body font, margins, image dimensions, front matter, heading spacing, or even a few paragraphs can move chapter openings throughout the book.

Generate or update the print TOC after those variables are settled. Then spot-check entries throughout the book rather than checking only the first few chapters. A contents page that is accurate through Chapter 3 can still drift later if a substantial edit has moved the rest of the manuscript.

Front-matter numbering also needs attention. Some books use roman numerals for preliminary pages and Arabic numerals for the main body; others suppress visible numbers on opening pages while still counting them in the pagination. The contents page should reflect the numbering system the reader actually encounters.

Paperback and hardcover TOCs should also be verified separately whenever the editions have different trim sizes, fonts, margins, or other layout settings. Sharing the same manuscript does not guarantee identical pagination.

The KDP typography guide explains how font size, line length, spacing, and hierarchy can alter the final print layout.

How to Catch a Broken TOC Before Publishing

The most useful QA method is to compare the structure in three places: the manuscript, the visible TOC, and the Kindle navigation menu. They should all describe the same book, even when the visible TOC is deliberately less detailed than the underlying structure.

Use Kindle Previewer for the eBook. Amazon’s current Previewer guidance specifically recommends checking both the visible TOC page and the Kindle Interactive TOC, confirming that every item is clickable and leads to the correct location. :contentReference[oaicite:2]{index=2}

For print, check the final PDF rather than the editable Word manuscript. That is the file whose pagination is actually going to print.

Where Should the Table of Contents Go?

For Kindle, Amazon recommends placing the visible HTML TOC toward the beginning of the book rather than at the end. That makes it available naturally to readers paging forward through the front matter and helps it function as part of the book’s navigation rather than as an appendix.

In a print nonfiction book, the contents page usually sits in the front matter after the title and copyright material and before the main body. The exact front-matter sequence can vary by book and genre, but the TOC should not become a barrier of administrative pages between the reader and the actual content.

If a long TOC runs across several pages, make sure the hierarchy remains visually obvious. Indentation, spacing, and typography should help readers distinguish parts, chapters, and lower-level entries without turning the contents page into a dense index.

The KDP front matter and back matter guide covers the wider sequence and which front-matter elements different books actually need.

Frequently Asked Questions

What to Do Next

Start with the headings, not the contents page. Make sure every real chapter and section has a consistent structural role, stabilize the chapter names, and only then generate the TOC from that structure.

For Kindle, verify both layers: the visible clickable contents page and the logical navigation available through the reading interface. For print, wait until pagination is stable, update the page numbers, and check the final PDF rather than relying on what Word showed several revisions earlier.

The useful test is not whether the TOC looks finished. It is whether a reader can choose any entry, follow it, and arrive exactly where the book promised to take them.