Installing Translation Extensions on Chrome / Edge / Firefox

"Why isn't the extension doing anything?" is a common installation complaint, but it usually points to a specific step that was missed: the permission prompt was closed, the icon was hidden in the toolbar menu, the store could not be reached, or the browser is managed by an organization.

This guide keeps the focus on verifiable install steps for Chrome, Edge, and Firefox. It also covers the cases that usually cause confusion: unavailable stores, managed devices, hidden toolbar icons, and manual packages that should not be trusted unless the source can be checked.

Whether you're setting up Immersive Translate for the first time or troubleshooting an install that used to work, start with the download route and source checks before reinstalling anything.

Why Extension Installation Goes Wrong

Before we get into the how, let's understand the why. Browser extensions aren't simple files you double-click. They live inside a managed ecosystem controlled by the browser vendor, and that ecosystem has guardrails — some helpful, some frustrating. Here are the four most common reasons installation fails or appears to fail:

1. Permission prompts get dismissed or overlooked

When you click "Add to Chrome," a dialog pops up listing the permissions the extension needs — things like "Read and change all your data on all websites." That sounds alarming, and many users instinctively click "Cancel" or just close the popup. Without those permissions, the extension installs but can't actually interact with web pages. It sits in your toolbar doing absolutely nothing. The fix is simple: accept the permissions. Translation extensions need page access because their entire job is reading and modifying page content. There's no way around it.

2. The extension store is inaccessible

In certain regions — most notably mainland China — the Chrome Web Store is blocked at the network level. Users in corporate environments sometimes face similar restrictions. If you can't reach the store, you can't install extensions through the standard flow. We'll cover workarounds in detail in the dedicated section below.

3. Browser policies disable extension installation

IT departments in schools, companies, and government offices routinely deploy group policies that prevent users from installing extensions — or limit them to a pre-approved whitelist. If you see a message like "Your browser is managed by your organization" in Chrome settings, this might be your issue. The solution usually involves talking to your IT admin, though we'll cover some self-help options too.

4. Outdated browser version

Modern extensions use Manifest V3 APIs that only work on recent browser versions. Chrome 110+, Edge 110+, and Firefox 109+ are the baseline. If you're running an old version — common on machines with restricted update policies — the extension store page might show "Not compatible with your browser" or silently fail to install. Update your browser first; then try again.

Installing on Google Chrome

Chrome is often the first browser people try when installing a translation extension. The process is straightforward when the Web Store is reachable, but confusing when the store is blocked, the permission prompt is missed, or the icon is hidden after installation. Here's the full flow.

Step 1: Open the Chrome Web Store listing

Navigate to the Chrome Web Store. You can go through the download page, or search for "Immersive Translate" in the Web Store's search bar. Do not rely on the icon alone. Check the extension name, publisher details, recent update information, and permission prompt before installing.

Step 2: Click "Add to Chrome"

On the extension's listing page, click the blue "Add to Chrome" button in the upper right. A confirmation dialog appears listing the permissions the extension requires. For a translation extension, you'll typically see:

• "Read and change all your data on all websites" — Required to detect foreign-language text and insert translations into the page DOM.
• "Display notifications" — Used for update alerts and translation completion pings (optional in some extensions).

Click "Add extension." Chrome downloads and installs the extension in a few seconds. You'll see a confirmation bubble near the toolbar, and the extension icon appears in your extensions area.

Step 3: Pin the extension to the toolbar

By default, Chrome hides new extensions behind the puzzle-piece icon in the toolbar. Click that icon, find Immersive Translate in the dropdown, and click the pin icon next to it. This keeps the extension visible and one-click accessible on every page. Skipping this step is why many users think the extension "disappeared" after installation.

Step 4: Verify installation

Open any foreign-language webpage — a Wikipedia article in German, a news site in Japanese, anything not in your browser's default language. Click the Immersive Translate icon in the toolbar. If you see the extension popup with a "Translate this page" button, installation succeeded. If the icon is grayed out or nothing happens when you click it, jump to the troubleshooting section.

Step 5: Grant site-specific permissions (if needed)

Some Chrome configurations require you to explicitly allow extensions on specific sites. If translation works on some pages but not others, right-click the extension icon → "This can read and change site data" → select "On all sites." This is especially common after Chrome updates that tighten default extension permissions.

Installing on Microsoft Edge

Edge is built on Chromium, which means it supports Chrome extensions natively — with one extra step. Edge has its own Microsoft Add-ons store, but it also lets you install directly from the Chrome Web Store.

Option A: Install from the Microsoft Add-ons store

1. Open Edge and navigate to the Edge Add-ons store (accessible from Settings → Extensions → "Get extensions for Microsoft Edge").
2. Search for "Immersive Translate" or your preferred translation extension.
3. Click "Get" → "Add extension" in the confirmation dialog.
4. Pin the extension to the toolbar using the same puzzle-piece icon method as Chrome.

This is the cleanest approach and the one Microsoft recommends. Extensions installed from the Edge Add-ons store receive automatic updates through Edge's own update channel.

Option B: Install from the Chrome Web Store

1. In Edge, navigate to the Chrome Web Store (yes, it works in Edge).
2. Edge will display a banner at the top: "You can add extensions from the Chrome Web Store." Click "Allow extensions from other stores" if this is your first time.
3. Find the extension, click "Add to Chrome" (the button text doesn't change — it still says Chrome), and confirm.

This method is useful when the extension is available on the Chrome Web Store but hasn't been published to the Edge Add-ons store yet, or when the Edge store version lags behind.

Edge-specific gotchas

• Sleeping tabs. Edge aggressively puts inactive tabs to sleep, which can pause extension background scripts. If translations seem to stop working after a tab has been idle, disable sleeping tabs for frequently-translated sites: Settings → System and performance → "Never put these sites to sleep."
• Efficiency mode. Edge's "Efficiency mode" throttles background activity, which can interfere with extensions that pre-translate content. Turn this off while translating, or add an exception.
• Managed by organization. Edge in corporate environments is even more likely than Chrome to have extension policies. Check edge://policy to see if an admin has restricted installations.

Installing on Firefox

Firefox uses a completely different extension system (WebExtensions API via the Firefox Add-ons store at addons.mozilla.org). Chrome extensions don't install on Firefox directly — you need the Firefox-specific version. Fortunately, most major translation extensions ship Firefox builds.

Step 1: Visit the Firefox Add-ons page

Open Firefox and go to addons.mozilla.org. Search for "Immersive Translate" or navigate through the download page.

Step 2: Click "Add to Firefox"

Firefox shows a permission dialog similar to Chrome's. Review the permissions and click "Add." The extension installs immediately.

Step 3: Confirm in the toolbar

Firefox typically shows a brief notification that the extension was added. The icon should appear in the toolbar automatically. If it doesn't, right-click the toolbar → "Customize Toolbar" and drag the extension icon to your preferred location.

Step 4: Check for Container Tab compatibility

If you use Firefox's Multi-Account Containers feature (popular among privacy-focused users), be aware that some extensions don't share state across containers. A translation extension configured in one container might appear unconfigured in another. Most well-built extensions (including Immersive Translate) handle this gracefully, but it's worth checking if you notice inconsistent behavior.

Firefox-specific considerations

• Enhanced Tracking Protection. Firefox's built-in tracker blocking can occasionally interfere with translation API calls. If translations fail on certain sites, click the shield icon in the URL bar and try disabling Enhanced Tracking Protection for that site.
• Private browsing mode. Extensions are disabled in private windows by default. To enable: go to about:addons, click on the extension, and toggle "Run in Private Windows" to Allowed.
• Android version. Firefox on Android supports a curated set of extensions. Immersive Translate is available on Firefox for Android — install it from the Add-ons menu within the mobile browser.

When the Chrome Web Store Is Blocked or Unavailable

This section is critical for users in regions where Google services are restricted — particularly mainland China — and for anyone behind a corporate firewall that blocks extension stores. If you can open chrome.google.com/webstore without issues, skip ahead. If you can't, read every word below.

Method 1: Use the Edge Add-ons store instead

The Edge Add-ons store (microsoftedge.microsoft.com/addons) is accessible in most regions where the Chrome Web Store is not. And since Edge is Chromium-based, you can install Edge extensions in Edge with zero friction. If you're already using Chrome and can't access its store, consider temporarily switching to Edge for translation work. Alternatively, install Edge just for the purpose of grabbing the extension file.

Method 2: Direct .crx or .xpi download from a verifiable source

Some extension projects provide direct download files or manual install notes. For Immersive Translate, start with the download page and only proceed if the source is clear. Chrome and Edge use .crx style packages; Firefox uses .xpi.

• Chrome/Edge: Open chrome://extensions or edge://extensions, enable "Developer mode" in the top-right corner, then drag the .crx file into the page. Chrome will warn about installing extensions from outside the Web Store — this is expected. Click "Add extension" to proceed.
• Firefox: Open about:addons, click the gear icon, select "Install Add-on From File," and choose the .xpi file.

Method 3: Use a VPN or proxy to access the Chrome Web Store

If your network blocks the Chrome Web Store but doesn't restrict VPN usage, connecting through a VPN server in a country where Google services are available (the US, Japan, Singapore, etc.) will restore access. This is the simplest workaround for users in restricted regions who prefer the standard installation flow. Once installed, the extension works normally without the VPN — you only need it for the initial download.

Method 4: Sideloading an unpacked extension (Developer mode)

This is a last-resort method, primarily useful for developers or advanced users. If you have the extension's source code (e.g., from GitHub):

1. Download or clone the extension's repository.
2. Open chrome://extensions and enable "Developer mode."
3. Click "Load unpacked" and select the extension's root directory (the folder containing manifest.json).
4. The extension loads immediately, but Chrome will display a warning banner every time you open the browser, reminding you that developer mode extensions are active.

This method doesn't receive automatic updates — you'll need to manually pull new versions and reload. For most users, Method 1 or Method 2 is far more practical.

Installation Methods Compared Across Browsers

Here's a consolidated view of every installation path, so you can pick the one that matches your situation without re-reading the entire guide.

A few observations. A recognized extension store is usually the preferred route because it keeps installation and updates clear. If the Chrome Web Store is blocked, Edge Add-ons is often the practical alternative. Direct file installation can work, but it creates an ongoing maintenance burden if automatic updates are not available. Sideloading is better treated as an advanced fallback, not the default user path.

For a broader comparison of what you can actually do with translation extensions once they're installed, see our head-to-head review of 8 popular translation extensions.

Post-Installation Setup and First Translation

Getting the extension into your browser is step one. Configuring it so it actually works well is step two — and the step most people skip, leading to a mediocre first impression. Here's what to do in the first five minutes after installation.

1. Set your target language

The extension usually auto-detects your browser's UI language, but it's worth confirming. Open the extension popup (click the icon in the toolbar), go to Settings, and verify that the "Target language" is set to English (or whatever language you want translations in). A surprising number of support tickets boil down to the target language being set to the wrong value.

2. Pick your default translation engine

Most translation extensions default to Google Translate. That's fine for getting started, but you can get noticeably better results by switching engines based on your primary use case:

• DeepL — best for European languages (French, German, Spanish, Italian, Dutch). Reads more naturally than Google for these pairs.
• Google Translate — widest language coverage (130+ pairs), solid baseline quality. Best default if you translate across many languages.
• OpenAI (GPT-4o) — best for nuanced, context-heavy text and East Asian languages. Requires an API key.

You can change engines at any time, and Immersive Translate lets you set per-domain engine rules — DeepL for Le Monde, GPT-4o for arXiv, Google for everything else.

3. Try your first translation

Open a foreign-language page. Press Alt + A (Windows/Linux) or Option + A (macOS) to translate. Translated paragraphs should appear below each original paragraph in a bilingual layout. If nothing happens, check the extension icon, page permissions, and whether the current page is a browser internal page.

If you want a deeper walkthrough of the translation experience itself — bilingual modes, display customization, engine benchmarks — head to our complete web page translation guide.

4. Configure keyboard shortcuts

The default shortcuts work for most people, but if they conflict with other extensions or system-level shortcuts, you can remap them:

• Chrome: Go to chrome://extensions/shortcuts and find Immersive Translate in the list.
• Edge: Go to edge://extensions/shortcuts.
• Firefox: Go to about:addons → gear icon → "Manage Extension Shortcuts."

At minimum, set a shortcut for "Translate current page" — it's the action you'll use most, and having it on a keyboard shortcut removes the need to mouse over to the toolbar icon every time.

5. Disable conflicting extensions (if any)

Translation extensions modify page content by injecting translated text into the DOM. Other extensions that also modify page content — Grammarly, certain ad blockers with cosmetic filtering, reader-mode extensions — can occasionally conflict. If translations look broken or elements are misplaced, try disabling other content-modifying extensions temporarily to isolate the issue. In practice, Immersive Translate coexists well with uBlock Origin, Bitwarden, and Dark Reader, which cover the vast majority of users.

Troubleshooting Installation Problems

You followed every step above and something still isn't working. Let's diagnose. These are the most common issues, ordered by frequency, drawn from actual support tickets.

"The extension icon is grayed out"

This means the extension is installed but not active on the current page. Common causes:

• You're on a browser internal page (chrome://settings, about:blank, the New Tab page). Extensions can't run on these pages — it's a browser security restriction, not a bug. Navigate to an actual website and try again.
• Site permission is restricted. Right-click the extension icon → "This can read and change site data" → "On all sites." On Chrome 120+, this is sometimes reset after updates.
• The extension crashed. Go to chrome://extensions, find the extension, and click the reload icon (circular arrow). If that doesn't work, remove and reinstall.

"Installation failed — CRX_HEADER_INVALID"

This error appears when you try to install a .crx file that is corrupt, incomplete, or incompatible with your Chrome version. Solutions:

• Re-download the file from the official source. Partial downloads (interrupted by network issues) are the most common cause.
• Check your Chrome version. If the extension requires Manifest V3 and you're on an older Chrome, the file is structurally incompatible.
• Clear your browser cache and try again. Occasionally, a cached redirect causes the download to fail silently.

"This extension is not from any known source"

Chrome shows this when you install a .crx file outside the Chrome Web Store without enabling Developer mode. The fix: open chrome://extensions, enable "Developer mode" in the upper right, then retry the installation. Chrome will still warn you, but it will allow the install to proceed.

"Your administrator has blocked this extension"

This is a Group Policy restriction, common in corporate and school environments. You cannot override this as an end user. Options:

• Contact your IT administrator and request that the extension be added to the allowed list.
• Use a personal device or a different browser profile that isn't managed.
• If your organization uses Edge but only blocks Chrome extensions, try installing from the Edge Add-ons store — the policy might only apply to Chrome.

"The extension installed but does nothing when I click it"

Nine times out of ten, the page you're testing on is in your browser's default language, so the extension has nothing to translate. Navigate to a page that's actually in a foreign language. If it still does nothing:

• Open the extension popup and check if it's asking you to complete initial setup (language selection, terms acceptance).
• Check the browser console (F12 → Console tab) for error messages. If you see Content Security Policy (CSP) errors, the website is blocking injected scripts — this is rare but happens on some banking and government sites.
• Try a different website. If the extension works on some sites but not others, the issue is site-specific, not installation-related.

"Extensions keep getting disabled after restart"

Chrome periodically audits extensions and may disable ones that weren't installed through the Web Store or that have known security issues. If your extension keeps getting turned off:

• Install from the official Chrome Web Store if at all possible — this is the only way to guarantee Chrome won't interfere.
• If you're sideloading, accept that Chrome will nag you every session. There's a "Disable developer mode extensions" dialog that appears at startup; just dismiss it.
• On managed devices, check with IT — some policies automatically remove unauthorized extensions on a schedule.

Frequently Asked Questions

Can I install the same extension on Chrome and Edge simultaneously?

Yes. Chrome and Edge maintain completely separate extension directories. Installing Immersive Translate on both browsers won't cause conflicts. However, settings don't sync between them — you'll need to configure each browser independently. Some extensions offer cloud sync for settings; check the extension's options page.

Do translation extensions work on mobile browsers?

It depends on the browser. Firefox for Android supports a curated set of extensions, including Immersive Translate. Chrome for Android does not support extensions at all — this is a long-standing limitation with no announced fix. Safari on iOS supports web extensions through the App Store. For mobile translation, the Firefox Android route is your best bet if you want a desktop-equivalent experience.

Will a translation extension slow down my browser?

A well-built translation extension adds negligible overhead to normal browsing. It only activates when you trigger translation (or on domains you've configured for auto-translation). Memory usage for Immersive Translate is typically 30–50 MB, which is less than a single average web page in 2026. The CPU impact is near zero until you actually translate something, at which point you'll see a brief spike as the DOM is modified. On modern hardware, this is imperceptible.

Is it safe to grant "Read and change all your data on all websites" permission?

This permission sounds terrifying but is technically necessary for any extension that modifies web page content — which is literally what a translation extension does. The key is trust: install only from official stores and verified developers. Immersive Translate is open-source with its code publicly auditable on GitHub. If the permission still bothers you, some browsers let you restrict the extension to specific sites only (click the extension icon → "This can read and change site data" → "When you click the extension"). This means you manually activate it per-site, which is more private but less convenient.

How do I completely remove a translation extension?

Right-click the extension icon → "Remove from Chrome" (or "Remove from Edge" / "Remove" in Firefox). To verify it's fully gone, go to chrome://extensions (or equivalent) and confirm it's no longer listed. If the extension stored local data, you may also want to clear browsing data for the extension's own domain.

I'm in a country where the Chrome Web Store is blocked. What's my best option?

Try the Edge Add-ons route first. Edge is Chromium-based and avoids the Chrome Web Store dependency. Only consider manual files when the source can be verified. Full instructions are in the Chrome Web Store blocked section above.

---

Installing a browser extension should be a 30-second task. When it isn't, the problem is almost always one of the scenarios covered above — a permission that was denied, a store that can't be reached, a managed browser that blocks installations, or a version mismatch. Now you know the fix for each. If you've just finished installing, your next step is learning what the extension can actually do: start with our complete web page translation guide, or explore the PDF translation guide if you work with academic papers and documents. The setup is done. Go read something in a language you couldn't read five minutes ago.