Word TOC Not Updating After Translation

CAT tools have long treated a Word table of contents as something you should not translate. Translate the headings, they say, then right-click the TOC and choose Update Entire Table, or press F9. That is standard advice—and it works if everyone who opens the file has desktop Microsoft Word.

The delivery problem starts after you send the file. A client on WPS, a reviewer in a browser preview, or a PDF exported the same day will not rebuild those fields. They show whatever snapshot was stored in the document. If that snapshot is still in the source language, the first page of a finished translation looks unfinished.

A table of contents is not a live copy of headings

A Word automatic table of contents is a TOC field. When it is generated, Word writes a visible field result for each “number + heading + dot leader + page number” entry; newer files may also wrap the whole TOC in a content control. If you later change a body heading, that displayed result does not update by itself.

That is why tools that translate only paragraph text, without handling the displayed TOC result, can leave the TOC in the source language. Translating the entire TOC block with machine translation is riskier: the outer TOC field can contain bookmark links in HYPERLINK \l and PAGEREF fields that calculate page numbers. Editing those runs directly can break page numbers or navigation first.

Some templates do not store each TOC line as a standard hyperlink. They use the field form above (HYPERLINK \l plus a nested PAGEREF). Tools that look only for ordinary hyperlink elements can miss those entries.

WPS, mobile previews, and browser-based viewers often do not rebuild fields the way Word does. They simply draw the snapshot stored in the file. Asking the recipient to press F9 is asking them to finish the layout.

Rebuild from translated headings—not by translating the TOC

SimplifyAI does not send the TOC block for translation. Instead, it synchronizes the visible headings from the already translated body headings while preserving the field structure in the TOC.

Specifically, it aims to:

• Replace only the heading text. Chapter-number styling, dot leaders, and page numbers remain unchanged. Page numbers are still handled by Word’s PAGEREF, and are not recalculated.
• Recognize both link formats. This includes standard hyperlinks and the HYPERLINK \l fields commonly found in Chinese-language templates. The instruction text can sometimes be split across multiple runs and must be combined to identify the matching bookmark.
• Update numbered prefixes too. When a body heading’s prefix changes from 第三部分 to Part 3, the old rendered prefix in the TOC snapshot is rebuilt with the same rule. If the original chapter number cannot be read reliably, that line is skipped—writing the wrong Part 4 is worse than leaving a visibly untranslated prefix.
• Match bookmarks placed on blank lines. Word sometimes starts a _Toc bookmark on the blank line before a heading. In a real handbook, a few entries out of more than a hundred were written that way; if they are not matched, the whole TOC line stays stale.
• Keep the review preview and the downloaded file aligned. The TOC you check online should match the file you send.

When a file is opened in Word, Word may rebuild fields again if the file is marked for field updates. That is when page numbers refresh for the new pagination. Before then, translated headings are already visible in WPS.

What is supported—and what still needs review

The system automatically updates visible TOC headings based on body headings and updates TOC number prefixes when the numbering has been localized.

You should still open the file and check whether TOC links go to the correct chapters. If you previously edited a TOC entry manually and it no longer matches its heading, that entry will not be overwritten.

What it does not currently do: recalculate page numbers for you; automatically follow heading changes you make in Word after translation. As with native Word behavior, you will need to update fields yourself. Manually typed imitation TOCs, rather than field-based TOCs, are also outside this workflow.

For why a numbering prefix such as 第三部分 becomes Part 3, see Word Auto-Numbering Not Translated. “Page X of Y” in footers uses a separate set of fields; see Word Footer Page Numbers Stuck After Translation.

Best suited for these files

This approach is useful for deliverables sent to external clients, where you cannot expect recipients to open Word and refresh fields; annual reports that will immediately be converted to PDF, where fields can no longer be refreshed afterward; and policies or manuals opened only in WPS by colleagues.

Conclusion

A table of contents looks like ordinary text, but underneath it are several layers of fields. Upload a Word document with an automatic TOC to SimplifyAI, then open the same translated file in both Word and WPS to confirm that the first page is already in the target language.