EPUB Navigation Document vs NCX: What Should Authors Include?
An ebook can open perfectly and still feel broken if readers cannot move through it. The visible contents page may look fine while a device menu is empty, chapter links jump to the wrong place, or a screen reader receives an incomplete structure. Authors are often confused because an EPUB can contain both a modern navigation document and an older NCX file.
The practical answer is not to choose one blindly. A modern EPUB 3 needs a valid navigation document. An NCX can still serve as a compatibility aid when an older reading system or distribution workflow expects it. When both exist, they should describe the same book structure and point to valid destinations.
What the EPUB navigation document does
The EPUB navigation document is a specialized XHTML file inside the package. It supplies machine-readable navigation, including the main table of contents. Because it is XHTML, it can also appear as a page readers see inside the book, allowing one structured source to support both a device menu and a visible contents page.
Its hierarchy should reflect meaningful reading order. A novel may need chapter-level entries. Practical nonfiction may benefit from parts, chapters and selected subsections. Tiny decorative divisions usually create noise. EPUB 3 can also include landmarks for major regions and a page list for stable print-correlated references; these solve different problems from chapter navigation.
What the NCX file was designed to do
NCX stands for Navigation Control file for XML. It was central to EPUB 2 and often appears as toc.ncx. It represents a hierarchy of labels and targets. Many conversion tools still generate it, and some older reading systems continue to consult it.
That history explains contradictory advice. One vendor may call NCX essential, while another says EPUB 3 no longer relies on it. The distinction is between the current EPUB 3 navigation requirement and optional support for legacy software. An NCX should not be the only navigation mechanism in an EPUB 3 file.
Navigation document versus NCX at a glance
Use the navigation document as the source of truth for an EPUB 3 edition. Treat NCX as a compatibility output. The navigation document uses XHTML, belongs to the current EPUB architecture and may be rendered for readers. NCX uses an older XML vocabulary and normally remains hidden.
The files can coexist safely. The main risk is inconsistency. A chapter renamed during proofreading may be updated in the visible contents but not in NCX. A new section may appear in one hierarchy only. Automated conversion can also leave stale targets after filenames change.
When including both files is sensible
Including both can be reasonable when an aggregator, library channel, legacy device or established conversion pipeline explicitly expects NCX. It may also be a conservative choice when the same master EPUB travels through several distribution systems with uneven support.
Do not add NCX merely because an old checklist says every ebook needs one. Extra files create another object to maintain. Ask the distributor or formatter which EPUB version is delivered, which navigation files are generated and whether NCX is required for a named channel.
If both are included, generate them from one structured outline whenever possible. After any late change to a title, filename or chapter order, regenerate both outputs and test them again.
How authors should structure the table of contents
A useful hierarchy follows reader intent, not every manuscript heading. Start with parts and chapters. Add section entries only when readers are likely to jump to them directly. Deep menus become cumbersome on small screens, especially when labels are long.
Keep labels concise and descriptive. They should normally match the heading readers reach. Avoid repeated labels that become indistinguishable in a menu. Do not rely on colour, indentation or punctuation alone to communicate hierarchy.
Every target should land on the intended heading or section start. Linking detailed entries only to a chapter’s top defeats their purpose. Anchors must be unique, filenames must match exactly and encoded characters must survive packaging.
A practical pre-upload test
Open the EPUB in more than one standards-aware reader and use the application’s navigation panel, not only the visible contents page. Confirm that expected entries appear, nesting is understandable and every link reaches the correct destination.
Then inspect the visible contents page. Check that it does not conflict with the device menu, omit major chapters or expose internal production labels. Validate the package to find missing resources, broken references and structural errors, but remember that validation cannot judge editorial usefulness.
Test keyboard and assistive-technology navigation where possible. Logical labels, meaningful order and working landmarks reduce friction for everyone. Finally, inspect the retailer-converted preview if the platform provides one, because conversion may change the file customers receive.
Questions to ask a formatter or conversion service
Ask which EPUB version is produced, whether the navigation document is visible or hidden, whether landmarks and a page list are included, and whether NCX is generated. Request confirmation that all navigation layers come from the same outline.
Also ask how late changes are handled. One edit to a chapter title can affect the heading, visible contents page, navigation document, NCX and retailer metadata. The workflow should update all relevant layers together.
For a production review, share the intended hierarchy and distribution channels before conversion.
Frequently asked questions
Does every EPUB 3 need a navigation document?
Yes. The EPUB navigation document is a core part of an EPUB 3 publication and supplies essential navigation such as the table of contents.
Does every EPUB 3 need an NCX file?
No. NCX is a legacy EPUB 2 navigation format. It may be included for compatibility, but it does not replace the EPUB 3 navigation document.
Can an EPUB contain both a navigation document and an NCX?
Yes. They can coexist when both are valid and consistent. The EPUB 3 navigation document should remain the primary source of navigation.
Should the visible table of contents match the navigation menu?
Their wording and hierarchy should generally agree, although a visible contents page may be simplified for design. Major chapters should not conflict or disappear between them.
How deep should an ebook table of contents be?
Use the shallowest hierarchy that still helps readers. Most books need parts and chapters; add subsections only when readers are likely to navigate to them directly.
Why does the table of contents work in one app but not another?
Different reading systems may use different navigation resources or conversion rules. Inconsistent files, broken targets or legacy support can therefore produce different results.
Will EPUB validation prove that navigation is good?
Validation can find structural errors, but it cannot decide whether labels, hierarchy and destinations are useful. Manual testing in multiple readers is still necessary.
Should authors add a page list to an EPUB?
Add a page list when stable page references matter, such as an edition that corresponds to a print book. It serves a different purpose from chapter navigation.
Comments