When translating a contract or manual with dozens of pages, the body text may be fully translated while the footer gives the problem away: what used to increment as “Page 3 of 36” now prints the same “Page 1 of 36” on every page.
This is different from footnote numbering in the document (see Will footnote and endnote numbering shift when translating a Word document?). This article is about page numbers at the bottom of the page that change as you move through the document.
Page numbers are not typed-in numbers
In Word, the 3 in “Page 3” is usually not typed by the author. It is a field that recalculates: the current page uses PAGE, while the total page count uses NUMPAGES. When Word refreshes fields—for example, during certain repagination or printing operations—it calculates the numbers from the actual page sequence.
A standard translation tool may only see the cached text from the last time the file was saved—a plain “3.” It then sends the entire phrase “Page 3 of 36” for translation and writes “Page 3 of 36” back as ordinary text. The fields are gone, and the numbers are frozen. In a 36-page document, every page shows the same number, which can look worse than leaving the footer untranslated.
There is another issue that is easy to miss: some designs in Word’s page-number gallery place numbers in text boxes inside floating shapes rather than directly in footer paragraphs, leaving the footer paragraph nearly empty. A tool that scans only regular paragraphs may conclude that there is no footer text at all and skip the entire footer.
Protect the calculation, not the whole footer
Not everything in a footer is a field that must remain untouched. Automatically updating content such as PAGE and NUMPAGES needs to stay in place. But visible text in the same footer, such as HYPERLINK (“Back to cover” or “Company website”), is author-written content and should still be translated. Treating the entire footer as protected structure can quietly leave link text untranslated.
When SimplifyAI processes these footers, it generally does three things:
- Protects only the parts that recalculate, while sending surrounding words such as “Page” and “of” for translation. Target-language word order can change: English uses
Page 3 of 36, while Japanese commonly uses36 頁中の 3 頁; the numbers remain live fields. - Scans both footer paragraphs and text boxes. Word uses one newer text-box format, while WPS and some older readers use a fallback shape format. The translated content is written in both locations to avoid a footer that looks correct in Word but appears blank for someone else.
- Leaves a number blank rather than placing the sentence inside the page-number field. If the model misses where a page number belongs, the sentence remains and the page number is left empty. The issue is recorded for review. It does not place the full translated sentence into a field’s cached result—the behavior that causes the same number to appear on all 36 pages.
After you open the file in Word, Word itself still recalculates the page numbers based on the document’s pages. SimplifyAI does not replace Word’s field refresh.
What is automated—and what still needs review
The system can automatically identify page-number fields in headers and footers, translate surrounding text, return fields in the target-language word order, and cover page numbers inside text boxes.
A quick human review is still recommended when the footer also includes a company address, confidentiality label, or document number, so you can confirm the wording and terminology. For settings such as “Roman numerals for the table of contents, then restart at 1 for the main body,” translation does not alter your section rules.
What it does not currently do: update page numbers next to table of contents entries. Those use a separate set of PAGEREF fields that Word recalculates when fields are refreshed; see Word TOC Not Updating After Translation. It also does not turn repeated PDF header or footer text that merely looks like a footer into a real Word footer.
Files this is useful for
Contracts based on company templates where footer text is fixed but page counts must change; manuals that may need spacing adjustments after translation, causing the total page count to change; and files shared with colleagues who only open them in WPS or a web preview, where they may not be able to press F9 to refresh fields.
Conclusion
In long-document translation, the visible problems often appear outside the body text. Upload a Word file with page-number footers to SimplifyAI, then scroll through the translated document and check whether the numbers still update from page to page.