Traduzir-Paginas-Web: Real-Time Page Translation Extension for Firefox

What Traduzir-Paginas-Web does and which browsers it supports

Traduzir-Paginas-Web, also known as TWP, translates the current page in place without navigating to a translation proxy or opening new tabs. According to the README's FAQ section, the page is translated without having to open new tabs, the translation language can be changed, and auto-translate can be enabled per site or globally. Tapping the Google Translate icon in the extension menu switches translation engines.

Browser support is currently limited to Firefox. The extension is available for Firefox desktop through Mozilla Addons and for Firefox Android through the same add-on catalogue (search for 'TWP - Translate For Mobile' under Firefox's Find more add-ons option, available from Firefox v120 onwards). The README states the extension will be officially released for Chrome, Edge, and Brave in the future but is not currently available for those browsers. It also advises users who previously installed it on Chromium-based browsers through registry modification to undo those changes using the registry uninstall scripts provided in the dist/chromium/ directory.

Choosing between Google, Bing, and Yandex as translation engines

TWP supports three translation engines: Google Translate, Bing Translator, and Yandex Translate. The README states that the user switches engines by touching the Google Translate icon in the extension popup. This engine choice is the feature that most distinguishes TWP from built-in browser translation. Firefox has no native page translation; other translation extensions commonly lock users to a single service.

The practical reason to choose one engine over another comes down to language pair coverage and personal preference. Yandex covers languages more common in Eastern Europe and Central Asia better than the other two. Google covers the widest set of language pairs overall. Bing can produce different output quality on specific language pairs, and some users may prefer it for data-sovereignty reasons. The extension does not document quality differences across engines; it acts as a configurable client for whichever service the user selects. Switching does not require reinstalling or configuring credentials; it is a single tap in the extension popup. The README does not document how the extension invokes each translation service (direct API call, web scrape, or other method), so users who need to comply with terms of service for any of these APIs should verify the mechanism.

Installing on Firefox desktop and Firefox for Android

For Firefox desktop, install directly from Mozilla Addons at the URL listed in the README:

https://addons.mozilla.org/firefox/addon/traduzir-paginas-web/

For Android, the process is slightly different because Firefox for Android requires manually finding the add-on:

1. Install Firefox v120 or later on Android. 2. Open the extension manager. 3. Scroll down and tap Find more add-ons. 4. On the add-ons website, search for TWP. 5. Install TWP - Translate For Mobile.

For developers who want to build the extension from source, the repository root includes a gulpfile.js and package.json. The build uses Gulp with Babel for transpilation and webpack for the polyfill. Build instructions are documented in build-instructions.md at the repository root.

Privacy: what TWP collects and what the translation services receive

The README addresses privacy directly in its FAQ. The extension itself collects no information; the project's privacy policy, linked from Mozilla Addons, states no data is collected by the extension. However, the page content is sent to Google or Yandex servers for translation, depending on which engine is active. Bing is listed as a supported engine in the extension description but the privacy FAQ mentions Google and Yandex specifically.

This is the fundamental privacy trade-off of any cloud translation service. A user who wants to translate confidential internal documents, personal medical records, or proprietary business content should be aware that the full text of those pages is transmitted to a third-party translation API. For public web content, this is the standard behaviour for all major page translation tools, built-in or extension-based. TWP does not add an additional data collection layer on top of whatever the chosen translation engine receives, and the PRIVACY file in the repository root contains the full statement. The extension requests access to data on all websites the user visits, which the README explains is required to read and modify page text for translation: this is a standard permission for any content-script-based translation tool.

Pages that cannot be translated and the Chrome support gap

Not every page can be translated. The README identifies a structural limitation: browser extensions cannot access certain pages for security reasons. The named examples are support.mozilla.org and addons.mozilla.org. These restrictions come from the browser, not from TWP; the extension simply cannot inject content scripts into privileged browser pages. This applies to other browser extension translation tools as well, so it is not a TWP-specific limitation.

The Chrome support situation is more significant. The README states the extension will be officially released for Chrome, Edge, and Brave 'in the future', but that release had not happened as of the v10.2.5.0 release on 2026-08-16. The README specifically instructs users who installed on Chromium through registry modification to uninstall using one of two .reg files in dist/chromium/: twp-registry-uninstall-self.reg for a minimal removal or twp-registry-uninstall-all.reg for a deeper removal. Teams standardized on Chromium-based browsers cannot currently use TWP.

How TWP compares to built-in browser translation in Chrome and Edge

Chrome and Edge include Google Translate page translation as a built-in feature that requires no extension. When a Chrome user visits a page in a foreign language, an automatic offer to translate appears. That built-in integration is tightly coupled to Google Translate and cannot be changed to a different service without additional tooling. Edge uses a similar mechanism with Microsoft Translator as the default, also without a choice of engine.

TWP takes a different approach on the engine side: it lets the user choose between Google, Bing, and Yandex, and the choice can be changed at any time in the extension popup. This matters for users in regions or contexts where Yandex provides better results, or for users who prefer Bing to reduce reliance on a single provider. The trade-off is that TWP is currently restricted to Firefox. A team that primarily uses Chrome and needs page translation does not yet have a TWP option, and must use the built-in Chrome integration or a different Chromium-compatible extension. For Firefox users specifically, TWP adds engine choice and active open-source maintenance that the browser's default behaviour does not provide, and the MPL-2.0 licence means the source can be inspected and forked by anyone who needs to audit what the extension does.

Editorial conclusion

Traduzir-Paginas-Web is the right extension for Firefox users who want in-page translation without switching tabs and who want a choice of translation engine rather than being tied to the browser default. The extension works on Firefox desktop and Android (Firefox v120+). Chrome, Edge, and Brave are not supported in the current release. The extension sends page content to the chosen translation service (Google, Bing, or Yandex) but collects no data itself. Check the MPL-2.0 licence terms if you plan to fork or redistribute. The last push was on 2026-09-03, and the latest release is v10.2.5.0 from 2026-08-16.

Frequently asked questions

Official sources

1. FilipePS/Traduzir-paginas-web on GitHub
2. License: MPL-2.0
3. Project website
4. README
5. Releases