Yes. Every self-published ebook needs a table of contents, and most platforms expect two distinct types: a logical TOC that powers device navigation menus (such as Kindle’s “Go To” feature) and an inline HTML TOC that appears as a clickable page inside the book itself. Amazon KDP labels the logical TOC as required and the HTML TOC as strongly recommended; other major retailers have similar expectations.
- What Is the Difference Between a Logical TOC and an HTML TOC?
- What Does Each Ebook Platform Require?
- How Do EPUB 2 and EPUB 3 Handle Navigation Differently?
- How Do Formatting Tools Handle Your Table of Contents?
- What Happens If You Skip the Table of Contents?
- How Should You Adapt a Print TOC for an Ebook?
- Frequently Asked Questions
What Is the Difference Between a Logical TOC and an HTML TOC?
A logical TOC is a machine-readable navigation structure embedded in the ebook file’s metadata; an HTML TOC is a visible page of clickable links inside the book that readers can see and tap. They serve different purposes and are built differently, but a well-made ebook includes both.
The logical TOC (sometimes called a “navigational TOC” or “device TOC”) is what reading apps and e-readers use to populate their built-in navigation menus. On a Kindle, it powers the “Go To” menu; on Apple Books, it fills the table of contents sidebar; on Kobo devices, it drives the built-in chapter navigation. Readers never see this structure as a page in the book. It lives in the EPUB’s NCX file (for EPUB 2) or the Navigation Document’s toc nav element (for EPUB 3).
The HTML TOC, by contrast, is a regular page in the ebook’s content flow. It typically appears near the front of the book, after the title page, and contains clickable links to each chapter or section. KDP’s documentation notes that readers expect to find an HTML TOC at the beginning of the book and that some older Kindle devices rely on it for navigation when the logical TOC is incomplete.
In our work helping independent authors fix technical issues with ebooks, the presence of neither or only one type of TOC is among the most common distributor rejection criteria we address. A visible HTML TOC without a corresponding logical TOC means the device’s navigation menu is empty; a logical TOC without a visible HTML page means readers who scroll through the book have no contents page to orient themselves.
What Does Each Ebook Platform Require?
Every major ebook retailer requires or strongly recommends an ebook table of contents, though the specifics vary by platform. Here is what each one expects.
Amazon KDP
KDP is the most explicit. According to KDP’s documentation, the logical TOC is “required for all Kindle books” and the HTML TOC is “strongly recommended.” KDP specifies that the HTML TOC should be placed toward the beginning of the book (not the end), that its entries must be clickable HTML links (not plain text), that HTML table tags should not be used for layout, and that page numbers should not appear. KDP also notes that incorrect TOC placement can affect the accuracy of the “Last Page Read” feature and whether the TOC appears in the book’s free sample.
Apple Books
Apple requires all books to include a complete listing of all chapters or book sections. For EPUB 2 files, this means a valid NCX; for EPUB 3 files, a Navigation Document. Apple uses these structures to build the table of contents that readers see in the Apple Books app sidebar.
Kobo
Kobo distinguishes between the device’s built-in navigation and a visible TOC page. Kobo’s documentation states that a fully functional in-book TOC page must be created inside the document, while noting that properly formatted chapter headings will still allow readers to navigate via the built-in navigation on Kobo apps and devices. Kobo also warns that EPUB files should validate without errors, because validation problems can prevent distribution to partner sites such as OverDrive.
Draft2Digital
Draft2Digital takes a more hands-off approach. If you upload a Word manuscript with consistent heading styles, D2D’s conversion engine will generate a working table of contents and insert page breaks between chapters automatically. However, if you upload a preformatted EPUB, D2D will not modify it; TOC quality and compliance become entirely your responsibility.
IngramSpark
IngramSpark’s current File Creation Guide requires EPUB 3.0 format and states that all EPUBs must comply with current validation standards. Since a valid EPUB 3 file must include a Navigation Document with a toc nav element, this effectively makes a functional ebook table of contents part of IngramSpark’s technical acceptance criteria.
How Do EPUB 2 and EPUB 3 Handle Navigation Differently?
EPUB 2 uses a DAISY NCX file (Navigation Control for XML) built with navPoint elements to define the table of contents hierarchy. EPUB 3 replaced the NCX with a Navigation Document that uses a standard HTML5 nav element with the epub:type="toc" attribute. The differences between EPUB 2 and EPUB 3 are significant for navigation: EPUB 3’s approach is more flexible, supports richer markup, and integrates naturally with the book’s HTML content.
If you are producing EPUB 3 files (which IngramSpark now requires and most modern tools generate by default), the Navigation Document is mandatory. You can optionally include an NCX file alongside it for backward compatibility with older reading systems that only understand EPUB 2 navigation. The DAISY Consortium notes that an NCX in an EPUB 3 file is permitted solely for this forward-compatibility purpose.
KDP’s documentation confirms that Kindle devices and applications support two levels of nesting in the logical TOC. This means you can have chapters as top-level entries with sections nested beneath them, but deeper hierarchies will be flattened. Keep this in mind if your book has a complex structure with parts, chapters, and sub-sections.
How Do Formatting Tools Handle Your Table of Contents?
How your ebook table of contents gets created depends on which tool you use to format and export the file. The behaviour varies significantly.
If you write in Microsoft Word and upload to KDP or use Calibre to convert, the TOC generation depends on your heading styles. Word’s built-in heading styles (Heading 1, Heading 2, etc.) are what conversion tools use to build the logical TOC. If you formatted your chapter titles manually with bold text and a larger font size instead of using heading styles, most converters will not recognise them as chapters; the resulting ebook will have no navigation structure.
Dedicated formatting tools such as Vellum (Mac only), Atticus, and Kindle Create handle TOC generation automatically. They build both the logical TOC and an HTML contents page from the chapter structure you define within the tool. This is one of their primary advantages over manual Word-to-EPUB workflows.
Draft2Digital’s conversion engine similarly auto-generates a TOC from consistent heading styles. But as noted above, if you bypass the conversion by uploading a finished EPUB, you inherit full responsibility for both navigation layers. The same applies to Amazon’s EPUB-to-Kindle conversion: Amazon will attempt to use whatever navigation your file contains, and gaps in the source file carry through to the Kindle version.
What Happens If You Skip the Table of Contents?
Omitting the ebook table of contents creates several practical problems that range from inconvenient to distribution-blocking.
On KDP, a missing logical TOC means the Kindle “Go To” menu shows no chapter list. Readers cannot jump to a specific chapter; they can only scroll or use the progress bar. KDP’s own documentation warns that a logical TOC is “especially important for books longer than 20 pages.” A missing HTML TOC means the book’s free sample may not include a contents page, which can affect a potential buyer’s first impression of the book’s professionalism.
On Kobo, a missing or malformed TOC can trigger EPUB validation errors. Kobo’s documentation explicitly warns that validation errors can prevent distribution to library partners such as OverDrive; a book that passes Kobo’s own checks may still fail to reach the broader library market if the EPUB has structural problems.
On IngramSpark, an EPUB 3 file without a valid Navigation Document will fail EpubCheck validation and may be rejected during the upload process entirely. Since IngramSpark distributes to thousands of retailers and libraries worldwide, a rejected file blocks the widest distribution channel available to indie authors.
Beyond platform mechanics, a missing table of contents signals to readers that the book was not professionally produced. In over 25 years of formatting books at Newgen, we have found that the table of contents is one of the first things readers check when evaluating an ebook’s quality; its absence is a common tell of a hastily assembled file.
How Should You Adapt a Print TOC for an Ebook?
A print-style table of contents does not translate directly to an ebook. There are three specific adjustments you need to make.
First, remove page numbers. Reflowable ebooks have no fixed pages; the text reflows based on the reader’s font size, screen size, and device. A TOC entry that reads “Chapter 3 ………….. 47” is meaningless in a reflowable ebook because there is no page 47. KDP’s guidelines state explicitly that page numbers should not appear in an ebook TOC.
Second, make every entry a clickable hyperlink. In a print book, the TOC is a reference page; in an ebook, it is a navigation tool. Each chapter title must be an HTML anchor link that jumps the reader to the correct location in the file. KDP notes that a TOC made of plain, non-linked text “is not useful on Kindle.”
Third, avoid using HTML table elements for layout. Some authors replicate the print TOC’s dot-leader formatting using HTML tables. KDP’s documentation specifically warns against this; table-based layouts can break on smaller screens and interfere with reading system accessibility features. A simple ordered or unordered list of linked chapter titles is the most reliable approach across all devices and platforms.
Frequently Asked Questions
Does a short ebook or novelette still need a table of contents?
Yes. Even a short ebook benefits from a logical TOC so that reading apps can display the book’s structure in their navigation menus. KDP’s documentation specifically states that a logical TOC is important for books longer than 20 pages, but the recommendation to include an HTML TOC applies regardless of length. A contents page also helps readers return to specific sections on re-reads.
Can I put my HTML table of contents at the end of the ebook instead of the beginning?
You can, but KDP advises against it. KDP’s navigation guidelines state that the HTML TOC should be placed toward the beginning of the book. Placing it at the end can affect the accuracy of the “Last Page Read” feature and means the TOC will not appear in the book’s free sample, which may influence purchase decisions.
Will Amazon build a table of contents for me if I upload a Word file?
KDP’s conversion process can generate a logical TOC from your Word document, but only if you used Word’s built-in heading styles (Heading 1, Heading 2) for your chapter titles. If you formatted chapter titles manually using bold text and font size changes, the converter will not recognise them as structural headings, and the resulting Kindle book will have no navigation. Using proper heading styles before uploading is the simplest way to ensure your ebook table of contents works correctly.
What is the difference between an NCX file and a Navigation Document?
An NCX (Navigation Control for XML) file is the EPUB 2 method for defining a table of contents using navPoint elements in an XML structure. A Navigation Document is the EPUB 3 replacement, which uses standard HTML5 with a nav element typed as epub:type="toc". Modern tools generate EPUB 3 files with Navigation Documents by default. You can include both in the same file for backward compatibility with older reading systems.
How many levels of nesting should my ebook table of contents have?
For most books, one level (chapters only) or two levels (parts and chapters, or chapters and major sections) is sufficient. KDP supports up to two levels of nesting in the logical TOC; deeper hierarchies are flattened on Kindle devices. If your book has a complex structure with parts, chapters, and sub-sections, consider whether readers genuinely need three levels of navigation or whether a simpler two-level structure would serve them better.
