Chrome for translators on Mac: reading, checking and reviewing localized pages in 2026

Most translators on a Mac use Chrome as a reading tool. You open the source site, check a term, read the client's reference pages and look at how the localized version renders. Chrome can help with all of that. It can also mislead you if you treat its output as a finished translation. The built-in Translate feature is aimed at readers, not at localization teams. This guide covers the settings and checks that matter for your work. It also covers what Chrome misses, and where Lazur helps while your hands stay on the keyboard.

How to translate a page in Chrome on Mac

Open the source page and wait for it to finish loading. Then use the Translate icon at the right end of the address bar. You can also right-click the page and choose Translate to your language. Chrome shows the translated page in place, so you can read it from top to bottom.

1. Click the Translate icon at the right end of the address bar, or right-click the page.
2. Pick your target language from the menu. If the menu offers the wrong one, choose More, then Choose another language.
3. Read the translated text. Check headings, buttons and menus first, because mistakes there stand out.
4. If translation fails or stalls, refresh the page with ⌘R and try again.

How to translate selected text in Chrome on Mac

Sometimes you need one paragraph, not the whole page. Highlight the text. Right-click and choose Translate selection to your language. Chrome shows the translation for that selection only. Say you are checking a German product description. Select the warranty paragraph alone, translate it and compare it with your draft.

To change the target language for a selection, select More, then Choose another language. Use the selection tool to read, not to produce client text. Copying machine output straight into a file skips the review your client pays for.

Chrome language settings for translators on Mac

Open More (⋮), then Settings, then Languages. Google Translate has its own section. The Use Google Translate toggle turns translation offers on or off. Two lists sit in the same section. Never offer to translate these languages stops the prompt for languages you read well. Automatically translate these languages sends matching pages to your reading language without asking.

Review these lists every time a project changes. A language you read well today may need a new rule next month. Keep the lists short. A short list for languages you read unaided, and a second for languages you always need translated, is enough.

Why the Chrome translate prompt does not appear

Chrome decides when to offer translation with a heuristic. That is a guess based on the page, not a rule you can see. Polyglot, a localization tool vendor, says the prompt may never appear on short screens such as checkout or signup pages. Its post gives no failure rates, so treat that claim as a warning, not a measurement.

The fix is simple. Click the Translate icon yourself when a page is in a language you do not read. Do not assume a missing prompt means the page is already in your language. Check the language of the page first, then decide.

What Chrome translation misses in a localized site

Chrome translates visible text. Translators care about much more than that. Polyglot says the browser misses placeholders, aria-labels, alt text and title text. Those strings show up in forms, screen readers and tooltips. A long translation in one of them can also break a layout.

• Placeholders, the grey hint text inside an input field.
• aria-label values, which screen readers announce to people who cannot see the page.
• Alt text on images, which describes pictures for screen readers.
• title attributes, which appear as tooltips when someone hovers over an element.
• Brand names and product terms, which can be translated when they should stay in English.
• The same button verb rendered two different ways on two screens.

Polyglot also says Chrome rewrites text nodes in place, and that can break React apps. The linked issue was filed in 2017 and has more than 100 comments. If a localized web app goes blank or behaves oddly after translation, reload with translation off. Then report the bug with a screenshot and your Chrome version.

How to check locale formats with DevTools in Chrome

Chrome DevTools can change what a page sees about your locale. Open DevTools with ⌘⌥I. Press ⌘⇧P to open the Command Menu inside DevTools. Type Sensors, then open the Sensors panel. Chrome's DevTools post for Chrome 83, from 2020, describes locale emulation there. Check the current panel, because the layout may have changed since then.

The emulation changes what the page reads through Intl APIs, navigator.language and navigator.languages, and the Accept-Language request header. If a site formats prices and dates from the browser, you will see the change. If it does not, the site may set its format on the server or in a cookie. Then the problem sits with the developer, not the browser. Write down which one you found.

Does Chrome on Mac show menus in another language

Not as a Chrome setting. Google's help page says Chrome on Mac follows the system's default language. The option called Display Google Chrome in this language is available only on Windows. To see Chrome's own menus in another language on a Mac, you change the language of macOS. That changes every app, so use a test user or a spare account for it.

Which Chrome version to check on Mac before a review

Open Chrome > About Google Chrome to see your build. Wikipedia and releases.sh both list 157.0.8103.39 as the stable macOS build, dated 3 November 2026. Chrome 158.0.8127.18 reached Windows on 4 November 2026. releases.sh says Mac will be coming shortly, as an early stable release to a small share of users. Write the version into every bug report, since translation behavior can change between builds.

Where Lazur fits in a Chrome review on Mac

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘, Option and Command together, to ask about anything on screen. Lazur answers out loud. It sees the screen only while you hold the shortcut. It points at things, explains them and guides you through settings. It does not click for you, and it does not operate other apps.

What to say to Lazur while you work in Chrome

• “Lazur, where is the Translate icon?” Lazur draws a circle and a label around it.
• “Lazur, what does this German error message mean?” Lazur explains it out loud.
• “Lazur, walk me through adding Spanish to the Never offer list.” Lazur guides you click by click.
• “Lazur, draft a short query to the client about this term.” You check the wording before you send it.
• “Lazur, research how banks in the Netherlands name this account type.” The research runs in Lazur's own Chrome tabs, and you get a summary and a report.
• Hold fn and dictate the QA notes. Dictation writes clean text at your cursor in any app.

How a guided task works in Chrome

Ask Lazur to walk you through a settings change, and it names the first place to click. Then it waits. You click, and it moves on to the next step. The waiting is deliberate. A guide that runs ahead of your screen causes wrong clicks, and on a settings page a wrong click can change more than you meant to.

Use point when you need a location. Use explain when you need meaning. Use guide when a change has several steps. Use draft when you need words in your voice, and always read them before you send them.

Common mistakes with Chrome translation

• Treating Chrome's output as a finished translation. Survey respondents often find machine output needs significant edits.
• Skipping the refresh when translation stalls, then blaming the browser.
• Assuming no prompt means the page is already in your language.
• Checking visible text only, and missing alt text, placeholders and aria-labels.
• Pasting confidential client text into an online tool without reading the contract first.
• Using Chrome to judge a site's localization quality, when it only reads the source.

The effort is easy to underestimate. The GTS article says post-editing effort is often underestimated. A page that looks fine after Chrome translates it may still need a full pass with your glossary and termbase. Budget for that pass before you quote a rate.

How much post-editing work do translators do

The GTS survey gives the clearest numbers here. It invited 3,300 professional freelance translators, and 212 responded. The stated margin of error is about 6.68%. Of respondents, 87.93% do post-editing. 66.18% rate machine output as acceptable but in need of significant edits. 21.74% call it poor and in need of extensive rework. The raw tables give slightly different splits, so treat the figures as directional.

Acolad's 2025 translators survey, dated 20 May 2025, reports that 79% of translators are familiar with AI tools. It says 42% use them daily and 21% use automated post-editing. The article does not state its sample size, so weigh it lightly.

So what does this mean for Chrome? Chrome gives you a reading pass at no cost. It does not give you a glossary, a terminology check or a memory of past decisions. Those gaps are where a good part of the work sits. For tools that cover the rest, see tools for translators on Mac.

A Chrome setup checklist for translators on Mac

1. Open Chrome > About Google Chrome and note the version.
2. Go to Settings > Languages > Google Translate and set your two lists.
3. Test one localized page with the Translate icon and one selection.
4. Open DevTools with ⌘⌥I, then check locale formats with Sensors.
5. Keep your glossary in its own file, not inside Chrome.
6. Hold ⌥ ⌘ and ask Lazur to point at anything you cannot find.

Lazur on Mac: requirements, pricing and privacy

Lazur runs on macOS, on Apple silicon and Intel Macs. Windows is planned, not available. A free trial needs no credit card, and it starts the first time you open the app. Paid plans come in monthly and annual options. Dictation is unlimited on both. Check pricing for current plans, and download Lazur when you are ready.

Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers so they can answer you, and Lazur says they are not stored. Content is never used to train AI models. Memory of what you asked and did stays on your Mac.

Client material is still your call. Read the contract and any NDA before you send a page to an AI service, Lazur included. Hold the shortcut only when you need help. Close sensitive tabs before you ask a broad question about the screen.

Next steps for your Chrome review routine

Start with one localized page this week. Set your language lists, run the Translate icon, then check locale formats in DevTools. Write down what Chrome missed. Then try Chrome with Lazur on the same page, and ask it to point, explain and guide. Keep the habits that save you time, and drop the ones that do not.