A reviewed Word file can look perfectly translated and still be wrong for the next person who opens it: a comment may have vanished, a resolved thread may be out of sight, or an anchor may point to the wrong sentence. For a business team, that isn’t a cosmetic defect. Comments can contain decisions, questions, and instructions that the translator or reviewer needs to see.
The safest approach is to treat comments as structured review data, not as spare text that will automatically follow the document. Make a copy, decide whether comments should be translated or retained in their original language, test the workflow, then check the returned file.
Microsoft documents comment translation in Word for the web, but its desktop translation instructions don’t make the same explicit promise. Google Docs describes making a translated copy without specifying what happens to existing comment threads or anchors. The difference matters when the document’s review history is part of the deliverable.
What you need to preserve when translating a reviewed document¶
A Word document’s review information isn’t just a set of sentences in the margin. Comments have text, thread relationships, status, and a connection to the passage being discussed. A translated file can preserve some of those details and still fail the reviewer’s needs if another part is missing.
Start by naming the things that matter in your particular file. The checklist below turns an ambiguous request like “keep the comments” into verifiable requirements.
| What to preserve | What it means in practice | How to check the translated copy |
|---|---|---|
| Comment text | The words in each comment, including replies | Open every thread and compare its text with the source |
| Comment language | Comments may stay in the source language or be translated for the target team | Confirm the language choice before translation |
| Comment anchor | The passage or phrase a comment refers to | Open the thread and check that the highlighted passage is still the intended one |
| Thread structure | Replies stay grouped with the parent comment | Check that replies haven’t become separate comments or disappeared |
| Comment status | Active and resolved threads remain distinguishable | Inspect the Comments pane, including its List view |
| Tracked changes | Insertions and deletions remain available if reviewers need them | Check revision markup separately from comments |
| Source integrity | The original file remains available for reference | Keep a read-only source copy and work from a duplicate |
A comment anchor is the connection between a thread and a particular piece of document content. Microsoft’s Open XML documentation describes comment data in a separate comments part, while the document content contains references that connect comments to the text. A plain-text export can retain the comment’s words yet lose the connection that tells Word where to display the thread (Microsoft Open XML documentation).
That mechanism explains why “I can still see the comment text” isn’t enough to pass quality review. The comment has to remain attached to the relevant passage, and the passage itself may change during translation. A thread attached to a sentence fragment in the source might need to point to the corresponding phrase in the target, not just to a similar location on the page.
The language choice deserves its own decision. Some teams want every comment translated so target-language reviewers can work without switching languages. Other teams want the comments left as written, because the source-language wording is part of the audit trail or because the comment author must confirm the original wording. A third workflow keeps the original comment and adds a translated version for the target reviewers. Those are different deliverables; don’t let the translation tool make the choice by accident.
The document can also contain review information outside the comment pane. Tracked changes show additions and deletions, while comments record discussion. Microsoft treats these as distinct review markup: hiding either type doesn’t remove it, and tracked changes must be accepted or rejected to remove the revision markup (Microsoft’s Track Changes guidance). Decide what should happen to both before sending a reviewed file for translation.
Translation options: bureau, freelancer, or online workflow¶
The right method depends on the document’s purpose, the review requirements, and how much control you need over the file. A short internal memo with a handful of comments can follow a different route from a contract with multiple reviewers and tracked edits. Don’t compare options only by whether the body text gets translated; compare what happens to comments, anchors, and revision history too.
A translation bureau can handle a document as a managed project. That may suit a file where the language work, review, or formatting needs human coordination. Before sending the file, ask how the bureau treats active and resolved comments, whether comments are translated or left alone, and whether the target version will preserve the original anchors. Ask for a test file or a written description of the handoff, not just a general assurance that “formatting is preserved.” Formatting and comment handling are separate questions.
A freelance translator can be a practical option when one person can translate and review the document. The translator needs clear instructions about the comment policy, access to the source file, and a way to return the file in the format the team will use. If a comment contains confidential negotiation details or internal names, agree whether that material is in scope for translation. Also decide who will verify the anchor behavior in Word after the translated file comes back.
An online workflow can move the body text quickly, but its comment behavior varies. Microsoft’s desktop Word route is under Review > Translate > Translate Document. Word opens a translated copy in a separate window, rather than replacing the source. Microsoft’s instructions list availability for Microsoft 365 subscriptions and Office 2021, with internet access and connected experiences enabled; those details were checked on 2025-12-17 (Microsoft Support). The article describes the translated copy, but doesn’t explicitly guarantee that every thread or comment anchor will be preserved.
Word for the web is the clearest documented Microsoft-native option for translating the comments along with the document. Microsoft’s service description says, “Even comments are translated.” The same page describes comment actions such as inserting, editing, replying to, and resolving comments, making the browser a workable place to review the output (Word Online service description).
“Even comments are translated.”
That statement answers whether comment text is included in the documented Word for the web translation service. It doesn’t settle whether every anchor or thread detail will behave exactly as your team expects. Make a test copy and check the resulting comment locations and replies before using the route for a large or sensitive document.
Google Docs has a built-in Tools > Translate document workflow. Google says the translation creates a copy in a new window and in Google Drive. If the translation option isn’t available while editing a Microsoft Office file, Google’s instructions say you may need to convert the file to Google Docs first (Google Docs Editors Help). The instructions don’t state that existing comments or anchors are translated or retained, so treat comment preservation as unconfirmed until you inspect a test copy.
For a document that must move between translation tools, a localization workflow may use XLIFF. XLIFF 2.0 is an OASIS standard interchange format for localizable content, translations, and supporting data (XLIFF 2.0 standard). Its annotation model matters: ordinary XML comments are ignored by XLIFF agents, while a note element or another recognized annotation mechanism is used for comments that should be preserved. A standards-aware workflow can help carry supported data between tools, but XLIFF itself doesn’t promise that a Word comment anchor will round-trip intact.
How it works in ChatsControl: the tool translates DOCX documents while retaining document structure and formatting, then provides a bilingual side-by-side review view for checking the source against the translation. That view can help a reviewer compare the passage and translation, but it isn’t a Word comment-thread preservation guarantee. If comments and their anchors are central to the job, test the actual Word output separately or use a workflow specifically verified for those comments.
Compare the methods before you send the file¶
A short comparison helps teams choose a workflow based on its documented behavior rather than assumptions. The table separates what the available documentation says from what still needs a test.
| Method | What the documentation says | What you still need to verify | Fits when |
|---|---|---|---|
| Word desktop translation | Creates a translated copy in a separate window | Whether comments, replies, and anchors survive as required | You want a built-in route and can inspect the output |
| Word for the web | Document translation includes comments; Word for the web supports comment review | Anchor placement and thread behavior in your file | You need comments translated and can test in the browser |
| Google Docs translation | Creates a translated copy in a new window and Drive | Whether existing comments and anchors remain | Your team already uses Docs and can validate a converted copy |
| Bureau or freelance workflow | Can be arranged around your file and review needs | The translator’s exact treatment of comments and tracked changes | You need a person to follow a specified review brief |
| XLIFF workflow | Carries localizable content, translations, and supporting data | Whether the specific tool maps Word comments and anchors through import and export | Your team uses standards-aware localization tools |
The main distinction is between a documented feature and a verified result. A product description may say that comments are translated, while leaving anchor behavior unspecified. A translator may say a DOCX is supported, while not knowing whether resolved threads are included. Ask about the exact file and workflow rather than treating a general compatibility statement as proof.
For teams that process files in batches, record the answer in a short workflow note. Include the source format, the tool or service, the comment-language policy, the tracked-changes policy, and the checks the recipient must complete. That note turns one person’s knowledge into a repeatable handoff.
Privacy can also affect the choice. A comment may expose more than the document body: it can contain a negotiation position, an internal name, or an unresolved legal question. Check the provider’s data handling before uploading confidential material. ChatsControl has optional retention settings and uploaded documents are auto-deleted after 30 days by default, according to its product information; that setting doesn’t replace your organization’s own data-handling rules.
A note on certified or sworn output: a translated document with comments isn’t automatically a certified translation. If the receiving authority needs a legally certified version, confirm the required format and whether review comments belong in the final copy. A human certified-translation service may be relevant for that separate requirement, but the comment workflow still needs its own checks.
A step-by-step workflow for translating a DOCX with comments¶
Use the same sequence for a one-off file or a repeatable team process. The key is to make decisions before translation and check the structure after it.
-
Keep an untouched source copy. Save the original DOCX in a location your team can access, and work from a duplicate. The source copy lets you compare the comment text, locations, thread structure, and tracked changes if the output behaves unexpectedly.
-
Set the comment policy. Decide whether comments should be translated, retained in the source language, or supplied in both languages. Also decide whether resolved comments belong in the target. Write the policy down in the translation brief so the translator or tool isn’t left to guess.
-
Decide what to do with tracked changes. Don’t accept changes just to make the file look clean. If reviewers need the revision history, keep it and state that requirement. If the target must contain clean text, agree who will accept or reject changes and when. Word’s Reviewing Pane can show counts of tracked changes and comments, which helps with a before-and-after check (Microsoft Track Changes guidance).
-
Record a baseline. Open the Comments pane and choose List view. Note the active and resolved threads, replies, and any comments tied to important passages. Microsoft’s modern comments guidance explains that contextual view hides resolved comments by default, while List view includes active and resolved threads (Microsoft Support). The visible margin bubbles alone aren’t a complete inventory.
-
Run a small test. Use a duplicate or a representative section before processing the full document. Include the kinds of comments that create risk: a resolved thread, a reply chain, an anchor on a phrase that will change substantially, and tracked changes if the file contains them. A test reveals whether the chosen route matches the team’s expectations.
-
Translate and inspect the result. Open the translated copy in Word, not only in a preview. Check that the file opens, that the body is present, and that the intended comment language has been applied. For a browser-based workflow, review the result in the browser if that is where comments are managed.
-
Compare the threads and anchors. Use the baseline to compare counts and content. Open each thread and confirm that its highlighted passage is the one the comment discusses. Check replies and resolved status, not just whether a bubble is visible.
-
Check revisions separately and release the target. Inspect tracked changes independently from comments. Record any missing or moved thread, correct it in the target, and tell the next reviewer whether the comments are translated, retained in the source language, or bilingual. Keep the source alongside the target according to your team’s retention rules.
The baseline is especially useful when a document has resolved threads. Word’s contextual view hides resolved comments by default, so a reviewer who checks only the margin may think a thread has disappeared. List view includes active and resolved comments, and reopening a resolved comment makes it visible again in contextual view (Microsoft’s modern comments guidance).
Word for the web also lets users resolve comments without deleting them. Microsoft says resolved comments no longer appear in the document margin but remain available in the Comments pane; deleting a thread is the action that permanently removes it (Microsoft Support). That distinction matters when someone reports “the comment is gone.” Check the pane before deciding the thread was lost.
What can go wrong, and how to catch it¶
Comment failures often happen because a team checks the words but not the document relationships. A DOCX isn’t a plain-text file with decorative bubbles. Microsoft Open XML documentation describes a comments part that stores comment content separately from the surrounding main document text. The document content uses references to connect that data to a location.
“If a comment is not referenced by document content via a matching id attribute on a valid use of the commentReference element, then it may be ignored when loading the document.”
The quoted rule appears in Microsoft’s Open XML documentation, which reproduces an ISO/IEC 29500:2016 excerpt (Microsoft Open XML documentation). In plain language, comment text without the matching reference may not appear as a usable comment when Word loads the file. The same documentation notes that duplicate comment IDs can also cause comments to be ignored. A workflow that copies visible words but mishandles the underlying references can therefore produce a file that looks complete in a text extraction but isn’t complete in Word.
Common problems include:
- A thread seems missing because it’s resolved. Check List view in the Comments pane before concluding that translation removed it. Contextual view hides resolved comments by default (Microsoft Support).
- A comment survives but points to the wrong text. Translation changes word order and sentence length. Check the highlighted passage, not just the bubble’s position on the page.
- Replies become hard to interpret. Compare the whole thread, including replies, and confirm that the parent comment still provides the context for each response.
- The comment text is translated but the team needed the source wording. Set a policy before translation. For audit-sensitive material, retain the source copy and state which version of the comment is shown in the target.
- Tracked changes are mistaken for comments. Review them separately. Hiding markup doesn’t remove it, and accepting or rejecting changes is a different action from resolving a comment (Microsoft Track Changes guidance).
- A conversion changes the workflow. Google Docs may require converting a Microsoft Office file if the translation feature isn’t available in Office editing mode. Check what happens to comments on the converted copy before using it as the final target (Google Docs Editors Help).
- The team assumes XLIFF means Word comments are safe. XLIFF 2.0 distinguishes ordinary XML comments from recognized annotations. The standard supports carrying defined data between tools, but it doesn’t guarantee a specific Word comment-anchor mapping (OASIS XLIFF 2.0).
- A preview is mistaken for a file-level check. Open the actual DOCX in Word and inspect the Comments pane. A visual preview may not expose resolved threads or show the full reply structure.
For an agency or in-house localization team, assign the final comment check to a named role. The translator can confirm the language and wording, while a project reviewer checks anchor placement and status. When one person has to do both, make the checklist explicit and preserve the source file for comparison.
ChatsControl offers a bilingual review view that displays the source and translation together, with translated text highlighted and the original available on hover. That can help a reviewer compare wording and spot a mismatch in the body. It doesn’t replace the Word Comments pane for checking comment threads, resolved status, or anchors; use the review view for translation comparison and Word for comment QA.
FAQ¶
How do I translate a Word document and keep its comments?¶
Start with a test copy and decide whether the comments should be translated or retained in their original language. Word for the web explicitly says comments are translated, but check the target’s thread text, count, and anchors before relying on the workflow (Microsoft Word for the web service description).
Does Microsoft Word translate comments in a document?¶
Microsoft’s Word for the web service description says comments are translated. Microsoft’s desktop translation instructions describe a translated copy but don’t explicitly promise that every comment thread or anchor is preserved (Word for the web, Word desktop translation).
How can I preserve comment anchors when translating a DOCX?¶
Use a workflow that retains the DOCX comment data and its references to document content, then open the target in Word and check each thread against the passage it discusses. Microsoft Open XML documentation explains that a comment without a matching reference may be ignored when the document loads (Microsoft Open XML documentation).
Should I accept tracked changes before translating a reviewed Word file?¶
Don’t accept changes just to hide the markup. Decide whether the target should retain the revision history, then handle tracked changes deliberately and inspect them separately from comments. Microsoft says hiding tracked changes doesn’t remove them; changes must be accepted or rejected to remove the revision markup (Microsoft Support).
Can Google Docs translate a document and retain its comments?¶
Google’s help describes a translated copy in a new window and in Google Drive, but doesn’t say that existing comments or their anchors are translated or retained. Test a copy and inspect the comments before treating the result as a preservation-safe workflow (Google Docs Editors Help).
What should I check after translating a DOCX with comments?¶
Compare source and target comment counts and content, inspect active and resolved threads in List view, and confirm that every anchor points to the intended passage. Check tracked changes separately because Word treats revision markup and comments as distinct review information (Microsoft modern comments guidance).
Does preserving comments mean the translated file is certified?¶
No. Comment preservation is a document-workflow question; certification is a separate requirement set by the receiving organization or authority. Confirm whether the final deliverable needs a certified translation and whether comments belong in that deliverable before sending the document.
Should I delete resolved comments before sending a document for translation?¶
Delete a resolved thread only if your team has decided it should no longer be part of the record. Word can hide resolved comments from the margin while keeping them in the Comments pane, so inspect the list before removing anything (Microsoft Support).