If you searched for the Google Translate extension expecting it to translate whole pages, you’ve already spotted the confusing part: that job moved somewhere else. Chrome now handles full-page translation on its own, natively, without any extension involved. The Google Translate extension for Chrome still exists on the Chrome Web Store, but its actual job today is narrower. It translates text you highlight and right-click, not the page you’re reading top to bottom.
This guide sorts out what the extension still does, how to use Chrome’s built-in translate instead, where the settings live, and what happens (or doesn’t) if you’re on Firefox, Edge, Brave, or Vivaldi. We’ll also cover the one thing none of these tools do: keep your tabs from disappearing while you’re deep in research across a dozen translated pages.
What Is the Google Translate Extension for Chrome?
The Google Translate extension is a free Chrome Web Store add-on, published by Google Ireland, Ltd., that lets you highlight text on any page and translate it on the spot. Its own store listing is explicit about the split: full-page translation “is now supported natively in Chrome browsers and is no longer supported in the Google Translate extension.” So the extension’s remaining job is highlight-to-translate and right-click selection translation, covering 53 languages according to that same listing.
That’s a meaningful change from what a lot of people remember. Years ago, the extension was the way to get a translate button in your toolbar for entire pages. Now that behavior is built into Chrome itself, and the extension has been repositioned as a lighter, more targeted tool for snippets, phrases, or single words you stumble across while reading.
Worth knowing before you search the Chrome Web Store yourself: every listed extension, this one included, has gone through Google’s formal review pipeline before it’s allowed to appear, and legitimate listings show a developer name you can check against the publisher shown here — Google Ireland, Ltd. Google also runs a separate Established Publisher badge program for developers with a verified identity and a track record of policy compliance, though that badge isn’t unique to this listing. If a search result shows a different developer name claiming to be Google Translate, that’s worth a second look before installing.
Here’s the short version, by situation, before we get into the how-to details:
| You want to… | Use this |
|---|---|
| Translate an entire page | Chrome’s built-in translate (no extension needed) |
| Translate a highlighted word or sentence | Google Translate extension, or Chrome’s right-click menu |
| Set a default translate language | Chrome Settings > Languages > Google Translate |
| Translate on Firefox | No official Google extension; check Firefox’s own translation tools |
| Translate on Vivaldi | Same Chrome Web Store extension, installed via Add to Vivaldi |
Same name, smaller job. If you installed this extension years ago expecting a page-wide translate button, that behavior has since moved into Chrome itself. The extension you have now is doing selection translation only.
How Do I Translate a Full Web Page in Chrome Without Installing Anything?
You don’t need any extension for this — Chrome translates whole pages on its own. When you land on a page written in a language different from your Chrome settings, Chrome shows a translate icon at the right of the address bar, or you can right-click the page and choose “Translate to [Language]” from the context menu.
- Open a page in a foreign language. Chrome checks the page’s language against your browser settings automatically.
- Look for the translate icon. It appears on the right side of the address bar when Chrome detects a mismatch.
- Click it and choose your language. Chrome translates the full page in place.
- Or right-click instead. Choose “Translate to [Language]” from the context menu if the icon doesn’t appear or you dismissed it earlier.
This is the feature that replaced the old extension-driven full-page translate. It’s genuinely convenient because there’s nothing to install and nothing to manage — Chrome just offers it when it thinks you need it. The trade-off is that it’s opt-in per page; if you dismiss the prompt, you have to go looking for the right-click option to bring it back.
How Do I Install the Google Translate Extension in Chrome?
You install it the same way as any Chrome Web Store extension: find the listing, click Add to Chrome, and confirm the permissions prompt. It then sits in your toolbar (or the extensions overflow menu) ready for the next time you highlight text.
- Go to the Google Translate listing on the Chrome Web Store. Confirm the developer shown is Google Ireland, Ltd.
- Click Add to Chrome. A permissions dialog appears — review it and confirm.
- Pin the icon. Click the puzzle-piece icon in your toolbar, then pin Google Translate so it’s always one click away.
- Test it. Highlight a sentence on any page, right-click, and look for the translate option.
If you land on a listing that looks off (wrong developer name, odd permissions, a rating pattern that seems inflated) Chrome Web Store has a built-in way to report it. Open the listing, sign in, scroll to the bottom, and click “Flag Issue,” then fill out the form describing the problem. Google states its team reviews every report and takes any necessary action, which is worth knowing if you ever install something that claims to be an official Google product but doesn’t behave like one.
Once it’s installed, it doesn’t do much on its own until you actually select text. There’s no ongoing background translation and no full-page button waiting for you. That’s the intended design now that page translation lives elsewhere. If you’re looking for other extensions worth your toolbar space, our Chrome extensions roundup covers picks organized by task rather than hype, and our guide to adding extensions to Chrome walks through the general install and permissions process in more depth.
How Do I Translate Selected Text or a Single Phrase?
Highlight the text, right-click it, and choose “Translate selection to [Language].” Google’s own Chrome help documentation confirms this exact flow works directly in the browser, whether or not you’ve installed the extension.
This is genuinely the extension’s core job today. If you’re reading a page that’s mostly in a language you understand but has a paragraph or a quote in another one, this is faster than triggering a full-page translation that would re-translate text you didn’t need touched. It’s also useful on pages where Chrome’s automatic language detection gets confused — a page mixing two languages, for instance, where the full-page prompt might not appear at all.
Where Are Chrome’s Translate Settings, and How Do I Set a Default Language?
Chrome’s translate settings live at Settings, then Languages, then Google Translate. From there you control whether translation is offered at all, which language it defaults to, and which languages get auto-translated or skipped entirely.
According to Google’s own support documentation, that settings page includes four controls worth knowing:
- Use Google Translate — a master on/off toggle for the whole feature.
- Translate into this language — sets your default target language.
- Automatically translate these languages — a list of languages Chrome translates without prompting.
- Never offer to translate these languages — a list Chrome skips entirely, even if it detects a mismatch.
If you keep getting translate prompts for a language you already read comfortably, that “never offer” list is the fix. And if translation seems to have stopped working altogether, the master toggle is the first thing to check before assuming something’s broken.
One toggle controls everything. If the master “Use Google Translate” toggle gets switched off (sometimes by accident while adjusting other language settings) neither the address-bar icon nor the right-click option will appear. Check this setting first if translate seems to have vanished.
Is There a Google Translate Extension for Firefox?
Not an official one from Google. The Google Translate extension on the Chrome Web Store is built for Chromium-based browsers, and Firefox runs its own separate add-ons marketplace rather than installing Chrome Web Store listings directly.
That’s the honest answer to a search that comes up a lot: “Firefox Google Translate extension” and “Google Translate extension for Firefox” both get real search volume, which tells you plenty of people expect a direct equivalent and don’t find one under Google’s name. If you’re on Firefox, your best bet is to check Firefox’s own translation capabilities and Mozilla’s official add-ons store for translation tools, rather than searching for a Chrome Web Store listing that won’t install there anyway.
This is a good moment to mention: whichever browser you land on, the tabs you’re translating and cross-referencing across don’t stay organized on their own. If you’re a heavy Firefox user, our Firefox extensions guide covers what’s available in that ecosystem, and BelayTab itself runs on Firefox too, alongside Chrome, Edge, Brave, Opera, Vivaldi, Arc, and Safari on Mac.
Google Translate Extension vs Chrome’s Built-In Translate: Which Should You Use?
For whole pages, use Chrome’s built-in translate. For highlighted snippets, either the extension or Chrome’s own right-click option works — the extension just puts a dedicated icon in your toolbar for it.
| Chrome’s built-in translate | Google Translate extension | |
|---|---|---|
| Translates full pages | Yes, natively | No longer supported |
| Translates selected text | Yes, via right-click | Yes, its main job now |
| Needs installing | No | Yes, from Chrome Web Store |
| Settings location | Settings > Languages > Google Translate | Same settings apply |
| Works offline | No | No |
| Available on Firefox | Firefox has its own translation tools | No official version |
The practical upshot: most people don’t need to install anything for translation to work in Chrome today. The extension earns a spot in your toolbar only if you specifically want a visible icon for selection translation, or you’re used to the older workflow and prefer having a dedicated button rather than remembering the right-click path.
If you’re deciding whether to bother installing the extension at all, think about how often you hit the highlight-and-translate case versus the full-page case. Most casual browsing skews heavily toward full pages, which Chrome already handles without any extra install. The extension earns its keep for people doing something more specific: reading multilingual documentation, cross-checking a term across sources, or working through a page that mixes languages in a way the full-page translator doesn’t handle cleanly.
Does the Google Translate Extension Work in Edge, Brave, Vivaldi, and Other Chromium Browsers?
Yes, on most Chromium-based browsers, though the install path differs slightly by browser. Vivaldi’s own help documentation confirms that Chrome Web Store extensions, including this one, install directly through an “Add to Vivaldi” button after you browse to the listing in the Chrome Web Store.
- Vivaldi. Chrome Web Store extensions install directly, per Vivaldi’s own help docs — browse the store, then click Add to Vivaldi.
- Brave. Chromium-based and runs Chrome Web Store extensions, so the Google Translate listing installs the same way it does in Chrome.
- Edge. Chromium-based with its own Microsoft Edge Add-ons store; check that store first, and see our Edge extensions guide for the general process.
- Opera and Arc. Also Chromium-based, though it’s worth confirming availability in each browser’s own extension gallery before assuming full parity with Chrome.
Vivaldi in particular gives you more direct control over the extension once it’s installed than a lot of Chromium browsers do. Its Extensions page is reachable through Tools > Extensions, the shortcut Ctrl + Shift + E, or by typing vivaldi://extensions into the address bar, and you can reorder toolbar icons by holding Ctrl while dragging, or tuck less-used ones into a dropdown instead of leaving every icon visible. Vivaldi’s own docs note that store extensions “may occasionally behave differently” there than in Chrome, so it’s worth testing the translate icon’s placement after install rather than assuming it lands exactly where it does in Chrome.
Worth noting: even on browsers where the extension installs cleanly, the same limitation applies everywhere. It translates selected text, not full pages, because that split is baked into the extension itself, not just Chrome’s version of it. If a Chromium browser you use has its own built-in full-page translate (several do) that’s likely the faster path for whole pages regardless of which extension you have installed.
Why Isn’t Chrome Offering to Translate a Page?
The most common cause is a settings mismatch: either the page’s language is on your “never offer to translate” list, or the master translate toggle is off. Start at Settings, then Languages, then Google Translate, and work through the list below before assuming something’s broken.
- Check the master toggle. “Use Google Translate” needs to be on for either the icon or the right-click option to appear.
- Check your never-translate list. If the page’s detected language is on it, Chrome won’t prompt, even if you want it to this once.
- Try the right-click menu manually. Even if the icon doesn’t show, “Translate to [Language]” in the right-click menu often still works.
- Reload the page. Occasionally the prompt just doesn’t fire on the first load, especially on pages that build content dynamically.
- Confirm the page differs from your settings language. Chrome won’t offer to translate a page it thinks already matches your language settings, even if the content reads oddly.
How Do I Keep My Research Tabs Safe While Translating and Cross-Referencing Pages?
You protect them by saving the session, not by relying on translation tools, since neither Chrome’s built-in translate nor the Google Translate extension has anything to do with tab survival. Translation work tends to spawn a lot of open tabs fast — the original source, a translated version, a couple of cross-reference pages, maybe a dictionary tab you opened to check one word. None of that is backed up by Chrome’s translate feature.
Chrome’s own session restore can bring tabs back after a normal close, but it’s a single, overwritable slot. It doesn’t keep named versions of your research, and a crash or an accidental “close window” doesn’t always leave it intact. If you’re routinely juggling tabs across languages and sources, our guide on tab overload covers the broader problem, and our session manager comparison looks at dedicated tools for exactly this.
BelayTab approaches it differently: it’s free, needs no account, and takes automatic snapshots of every open window on a five-minute timer and again when a window closes, plus a version history of the last 20 versions per session so restoring never overwrites older work. You can also save a window manually with one click or Ctrl + Shift + S (Cmd + Shift + S on Mac), name it something you’ll recognize later (“translation project, sources”) and get back to it days later exactly as you left it, tab groups and all.
- Install BelayTab from the download page. It works alongside Chrome, Edge, Brave, Opera, Vivaldi, Arc, Firefox, and Safari on Mac.
- Save your research window as a named session. One click, or the keyboard shortcut, saves every open tab in that window.
- Keep working across translated tabs. Automatic snapshots run every five minutes in the background, no extra steps needed.
- Restore anytime from the Recovery screen. Snapshots, deleted sessions, and recently closed windows are all in one place.
That Recovery screen pulls together more than snapshots, too: it also lists anything you’ve deleted in the last 30 days and the browser’s own recently closed windows, so you’re not hunting through separate menus to figure out which one has the sources you need. If you’re migrating from another tab-saving habit — a pile of OneTab links, a Session Buddy export, or just a plain list of URLs you’d been keeping in a notes app — BelayTab can import those directly instead of making you rebuild your translation project’s tab list from scratch.
None of this replaces a translation tool, and it isn’t meant to. BelayTab doesn’t read page content, doesn’t touch what language a page shows in, and has no host permissions that would let it. It just makes sure the tabs you built up while translating are still there when you come back to them. If you want the fuller picture of how saving and restoring works, the save tabs feature page and restore tabs feature page cover the mechanics in more detail, and the download page has links for every supported browser.
