Translate Headers, Footers, and Page Numbers in Word

A translated contract arrives with all its paragraphs in the target language, but the footer still says “Confidential - Draft” and the first page displays “Page 0.” The body may look finished while the running text around the page edges tells a different story.

Headers, footers, and page numbers need their own check because they don’t behave like ordinary paragraphs. Some visible text is stored in separate header or footer parts, and some page numbers are fields that Word calculates rather than plain characters. A translation workflow can handle the body while missing one of those pieces.

The practical goal isn’t just to translate every visible word. You need to preserve the document’s structure, identify the text that should change, keep dynamic fields working, and verify that the finished pages display the right information.

What Word headers, footers, and page-number fields are¶

A Word header is content positioned in the top margin area of a page; a footer sits in the bottom margin area. Either can contain ordinary text, images, a page number, or a mixture of those elements. A running project name in a header is ordinary text. A displayed page number may instead be a field that Word updates.

That distinction matters during translation. Ordinary text needs translation when it carries meaning. A page-number field usually needs to remain a field, not become a translated, typed-in number that stops changing when the document is edited.

A field is a Word instruction that displays information, such as the current page number or total page count. Microsoft’s guidance describes page numbers as insertable at a chosen position in a header or footer, and notes that a page count can appear alongside the current number, as in “page 7 of 9” (Microsoft Support, accessed October 19, 2026). The visible label may be ordinary text, while the numbers beside it are fields.

Microsoft Support says, “Sometimes you need to manually trigger an update of the information in fields like those used in a table of contents, headers and footers, cross-references, bookmarks, and formulas in tables.” (Source)

That’s why a page number that looks correct before translation can be stale afterwards. The field may still be present but not refreshed, or a translator may have replaced a field with static text. You can’t tell which happened just by reading the displayed number.

Word also organizes headers and footers by section. A section is a part of the document that can have its own layout and numbering settings. A section break lets you change those settings without treating the entire file as one continuous layout.

Microsoft Learn’s Open XML documentation says a section can have up to three header types: first page, odd page, and even page (Microsoft Learn, accessed October 19, 2026). Those header types can carry different text or formatting. Footers follow the same practical idea: inspect the versions that the document uses, rather than assuming one header and one footer cover every page.

A document can therefore contain several different pieces of edge content:

• A title or document name repeated at the top of each page.
• A different header on the first page of a section.
• Separate headers on odd and even pages.
• A footer with a confidentiality note, company name, or document version.
• A page-number field, a total-pages field, or both.
• A logo, line, or other visual element that shares space with the text.

The mechanism is easy to miss because Word presents these elements in the page layout, while storing them separately from the main body. A translator or automated workflow that processes only body paragraphs may leave header text untouched. A workflow that changes the displayed contents without preserving field instructions may leave page numbers frozen.

For a broader overview of ways to translate a Word/DOCX file without losing formatting, focus on the file structure as well as the visible page. Headers and footers are a small part of the total document, but a missed label can change how a page is understood.

How to translate headers and footers in practice¶

Start with a copy of the source file. Word’s whole-document translation feature opens a translated copy in a separate window instead of replacing the original. Microsoft’s current guidance, accessed on October 19, 2026, describes the route as Review > Translate > Translate Document, followed by choosing the target language and selecting Translate (Microsoft Support). The exact labels can vary with the Word version.

Microsoft Support says, “A copy of the translated document will be opened in a separate window.” (Source)

Working with a separate copy gives you a reference for comparison, but it doesn’t prove that every header, footer, or field survived as intended. Treat the translated copy as a draft that needs a structural check.

Before translating, make a quick inventory. Open the header and footer areas and look for changes between the first page, odd pages, even pages, and sections. If you don’t see the same content throughout the file, don’t assume you’ve found a formatting error: the original may deliberately use different versions.

A practical workflow looks like this:

1. Keep the original file unchanged. Save a working copy of the DOCX and note which pages or sections use different edge content.
2. Identify each section and page type. Check the first page and, if the document uses them, odd and even pages. Record where the header or footer changes.
3. Translate the text, not the field instructions. Names of departments, document titles, confidentiality statements, and labels may need translation. Page-number and page-count fields should remain dynamic.
4. Compare the translated copy with the source. Check that the expected header and footer text appears in every relevant section and that nothing has shifted or disappeared.
5. Update fields and inspect numbering. Refresh the fields, then confirm page numbers, total-page values, numbering style, and starting values.
6. Review the final page layout. Check the Word file in Print Layout, then compare a PDF or print preview when the document will be delivered in that form.

That checklist separates language review from layout review. A target-language phrase can be accurate but too long for its original space. A field can be intact but show an outdated value. Those are different problems, and they need different fixes.

Word also offers a selected-text translation flow: highlight text, choose Review > Translate, pick a language, then select Insert. Microsoft’s guidance says that action replaces the highlighted text with the translation (Microsoft Support, accessed October 19, 2026). That flow can be useful for a specific header or footer phrase, but first make sure you’ve selected the text and not a field or a neighbouring element.

If you translate a header manually, enter the header area by opening it, select only the text that needs translation, and preserve surrounding elements. Don’t delete the entire header to replace one phrase: the header may also contain a logo, line, page number, or other field. The same caution applies to footers.

The source and target languages can also affect line length. A translated document title may wrap onto a second line, overlap a logo, or move a page number away from its original alignment. The language change doesn’t automatically mean the layout is wrong, but you need to inspect the result rather than assuming the original spacing will still fit.

For teams handling structured legal files, the guide to translating legal documents without layout errors covers related risks in the body and page design. The same basic rule applies here: compare the visible page with the underlying structure, not just the translated text.

Why headers differ between sections¶

Different headers usually reflect intentional document design. A report may have a title page without a running header, then use a short report name on later pages. A front section may use Roman numerals for page numbering, while the main text uses Arabic numerals. A two-sided document may place the page number or running title differently on odd and even pages.

Word’s “Different First Page” option applies to the first page of any section, not just the first page of the whole document. Microsoft states that distinction in its instructions for starting page numbering later in a document (Microsoft Support, accessed October 19, 2026). A new section can therefore have its own first-page header even when it begins well after the cover.

Microsoft Support explains, “Different first page can be applied to the first page of any section in your document, not just the very first page.” (Source)

That detail is useful when a translated file appears to have a “missing” header on the first page of a later section. The page may be using the section’s separate first-page header, which could be intentionally blank or contain different text.

Sections can also inherit header or footer content from the preceding section. Word calls this setting “Link to Previous.” Microsoft’s instructions say to turn off Link to Previous in the next section when section-specific headers or numbering are needed; if the option is dimmed, check that a section break exists (Microsoft Support, accessed October 19, 2026).

Headers and footers are linked separately. If the page number sits in the footer, changing the footer’s link setting is the relevant action; changing only the header’s link may not affect it. That separation explains why one section can show a different running title but retain continuous page numbering, or use a different page number while keeping the same header text.

A useful diagnostic is to open the header or footer in each section and inspect the Link to Previous state. If a section should differ but remains linked, editing its header can also change the previous section’s content. If it should continue the same design, unlinking it without a reason may create inconsistent pages.

Section breaks also control numbering changes. Microsoft’s procedure for different numbering or formats in different sections uses Layout > Breaks > Next Page between sections (Microsoft Support, accessed October 19, 2026). A page break and a section break aren’t interchangeable: a page break moves content to a new page, while a section break gives Word a boundary where section-specific layout or numbering can begin.

The difference matters when a translated file has a cover and contents pages followed by the main text. If the main text needs to begin numbering at “Page 1,” its section’s page-number settings need to reflect that design. Microsoft documents setting the starting value to 0 when the third page of a document should display “Page 1” (Microsoft Support, accessed October 19, 2026). The field’s displayed value depends on the section settings, not on typing a replacement number into the footer.

A practical example: a manual begins with a cover, a contents page, and then a first chapter. The chapter begins on the third physical page, but the printed number should start at 1. A translation that adds pages to the contents could change the physical location of the chapter without changing the intended numbering scheme. Check both where the section begins and what its page-number field displays.

When you need to update or change page numbers¶

Page numbers can appear to be plain text even when Word stores them as fields. That’s why you should test the numbering after translation, after substantial editing, and before producing the final copy. A changed translation may add lines, move section boundaries, or alter the total number of pages.

Word provides a page-number format for each section. Microsoft documents choices such as letters (a, b, c) or Roman numerals (i, ii, iii), as well as a starting number for the section (Microsoft Support, accessed October 19, 2026). If a translated file uses a different format from the source, check whether the change was requested or accidental.

The “page X of Y” format combines two values: the current page and the total number of pages. Microsoft documents this display option alongside its instructions for adding page numbers to headers and footers (Microsoft Support, accessed October 19, 2026). A stale total can make the document look incomplete even when the current page field is updating correctly.

To refresh fields, Microsoft’s documented method is to press Ctrl+A and then F9. The same guidance notes that in documents with tables containing fields or formulas, you may need to select and update each table separately (Microsoft Support, accessed October 19, 2026). The shortcut updates fields in the selected content; it doesn’t replace the need to inspect headers and footers manually.

Some useful checks:

• Turn on field shading if you need to distinguish fields from ordinary text. Word’s path is File > Options > Advanced, then set Field shading to Always (Microsoft Support, accessed October 19, 2026).
• Update fields before you assess page numbers or a page count.
• Check the first page of every section, not just the document’s first page.
• Compare the displayed numbering with the intended numbering scheme.
• Confirm that “page X of Y” shows the right total after layout changes.
• Review page numbers after saving or exporting the final version.

Field shading helps with a common inspection problem: a typed number and a page-number field can look nearly identical in the document. The shading can help you spot which items Word treats as fields. It doesn’t tell you that a field is correct; it only makes the structure easier to see.

Microsoft also documents an option to update fields automatically before printing under File > Options > Display > Printing options (Microsoft Support, accessed October 19, 2026). Automatic updating can reduce the chance of printing stale field values, but you should still check the final output. A document that looks right in Word can shift when printed or exported, especially if translated text takes up more room.

If you’re working with PDFs or scans rather than editable DOCX files, the checking process changes: the PDF may have fixed page layout, while a scan is an image that needs text recognition before editing. The guide to PDF and scan translation with AI-OCR explains why those sources need a separate layout and text check.

What should stay as a field, and what should be translated?¶

Keep dynamic values such as page numbers and total-page counts as fields. Translate human-readable labels and running text, such as “Confidential,” “Appendix,” or a document title, when the project requires those labels in the target language. A label such as “Page” may need translation even when the number beside it remains a field.

Some content needs a decision rather than an automatic rule. A company name, product name, document code, or official form title may need to stay in its original form. Follow the project’s terminology and client instructions instead of translating every visible string.

Don’t replace a field with a typed value to make one page look right. A static “Page 4” won’t recalculate if content shifts or a section changes. If the displayed number is wrong, inspect the field and section settings first.

Common mistakes and a final review checklist¶

The most frequent problems come from treating the header and footer as a single fixed strip that repeats unchanged. Word can use separate content by section and page type, and those parts may be linked or independent. A one-page spot check won’t reveal every variation.

A second common mistake is assuming that a translated copy has preserved every dynamic element. Word’s whole-document flow creates a separate translated document, but Microsoft’s description of that flow doesn’t promise that every field or layout detail will be correct in every file. Review the copy rather than treating successful translation as proof of successful formatting.

A third problem is translating a page number as though it were a word. Translating the label can be appropriate; changing the numeric field into fixed text can break future updates. A quick way to catch the difference is to enable field shading and inspect the item before editing.

A fourth problem appears when someone changes the header but not the footer, or the footer but not the header. Word links those areas separately, so a section can inherit one while using a different version of the other. Check the Link to Previous setting in the specific area you’re editing.

A fifth problem is overlooking graphics and spacing. Microsoft notes that graphics or other header and footer elements may need to move to make room for inserted page numbers (Microsoft Support, accessed October 19, 2026). A longer translated title can create the same kind of collision, even if you didn’t add a page number.

Use this checklist before delivery:

• Compare the translated header text with the source section by section.
• Check first-page headers and footers wherever the setting is enabled.
• Check odd and even pages if the document uses different versions.
• Confirm whether each section should link to the previous one.
• Preserve page-number and total-page fields.
• Update the fields before checking displayed values.
• Confirm the format and starting number for each section.
• Inspect a page with the longest header or footer text for wrapping or overlap.
• Review the final Word file and the exported or printed version.
• Keep the source file so you can compare any unexpected change.

For a small file with one repeated header and one footer, a quick visual review may be enough. For a long report with multiple sections, different page types, and separate numbering schemes, check every distinct layout rather than sampling only the first and last pages.

The final test is simple: can someone open the translated file, understand the running labels, and follow the numbering without guessing? If the answer depends on a field that hasn’t been refreshed or a section setting that hasn’t been checked, the document isn’t ready yet.

FAQ¶

How do you translate headers and footers in a Word document?¶

Check every section and page type, then translate only the text that should change. Preserve page-number fields, compare the translated copy with the original, and inspect the layout after updating fields. Word’s whole-document translation opens a separate translated copy, but a separate copy still needs review.

Will translating a Word document preserve page numbers and formatting?¶

Word’s whole-document translation opens a translated copy, but that doesn’t guarantee that every field or layout detail will display as intended. Check the section structure, update page-number fields, and inspect the translated document’s page layout before delivery.

How can you check page-number fields after translating a DOCX?¶

Turn on field shading to help distinguish fields from ordinary text, update the fields, and inspect the page numbers in every section. Compare the displayed numbering and total-page count with the document’s intended structure, then check the final PDF or print preview.

Why do headers and footers differ between sections in Word?¶

Word sections can have independent headers and footers when Link to Previous is turned off. First-page and odd/even-page settings can also give a section different header or footer content, so a document may intentionally display different text on different pages.

How do you update page numbers after translating a Word document?¶

Microsoft’s documented method is to select the document with Ctrl+A and press F9, then inspect the page-number fields in headers and footers. Tables containing fields or formulas may need to be selected and updated separately.

Should I translate the word “Page” in a page-number footer?¶

Translate the label when the target-language document needs a localized label, but keep the page number itself as a dynamic field. A typed number won’t update automatically if the document’s pagination changes.

Why does the page count in “Page X of Y” look wrong?¶

The total-page field may not have refreshed after text or layout changes. Update the fields and check whether section settings or the final page layout have changed the document’s page count.