KDP Table of Contents: eBook Navigation and Print TOCs That Work
Build reliable KDP eBook navigation and accurate print tables of contents using heading styles, tested links, final page numbers, and format-specific QA.
A table of contents is easy to overlook because the page itself looks simple. The real test is whether every entry, heading, destination, and page number still works after the manuscript has been converted and paginated.
KDP treats eBook navigation and print contents pages as different production problems. A Kindle book needs reliable navigation in a reflowable file, while a print TOC has to reflect fixed page numbers after layout is final. Trying to build one TOC early and reuse it unchanged across both formats is how broken links and wrong page numbers survive into publication.
The safest workflow starts with consistent heading styles in the source manuscript. Use the KDP manuscript preparation checklist first, then generate and test the TOC after the book’s structure is stable.
The Two TOC Functions in a Kindle eBook
KDP’s current TOC guidance describes two useful navigation structures. The first is a visible TOC page in the book, often called the HTML TOC, where the reader can see a list of chapters or sections and tap an entry. The second is the Kindle Interactive TOC, the navigation structure available from the Kindle reading interface.
Modern EPUB files may express navigation using EPUB navigation documents rather than the old NCX terminology you still see in legacy tutorials. The practical requirement is unchanged: Kindle needs a logical navigation structure that points to the correct places. Do not assume that a visually attractive contents page automatically creates working device navigation.
Dedicated tools such as Kindle Create, Vellum, and Atticus can generate the navigation structure from correctly marked chapter headings. Word-based workflows can also work, but they depend on real heading styles and clean conversion rather than manually enlarged text.
Does Every eBook Need a Visible TOC Page?
A usable Kindle navigation structure is important for every long-form eBook. Whether a visible contents page improves the reading experience depends on the book. Practical nonfiction, reference books, textbooks, collections, and books with titled sections usually benefit from a visible TOC because readers often move nonlinearly through the material.
For straightforward fiction with simple numbered chapters, a front-matter TOC page can be less useful to the reader than device navigation alone. Do not remove it merely because another novel omitted one, and do not add one merely because an old template included it. Test the finished book and use the structure that makes navigation clear for that audience.
Build the Source Around Heading Styles
TOC reliability begins before conversion. Chapter titles should use a consistent heading style, and nonfiction subheads should follow a logical hierarchy. Manual formatting, such as making a line 18-point bold without assigning a heading style, may look correct in Word while remaining invisible to the conversion tool.
Keep heading text stable before generating the final TOC. If you rename “Chapter 7: Market Research” to “Finding Your Market” late in production, update both the navigation structure and any visible contents page. This is one reason the pre-formatting checklist puts structural cleanup before final layout.
Creating and Updating a TOC in Word
Word can generate a table of contents from heading styles. Use the built-in TOC feature rather than typing chapter names and page numbers manually. For print, update the TOC only after pagination is stable because any edit that changes page flow can change several page numbers at once.
For an eBook conversion, the visible Word TOC is only part of the job. The converter or formatting tool still needs to create valid Kindle navigation from the document structure. After conversion, test the actual Kindle file rather than assuming that working links inside the DOCX survived unchanged.
TOC Depth: Show the Structure Readers Need
More levels are not automatically better. A 300-page nonfiction book with 60 sub-subsections can produce a contents page that is harder to scan than the book itself. Use enough depth to help readers understand the architecture and jump to meaningful destinations, while leaving minor subheads out of the visible TOC if they create noise.
The interactive navigation can be somewhat more detailed than the printed page when that helps orientation. Whatever depth you choose, keep the hierarchy consistent. A Heading 3 should not appear as if it were a top-level chapter, and two headings with the same visual level should not perform different structural roles.
Print TOCs: Page Numbers Must Be Final
A print TOC is a fixed-page reference. It normally lists chapter or section titles with the page where each begins. Page numbers are therefore only trustworthy after the trim size, font, margins, images, front matter, and all text changes have stabilized.
Do not finalize page-number formatting until you know where front matter ends and the main text begins. Some books use roman numerals in front matter and Arabic numerals in the body; others suppress visible numbers on certain opening pages while still counting them in pagination. The TOC must reflect the numbering readers actually see, not the raw page sequence in the editing file.
Regenerate the print TOC after any late change that can move text. Then spot-check entries throughout the book, including the final third, where unnoticed drift often becomes obvious. The KDP typography guide explains how heading hierarchy and page design affect the printed contents page.
Common TOC Failures and How to Catch Them
A useful final check is to compare three lists side by side: the headings in the manuscript, the entries in the visible TOC, and the destinations in Kindle navigation. They should describe the same book structure even if the visible TOC intentionally shows fewer minor subheadings. This catches the subtle cases where a chapter exists in the manuscript but was excluded from navigation because its style changed during editing.
The most common problems are stale page numbers, links that land one heading early or late, duplicated entries, missing chapters, headings that appear at the wrong level, and a navigation menu that does not match the visible TOC. These errors usually come from inconsistent styles or from changing the manuscript after the TOC was generated.
Use Kindle Previewer for the eBook and Print Previewer for the print edition. For Kindle, test both the in-book contents page and the device navigation. For print, compare the TOC against the final PDF page by page. If you are also publishing a hardcover with different pagination, generate a separate print TOC for that edition rather than assuming the paperback page numbers will match.
Where the TOC Fits in the Wider Front Matter
In nonfiction, the contents page usually sits after the title and copyright material and before the main body, although the exact order depends on the book. Fiction can use much lighter front matter. The important point is that the TOC should support the reading experience rather than become a wall of administrative material before chapter one.
See the KDP front matter and back matter guide for the wider sequence. If the manuscript structure is still changing, finish that work before polishing a TOC that will immediately become stale.
Frequently Asked Questions
Does every Kindle eBook need navigation?
A Kindle book should have reliable logical navigation. KDP’s current guidance describes both a visible TOC page and the Kindle Interactive TOC; the exact visible presentation should suit the book while the navigation itself must work.
Can I type a TOC manually in Word?
You can, but it is fragile. A TOC generated from consistent heading styles is easier to update and much less likely to contain stale page numbers or mismatched chapter names.
Should fiction include a visible table of contents?
It depends on reader value and structure. Titled chapters, collections, and complex books often benefit from one; simple linear fiction may rely more heavily on Kindle navigation. Test the finished book rather than following a blanket rule.
Do paperback and hardcover TOCs use the same page numbers?
Only if the interiors genuinely paginate identically. Different trim sizes, fonts, paper choices, or layout settings can change page numbers, so validate each print edition separately.
How many heading levels should I include?
Include enough levels to reveal meaningful structure without turning the TOC into an index. Most readers need chapters and major sections more than every minor subheading.
What is the fastest TOC QA check?
In the eBook, tap every entry and use the Kindle navigation menu. In print, compare each listed page number with the final PDF after all text and layout changes are complete.
What to Do Next
Stabilize the heading hierarchy, generate the TOC from that structure, and then test the converted eBook and final print PDF separately. If the book changes after that point, regenerate the TOC rather than patching individual entries by hand.
