How to Translate a Word Document and Keep the Layout

Word documents are far friendlier to translate than PDFs, because the text is real, editable text with structure behind it. Yet translated DOCX files still come back with broken numbering, the wrong spell-check language, overflowing tables and a table of contents that points at page numbers that no longer exist.

Most of that is avoidable. The trick is to prepare the document before translating and to know which Word features need attention afterwards.

Before you translate: clean up the source

Ten minutes of preparation saves an hour of repair.

Accept or reject tracked changes

If the document has tracked changes, a translation tool may translate deleted text, skip inserted text, or mangle both. Decide on the final version first: Review → Accept All Changes (or reject what shouldn’t stay), then turn off Track Changes. Do the same for comments you don’t need — or keep them deliberately if the reviewer of the translation should see them.

Replace direct formatting with styles

A document where every heading is “Calibri 16, bold, blue” applied by hand is fragile. A document where headings use the Heading 1 style is robust: translated headings keep their look, and the navigation pane and table of contents still work.

Open the Styles pane and click through the document. If body text is “Normal + 11pt + Bold”, consider cleaning it up. It’s the single biggest predictor of how well a document survives translation.

Remove manual line breaks and spacing hacks

Text that was forced into shape with manual line breaks (Shift+Enter), repeated spaces or empty paragraphs will look wrong as soon as the line length changes. Use paragraph spacing, indents and tab stops instead. Turn on Show/Hide ¶ (Ctrl+Shift+8) to see them.

Find text that isn’t in the body

Translators — human or machine — commonly miss text in:

• Headers and footers (including different first-page and odd/even headers)
• Text boxes and shapes
• Footnotes and endnotes
• SmartArt and charts
• Alt text on images
• Document properties (title, subject) that appear in the exported PDF’s metadata

Make a list so you can check them afterwards.

Choosing how to translate

Word’s built-in translator

Recent versions of Microsoft Word include Review → Translate → Translate Document, which produces a translated copy using Microsoft’s translation service. It keeps much of the formatting and is convenient for internal documents. Check your organization’s policy first, since the text is sent to an online service.

Document upload in online translators

Several online translators accept DOCX uploads and return a translated DOCX. Quality and formatting fidelity vary by language pair and document complexity, and free tiers often limit file size or page count.

Dedicated file translators

Tools built specifically around files — such as 2Translate, which is launching soon — translate the document with its full context and write the translation back into the same structure: styles, tables, headers, footnotes and all.

A human translator with a CAT tool

Professional translators use computer-assisted translation (CAT) tools that open DOCX files, show only the translatable segments, protect the tags that represent formatting, and rebuild the file afterwards. If you’re hiring someone, send the DOCX, not a PDF.

After translating: the repair pass

No method is perfect. Open the translated file and work through these.

1. Set the proofing language

Word marks text with a language, which drives spell-check, grammar check and hyphenation. After translation, text may still be tagged as English, so the whole document lights up with red squiggles — or worse, spell-check silently stops helping.

Select all (Ctrl+A), then Review → Language → Set Proofing Language, and choose the target language. If you use styles, also set the language in the Normal style so new text inherits it.

2. Update fields and the table of contents

Tables of contents, cross-references (“see page 12”), captions and page numbers are fields. Their displayed text is cached, so it may still show the source language or old page numbers.

Select all and press F9 to update fields. For the table of contents, choose Update entire table, not just page numbers, so translated headings appear.

3. Check text expansion in tight spaces

Longer text causes most layout breakage. Look for:

• Table cells that now wrap onto three lines, or rows that split across pages
• Text boxes with clipped text — a text box doesn’t grow unless it’s set to resize to fit
• Headings that now wrap and push content onto the next page
• Buttons, labels or callouts in a fixed-size shape

Fix them with the source structure in mind: adjust column widths, allow rows to break across pages, or let shapes autofit. Avoid shrinking font sizes in one place only.

4. Check fonts

If the target language uses characters your font doesn’t include, Word silently substitutes another font for those characters, giving a patchy look. Choose a font family that supports the target script and apply it through the styles, not by hand.

5. Check lists and numbering

Numbered lists, outline numbering (“1.2.3”) and legal clause numbering can restart or lose indentation if the list structure was damaged. Compare against the original page by page. If your document has numbered headings, make sure they are still linked to the heading styles.

6. Review dates, numbers and units

Translation doesn’t automatically localize formats. Decide whether 03/04/2026 should become 04/03/2026 for your audience, whether 1,500.50 should become 1.500,50, and whether imperial units need converting. Then apply the decision consistently.

7. Hyphenation and line breaking

If automatic hyphenation is on, it uses the proofing language set in step 1, which is another reason not to skip that step. Languages with long compound words, like German or Finnish, benefit a lot from correct hyphenation in narrow columns.

Right-to-left targets

When translating into Arabic or Hebrew, paragraphs need right-to-left direction, tables usually need mirrored column order, and numbered lists flip sides. Word handles this well when the paragraph direction is set correctly (the right-to-left paragraph button in the Home tab, available when an RTL language is enabled). Expect manual review of every table.

A final comparison checklist

Area	Check
Body text	Fully translated, no source-language leftovers
Headers/footers	Translated on every section, including first-page variants
Text boxes and shapes	Translated and not clipped
Footnotes	Translated, numbering intact
TOC and cross-refs	Updated with F9, headings in the target language
Proofing language	Set to the target language
Tables	No overflow; header rows repeat across pages if they did before
Images	Alt text translated; text inside images handled separately
Properties	Title and subject translated if the file will be shared as PDF

If the end product is a PDF, do this review in Word and only then export — fixing layout in a translated PDF is far harder.