{"id":11995,"date":"2026-03-27T21:22:05","date_gmt":"2026-03-27T21:22:05","guid":{"rendered":"https:\/\/www.vappingo.com\/word-blog\/?p=11995"},"modified":"2026-04-06T15:27:18","modified_gmt":"2026-04-06T15:27:18","slug":"kdp-table-of-contents","status":"publish","type":"post","link":"https:\/\/www.vappingo.com\/word-blog\/kdp-table-of-contents\/","title":{"rendered":"Creating a Table of Contents for KDP: Ebook Navigation, Print TOCs, and the Mistakes That Break Both"},"content":{"rendered":"

<\/p>\n

\n
\n
Book Production \u00b7 Vappingo<\/span><\/div>\n
Creating a Table of Contents for KDP: Ebook Navigation, Print TOCs, and the Mistakes That Break Both<\/em><\/div>\n

A table of contents works differently in ebooks than in print \u2014 and understanding both versions is essential for a professional KDP book. This guide covers how to build functional TOCs for each format, what makes them break, and when fiction authors can safely skip the visible TOC altogether.<\/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

The table of contents is one of the most technically misunderstood elements in KDP publishing. For ebooks it’s not one thing but two \u2014 there’s the visible HTML table of contents that readers can see as a page in the book, and there’s the navigational NCX or Nav TOC embedded in the EPUB file that powers the “Go To” chapter menu on Kindle devices. Both can exist independently of each other, both can fail in different ways, and the rules for fiction and non-fiction differ. For print books, the requirements are simpler but the placement and formatting conventions still trip up many self-published authors. This guide untangles the requirements clearly so your TOC \u2014 visible and navigational \u2014 works correctly on every format and device.<\/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

The Two TOCs in Every Kindle Ebook<\/h2>\n

Every Kindle ebook contains two distinct table of contents structures. The first is the HTML TOC: a page in the book’s content, typically placed in the front matter before chapter one, that lists chapter titles as clickable links. This is the version readers see if they navigate to the front of the book. The second is the NCX (Navigation Control for XML) or Nav document \u2014 an invisible structural file embedded in the EPUB that Kindle devices and apps use to power the chapter navigation menu accessible from the reading interface’s “Go To” option.<\/p>\n

These two TOCs are built and function independently. It’s possible to have a beautiful visible HTML TOC but a broken NCX that makes chapter navigation fail from the menu. It’s also possible \u2014 and common in correctly formatted fiction ebooks \u2014 to have no visible HTML TOC at all but a functional NCX that enables chapter navigation. Understanding which you need, and how to build each correctly, prevents the most common TOC-related formatting failures.<\/p>\n

The NCX\/Nav TOC is required in all Kindle ebooks regardless of genre. KDP’s content quality standards expect the Kindle navigation menu to function correctly, and a missing or broken NCX is one of the issues their review system can flag. If you’re using a dedicated formatting tool like Vellum or Atticus, the NCX is generated automatically from your heading styles and you don’t need to do anything to create it. If you’re working in Word and converting to EPUB, ensure your conversion tool generates the NCX \u2014 most do, but verify in KDP’s Online Previewer by testing the “Go To” chapter navigation after upload.<\/p>\n

When Fiction Ebooks Need a Visible HTML TOC<\/h2>\n

Most commercial fiction ebooks don’t include a visible HTML table of contents as a readable front-matter page. Fiction readers read front-to-back and don’t typically need a clickable chapter list \u2014 they use the Kindle navigation menu (powered by the NCX) if they want to jump to a specific chapter, and they don’t navigate by chapter title the way non-fiction readers do. A visible HTML TOC in a fiction ebook that lists “Chapter 1, Chapter 2, Chapter 3…” adds visual clutter to the front matter without serving any genuine reader need.<\/p>\n

The exception is fiction with titled chapters rather than numbered ones \u2014 a historical novel where each chapter is titled with a date and location, a mystery where each chapter title is a character’s name, or a literary novel with thematically titled chapters. In these cases, a visible TOC adds navigational value because the chapter titles themselves carry meaningful information that readers may want to reference. Titled-chapter fiction benefits from a visible HTML TOC in the same way non-fiction does; numbered-chapter fiction generally doesn’t.<\/p>\n

For non-fiction ebooks, a visible HTML TOC is essential. Non-fiction readers navigate non-linearly \u2014 they jump to the section most relevant to their current need, return to a chapter they partly read, and use the TOC as an index to the book’s content. A non-fiction ebook without a visible, functional, clickable TOC feels unfinished and receives the corresponding negative feedback in reviews. The TOC should be the first substantive page after the copyright page in any non-fiction ebook, and every section heading and sub-heading that you want readers to navigate directly to should appear as a clickable entry.<\/p>\n

Building a Functional Ebook TOC in Word<\/h2>\n

If you’re building your ebook in Microsoft Word before converting to EPUB, the HTML TOC is generated from Word’s built-in Table of Contents feature (Insert \u2192 Table of Contents), which scans your document for text styled as Heading 1, Heading 2, and Heading 3 and generates a clickable list. The critical prerequisite is that all your chapter titles and section headings are styled with the correct heading styles \u2014 not manually formatted as large bold text, but actually styled using Word’s Heading 1, Heading 2, or Heading 3 style definitions. Manual formatting produces text that looks like a heading but isn’t recognised by the TOC generator.<\/p>\n

After generating the TOC in Word, it will appear as a field code in your document \u2014 a dynamic element that can be updated as the document changes. Before converting to EPUB, click inside the TOC field and press F9 to update it, ensuring all heading changes are reflected. When the TOC is generated correctly in Word and converted to EPUB by a compatible converter, the TOC entries become clickable hyperlinks in the ebook that jump to the corresponding headings. Validate this in KDP’s Online Previewer after upload \u2014 click each TOC entry and confirm it navigates to the correct location.<\/p>\n

The full manuscript preparation process, including heading style setup that makes TOC generation work correctly, is covered in the Manuscript Preparation guide<\/a>. The ebook formatting specifics \u2014 including how heading styles map to the NCX generation \u2014 are covered in the KDP Ebook Formatting guide<\/a>.<\/p>\n

TOC Depth: How Many Levels to Include<\/h2>\n

A TOC can include multiple heading levels \u2014 top-level chapters (Heading 1) only, or chapters plus sub-sections (Heading 1 and Heading 2), or all three levels (Heading 1, 2, and 3). The right depth depends on your book’s structure and how readers are likely to use the TOC. For most non-fiction books, a two-level TOC \u2014 chapter titles and major section headings within each chapter \u2014 provides sufficient navigational detail without creating an overwhelming list. A single-level TOC (chapter titles only) works for books where chapters are the primary navigation units. A three-level TOC risks becoming longer than it’s useful, particularly if your Heading 3 sub-sections are numerous \u2014 but is appropriate for reference books and textbooks where readers need fine-grained navigation.<\/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

For the NCX\/Nav TOC (the navigation menu), include all heading levels you want accessible through the Kindle “Go To” menu. NCX depth and visible HTML TOC depth can differ \u2014 your visible TOC might show only Heading 1 and Heading 2 while the NCX includes Heading 3 for finer navigation through the chapter menu. Formatting tools handle this separation automatically; manual formatters need to configure both separately.<\/p>\n

Print TOC: Placement, Page Numbers, and Typography<\/h2>\n

Print tables of contents operate differently from ebook TOCs in one fundamental way: they show page numbers rather than hyperlinks. In a print book, each TOC entry lists the chapter title and the page number where that chapter begins. Print TOC placement is standard: after the copyright page and before any preface, introduction, or part opener pages \u2014 typically on the page designated iii or iv in Roman-numeral front matter pagination.<\/p>\n

Print TOC page numbers must be accurate \u2014 this sounds obvious, but it’s one of the most common errors in self-published print books, because authors generate the TOC before finalising the layout and then make text changes that shift page numbers without updating the TOC. Always regenerate and verify your print TOC as the very last step before creating your final PDF, after all text changes and layout adjustments are complete. In Word, right-click inside the TOC field and select “Update Field \u2192 Update entire table” to regenerate page numbers from the current document state. In dedicated formatting tools, the TOC is automatically regenerated during export.<\/p>\n

Print TOC typography should be consistent with your interior’s typographic style \u2014 use the same body font family as the rest of the book, with appropriate tab leaders (the dotted or solid line connecting entry titles to page numbers on the right margin) and consistent heading hierarchy if your TOC includes multiple levels. A print TOC that uses a dramatically different font or style from the rest of the book’s interior creates a jarring visual inconsistency that trained editors notice immediately and that readers sense even if they can’t articulate why. The Paperback Formatting guide<\/a> covers interior typography conventions in more detail, and Joel Friedlander’s book design resources at thebookdesigner.com<\/a> provide extensive guidance on professional front-matter design including TOC layout.<\/p>\n

TOC Errors That KDP Flags<\/h2>\n

KDP’s automated review process occasionally flags TOC-related issues. The most commonly flagged problem is a visible TOC in an ebook that links to incorrect locations \u2014 typically caused by heading styles that changed after the TOC was generated and weren’t updated. The second common flagged issue is a missing NCX in an ebook that has a visible HTML TOC but no navigational structure \u2014 a sign that the EPUB was built from a Word document without proper heading styles or that the converter failed to generate the navigation file.<\/p>\n

A third issue that KDP sometimes flags is a TOC that lists entries with no corresponding content in the book \u2014 entries that point to headings that have been deleted or renamed since the TOC was generated. Always validate your ebook TOC in KDP’s Online Previewer by clicking every entry and confirming it navigates correctly. For print books, check that every page number in the TOC corresponds to the actual chapter start page by cross-referencing two or three entries against the formatted document before exporting your final PDF.<\/p>\n

Your manuscript’s structural consistency \u2014 correctly applied heading styles, consistent chapter naming, a clean style hierarchy \u2014 is the foundation on which all of these TOC functions depend. Heading style inconsistencies in the source document produce TOC errors in every format, and these are among the harder formatting errors to diagnose after the fact. A proofread and structurally reviewed manuscript from Vappingo’s manuscript proofreading service<\/a> gives you a clean foundation to build from \u2014 with consistent heading structure that makes TOC generation work correctly the first time. For the EPUB standard’s technical specification of navigation document requirements, the W3C’s EPUB 3 documentation at w3.org<\/a> is the definitive reference.<\/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

Structural Consistency Starts With a Proofread Manuscript<\/p>\n

Heading inconsistencies in your source document produce broken TOCs in every format. Vappingo’s proofreaders review your manuscript for structural consistency \u2014 including heading hierarchy \u2014 so your TOC generation works correctly from the start.<\/p>\n

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

\n
Related Reading<\/div>\n\n\n\n\n

\nEbook<\/span>
\nKDP Ebook Formatting: The Complete Technical Guide<\/span>
\n<\/a><\/td>\n
\nPrint<\/span>
\nKDP Paperback Formatting: Margins, Trim Sizes, and PDFs<\/span>
\n<\/a><\/td>\n<\/tr>\n

\nFoundation<\/span>
\nPreparing Your Manuscript for KDP<\/span>
\n<\/a><\/td>\n
\nContext<\/span>
\nKDP Front Matter and Back Matter: What to Include and Where<\/span>
\n<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"

Book Production \u00b7 Vappingo Creating a Table of Contents for KDP: Ebook Navigation, Print TOCs, and the Mistakes That Break Both A table of contents works differently in ebooks than in print \u2014 and understanding both versions is essential for a professional KDP book. This guide covers how to build functional TOCs for each format, … 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":[31],"tags":[],"class_list":["post-11995","post","type-post","status-publish","format-standard","hentry","category-kdp-publishing"],"_links":{"self":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/11995","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=11995"}],"version-history":[{"count":1,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/11995\/revisions"}],"predecessor-version":[{"id":11996,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/11995\/revisions\/11996"}],"wp:attachment":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/media?parent=11995"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/categories?post=11995"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/tags?post=11995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}