Use EpubBit
Professional EPUB tools for indie authors worldwide.
EpubBit guides/Formats
Formats

A Chapter-Structure Checklist for Clean Navigation and a Useful EPUB Table of Contents

A practical checklist to structure chapters in your EPUB for clean navigation and a useful table of contents, with concrete thresholds and verification steps.

11 min read · EpubBit Editorial Team

When readers open your EPUB, they rely on the table of contents (TOC) and navigation to move through your book. A broken or shallow TOC frustrates readers and can trigger retailer quality flags. This guide gives you a chapter-structure checklist to ensure clean navigation and a useful TOC. We'll cover heading hierarchy, file organization, navigation documents, NCX fallbacks, and verification steps. The advice is practical and applies to reflowable EPUB 3, which is the dominant format for indie authors.

1. Start With a Logical Chapter Map

Before you touch any EPUB tool, sketch your book's structure. Decide which parts are chapters, which are front matter, and which are back matter. A common mistake is treating every heading as a chapter. That produces a bloated TOC that overwhelms readers.

Use this rule of thumb: include in the TOC any section a reader would want to jump to directly. Typically that means:

  • Front matter: Title Page, Copyright, Dedication, Epigraph, Foreword, Preface, Acknowledgments (optional)
  • Body: Introduction, Chapter 1 through Chapter N, Conclusion, Epilogue
  • Back matter: Afterword, Appendix, Glossary, Bibliography, About the Author

If your book has parts (Part I, Part II), decide whether to nest chapters under them. Nesting is fine but adds complexity. For most indie novels and nonfiction, a flat TOC with 10–30 entries works best. If your TOC exceeds 50 entries, consider whether some entries are better as subheadings within a chapter rather than separate TOC items.

2. Use a Consistent Heading Hierarchy

EPUB navigation is built from HTML headings. The h1–h6 tags create a document outline that reading systems and assistive technologies use. Inconsistent heading levels break that outline.

Recommended hierarchy for a typical book:

  • h1: Book title or part title (one per file, if used)
  • h2: Chapter title
  • h3: Section within a chapter
  • h4: Subsection

Do not skip levels (e.g., h2 directly to h4). Do not use headings for visual styling alone. If you need a bold paragraph, use CSS, not an h3. A clean hierarchy makes automatic TOC generation reliable. In EpubBit, you can inspect the heading outline and catch skipped levels before export.

3. One Chapter per XHTML File (or a Deliberate Alternative)

EPUB 3 content documents are XHTML files. You can put multiple chapters in one file, but for navigation and performance, one chapter per file is the safest default. It keeps file sizes small, makes the spine order obvious, and simplifies TOC targeting.

If you combine chapters into one file, you must use fragment identifiers (e.g., chapter1.xhtml#section2) in your TOC. That works, but it is easier to break. For a 300-page book, expect 15–40 XHTML files. If a single file exceeds 300 KB of text, consider splitting it. Large files can slow down reading systems on older devices.

File naming matters less for readers but helps you. Use lowercase, no spaces, and descriptive names: chapter-01.xhtml, chapter-02.xhtml, appendix-a.xhtml. Avoid special characters.

4. Build the EPUB 3 Navigation Document

EPUB 3 requires a navigation document (often called nav.xhtml) with epub:type="toc". This is the primary TOC for modern reading systems. It should list every TOC entry in reading order.

A minimal navigation document looks like this:

<nav epub:type="toc" id="toc">
  <h1>Table of Contents</h1>
  <ol>
    <li><a href="titlepage.xhtml">Title Page</a></li>
    <li><a href="chapter-01.xhtml">Chapter 1</a></li>
    <li><a href="chapter-02.xhtml">Chapter 2</a></li>
  </ol>
</nav>

Check that every href points to an existing file and that the order matches the spine. If you use nested lists for parts, ensure the nesting is valid HTML. Do not include the TOC itself as a TOC entry unless you want readers to jump back to it.

5. Include the NCX for Backward Compatibility

Although EPUB 3 uses the navigation document, many older reading systems and some retailer conversion pipelines still read the NCX file (toc.ncx). Including a correct NCX improves compatibility. The NCX uses navMap and navPoint elements.

Key checks for NCX:

  • Each navPoint has a unique id.
  • The playOrder attribute increments sequentially starting at 1.
  • The src in content matches the navigation document targets.
  • The navLabel text matches the visible TOC text.

If your EPUB tool generates both from the same source, they should stay in sync. After export, open the EPUB as a ZIP and inspect both files. A mismatch between nav and NCX is a common validation warning.

6. Add a Visible Table of Contents Page

Readers expect a visible TOC page near the front of the book. This is separate from the navigation document, though it can link to the same targets. Place it after the title page and copyright page, before the first chapter.

The visible TOC should:

  • List all major sections in reading order.
  • Use the same labels as the navigation document.
  • Include page numbers only if your EPUB is fixed-layout; reflowable EPUBs do not have stable page numbers.
  • Be marked as a landmark in the navigation document if you want it accessible from the reader's menu.

If your book has parts, you can indent chapters under part headings. Keep the design simple: a list of links is sufficient. Avoid complex tables for TOC layout, as they can break on small screens.

7. Validate Navigation and TOC with Concrete Tests

After building your EPUB, run these checks. You can do them manually or with a tool like EpubBit, which can flag missing targets and heading issues.

  1. Open the EPUB in a reading system (e.g., Calibre Viewer, Apple Books, Thorium). Use the TOC menu and click every entry. Each should land on the correct section.
  2. Check the first and last entries. The first TOC entry should not be the TOC itself. The last should be the final back matter item.
  3. Verify heading levels. In a browser or editor, inspect the heading outline. No skipped levels from h1 to h3 without an h2.
  4. Run EPUBCheck. Look for navigation-related errors: missing nav element, missing epub:type, broken links, or NCX inconsistencies. Fix all errors before warnings.
  5. Test on a small screen. Long TOC labels may wrap awkwardly. Keep labels under 60 characters where possible.
  6. Check for duplicate targets. Two TOC entries pointing to the same file and fragment can confuse readers. Merge or remove duplicates.

If you use EpubBit, its validation report can highlight broken internal links and heading hierarchy problems in one pass, saving you from manual ZIP inspection.

8. Handle Special Cases: Parts, Appendices, and Footnotes

Special structures need extra care.

Parts

If you use Part I, Part II, create a separate XHTML file for each part title page. In the navigation document, nest chapter links under the part link. In the NCX, use nested navPoint elements. Ensure the part title page has an h1 and the chapters use h2.

Appendices

Label appendices consistently: Appendix A, Appendix B. Include them in the TOC after the conclusion. If an appendix has sub-sections, use h3 for those and consider whether they need TOC entries. Only include them if readers would jump directly.

Footnotes and Endnotes

Footnotes should not appear in the main TOC. They are typically linked from the text and may have a separate notes section. If you include a Notes section, add it to the TOC as a single entry. Ensure footnote links use unique IDs and that backlinks work.

9. Common Mistakes and How to Avoid Them

  • Auto-generating TOC from every heading. This creates dozens of trivial entries. Instead, mark only chapter-level headings for TOC inclusion.
  • Forgetting the navigation document. Some tools export only NCX. EPUB 3 requires the nav document. Check your export settings.
  • Using page numbers in reflowable EPUB. Page numbers are not stable. Use links only.
  • Broken fragment identifiers. If you rename a file or ID, update all TOC references. Run a link check.
  • Inconsistent labels. The TOC label, NCX label, and visible TOC should match. A mismatch looks unprofessional.
  • Missing landmarks. Landmarks (e.g., epub:type="landmarks") help readers jump to the body, TOC, or cover. Include them if your tool supports it.

10. A Final Pre-Submission Checklist

Before you upload your EPUB, run through this list:

  1. Chapter map matches the actual content.
  2. Heading hierarchy is consistent: h1 for book/part, h2 for chapters, h3 for sections.
  3. One chapter per XHTML file, or deliberate use of fragments.
  4. Navigation document exists with epub:type="toc" and lists all major sections in order.
  5. NCX file exists and matches the navigation document.
  6. Visible TOC page is present and links work.
  7. All internal links resolve; no broken targets.
  8. EPUBCheck passes with zero errors.
  9. Tested in at least two reading systems.
  10. TOC labels are concise and consistent.

This checklist takes about 15–30 minutes for a typical novel. It prevents the most common navigation complaints and ensures a professional reading experience.

Conclusion

A clean chapter structure and a useful EPUB table of contents are not afterthoughts. They are part of the reading experience. By planning your chapter map, using a consistent heading hierarchy, and validating both the navigation document and NCX, you give readers seamless navigation. Tools like EpubBit can automate parts of this validation, but the structural decisions remain yours. Follow the checklist above, verify with real reading systems, and your EPUB will be easier to navigate and more likely to pass retailer quality checks.