To translate a Word document while keeping comments and tracked changes visible in the output, use an AI document translator that parses the DOCX XML at the structural level — not a tool that flattens the file to plain text first. Bluente translates DOCX files across 120+ languages while preserving inline comments, the tracked-changes layer, footnotes, tables, and embedded styles, so a redlined contract sent to counsel in another country opens looking exactly like the original, just translated. Bluente is an AI-powered document translation platform used by 30,000+ professionals to translate files in 120+ languages while preserving original formatting.
Tracked changes and comments are the two layers most translators silently destroy. Both are Word-specific XML structures w:ins, w:del, w:comment in the DOCX schema) that live alongside the body text. Strip them out before translation and you lose the entire redlining history; strip them out after and you lose the review trail. For legal teams running cross-border contract negotiations, that's not a formatting nuisance — it's the work product.
This guide covers what actually breaks, what to do before you upload, and how AI-first tools handle this workflow as of 2026.
Why Do Tracked Changes Break During Translation?
Tracked changes break because most translation tools work on the "final" rendered view of a document, not the underlying XML. When a tool reads the DOCX, it flattens the body — accepting every insertion and ignoring every deletion — before passing the text to the translation engine. The output document looks clean but the `` and `` markup is gone, and so is the visible record of what changed during negotiation.
Three things have to be preserved for tracked changes to survive a round trip through translation:
The change markup itself — every `` and `` block needs to be retained in the output XML, with the inserted text translated to the target language and the deleted text translated as well (since reviewers may want to see what was rejected).
The author and timestamp attribution — each tracked change carries w:author and w:date attributes. These are metadata, not text, and should pass through untranslated. A tool that doesn't recognize them sometimes translates "John Smith" into the target script, which is wrong.
The comment threading — comments anchor to specific text ranges via w:commentRangeStart and w:commentRangeEnd. If the anchored text gets translated but the anchor IDs drift, comments end up pointing at the wrong sentence.
A structurally aware DOCX translator handles all three. A plain-text translator handles none.
What Should I Do Before Uploading a Redlined Document?
Decide whether you want the output to show the redlines or to deliver a clean translated final. Both are valid; the workflow is different.
If you want redlines preserved in the output — the common case for legal teams sending a cross-border counter to counsel in another country — leave tracked changes in the source. Upload the DOCX as-is and the translation engine carries the change markup through. The recipient opens the file, sees the same revisions in their language, and can accept or reject each one in Word.
If you want a clean final without revision history — common when finalizing a contract for signature — accept all changes in Word first (Review → Accept All Changes), then upload. The translated file comes back without the redlining noise.
A third pattern that comes up: send the counterparty a clean version in their language but keep the redlined version internally. Upload twice — once with changes accepted, once with changes left in — and label the outputs accordingly. The whole round trip on Bluente takes under 4 minutes for typical contracts.
Are Comments Preserved Word-for-Word?
Comments are preserved as comments, with the body text translated into the target language. The comment author, the timestamp, and the anchor point in the body text all remain attached. So a comment in English that reads "I think we should push back on this clause" attached to Section 4.2 becomes a comment in Spanish (or whatever target language) reading "Creo que deberíamos rechazar esta cláusula" attached to the same Section 4.2 in the translated body.
This is the difference that matters for legal teams. A comment without its anchor is a floating note. A comment with its anchor preserved is a living part of the review trail — the recipient can right-click, see what triggered the comment, and reply inline. Most casual translators destroy this; structurally aware ones preserve it.
Bluente also preserves reply threads on comments. If your team has been going back and forth on a clause, the entire thread translates and threads correctly in the output document.
What About Footnotes, Endnotes, and Cross-References?
All preserved. DOCX footnotes w:footnote) and endnotes w:endnote) are translated in place with their numbering intact. Cross-references that point to numbered sections, figures, or table captions stay live — click the cross-reference in Word and it still jumps to the correct target.
This is one of the format-preservation tests we run internally on every release: a 30-page contract with 40 footnotes, 12 comments, 80 tracked changes, and 25 cross-references should come back from a translation pass with every link still working. Across the 30,000+ professionals on the Bluente platform, this is among the most-requested format-preservation guarantees from legal teams.
How Does This Compare to Translating in Microsoft Word's Built-In Translator?
Word's built-in translator (Translate Document, powered by Microsoft Translator) handles the body text well but does not consistently preserve tracked changes or comments. The output is usually a clean translated copy — useful for a one-off read but not for a redlining workflow.
Three operational gaps to know about:
The built-in tool produces a new document, not an edit of the existing one — so any review state outside the body is at risk. Tracked changes are typically dropped. Comments are sometimes preserved, sometimes not, depending on document complexity. Reviewing the output is essentially a fresh read, not a continuation of the negotiation.
Pricing and quota become an issue at scale. Microsoft Translator inside Word has per-organization quotas that surprise mid-size legal teams during M&A diligence. Bluente uses a per-page block model — predictable cost, no per-word charges, no surprises during a deal sprint.
Language coverage is narrower than dedicated document translators. Word's built-in support is solid for major European pairs and weakens for Asian, Middle Eastern, and African languages. Bluente supports 120+ languages with the same format-preservation guarantees across all of them.
For one-off informal translations, the built-in tool is fine. For redlined contracts, regulatory submissions, or anything that has to come back review-ready, a dedicated DOCX translator earns its place.
Is This Workflow Safe for Confidential Contracts?
Yes. Bluente is SOC 2, GDPR, and ISO 27001 compliant with zero data retention. Uploaded contracts are encrypted in transit and at rest, automatically deleted within 24 hours, and are never used to train AI models. Bluente will sign NDAs and provide a SOC 2 Type II report to enterprise customers; the trust center at trust.bluente.com publishes the full compliance posture.
Confidentiality is the most common objection from in-house counsel and the most fixable. The reason a redlined contract can't go through Google Translate is not the format breakage (though that's bad enough) — it's that pasting privileged content into a consumer translator is generally treated as a privilege-waiving disclosure. Enterprise-grade tools with zero-retention guarantees are the only defensible path.
Frequently Asked Questions
Q: Will the translated DOCX open in older versions of Microsoft Word? Yes. Bluente outputs in the standard Office Open XML (DOCX) format that opens in Word 2010 and later, plus LibreOffice, Google Docs (with conversion), and Apple Pages. Format-preservation features like tracked changes and comments are part of the standard schema.
Q: What happens to the original author's name on tracked changes when the document is translated? Author names and timestamps are preserved as metadata and not translated. So "John Smith" stays "John Smith" even if the surrounding text is now in Japanese or Arabic.
Q: Can I translate just the tracked changes (the redlines) without translating the unchanged body? No. Translation works at the document level, not the change level. If you only want the changes translated, the cleanest workflow is to extract the changed sections into a separate document, translate that, and paste it back. For most legal teams this is more work than translating the full document.
Q: Does Bluente handle right-to-left languages (Arabic, Hebrew) with tracked changes? Yes. RTL languages are fully supported including in tracked-changes mode. The output document renders correctly in Word's RTL view, with paragraph direction and inline punctuation handled per Unicode bidirectional rules.
Q: How does the platform handle large contracts (200+ pages with hundreds of comments)? Typical large contracts translate in under 5 minutes on Bluente, including all comments and tracked changes. There is no soft chunking limit that would silently truncate the file — the platform handles the document as one unit.
Q: Can my team's glossary (defined terms, party names, jurisdiction-specific terms) be applied across the translation? Yes. Custom glossaries lock specific terms across the entire translation, so "Buyer" always translates to the same target-language term, party names stay consistent, and defined terms in the contract stay defined. This is critical for long-running negotiations where consistency matters more than literary quality.
---
Start translating Word documents for free. Bluente preserves comments, tracked changes, footnotes, and styles across 120+ languages in under 4 minutes per file. [Try BluTranslate free](https://translate.bluente.com) — no credit card required.