TwinreadImmersive Translate not working: causes and fixes
Updated
Most failures come from four things: a used-up quota, a network error to the translation service, a page the browser protects, or text the site marks as not for translation. Switching engine or using hover-to-translate fixes most of them.
Google Chrome 138 or later, or a Chromium browser with the built-in Translator API, on desktop. No account, no API key.
Check these first
These come from the vendor’s own troubleshooting page.
- Quota or network. If the indicator keeps spinning, look at the failure reason. A quota message means the allowance is used up. A network error means the connection to the engine failed. The fix the vendor gives is to switch to another translation service from the floating button or the extension icon.
- Pages it cannot touch. Browser start pages, other extensions’ pages and the Chrome Web Store do not allow translation.
- Parts left out. A site can mark text with translate="no" or a notranslate class. Turning on hover-to-translate and hovering over the text gets around it.
- Google Translate in China. The FAQ says to add translate.googleapis.com to the proxy rule.
If it still fails
Try a second engine, then a fresh tab, then check whether the site works with extensions switched off. If the problem is the quota, waiting for the daily reset or registering is the vendor’s answer.
A translator that runs on your computer
A tool that sends text to a service can fail for reasons outside your browser. Twinread hands the text to Chrome’s built-in translator. There is no quota on pages and no account, and after the language model has downloaded once, translating works offline.
It has limits of its own. It needs Chrome 138 or later on a desktop, it cannot change browser pages or the extension store, and it has one engine. Free has a few limits, among them 10 minutes of video subtitles a day and the first 5 pages of a PDF. If something here blocks you, the roadmap page takes suggestions, and Twinread keeps growing from them.
Questions
Why is Immersive Translate not translating?
The vendor FAQ lists a few causes: the monthly quota is used up, the connection to the translation service failed, the page is one the browser does not let extensions touch, or the site marks parts of itself as not to be translated (immersivetranslate.com/docs/faq, read on 6 October 2026).
Why does the spinner keep spinning?
Check the failure reason first. The FAQ says a quota limit means your allowance is exhausted, and a network error points to the connection. It suggests switching to another translation service.
Why are some parts of a page left untranslated?
Some sites mark content as not to be translated. The FAQ suggests turning on hover-to-translate and hovering over those parts.
Is there a translator that cannot hit a quota?
Twinread runs Chrome's built-in translator on your computer, so there is no request quota and no remote service to fail. It has its own limits: Chrome 138 or later on desktop, and a language model that downloads once.
Translate without a remote service
Twinread uses the translator built into Chrome, so there is no quota to run out. Install it, pick two languages and let Chrome download the model once.
Google Chrome 138 or later, or a Chromium browser with the built-in Translator API, on desktop. No account, no API key.
More guides
Sources, read on 6 October 2026: immersivetranslate.com/docs/faq. Twinread is an independent product and is not affiliated with Immersive Translate.