How-to

How to translate a Word document

DocTranslating translates whole Word documents (.docx and legacy .doc) into 100+ languages in a single operation — no copying sections into Google Translate and pasting them back. Text boxes, footnotes, tables, hyperlinks and inline formatting are preserved in the output. Microsoft Azure gives the highest formatting fidelity for Office files, DeepL is best for natural-sounding output on European languages, and Google Cloud has the widest language coverage. Gemini does not accept Word files — convert to PDF first or use one of the other three engines.

Updated June 12, 2026 · 9 min read

If you've been translating a Word document by pasting sections into Google Translate and copying the results back into your file, you already know the two things that make that workflow painful: formatting breaks the moment translated text goes back into Word, and the process takes hours on any document longer than a few pages. This guide covers the faster way — translating the entire .docx (or legacy .doc) file at once and getting a translated Word document back with the layout intact.

Why translating a Word document preserves formatting so well

A .docx file is really a small archive of XML — every heading, paragraph, table cell, text box, footnote and hyperlink is a labelled element that a translator can identify and translate individually. This is very different from a PDF, where text has been flattened into positioned glyphs with no structure. Because Word documents carry that structure natively, a document translator can extract the text, translate it, and rebuild it back into the same labelled elements — so the output opens in Word with the same layout, styling and page flow as the original.

In practice, that means the following survive translation reliably:

• Headings and body styles — H1, H2, quote blocks, and any custom style stays applied.
• Tables — rows, columns, merged cells and cell alignment carry over.
• Text boxes — including those containing captions, callouts and pull-quotes.
• Footnotes and endnotes — numbering and placement stay attached to the right text.
• Inline formatting — bold, italic, underline, colour, and hyperlinks.
• Embedded images — pictures stay in place; the surrounding text reflows around them.
• Headers and footers — including page numbers.

Step-by-step: translate a Word document

1. 1

   Upload your .docx or .doc file

   Drag your Word document onto the upload area or click to browse. DocTranslating detects the format automatically and only shows the translation engines that accept it. Modern .docx files work with three engines; legacy .doc files are supported by DeepL only.

2. 2

   Pick your source and target languages

   Set the language the document is written in (or leave it on auto-detect) and the language you want it translated into. For Word documents, auto-detect is usually reliable because the text is clean — unlike scanned PDFs where OCR quality gets in the way.

3. 3

   Choose the right translation engine

   Pick Microsoft Azure for the strongest formatting fidelity, DeepL for the most natural output on European languages, or Google Cloud for the widest language coverage. Gemini does not accept Word files. The next section explains when to use which.

4. 4

   Translate the whole document at once

   Click Translate. The entire document is processed in one operation — you don't need to split it into chunks or translate section by section. When it finishes, download the translated .docx and open it in Word to verify the layout.

Which translation engine is best for Word documents?

All three engines that accept Word files preserve the overall layout, but they differ in fidelity on complex formatting, in file-size limits, and in whether they accept the legacy .doc format at all.

What about tracked changes and comments?

This is the part where being honest matters. Machine translation APIs handle tracked changes and comments unpredictably across the industry — the underlying issue is that these features represent multiple versions of the same text (an original, a proposed revision, a reviewer's note), and translation pipelines are built to extract and translate a single canonical version. The three most common outcomes:

• Tracked changes get flattened — accepted changes are silently kept, rejected changes are silently dropped, and the revision history disappears from the translated file.
• Sections get omitted — DeepL in particular has a documented failure mode where tracked-changes markup causes whole paragraphs to be missing from the output.
• Comments get dropped — the comment threads usually don't appear in the translated document at all.

Translating old .doc files

Word documents saved before 2007 use the older binary .doc format. Of the three engines that translate Word files, only DeepL accepts .doc directly — Azure and Google Cloud need the modern .docx format. If your engine of choice is Azure or Google Cloud:

File size limits and long documents

The limits are 30 MB on DeepL, 20 MB on Azure and 10 MB on Google Cloud. Text-only Word documents are almost never that large — you usually only hit the limit when the file contains many embedded images. Two workarounds:

• Compress the embedded images inside Word — select any picture, then Picture Format → Compress Pictures. This is often enough to drop a 25 MB file to under 10 MB.
• Split the document — save it as two or more smaller files, translate each, and merge them back afterwards.

Right-to-left Word documents work cleanly

If you're translating a Word document written in Arabic, Hebrew or Persian — or translating into one of those languages — the good news is that Word documents don't have the RTL extraction problem that PDFs do. Because .docx carries text in logical reading order (not visual draw order), the words come out correctly and the layout mirrors properly. This is the opposite story from PDFs, where translating from a scanned RTL source is still a current limitation. If you have both an editable Word file and a PDF export of the same document, translate the Word file.