A translated Word file can look almost right and still be structurally broken: headings appear bold, but the Navigation pane is empty and the table of contents won’t update. That’s more than a cosmetic glitch when the document needs review, reuse, or a reliable contents page.
Keeping Word styles when translating means preserving the reusable paragraph and character definitions that control both appearance and document structure. A strong workflow protects those styles, checks the translated hierarchy, and refreshes the automatic table of contents at the end. The method depends on whether you translate inside Word, paste translated text back, or use a document-translation tool.
What you’re really preserving: appearance and structure¶
A Word style is a reusable set of formatting and document properties. Applying a heading style tells Word that a paragraph is a heading, not just a line that happens to be large and bold. The distinction matters because Word uses heading styles for functions such as navigation, reorganizing sections, and building a table of contents. Microsoft’s guidance on heading styles recommends using them rather than formatting every heading manually.
A style can define a paragraph, characters, a table, or numbering. Style definitions can also inherit properties from a base style, so one change can affect multiple elements. In a DOCX file, a paragraph can refer to a paragraph style through a style identifier, while direct paragraph formatting can override properties from the named style. The WordprocessingML paragraph-style reference and style-definition reference describe that underlying structure.
That explains why “it still looks like a heading” isn’t a sufficient check. Someone may have manually applied a larger font and bold formatting, while the paragraph itself uses the Normal style. The line looks right on the page, but Word may not include it in the Navigation pane or an automatic table of contents.
A translated document has several layers to protect:
| Layer | What it controls | What to check after translation |
|---|---|---|
| Paragraph style | Heading level, body text, spacing, and other paragraph properties | Whether each paragraph still uses the intended style |
| Direct formatting | Local changes such as bold, italic, or font adjustments | Whether emphasis is retained without overriding the intended style |
| Character style | Formatting applied to a span of text, such as a named term | Whether the emphasized span remains attached to the right words |
| Document structure | Relationships among headings, sections, and contents entries | Whether hierarchy and order still make sense |
| Generated elements | Automatic table of contents and page references | Whether heading text and page numbers have been updated |
Translation changes the words, and those words can change paragraph length, line breaks, and page count. A longer translated heading may wrap onto another line. A shorter paragraph may pull the next section up the page. Those layout changes do not automatically mean that the style has disappeared, but they do mean the document needs a new visual check.
A useful way to think about the file is to separate its content from its rules. Content is the heading text and body copy. Rules are the styles, hierarchy, spacing, and links that tell Word how to display and use that content. A workflow that moves only plain text may preserve the first while discarding much of the second.
Prepare the source file before you translate¶
A quick source-file check makes problems easier to diagnose. If headings are already manually formatted, translation may simply expose a structure that was missing before the language changed.
Check whether headings use heading styles¶
Open the document and select a heading. Look at the style shown in Word’s Styles area. A section title might use Heading 1, a subsection Heading 2, and a lower-level heading Heading 3. The exact names can differ if the Word interface uses another language, but the underlying built-in styles can still be present.
Microsoft’s guidance says built-in heading styles support a table of contents, document reorganization, and design changes without manually reformatting each heading. The heading-style instructions also explain that you can customize a heading style and update it to match a selection, then reuse those customizations wherever the same style is applied.
For example, a report might use Heading 1 for “Overview,” Heading 2 for each business area, and Heading 3 for a subsection inside one area. A line that only looks like Heading 2 because it is bold and larger may not be included in the document’s hierarchy. Apply the right heading style before translation if the document’s structure matters.
Confirm that the hierarchy makes sense¶
A document’s hierarchy should reflect its outline, not only its visual design. A section heading generally needs to sit above its subsections. If every title uses Heading 1, Word has no useful distinction between major sections and their children, even if the page uses different font sizes.
In Word for Windows, heading-styled text in the document body appears in the Navigation pane. Microsoft’s Navigation pane instructions note that headings inside tables, text boxes, headers, or footers don’t appear there. The same page notes that Mac and web behavior differs, so don’t assume that every version displays the pane identically.
The pane gives you a fast structural check. If a heading is missing, select its paragraph and inspect the style. If a subsection appears at the wrong level, apply the correct heading style rather than changing only its font size. The Navigation pane can also be used to move sections by dragging headings and to change heading levels, though protected regions can restrict moving them. See Microsoft’s guidance for the Navigation pane.
Save an untouched copy¶
Keep the source file unchanged before using any translation workflow. Microsoft’s full-document Translate workflow opens a machine-translated copy in a separate window rather than replacing the original, but a separate backup still gives you a known reference for comparison. Microsoft documents the full-document and selected-text workflows here.
A copy also helps when a translation creates unexpected changes to a document’s design. You can compare a suspect heading, paragraph, or contents page with the original instead of trying to reconstruct how it looked from memory.
Microsoft Community includes a report of a particular Windows setup where translating an entire document changed fonts, font size, and font color. That report describes one user’s experience, not a universal product rule. The community response is a reason to verify the result rather than assume formatting will always stay unchanged.
As a Microsoft Community respondent describes one Windows 10 test:
“I’ve tried replicating your concern (using a PC with Windows 10 OS) by translating the whole document, and yes the fonts, font size and font color changed after translating the document.”
The practical takeaway is simple: make a copy, run the workflow, and compare the formatting you care about. An anecdotal report can’t tell you what will happen in every Word version, account, or file, but it can remind you to include a visual check.
Compare the main ways to translate a Word document¶
The right approach depends on the document’s complexity and how much control you need over the final file. Word has built-in translation, manual copy and paste offers more direct control over the text but creates formatting risks, and a document-translation tool can handle the file as a document rather than as a block of text.
| Approach | How it works | Main style risk | Suited to |
|---|---|---|---|
| Word full-document Translate | Creates a translated copy in a separate window | Appearance and style behavior still need checking | A document where convenience matters and a review pass is possible |
| Translate selected text and insert it | Replaces highlighted text with the translation | The selected range may not include the full paragraph or surrounding structure | A short passage or targeted correction |
| Copy and paste translated text | Moves translation back into the source document | Paste choices may retain, merge, or strip formatting | A document where a reviewer can check each affected section |
| Document-translation tool | Processes a file and returns a translated document | A returned file still needs style, hierarchy, and contents-page checks | DOCX work where preserving document layout is a priority |
Option 1: Translate the document inside Word¶
Word’s full-document workflow is Review > Translate > Translate Document: choose the target language and select Translate. Word creates a translated copy in a separate window instead of replacing the original. Microsoft says the feature is available to Microsoft 365 subscribers and Office 2021, requires an internet connection and Office connected experiences enabled, and excludes Microsoft 365 operated by 21Vianet. Availability can depend on Word version and account, so check Microsoft’s current instructions.
That copy-based workflow gives you a source file to compare with the translation. After it opens, check heading levels, body styles, and any automatic contents page. Don’t treat the separate window as proof that formatting is identical; the reported community issue above shows why a review pass matters.
Word also offers translation for selected text. The selected-text flow uses Review > Translate and then Insert to replace the highlighted passage. That is different from full-document Translate, which creates a copy. Microsoft’s instructions describe both approaches, and menu labels can vary by version or platform. Check the current Word workflow.
Selected-text translation can make sense when you need to replace a sentence or section without generating another full document. Select only the text you intend to replace, then check the paragraph afterward. A selection that omits a heading marker, paragraph break, or nearby text can make the result awkward even when the translated sentence itself is correct.
Option 2: Copy the translation back into Word¶
Copy-and-paste workflows put the choice of formatting directly in your hands, but the paste option matters. Word’s choices include Keep Source Formatting, Merge Formatting, and Keep Text Only. Microsoft explains the paste options and their effects.
- Keep Source Formatting retains the copied formatting and can copy the associated style definition into the destination document.
- Merge Formatting applies the destination paragraph style while keeping some emphasis.
- Keep Text Only removes formatting and non-text elements, including pictures and tables.
A common example is a translated heading pasted from another document. Keep Source Formatting may bring along a style definition with the same name but different settings. Merge Formatting may apply the destination paragraph style while retaining some local emphasis. Keep Text Only strips the formatting entirely, so you’ll have to reapply the correct style and restore any non-text elements that were removed.
Word also lets users set paste behavior separately for pasting in the same document, between documents, between documents with conflicting style definitions, and from other programs. That distinction matters when a team’s source and destination files use styles with matching names but different definitions. Microsoft lists these paste-setting contexts.
Microsoft’s paste guidance describes Keep Source Formatting this way:
“This option retains formatting that was applied to the copied text. Any style definition that is associated with the copied text is copied to the destination document.”
The option can preserve more than the visible look of a paragraph: an associated style definition may travel with the copied text. If the destination document already has a style with the same name but different settings, check the result instead of assuming the two styles are identical.
Option 3: Use a document-translation tool¶
A document-translation tool treats the file as a document rather than asking you to move text between windows and rebuild its structure. That can reduce the amount of formatting work, but it doesn’t remove the need to review headings, styles, and generated elements.
For a DOCX, ChatsControl reads text paragraph by paragraph and cell by cell together with formatting such as bold, italic, fonts, and links. The translated text is written back into the same paragraphs and runs, which is why document elements such as tables, numbering, and layout can remain in place. A typical workflow is to upload the DOCX, review the returned Word file, and check the translated headings and contents page. ChatsControl is a document-translation tool, not a full CAT tool or TMS, so it doesn’t provide translation-memory leverage or team vendor workflows.
The tool also offers bilingual side-by-side review: the source and translation appear together, with translated text highlighted and the original available on hover. That view helps a reviewer compare passages without repeatedly switching between files. It doesn’t replace a style check in Word, and the document still needs a final review for hierarchy and layout.
A practical choice depends on what you need to control:
- Choose Word’s built-in workflow when the translation feature is available to your account and you can review the copy.
- Choose copy and paste when you need to replace selected material and can manage paragraph styles deliberately.
- Consider document-level processing when moving each passage manually would create too much layout work.
- Bring in a human reviewer when meaning, specialized terminology, or the required status of the translation calls for human judgment.
Step-by-step: translate without losing heading levels¶
A repeatable process makes it easier to catch problems before the translated file goes to a client, reviewer, or publication workflow. The steps below work whether Word or a document-translation tool produces the first translated copy.
1. Save the original and identify the target language¶
Save a working copy before you translate. Note the source language, target language, and any language-specific terminology that must remain consistent. A backup gives you a direct comparison if paragraph formatting or a heading changes.
Microsoft’s Word translation instructions say whole-document Translate requires an internet connection and Office connected experiences enabled, and feature access depends on version and account. Check that the workflow is available in your setup before planning around it. Read Microsoft’s instructions and availability notes.
2. Inspect styles and heading levels¶
Use the Navigation pane where available, then select each major heading and check its assigned style. Confirm that major sections, subsections, and lower-level headings follow a consistent hierarchy. A title that is only bold and enlarged may not function as a heading for Word’s document tools.
If styles need repair, apply the appropriate built-in heading style. Customize the style itself when you want consistent visual changes rather than formatting each heading by hand. Microsoft explains how to add and customize Word headings.
3. Choose a translation workflow¶
Decide whether to translate the whole document, selected text, pasted passages, or the document file as a whole. The choice affects what you need to check afterward. Full-document Translate creates a separate copy; selected-text Translate inserts over the selection. Microsoft describes the difference.
When comparing document tools, check the output file type and the document elements that matter to your project. For example, confirm whether headings, tables, lists, links, and page layout remain workable in the returned Word file. Don’t infer that a tool supports a file type or feature unless its documentation says so.
4. Translate and preserve the paragraph structure¶
After translation, confirm that each translated heading remains in its own paragraph and that body text still uses the appropriate style. Watch for headings that become part of the preceding paragraph or split across paragraphs during editing. A paragraph boundary is a structural part of the Word file, not just a space between lines.
For a pasted passage, decide how the destination should handle formatting before you paste. Merge Formatting may be suitable when the destination style should control the paragraph. Keep Source Formatting can bring the copied style definition into the destination. Keep Text Only is for cases where stripped formatting is intentional and you’re prepared to restore the document elements that it removes. Compare Word’s paste options.
5. Check the translated outline¶
Open the Navigation pane and compare its outline with the source document. Check the order, level, and wording of each visible heading. In Word for Windows, headings in tables, text boxes, headers, and footers don’t appear in the pane, so inspect those locations separately if your document uses them. Microsoft notes these Navigation pane limits.
For a typical report, the outline should still show the main sections first and their subsections beneath them. If one heading appears at the wrong level, change the applied heading style or use the Navigation pane’s heading-level controls rather than correcting the look with manual bolding alone.
6. Set the proofing language for translated text¶
Proofing language tells Word which spelling and grammar rules to use; it doesn’t translate the document. You can select text and set its proofing language through Review > Language > Set Proofing Language. Microsoft also recommends installing proofing tools for the language, and notes that automatic language detection can miss language changes in mixed-language sentences. See Microsoft’s instructions for proofing languages.
Mixed-language documents need extra care. A translated paragraph may contain a product name, legal phrase, or quotation in the source language. Set the proofing language for the relevant selected text when automatic detection marks the passage incorrectly, and check whether proofing tools are available for the target language.
7. Update the automatic table of contents¶
Click inside an automatic contents page and choose Update Table. Select Update entire table when heading text or pagination has changed. Update page numbers only refreshes the page references, not the heading text. Microsoft documents the table-of-contents update options.
A manually typed contents list is different: Word can’t automatically update it, so you have to edit it by hand. Confirm which kind you have before assuming that an update command will fix the entries.
8. Compare key styles and save the reviewed version¶
Compare representative headings and body paragraphs with the source. Check formatting that matters to the project, such as emphasis, hyperlinks, lists, captions, and the placement of page elements. Then save the reviewed translation as a separate final file so the untouched source remains available.
The point isn’t to make every translated page identical to the source page. Translation can change text length and pagination. The review should confirm that the intended style rules and document hierarchy remain intact, while any necessary layout adjustments are deliberate.
What to compare, and where formatting usually breaks¶
A document review is easier when you define what “preserved” means before translation. A file can retain its general look while losing a useful feature, or keep the heading levels while wrapping text differently on the page.
| Review item | Pass condition | What to do if it fails |
|---|---|---|
| Heading level | Each section and subsection uses its intended heading style | Apply the correct heading style and inspect the outline again |
| Navigation pane | Body headings appear in the expected order and hierarchy | Check the style, paragraph location, and Word version |
| Table of contents | Entries match headings and page references | Update the entire automatic table, or edit a manual list |
| Paragraph appearance | Heading and body text use the intended design | Check the assigned style and direct formatting |
| Pasted text | The destination formatting behaves as intended | Re-paste with a suitable option or reapply the destination style |
| Proofing | Translated passages use the intended checking language | Set the proofing language for the selected text |
Heading text changes, but the contents page does not¶
An automatic table of contents draws on document headings. When translation changes the heading text, the contents page may still show the old wording until you update the entire table. Updating only page numbers won’t refresh the text. Microsoft explains the difference between those update options.
For instance, a translated section title can be correct in the body but remain untranslated in the contents page. Update the entire table, then scan the entries for unexpected omissions. If the list was typed manually, edit the entries and page numbers yourself.
A heading looks right but disappears from navigation¶
The visual design alone doesn’t tell you whether a paragraph uses a heading style. Select the heading and check its assigned style. A paragraph with Normal style plus bold and larger text may appear like a heading without providing the same document functions.
In Word for Windows, the Navigation pane shows heading-styled text in the document body but not headings inside tables, text boxes, headers, or footers. A missing item can therefore indicate a style problem or simply a location the pane doesn’t display. Microsoft’s Navigation pane guidance covers both points.
Pasted text imports an unexpected design¶
When source and destination files use conflicting styles, Keep Source Formatting can bring a style definition along with the copied text. Merge Formatting applies the destination paragraph style while keeping some emphasis, while Keep Text Only removes formatting and non-text elements. Microsoft’s paste guide explains these behaviors.
Word also offers separate settings for different paste contexts, including when style definitions conflict between documents. Review those settings if the same paste produces different results in different contexts. Read about Word’s paste settings.
The interface language changes the style names¶
Word’s built-in style names can appear in the language of the interface. A Microsoft Q&A discussion gives examples such as Heading 1 appearing as Titre 1 in French or Überschrift 1 in German. See the Microsoft Q&A discussion.
A translated or localized label doesn’t necessarily mean the style itself has been replaced. Check the document’s structure and behavior rather than relying only on an English style name. The Q&A page also discusses using built-in style constants in VBA rather than assuming that the displayed English name is present in every localized interface.
Proofing mistakes look like translation mistakes¶
Word’s proofing language controls spelling and grammar checks; it does not translate text. A paragraph can contain the correct translation but still receive unsuitable spelling marks if Word checks it using another language’s rules. Microsoft explains how to set the proofing language.
Mixed-language sentences can be tricky because automatic detection may miss a switch in language. Select the relevant text and set its proofing language when the document needs a targeted check. Keep this step separate from assessing whether the translation itself is accurate.
A practical review checklist for translators and teams¶
Use this checklist before sending a translated Word file for approval. It works as a quick review aid for a one-off document and as a repeatable handoff between a translator and an editor.
- Keep the source copy. Confirm that the original file is unchanged and available for comparison.
- Check the style hierarchy. Verify that main sections and subsections use the intended built-in heading styles.
- Inspect the outline. Use the Navigation pane where available, and inspect headings in tables, text boxes, headers, or footers separately.
- Review pasted passages. Confirm that the selected paste option matches the destination document’s formatting rules.
- Check styles, not just appearances. Select representative headings and body paragraphs to verify their assigned styles.
- Set the proofing language. Apply the right language to translated passages and confirm that the needed proofing tools are available.
- Refresh generated contents. Update the entire automatic table of contents after heading text or pagination changes.
- Review the rendered pages. Look for awkward wrapping, displaced elements, and spacing changes that affect readability.
- Save the reviewed file separately. Keep the translated, reviewed version distinct from the source.
A team can use the same checklist at handoff. The translator checks language and structure during editing; the reviewer confirms hierarchy and contents-page behavior before delivery. A document tool may reduce manual layout work, but it can’t decide whether a translated heading is accurate or whether a human review is required for the project.
If the file is a DOCX with headings and tables, a document-level workflow can help avoid rebuilding the file from plain text. In ChatsControl, the DOCX text is processed with formatting at paragraph and cell level and written back into the corresponding paragraphs and runs. The bilingual review view can help compare source and translated passages, but reviewers still need to check the Word outline and refresh the contents page.
FAQ¶
How do I keep Word styles when translating a document?¶
Start with built-in heading styles and keep an untouched copy of the source. After translation, check the heading hierarchy and the assigned styles, not only the visual appearance. When you paste translated text back, choose a paste option that preserves or applies the formatting you want rather than Keep Text Only by default.
How can I translate a Word document without losing heading levels?¶
Use a workflow that keeps document paragraphs and styles intact where possible, then inspect the Navigation pane and the heading styles in the translated file. Word’s full-document Translate feature creates a separate copy, while selected-text Translate replaces the highlighted passage. Microsoft explains both workflows.
How do I update a Word table of contents after translation?¶
Click the automatic table of contents, choose Update Table, and select Update entire table to refresh heading text and page numbers. Update page numbers only won’t update the heading text. A manually typed contents list needs manual editing. See Microsoft’s instructions.
Why did Word change my formatting after translating?¶
Formatting can be affected by the translation workflow or by pasting content with different source and destination styles. Word’s paste options handle formatting in different ways, and a community report describes changed fonts, size, and color in one specific translation test. Check your own file rather than treating that report as a universal outcome. Microsoft’s paste guide and the community report explain those separate risks.
Do Word heading styles still work if the interface language changes?¶
Yes. Built-in style names can appear localized in Word’s interface, so Heading 1 may display under a different name. Check whether the paragraph uses the intended built-in heading style and appears at the right level in the document outline. The Microsoft Q&A discussion gives examples.
Can an online document translator preserve Word headings?¶
A document-translation workflow can process a DOCX as a file and return a Word document with formatting retained, but you should still verify its headings, layout, and automatic contents page. ChatsControl writes translated text back into the corresponding DOCX paragraphs and runs; it also provides side-by-side review. A final Word check remains part of the workflow.