{"id":12143,"date":"2026-04-06T19:03:25","date_gmt":"2026-04-06T19:03:25","guid":{"rendered":"https:\/\/www.vappingo.com\/word-blog\/?p=12143"},"modified":"2026-09-02T21:22:52","modified_gmt":"2026-09-02T21:22:52","slug":"table-of-contents-kdp-ebooks","status":"publish","type":"post","link":"https:\/\/www.vappingo.com\/word-blog\/table-of-contents-kdp-ebooks\/","title":{"rendered":"Table of Contents for KDP eBooks: Build Kindle Navigation That Actually Works"},"content":{"rendered":"<p><!-- vg-modern-guide --><\/p>\n<section aria-label=\"Article highlights\" class=\"vg-stats\">\n<div class=\"vg-stat\">\n<div class=\"vg-stat-icon\"><svg class=\"vg-svg\" viewBox=\"0 0 24 24\" aria-hidden=\"true\"><rect x=\"5\" y=\"3\" width=\"14\" height=\"18\" rx=\"2\"\/><path d=\"M8 8h8M8 12h8M8 16h5\"\/><\/svg><\/div>\n<div><strong>2<\/strong><span>TOC experiences: logical and visible HTML<\/span><\/div>\n<\/div>\n<div class=\"vg-stat\">\n<div class=\"vg-stat-icon\"><svg class=\"vg-svg\" viewBox=\"0 0 24 24\" aria-hidden=\"true\"><path d=\"M12 3 20 6v6c0 5-3.4 8.1-8 9.5C7.4 20.1 4 17 4 12V6l8-3Z\"\/><path d=\"m8.5 12 2.2 2.2 4.8-5\"\/><\/svg><\/div>\n<div><strong>1<\/strong><span>logical TOC required by Amazon<\/span><\/div>\n<\/div>\n<div class=\"vg-stat\">\n<div class=\"vg-stat-icon\"><svg class=\"vg-svg\" viewBox=\"0 0 24 24\" aria-hidden=\"true\"><path d=\"M12 3 2.7 20h18.6L12 3Z\"\/><path d=\"M12 9v5M12 17.5v.1\"\/><\/svg><\/div>\n<div><strong>0<\/strong><span>stable page numbers in a reflowable Kindle book<\/span><\/div>\n<\/div>\n<\/section>\n<p class=\"vg-stat-note\">A working Kindle TOC comes from document structure, not from a page that merely looks like a contents page. Build the hierarchy once, generate the navigation from it, and test the actual Kindle behavior before you publish.<\/p>\n<nav aria-label=\"Article contents\" class=\"vg-toc\">\n<div class=\"vg-toc-title\">In this guide<\/div>\n<ol>\n<li><a href=\"#two-tocs\">Kindle Uses Two Different TOC Experiences<\/a><\/li>\n<li><a href=\"#word\">Building a Reliable TOC in Microsoft Word<\/a><\/li>\n<li><a href=\"#kindle-create\">Kindle Create: The Lowest-Friction KDP Route<\/a><\/li>\n<li><a href=\"#epub\">If You Upload EPUB<\/a><\/li>\n<li><a href=\"#mistakes\">The TOC Mistakes That Cause the Most Problems<\/a><\/li>\n<li><a href=\"#test\">How to Test the TOC Before Publication<\/a><\/li>\n<li><a href=\"#repair\">How to Repair a Broken Live TOC<\/a><\/li>\n<li><a href=\"#word-troubleshooting\">When Word&#8217;s Automatic TOC Still Goes Wrong<\/a><\/li>\n<li><a href=\"#fiction-nonfiction\">How Much Detail Should the TOC Show?<\/a><\/li>\n<li><a href=\"#faq\">Frequently Asked Questions<\/a><\/li>\n<li><a href=\"#final-thought\">Build Navigation Into the Book, Not Onto the Page<\/a><\/li>\n<\/ol>\n<\/nav>\n<div class=\"vg-reading-column\">\n<p>A Kindle table of contents is navigation, not decoration. A list of chapter titles can look perfect in Word and still fail on a Kindle if the ebook does not contain the structural links Amazon uses for the Go To menu and chapter navigation.<\/p>\n<p>Amazon currently requires a logical TOC for Kindle books and strongly recommends a visible HTML TOC. The easiest way to get both right is to build the manuscript around real heading structure, let a reliable formatter generate navigation, and test the exported book in Kindle Previewer before upload.<\/p>\n<h2 id=\"two-tocs\">Kindle Uses Two Different TOC Experiences<\/h2>\n<p>The logical TOC is the navigation structure Kindle uses in its Go To menu. In a modern EPUB, that navigation is normally represented by the EPUB navigation document. Readers may never see it as a conventional page, but it is essential because Kindle uses it to expose chapters and sections through device navigation.<\/p>\n<p>The HTML TOC is the visible contents page inside the ebook. Amazon strongly recommends it because readers expect a tappable list near the front of many books. The visible page and the logical navigation can be generated from the same chapter structure, but they are not the same thing.<\/p>\n<aside class=\"vg-alert vg-alert-amber\">\n<div class=\"vg-kicker\">Amazon&#8217;s current TOC rule<\/div>\n<p>Amazon requires a logical TOC for Kindle books and strongly recommends an HTML TOC near the front of the book. <a href=\"https:\/\/kdp.amazon.com\/en_US\/help\/topic\/G201605710\" target=\"_blank\" rel=\"noopener\">See KDP&#8217;s TOC guidance<\/a>.<\/p>\n<\/aside>\n<h2 id=\"word\">Building a Reliable TOC in Microsoft Word<\/h2>\n<p>Use Word&#8217;s built-in heading styles for chapter and section titles rather than manually changing font size and bold. Heading 1 is the safest choice for chapter-level structure, with Heading 2 and lower levels used only where you genuinely want a hierarchy.<\/p>\n<p>Then use Word&#8217;s automatic Table of Contents feature rather than typing chapter titles and page numbers yourself. Reflowable Kindle books do not have stable page numbers, so a print-style TOC built around page references is the wrong model. Update the Word TOC after any chapter rename, addition, or deletion before you create the ebook file.<\/p>\n<h2 id=\"kindle-create\">Kindle Create: The Lowest-Friction KDP Route<\/h2>\n<p>Kindle Create can generate a TOC page and Kindle interactive TOC from the structure it recognizes in the manuscript. It currently exports KPF and, for reflowable books, EPUB. Amazon describes KPF as the preferred Kindle Create output when you want access to the full set of supported Kindle formatting features.<\/p>\n<p>The advantage is that Kindle Create handles much of the navigation structure for you. The tradeoff is that you still have to inspect which headings it recognized. A chapter title omitted from the structure will not become correct merely because the export succeeded.<\/p>\n<aside class=\"vg-alert vg-alert-amber\">\n<div class=\"vg-kicker\">Current Kindle Create outputs<\/div>\n<p>Kindle Create currently exports KPF and EPUB for reflowable books. Amazon recommends KPF when publishing through KDP because it preserves the full Kindle Create feature set. <a href=\"https:\/\/kdp.amazon.com\/en_US\/help\/topic\/GUGQ4WDZ92F733GC\" target=\"_blank\" rel=\"noopener\">See Kindle Create<\/a>.<\/p>\n<\/aside>\n<h2 id=\"epub\">If You Upload EPUB<\/h2>\n<p>KDP accepts EPUB files that meet its Kindle publishing specifications. A well-built EPUB should include a valid navigation document and chapter anchors, and the file should be tested in Kindle Previewer before publication.<\/p>\n<p>Do not assume an EPUB validator and Kindle Previewer answer exactly the same question. EPUB validation checks structural conformance; Kindle Previewer shows how Amazon&#8217;s conversion is likely to behave across Kindle reading environments. Use both when the file is complex.<\/p>\n<h2 id=\"mistakes\">The TOC Mistakes That Cause the Most Problems<\/h2>\n<p>The common failures are predictable: manually typed page numbers, chapter titles formatted to look like headings without real heading structure, stale TOC entries after chapter renaming, duplicate chapter names that point to the wrong anchor, broken links after conversion, and a visible TOC that works while the Go To navigation remains incomplete.<\/p>\n<p>Another mistake is overloading the TOC. A long nonfiction book may need section-level navigation, but a novel rarely benefits from dozens of scene-level entries. The TOC should help readers move through the book rather than expose every internal formatting decision.<\/p>\n<h2 id=\"test\">How to Test the TOC Before Publication<\/h2>\n<p>Open the final EPUB, DOCX, or KPF workflow in Kindle Previewer and test the Go To menu first. Confirm that every intended chapter appears once and that each entry lands at the correct heading. Then open the visible TOC and tap every important link.<\/p>\n<p>Test more than one device view because reflow can expose odd spacing or heading behavior. Finally, use KDP&#8217;s Online Previewer after upload for one last check. The file you tested locally is not the finished customer experience until it has passed Amazon&#8217;s conversion path too.<\/p>\n<h2 id=\"repair\">How to Repair a Broken Live TOC<\/h2>\n<p>Fix the source manuscript or formatting project rather than patching the converted file blindly. Correct heading structure, regenerate the navigation, export a fresh file, test it again, and upload the new manuscript from your Bookshelf.<\/p>\n<p>KDP says manuscript updates can take up to 72 hours to appear, while Read Sample can take longer to refresh. Do not assume a repair failed simply because the storefront sample still shows the old navigation immediately after the update.<\/p>\n<h2 id=\"word-troubleshooting\">When Word&#8217;s Automatic TOC Still Goes Wrong<\/h2>\n<p>Word documents can contain hidden complexity from copied text, old templates, imported styles, text boxes, section breaks, and manually overridden headings. If Kindle navigation is incomplete even though the visible TOC looks correct, inspect the actual paragraph styles rather than the appearance. A chapter title can look identical to Heading 1 while still being formatted as Normal text with larger type.<\/p>\n<p>Use Word&#8217;s Navigation Pane as a quick diagnostic. If the chapters do not appear there in the hierarchy you expect, the document structure is already wrong before KDP conversion. Repair the styles, update the automatic TOC, save a fresh DOCX, and test again.<\/p>\n<h2 id=\"fiction-nonfiction\">How Much Detail Should the TOC Show?<\/h2>\n<p>A novel usually needs a clean chapter-level TOC, and including every scene can create a cluttered navigation menu that reveals structure the reader does not need. Nonfiction often benefits from section-level navigation because readers return to specific topics, examples, or procedures rather than reading only front to back.<\/p>\n<p>Use the reader&#8217;s navigation problem as the test. Include a level when somebody is likely to want to jump directly to it. Leave it out when the entry merely exposes document scaffolding.<\/p>\n<div class=\"vg-checklist-box\">\n<div class=\"vg-kicker\">Before upload<\/div>\n<h3>Kindle TOC QA<\/h3>\n<ul>\n<li>Every intended chapter appears in Word&#8217;s Navigation Pane or formatter structure<\/li>\n<li>No page numbers are used as ebook navigation<\/li>\n<li>The logical Go To menu contains the correct entries<\/li>\n<li>The visible TOC links open the correct chapters<\/li>\n<li>Renamed or removed chapters are gone from the TOC<\/li>\n<li>The final file has been tested in Kindle Previewer and KDP Online Previewer<\/li>\n<\/ul>\n<\/div>\n<h2 id=\"faq\">Frequently Asked Questions<\/h2>\n<div class=\"vg-faq-list\">\n<details class=\"vg-faq\">\n<summary>Does every Kindle ebook need a table of contents?<\/summary>\n<div class=\"vg-faq-answer\">\n<p>Amazon requires a logical TOC for Kindle books and strongly recommends a visible HTML TOC.<\/p>\n<\/div>\n<\/details>\n<details class=\"vg-faq\">\n<summary>Should a Kindle TOC use page numbers?<\/summary>\n<div class=\"vg-faq-answer\">\n<p>No. Reflowable ebooks do not have stable page numbers, so navigation should link to chapter or section locations.<\/p>\n<\/div>\n<\/details>\n<details class=\"vg-faq\">\n<summary>Can I build the TOC in Word?<\/summary>\n<div class=\"vg-faq-answer\">\n<p>Yes. Use real heading styles and Word&#8217;s automatic TOC rather than a manually typed list.<\/p>\n<\/div>\n<\/details>\n<details class=\"vg-faq\">\n<summary>Does KDP accept EPUB?<\/summary>\n<div class=\"vg-faq-answer\">\n<p>Yes. KDP accepts EPUB files that meet its specifications and recommends testing them in Kindle Previewer.<\/p>\n<\/div>\n<\/details>\n<details class=\"vg-faq\">\n<summary>Is KPF still supported?<\/summary>\n<div class=\"vg-faq-answer\">\n<p>Yes. Kindle Create currently exports KPF, which Amazon describes as its preferred Kindle Create format for full Kindle feature support.<\/p>\n<\/div>\n<\/details>\n<details class=\"vg-faq\">\n<summary>How long can a manuscript update take to appear?<\/summary>\n<div class=\"vg-faq-answer\">\n<p>KDP currently says ebook manuscript updates can take up to 72 hours, while Read Sample can take longer to refresh.<\/p>\n<\/div>\n<\/details>\n<\/div>\n<h2 id=\"final-thought\">Build Navigation Into the Book, Not Onto the Page<\/h2>\n<p>The professional TOC is the one readers can actually use. If the hierarchy is real and the exported navigation is tested, Kindle handles the experience far more reliably.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>A Kindle TOC is navigation, not decoration. Learn how logical and visible TOCs work, how to build them in Word or Kindle Create, and how to test the final ebook before publishing.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,33,31],"tags":[],"class_list":["post-12143","post","type-post","status-publish","format-standard","hentry","category-editing","category-kdp-listings","category-kdp-publishing"],"_links":{"self":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/12143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/comments?post=12143"}],"version-history":[{"count":5,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/12143\/revisions"}],"predecessor-version":[{"id":13928,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/12143\/revisions\/13928"}],"wp:attachment":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/media?parent=12143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/categories?post=12143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/tags?post=12143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}