Microsoft’s official support channels confirm that Word for the web now handles automatic tables of contents—a feature once locked to desktop installs. The catch? The browser version’s capabilities are slim next to the full Windows or Mac app, leaving anyone who needs a styled, multi-level, or custom-mapped table of contents reaching for the desktop.

It is a meaningful gap. Word’s automatic table of contents is the fastest way to give a long report, manual, or dissertation a navigable skeleton, and getting it right matters for both the author and the reader. Yet confusion about when and how to use the right tool still produces broken page numbers, missing entries, and error messages that frustrate even experienced users.

The State of Tables of Contents Across Word Platforms

As of the latest Microsoft 365 builds, the automatic table of contents is available in Word for Windows, Word for Mac, and Word for the web. On desktop, the full workflow is intact: you assign built-in heading styles to your sections, place the cursor where the table should go, open the References tab, and pick an Automatic Table design. Word builds the list from headings, complete with page numbers and hyperlinks that update on command.

Word for the web’s version follows the same concept but with a trimmed ribbon. According to Microsoft’s online documentation, you can insert an automatic table using the References tab in editing mode, and you can update it later by right-clicking and choosing Update Table of Contents. The web app also preserves existing custom styles if the document was formatted on desktop, but it cannot change the look of the table itself—no font tweaks, no indentation adjustments, no level-restyling.

On mobile, the story is even thinner. Verified Microsoft research does not document a supported command for inserting an automatic table of contents in the Word mobile apps, leaving that task to the desktop or browser versions.

What a Web-Based TOC Means for Everyday Users

For the average home user or student, the web version’s addition removes a roadblock. If you are collaborating on a document in OneDrive and need a basic table of contents, you no longer have to switch over to a desktop app just for that one step. Apply Heading 1, Heading 2, and Heading 3 from the Home tab’s Styles gallery, click Insert Table of Contents on the References ribbon, and Word for the web gathers them into a clean list.

That same user can also update page numbers when the document shifts—right-click, update, job done. The simplicity covers the vast majority of short reports, meeting notes, and informal projects. Where it falls apart is when the default look doesn’t match the document’s style or when someone needs a table that pulls from custom paragraph styles instead of the built-in headings.

What Power Users Lose Without the Desktop App

Professionals crafting templates, technical writers, and IT admins managing firm-wide style sets will bump into the web version’s limitations fast. The missing pieces include:

  • Custom table formatting: On desktop, you can modify TOC 1, TOC 2, and TOC 3 styles to control font, size, color, and indentation for each level. The web app shows the results of those styles if they already exist but provides no dialog to edit them.
  • Style mapping: Some documents use custom paragraph styles like “ChapterTitle” or “SectionHead” instead of the built-in Heading 1 and Heading 2. Desktop Word lets you map those styles to TOC levels through the Custom Table of Contents dialog or a TOC field code. Word for the web ignores style mapping options.
  • Field-code editing: Advanced users who need a table built from TC entries, captions, or complex switches (\t, \u, \f, \c) must open the document in Word for Windows. Word for the web preserves existing field codes but does not offer a way to edit or insert them.
  • Numbered heading integration: Applying a multilevel list linked to heading styles is a desktop task. Once set, the web app can refresh the table, but the initial setup and any structural changes to the numbering scheme require the Windows or Mac application.

This desktop-web divide is not a bug but a deliberate design choice. Microsoft has been slowly bringing Office’s “backstage” features to the browser, yet the Custom Table of Contents menu, with its Modify and Options buttons, still lives only in the full-fat client.

How Word’s TOC Feature Evolved (and Why It’s Still Tricky)

Word’s table of contents mechanism hasn’t changed much since the days of field codes in the 1990s. Under the hood, an automatic table is still a {TOC} field that reads outline levels from the document. The modern References ribbon is a friendly wrapper around that same engine.

This legacy explains why the feature trips up newcomers. Word builds the table from structural information—heading styles—not from visual formatting. A paragraph that is bold, centered, and large font will not appear in the table unless it also carries a heading style or an assigned outline level. That mismatch produces the most common support question: “Why is my table missing headings?”

The introduction of the Navigation pane (View > Navigation Pane in Windows) helped; it reveals the document’s heading hierarchy before users commit to a table. Yet the underlying issue persists across all versions: if a heading is placed inside a text box, header, footer, or table, Word may not include it, because those elements sit outside the main document flow.

Actionable Steps: Build a TOC That Won’t Break

Serviceable advice falls into two buckets: prevention and repair. Based on Microsoft’s published guidance and the collective experience documented across support forums, here is what you should do.

Before you insert the table
- Apply the built-in heading styles consistently. Use Heading 1 for main sections, Heading 2 for subsections, and Heading 3 for deeper nesting. Avoid manual font sizes or bold to simulate headings.
- Verify the structure. In Word for Windows, open the Navigation pane (Ctrl+F) and click the Headings tab to see if all intended titles appear and are nested correctly.
- If you need a custom number prefix like “1.1.1”, attach a multilevel list to the heading styles rather than typing numbers by hand.

When you insert the table
- Place the table on its own page, usually after the cover page. Insert a page break (Ctrl+Enter) if needed.
- Choose an Automatic Table from the References menu. Never use Manual Table for a living document; it is just placeholder text that won’t update.
- Save the document immediately after insertion.

After any edit that moves text, adds sections, or renames a heading
- Click inside the table and use References > Update Table, or right-click Update Field. Always pick “Update entire table” when in doubt; “Update page numbers only” skips heading text changes.
- In Word for Windows, you can press F9 with the cursor in the table to trigger an update. To refresh all fields in the main body, press Ctrl+A then F9.
- Enable “Update fields before printing” under File > Options > Display > Printing options. This setting ensures that a printed or PDF-exported copy always shows current page references, though it doesn’t catch renamed headings, so still update the entire table manually before final distribution.

When the table breaks
- Missing heading? Reapply the correct style and update the entire table. Double-check that the title isn’t nested in a text box, header, or footer.
- Unwanted paragraph appearing? Apply the Normal style to it, then update.
- Garbled indentation or wrong level? The heading likely has the wrong style; correct it and update.
- “Error! Bookmark not defined”? That usually signals a damaged internal link. Remove the table (References > Table of Contents > Remove Table of Contents), verify the headings, and insert a fresh automatic table.
- Custom formatting lost after an update? You likely applied direct formatting to table entries instead of modifying the TOC styles. Re-apply your design through References > Custom Table of Contents > Modify, editing the TOC 1–TOC 9 styles there.

The Future of Document Navigation in Word

Microsoft is steadily narrowing the feature gap between its web and desktop apps, but the table of contents remains a clear bellwether for when a task requires the full Office client. As long as complex document production leans on style mapping, field codes, and precise typographic control, the desktop will keep its throne.

What to watch: AI-driven summarization tools in Word could one day suggest a table of contents structure automatically, perhaps even generating it from content rather than heading styles. For now, though, the rule is simple: use the web for quick collaborative inserts, but reach for the desktop when the table needs to match the rest of the document’s polish.