Word for translators on Mac: translate, review and hand off files in Word 2026

Where translators really use Word on a Mac

Most translators do their core work in a CAT tool, which stands for computer-assisted translation. Word shows up at the edges. You open it when a client sends a file, when a reviewer marks up a draft, or when you need to return a clean document.

Surveys back this up, with a caveat. In a 2023 survey of 2,803 freelance translators, 81% said they use CAT tools at least sometimes. 59% use them frequently, and 19% never use them. That survey did not ask about Word, so read it as context, not as a measure of Word use.

Word's built-in translation is a convenience, not a workspace. It does not give you a translation memory or a terminology base. Microsoft's support article only describes the Translate commands, so do not expect more from them.

Translate a whole document in Word for Mac

The built-in route sits on the Review tab. Go to Review > Translate > Translate Document, choose the target language, then click Translate. Word opens a machine-translated copy in a separate window. Your original file stays unchanged, so you can compare the two.

1. Save a copy of the source file under a new name, such as client-name-draft.docx.
2. Open the copy, then go to Review > Translate > Translate Document.
3. Choose the target language, then click Translate.
4. Read the new window against the original, section by section.
5. Save the translated copy under its own name before you edit it.

Microsoft's article says there are no document size or formatting limits. Read that as a claim you still need to test. Run a short sample first, then the full file, and compare the results before you commit to the method.

Expect to edit machine output, not write from scratch

The machine draft is a starting point, not a finished translation. In the 2023 survey, 31% of translators named the growing use of machine translation as a challenge. Respondents said editing machine-translated text was often harder than translating from scratch. Price your jobs with that in mind.

Read each paragraph for meaning first, then for terms, then for format. A draft can look finished while it still has errors, so check names, numbers, and dates against the source.

Translate one selection and keep the rest of the file

Use Translate Selection when only one passage needs a machine draft. Highlight the text, then go to Review > Translate > Translate Selection. Choose the language and click Insert. Insert replaces the highlighted text, so read the result before you move on.

Here is a worked example. Suppose one clause of a long contract is still in the source language. Select only that clause, run Translate Selection, then check the new text against the defined terms used elsewhere in the contract.

If the result is wrong, press ⌘ Z right away. That undoes the Insert while it is still the last change you made.

Check your subscription and Word version first

Translation in Word has conditions. Microsoft's article says the feature is available with an Office 365 subscription, Office 2024 for Mac, or Office 2021 for Mac. It needs an internet connection, and Office connected experiences must be enabled. It is not available to Microsoft 365 operated by 21Vianet.

Check your build in Word > About Microsoft Word. The latest Office for Mac release in Microsoft's release notes is Version 16.114.3 (Build 26102720), dated October 27, 2026. Its Word entry lists only quality and performance improvements. The Word entries from October 14 to 27, 2026 list no Word feature changes.

Why bilingual tables break after translation

Tables are the weak point in the reports. In a Microsoft Q&A thread titled Translate tables in Word, a user said text inside tables was not translated, while the rest of the document was. That thread is tagged Windows and mentions Word build 2404.

Other users in the thread said Translate Document left some cells untranslated. They said cell text moved into other parts of the document, and formatting was lost. Converting tables to text first was a workaround they called not a solution. No Microsoft representative answered in the visible posts.

Check a translated table cell by cell

1. Count the rows and columns in the source table, and write the numbers down.
2. Make a copy of the file, then run Translate Document on the copy only.
3. Compare the translated table's row and column count with your numbers.
4. Click into each cell that holds text, and confirm it is in the target language.
5. Look for cell text that landed in a paragraph or heading outside the table.
6. Reapply bold, alignment, and column widths where the formatting dropped.

This check takes longer on a table-heavy file, and the research does not measure how long. Build time for it into your schedule. Do not assume a table is fine because the text around it reads well.

Build a bilingual review table for a reviewer

Many reviewers want the source and the translation side by side. A two-column table does that. Wordfast's bilingual revision workflow works this way. It exports a Word file, DOC or DOCX, with a two-column table of source text and translation. The reviewer edits that file, and you import it back to update translation memory.

Keep the original TXLF file in place, because the import needs it. Wordfast offers an option to show tracked changes and glossary terms as comments. Its page does not say how tracked changes behave on import. Test a short file first, and compare the result before you trust it.

1. Start a new Word document. Go to Insert > Table, then pick two columns.
2. Add one row for each segment. Paste the source text into column one.
3. Paste your translation into column two, next to its source.
4. Save a DOCX copy and send the reviewer that copy only.
5. Keep your master file closed while the reviewer works.

This is a manual setup. The sources reviewed here do not describe a built-in bilingual review view in Word. Whatever layout you pick, keep the reviewer's file separate from your working file.

Track Changes can make long files crawl

Reviewers often send files with tracked changes, and Track Changes can slow a long document. A Microsoft Q&A thread titled Documents with tracked changes makes Word unusable reports typing lag of about 10 seconds per sentence, and at least 3 seconds for navigation, in some documents. Collapsing tracked changes reduced the lag but did not fix it. The thread is locked with no confirmed solution.

Microsoft's moderator suggested three steps: turn off Track Changes when you are not editing, save a copy without tracked changes, and run Online Repair. One MVP said the problem appeared mainly in 25 to 35 page formatted documents. That thread is also tagged Windows, so test the steps on your Mac before you rely on them.

Where Lazur fits in your Word workflow

Lazur is a voice assistant for the Mac. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. Ask where a control is, and Lazur draws a circle and a label around it. Ask how to do something, and Lazur guides you one click at a time, waiting for each click.

Lazur does not click buttons, edit files, or operate other apps for you. It is not a plugin or add-in for Word, and it has no partnership with any app maker. You stay in control of the file. Lazur acts as a guide and a second pair of eyes.

Dictate reviewer notes without leaving the page

Hold fn to dictate clean, formatted text at the cursor, in any app. Snippets, a personal dictionary, and clipboard slots handle the terms you repeat. Put client names, product names, and house style terms into the personal dictionary before a big job.

Dictation is included on both paid plans. Check the pricing page for current plan details. Dictation suits reviewer notes, glossary questions, and short emails, but read the output before it goes out.

Confidential files and AI rules

Check your contract before you use any AI tool on client text. In a 2025 study of 44 Saudi translators, nine participants said their workplaces forbid AI use because of text sensitivity. That was a convenience sample, so it does not represent every translator.

Here is how Lazur handles data, from its product facts. It listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer you, and they are not stored. Content is never used to train AI models.

Name files so you can find your way back

Translate Document opens its copy in a separate window, so the file list gets messy fast. Name each file with the client, the language pair, and the stage. A name like client-name-FR-review-v2.docx tells you what it is at a glance. Keep one clean copy per stage.

Mistakes translators make in Word on a Mac

• Translating the only copy. Run Translate on a copy, so the source file stays intact.
• Trusting tables. Check each cell after Translate Document, since reports say cells get skipped or moved.
• Leaving Track Changes on while you read. Turn it off when you are not editing.
• Assuming the draft saves time. The research here does not measure time savings in Word.
• Clicking Insert without reading. Insert replaces the highlighted text.
• Skipping the build check. Confirm your build number before you compare notes with a colleague.

Plans and getting started

Lazur runs on macOS, on Apple silicon and Intel Macs. Windows is planned, not available. Check pricing for the current trial and plan terms, since plan details can change. You can start from the download page.

What the research does not tell you

No source here measures how long Word-based translation takes. The 2023 survey reports time savings from CAT tools, and 45% of the CAT users who answered cited time savings as a benefit. That survey did not measure Word, and it did not measure time costs for Word workflows.

No Mac-specific translator survey turned up in the research. The Mac steps on this page come from Microsoft's support article and release notes. The table and Track Changes reports come from Windows threads, so test them on your own Mac.

Checklist before you send a translated file

• Confirm your Word build in Word > About Microsoft Word.
• Check every table cell against the source, and count rows and columns.
• Turn Track Changes off in the file you send, unless the client asked for markup.
• Read each Insert result in context before you move on.
• Keep the source file and any TXLF file in place until the job closes.
• Save a named final copy, separate from your working file.