{"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-04-06T19:03:25","modified_gmt":"2026-04-06T19:03:25","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: How to Build One That Actually Works on Kindle"},"content":{"rendered":"

<\/p>\n

\n
\n
Book Production \u00b7 Vappingo<\/span><\/div>\n
Table of Contents for KDP Ebooks: How to Build One That Actually Works on Kindle<\/em><\/div>\n

A broken table of contents is one of the most common KDP ebook problems \u2014 and one of the most avoidable. This guide covers exactly how Kindle TOCs work, why manually typed TOCs fail, how to build a working TOC from Word or a dedicated formatter, and what KDP requires for the NCX and HTML TOC that appear in your finished ebook.<\/p>\n

\n\n\n\n
9-minute read<\/span><\/td>\nAll levels<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

A Kindle ebook has two distinct table of contents structures, and understanding the difference between them is the starting point for getting both right. The first is the NCX (Navigation Control for XML) \u2014 a navigation file embedded in the ebook’s structure that powers the device’s Go To menu and allows readers to jump between chapters using Kindle’s built-in navigation. The second is the HTML TOC \u2014 the visible, readable table of contents page that appears in the book itself, typically after the front matter, that readers can see and tap to navigate.<\/p>\n

Both need to work correctly for a professional ebook experience. An ebook with a broken NCX produces a Go To menu that either doesn’t show chapters or takes readers to the wrong location. An ebook with a broken HTML TOC presents a list of chapter titles with no navigation function \u2014 visually present but non-functional, which frustrates readers and generates the kind of review complaint (“the table of contents doesn’t work”) that is entirely preventable. The cause of both problems is almost always the same: the TOC was built manually rather than from the structural heading hierarchy of the document.<\/p>\n

\n
\n Stop guessing what sells on Amazon.
\n Find it. Write it. Sell it.<\/span>\n <\/div>\n
\n Real Amazon data + 15+ years of copy expertise\n <\/div>\n
\n
<\/div>\n <\/div>\n
\n
\n
Validate
Before You Write<\/div>\n
Reduce Risk<\/div>\n <\/div>\n
\n
Stop Losing
Money on Ads<\/div>\n
Fix Fast<\/div>\n <\/div>\n
\n
Turn Searches
Into Sales<\/div>\n
Convert More<\/div>\n <\/div>\n <\/div>\n \n Start Finding Profitable Books\n <\/a>\n
\n Powered by Vappingo\n <\/div>\n <\/div>\n \n

Why Manually Typed TOCs Fail on Kindle<\/h2>\n

The most common TOC mistake in KDP ebooks is typing the chapter list manually \u2014 writing out chapter titles and page numbers as plain text, possibly formatted to look like a contents page, without any navigational linking to the actual chapter locations in the document. This approach produces a TOC that looks correct in the Word document but is completely non-functional in the converted ebook for two reasons.<\/p>\n

First, ebooks don’t have fixed page numbers. Kindle reflowable ebooks reformat dynamically based on the reader’s font size, device screen dimensions, and accessibility settings. A “page number” in an ebook has no stable meaning \u2014 the same content might be on page 12 at one font size and page 18 at another. A TOC built around page numbers is therefore structurally incompatible with ebook navigation from the start.<\/p>\n

Second, navigational links in an ebook TOC work by pointing to anchor IDs embedded in the document at each chapter heading location \u2014 not to page numbers or positions. A manually typed list of chapter titles has no connection to these anchors. Even if you manually insert hyperlinks into a Word TOC pointing to bookmarks at each chapter, the conversion process frequently breaks these links. The only reliable approach is a TOC generated automatically from heading styles, because this process creates the anchor-to-link relationship structurally rather than manually.<\/p>\n

Building a Working TOC from Microsoft Word<\/h2>\n

The correct Word workflow for a working Kindle TOC has two parts: correct heading style application throughout the manuscript, and a TOC generated from those styles using Word’s automatic TOC function.<\/p>\n

Every chapter title in your manuscript must be formatted using Word’s built-in Heading 1 style \u2014 not manually formatted to look like a heading, but actually assigned the Heading 1 paragraph style from the Styles panel. Sub-sections within chapters should use Heading 2. This heading structure is what KDP’s converter uses to build the NCX navigation file, and it’s what Word’s TOC generator uses to build the HTML TOC. Without consistent heading style application, neither the NCX nor the HTML TOC will reflect your book’s actual chapter structure.<\/p>\n

Once heading styles are applied consistently throughout the manuscript, generate the TOC using References \u2192 Table of Contents \u2192 Automatic Table 1 or 2. Word generates a TOC with active hyperlinks to each heading. This TOC converts to a functional HTML TOC in the ebook with working navigation links. The NCX is built separately by KDP’s converter from the same heading structure \u2014 it doesn’t come from your Word TOC directly, but both depend on the same heading style foundation.<\/p>\n

One important detail: update your Word TOC before every export. If you’ve edited the manuscript after generating the TOC \u2014 adding or removing chapters, renaming chapters \u2014 the TOC entries may not reflect the current document. Right-click the TOC and select Update Field \u2192 Update Entire Table before exporting to ensure it’s current.<\/p>\n

Building a Working TOC from Vellum and Atticus<\/h2>\n

Dedicated formatting tools handle TOC generation automatically, which is one of their significant advantages over Word for ebook production. Both Vellum and Atticus generate the NCX and HTML TOC from your manuscript’s chapter structure without any manual configuration \u2014 the chapter titles you assign during import or setup become the TOC entries, with working navigation links created by the tool during export.<\/p>\n

In Vellum, each chapter you create in the manuscript panel automatically appears in the generated TOC. Chapter titles, part titles, and any other structural elements you include appear as TOC entries at the appropriate hierarchy level. The TOC style \u2014 whether it shows chapter numbers, titles, or both \u2014 is controlled by your chosen Vellum style, not by manual configuration. In Atticus, the chapter structure panel similarly generates the TOC automatically, with the option to include or exclude specific chapters from the TOC (useful for excluding front matter like the copyright page from the navigation).<\/p>\n

For authors using Scrivener, the compile function generates the TOC from your Scrivener binder structure. The Scrivener for KDP guide<\/a> covers the compile settings that produce a correctly structured EPUB with a working TOC.<\/p>\n

The NCX vs the HTML TOC: What Each Does<\/h2>\n

Understanding the difference between the NCX and the HTML TOC helps you diagnose which one is broken if a reader reports a navigation problem.<\/p>\n

The NCX powers the Go To menu \u2014 on a Kindle device, the menu accessed by tapping the top of the screen and selecting Go To \u2192 Table of Contents or Beginning or Cover. This navigation is device-level and doesn’t require the reader to navigate to a specific page in the book. If the Go To \u2192 Table of Contents menu shows no entries, or shows entries that navigate to wrong locations, the NCX is broken or missing. The NCX is generated from the heading structure of your document \u2014 it can’t be manually edited in Word, but it can be edited directly in an EPUB file using a tool like Sigil if you need to fix a specific navigation entry after export.<\/p>\n

The HTML TOC is a page in the book \u2014 typically placed after the copyright page and before chapter one. It’s what readers see when they read through the front matter, and it’s what the Look Inside feature shows if the TOC falls within the Look Inside preview range. Readers tap entries in the HTML TOC to navigate to chapters. If the HTML TOC is present but non-functional \u2014 entries don’t navigate anywhere when tapped \u2014 the links in the TOC are broken. This is almost always caused by a manually typed TOC or a TOC whose hyperlinks didn’t survive the Word-to-Kindle conversion.<\/p>\n

\n

Navigation Works. Does Your Text?<\/p>\n

A working TOC gets readers to the right chapter. What they find when they arrive \u2014 the quality of the writing, the consistency of the editing, the absence of errors \u2014 determines whether they finish the book and leave a positive review. Vappingo’s manuscript proofreading service ensures the text readers navigate to is as polished as the navigation that takes them there.<\/p>\n

Get a Quote \u2192<\/a><\/p>\n<\/div>\n

KDP’s TOC Requirements and the “Go To” Location<\/h2>\n

KDP requires every ebook to have a functional NCX navigation file \u2014 this is a mandatory element of the EPUB specification that KDP enforces. An EPUB uploaded without an NCX will either be rejected or produce an ebook with a non-functional Go To menu. KDP also requires a defined “start reading” location \u2014 the position in the book where the reader is taken when they open the ebook for the first time. By default this is the beginning of the file, but it should be set to chapter one (or the first page of content after front matter) so readers aren’t dropped onto the copyright page when they open a new purchase.<\/p>\n

In Word, the start reading location is set by placing a bookmark named “Start” at the beginning of chapter one. In Vellum and Atticus, the start reading location is set automatically based on where you designate the first chapter in your project structure. In a raw EPUB file, it’s set in the OPF file’s spine element. Getting this detail right is a small but professionally important element of the reading experience \u2014 it’s the first thing a reader experiences when they open your book, and landing on a copyright page rather than chapter one creates an immediately suboptimal first impression.<\/p>\n

Testing Your TOC Before Publishing<\/h2>\n

Before uploading to KDP, test your ebook’s navigation in Kindle Previewer \u2014 KDP’s free desktop tool that renders your file exactly as it will appear on different Kindle devices and apps. Open your file in Kindle Previewer, navigate to the Go To menu, and verify that every chapter entry navigates correctly. Then navigate to the HTML TOC page and tap each entry to confirm the links work. This two-minute test catches the majority of TOC problems before they reach readers.<\/p>\n

For EPUB files specifically, running the file through the EPUB Validator at validator.idpf.org<\/a> before upload checks the structural integrity of the NCX and the internal link structure of the HTML TOC. Validation errors related to navigation are clearly flagged and typically include the specific file and line number where the problem occurs, making them straightforward to fix in a tool like Sigil \u2014 available free at sigil-ebook.com<\/a> \u2014 before resubmitting. The KDP Formatting Errors guide<\/a> covers the broader range of ebook errors \u2014 including TOC problems \u2014 and their specific fixes. The KDP Manuscript Formatting Requirements guide<\/a> covers the complete technical specification for ebook and print files.<\/p>\n

\n
\n Stop guessing what sells on Amazon.
\n Find it. Write it. Sell it.<\/span>\n <\/div>\n
\n Real Amazon data + 15+ years of copy expertise\n <\/div>\n
\n
<\/div>\n <\/div>\n
\n
\n
Validate
Before You Write<\/div>\n
Reduce Risk<\/div>\n <\/div>\n
\n
Stop Losing
Money on Ads<\/div>\n
Fix Fast<\/div>\n <\/div>\n
\n
Turn Searches
Into Sales<\/div>\n
Convert More<\/div>\n <\/div>\n <\/div>\n \n Start Finding Profitable Books\n <\/a>\n
\n Powered by Vappingo\n <\/div>\n <\/div>\n \n

One final detail worth noting: the TOC page itself should be excluded from the reading order where possible \u2014 meaning it should be present in the HTML TOC as a navigational aid but not appear as a chapter entry within the TOC. A TOC that lists itself as an entry (“Table of Contents \u2014 page 1”) is a minor but telling signal of an inexperienced formatting workflow. In Vellum and Atticus, the TOC page is automatically excluded from its own entries. In Word, the auto-generated TOC includes only content styled with Heading 1 and Heading 2 \u2014 as long as the TOC page itself doesn’t use those styles, it won’t appear as a self-referential entry.<\/p>\n

\n
\n Stop guessing what sells on Amazon.
\n Find it. Write it. Sell it.<\/span>\n <\/div>\n
\n Real Amazon data + 15+ years of copy expertise\n <\/div>\n
\n
<\/div>\n <\/div>\n
\n
\n
Validate
Before You Write<\/div>\n
Reduce Risk<\/div>\n <\/div>\n
\n
Stop Losing
Money on Ads<\/div>\n
Fix Fast<\/div>\n <\/div>\n
\n
Turn Searches
Into Sales<\/div>\n
Convert More<\/div>\n <\/div>\n <\/div>\n \n Start Finding Profitable Books\n <\/a>\n
\n Powered by Vappingo\n <\/div>\n <\/div>\n \n
\n
Related Reading<\/div>\n\n\n\n\n

\nTroubleshooting<\/span>
\nHow to Fix KDP Formatting Errors: The Complete Troubleshooting Guide<\/span>
\n<\/a><\/td>\n
\nSpecifications<\/span>
\nKDP Manuscript Formatting Requirements: The Complete Specification Guide<\/span>
\n<\/a><\/td>\n<\/tr>\n

\nWord Formatting<\/span>
\nFormatting Your KDP Book in Microsoft Word<\/span>
\n<\/a><\/td>\n
\nScrivener<\/span>
\nScrivener for KDP Authors: Writing, Organising, and Exporting<\/span>
\n<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"

Book Production \u00b7 Vappingo Table of Contents for KDP Ebooks: How to Build One That Actually Works on Kindle A broken table of contents is one of the most common KDP ebook problems \u2014 and one of the most avoidable. This guide covers exactly how Kindle TOCs work, why manually typed TOCs fail, how to … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-12143","post","type-post","status-publish","format-standard","hentry","category-editing"],"_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":2,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/12143\/revisions"}],"predecessor-version":[{"id":12145,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/12143\/revisions\/12145"}],"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}]}}