Immersive Translate Not Working? 5 Common Fixes (2026)

Last week my Chrome updated to version 126, and Immersive Translate just stopped working. The floating ball vanished from the bottom-right corner, and clicking the toolbar icon did nothing. After two hours of poking around, I traced the problem to a permission reset triggered by the browser update. This article collects the five most common failure patterns I have personally hit or seen reported in community threads, organized as an elimination checklist so you can narrow down the cause without reinstalling everything right away.

Fix 1: The Extension Is Not Loading at All

You open a page and there is no floating ball, no toolbar icon highlight, nothing. This is the most common form of "Immersive Translate is broken."

I restarted Chrome first — did not help. Then I opened chrome://extensions/ and found the extension was toggled on but had a small warning line: "This extension may be corrupted." Clicking "Repair" triggered a re-download, and the floating ball came back immediately.

A different scenario: the extension is gone entirely from your list. If you originally installed from the Chrome Web Store, a store-side update can occasionally remove an older version silently. Head to the download page to grab the latest install link. Edge users should check edge://extensions/, and Firefox users should check about:addons — same logic applies.

If you are on a managed work or school device, group policies may block third-party extensions outright. Open chrome://policy/ and look for ExtensionInstallBlocklist entries. If you see one, you will need IT to whitelist the extension ID — there is no workaround on your end.

Fix 2: Extension Is There but Pages Do Not Translate

The floating ball is visible, the icon looks normal, but clicking "Translate" does nothing to the page content. I ran into this on Windows 11 with Chrome 126 and eventually traced it to the "Never translate this site" list.

Open the Immersive Translate settings panel and look for the "Never translate" site list. I had accidentally right-clicked "Never translate this site" on github.com during a test weeks earlier, and then every English README stayed untranslated. It took me an embarrassingly long time to figure out.

Another trap: the page content already matches your "source language" setting. If your source language is set to English and you open an English page, the extension correctly skips translation. This gets confusing on bilingual pages — a page may declare lang="zh" in the HTML tag but serve mostly English content, or vice versa. The extension reads the content, not the tag, so behavior can be unexpected on mixed-language pages.

Fix 3: Your Settings Got Reset After a Browser Update

During the Chrome 125-to-126 upgrade cycle, my Immersive Translate engine reverted from DeepL back to the default. Translation style, shortcuts, and display mode all returned to factory settings.

This usually happens when the browser clears the extension's local storage during an update. The fix: go to Immersive Translate settings, find the backup/restore option, and import your saved config file. If you never exported one, you will have to reconfigure manually — and then immediately export a backup this time so the next update does not cost you another fifteen minutes.

This behavior has been reported on both Windows 10 22H2 and macOS Sonoma 14.5. It is not an Immersive Translate bug; it is a side effect of the browser's extension storage handling during major version upgrades.

Fix 4: Another Extension Is Interfering

I run Tampermonkey, uBlock Origin, and a second translation extension (TWP — Translate Web Pages) alongside Immersive Translate. One day I noticed Immersive Translate stopped working on Google Docs specifically, while it was fine on regular pages.

My debugging approach was brute-force but effective: open chrome://extensions/, disable other extensions one by one, and refresh the target page after each toggle. The culprit turned out to be TWP — both extensions were fighting over the same DOM nodes for inline translation, and neither could finish the job. Disabling TWP fixed the problem instantly.

uBlock Origin usually does not conflict directly, but custom filter rules can block translation API domains. If you have added rules that block *.deepl.com, translate.googleapis.com, or similar endpoints, translation requests get silently dropped. Check the uBlock logger for red entries related to translation domains.

Fix 5: Network Is Blocking the Translation API

Immersive Translate calls online translation engines — Google, DeepL, OpenAI, and others — over HTTPS. If your network cannot reach those API endpoints, translation stalls at "Translating…" and eventually times out.

In mainland China, direct access to Google Translate APIs is often unreliable. If you are using the Google engine and it keeps timing out, switch to another available engine inside Immersive Translate settings. The switch takes a few seconds and does not require reinstalling the extension.

I also hit this inside a corporate network once — the company firewall was blocking api-free.deepl.com. Switching to a phone hotspot restored translation immediately, confirming it was a network issue. In that case, either ask IT to whitelist the domain or switch to an engine that uses a different endpoint.

Still Not Working After All Five Checks?

If none of the above solved it, try the nuclear option: fully uninstall Immersive Translate, restart your browser, clear browser cache (especially extension data), then reinstall the latest version from the download page. I had one case where the local extension files were corrupted in a way that "Repair" could not fix — a clean reinstall resolved it immediately.

Also check your browser version. If you are on Firefox below 115 or a Chromium fork that lags behind the stable channel, some WebExtension APIs may not be available. Updating the browser itself is sometimes the only real fix.

If you need to compare Immersive Translate with other options, the alternatives comparison covers DeepL, Google Translate, TWP, and dictionary extensions by use case.