Fix Chrome Translate Not Working on PC & Mobile (2025)

When Chrome’s built‑in page translation stops appearing or fails silently, the fix is usually small: a disabled toggle, a “Never translate” rule you forgot about, an extension blocking requests, or a site that opts out of translation. This guide shows exactly how to bring Chrome Translate back on desktop and mobile—without guesswork. You’ll learn the 60‑second checks, where the settings live, how to isolate extensions, what to clear (and what not to), and how to deal with dynamic pages or sites that intentionally block translation.

Quick 60‑second checklist

• Reload the page (Ctrl/Cmd + R).
• Right‑click blank space → Translate to [Your language].
• Click the Translate icon in the address bar (if visible) and select your language.
• Open the same page in Incognito (Ctrl/Cmd + Shift + N). If Translate works, an extension is blocking it.
• Try a clearly foreign‑language site (e.g., a Spanish news homepage). If Translate prompts there, the original page is the issue.

Why Chrome Translate stops working

• Translate is off in Languages settings, or you added too many “languages I read.”
• You previously chose “Never translate this site/language,” and Chrome is honoring it quietly.
• The page mixes languages or loads content later (single‑page app); auto‑detect doesn’t always trigger.
• An extension blocks requests to Google’s translation endpoints.
• Corrupted site data/cache or a stale browser profile.
• Network/VPN/firewall blocks translate.googleapis.com or related domains.
• Mobile toggles are off, or Chrome thinks you already read the page language.
• The site uses notranslate attributes (developer opt‑out).

Fix 1: Update Chrome

New versions often fix issues with translation prompts and UI.

Desktop (Windows/macOS/Linux): Menu (⋮) → Help → About Google Chrome (or go to chrome://settings/help) → Update → Relaunch.

Android: Play Store → Manage apps & device → Updates → Update Chrome → Relaunch.

iPhone/iPad: App Store → Updates → Update Chrome → Relaunch.

Fix 2: Enable and configure translation (desktop + mobile)

Chrome won’t offer translation if it believes you already read the page language.

Desktop

1. Open chrome://settings/languages
2. Turn on “Offer to translate pages that aren’t in a language you read.”
3. Under Preferred languages, keep only languages you truly read at the top (e.g., English). Fewer languages = more translate prompts.
4. Open Translate settings/exceptions and remove any “Never translate this site/language.”

Android

1. Chrome → Settings → Languages.
2. Turn on “Offer to translate pages in other languages.”
3. Make your primary language first in the list; remove extras you don’t need.
4. On a foreign page, tap the translate bubble and set “Always translate [language]” if helpful.

iPhone/iPad

1. Open a foreign page → More (⋯) → Translate.
2. In the translate bubble, tap the gear (if available) to undo “Never translate [language/site]” or set “Always translate [language].”
3. If Translate is missing, try another foreign site; ensure you’re on the latest Chrome for iOS.

Fix 3: Translate pages manually (no auto‑prompt)

• Address bar: Click the small Translate icon → choose your language.
• Right‑click menu: Right‑click blank space → Translate to [Language].
• Open the page in a new tab or reload, then try the menu again (helps on dynamic pages).

If “Translate” is missing in the menu, the feature is likely disabled—return to Fix 2.

Fix 4: Extension conflicts (how to isolate fast)

Privacy/ad‑blocking extensions frequently block translation requests.

1. Open Incognito (Ctrl/Cmd + Shift + N) → visit the page. If Translate works here, an extension is the culprit.
2. Go to chrome://extensions → toggle all off.
3. Re‑enable one by one, reload the page each time, until Translate breaks. That extension is blocking requests.
4. Keep it off for that site or allowlist these domains inside the extension:
   • translate.googleapis.com
   • clients5.google.com
   • gstatic.com

Fix 5: Clear cache/site data without over‑deleting

Corrupted cache can break features like Translate.

Desktop (site‑specific first)

• Click the lock icon in the address bar → Site settings → Clear data.
• Or open chrome://settings/siteData and search the domain → Remove.

Desktop (broader reset)

1. chrome://settings/clearBrowserData
2. Time range: All time
3. Select: Cookies and other site data; Cached images and files
4. Clear → Restart Chrome

Android/iOS

Chrome → Settings → Privacy and security → Clear browsing data → Cookies/site data + Cached images/files → Restart.

Fix 6: Use the official Google Translate extension

The extension gives you manual control when auto‑prompts don’t appear, especially on single‑page apps:

• One‑click full‑page translation from the toolbar.
• Translate selected text only (useful when a site blocks full‑page translation).
• Persistent language choice per site.

Install from the Chrome Web Store, pin the icon, and use it on pages where the built‑in prompt is unreliable.

Platform‑specific tips

Windows and macOS

• Reset settings: chrome://settings/reset → Restore settings to original defaults (extensions disabled; bookmarks/history kept).
• New profile test: Click your profile picture → Add → Create a new profile. If Translate works there, your old profile had a conflicting customization.

Android

• Disable data saver/VPN temporarily; some modes block subrequests.
• When the translate bubble appears, tap settings and undo “Never translate this site/language.”
• Confirm Languages settings and the order of your preferred language.

iPhone/iPad

• Use More (⋯) → Translate. If missing, the page may already match a listed reading language or the feature is temporarily unavailable—try another site.
• Still stuck? Update Chrome for iOS. As a last resort, reinstall (this clears app data) and sign back in.

Advanced fixes (policies, notranslate, SPAs, flags)

Remove “Never translate” exceptions

• Desktop: chrome://settings/languages → Translate settings/exceptions → remove language/site from the “never” list.
• On any translated page, open Translate settings and choose “Always translate [language]” to reverse earlier choices.

Network and security rules

• Temporarily turn off VPN/proxy and test. Corporate firewalls often block translation endpoints.
• Allowlist:
  • translate.googleapis.com
  • clients5.google.com
  • gstatic.com
• Try a different network (mobile hotspot vs office Wi‑Fi) to isolate.

Site‑level opt‑outs

Some sites use meta name="google" content="notranslate" or class="notranslate" to discourage full‑page translation.

• Translate selected text via the Google Translate extension.
• Use a simplified/reader/print view (if available), then translate that view.
• As a last resort, copy/paste into translate.google.com.

Single‑page apps (SPAs) and lazy‑loaded content

• Wait for content to load, then click Translate again.
• Soft‑reload (Shift + Refresh) after new sections appear.
• Translate in sections on infinite‑scroll pages.

Flags and experiments (use caution)

• If you changed translation flags: chrome://flags → Reset all to default → Relaunch.
• Avoid experimental Translate flags unless you understand side effects.

Enterprise/school devices

• If you see “Managed by your organization,” a policy (TranslateEnabled) may disable Translate. Contact IT.
• Test on a personal device or network to confirm it’s policy‑related.

Reinstall Chrome (desktop last resort)

1. Back up/sync bookmarks.
2. Uninstall Chrome.
3. Rename/delete your user data folder:
   • Windows: %LOCALAPPDATA%\Google\Chrome\User Data\
   • macOS: ~/Library/Application Support/Google/Chrome/
4. Reinstall and sign back in.

Real‑world notes and patterns

• Most common fix: Remove a “Never translate” rule and trim your “languages I read” list.
• Desktop conflicts: Extensions blocking subrequests (console shows ERR_BLOCKED_BY_CLIENT). Incognito test isolates this in seconds.
• Dynamic sites: Trigger translation again after content loads, or translate selected text.
• PDFs and images: Full‑page translation doesn’t rewrite embedded text. Open PDFs in Google Drive/Docs and use “Translate document,” or copy text out. For images, use a text extractor first.

Common mistakes to avoid

• Adding many “languages I read,” which suppresses the prompt.
• Over‑clearing data (signs you out everywhere) instead of clearing site‑specific data first.
• Debugging extensions without an Incognito A/B test—use it to save time.
• Trusting auto translation for sensitive workflows (contracts, regulated topics) without human review.

FAQ

Why doesn’t the Translate prompt appear on some pages?

The page might be in a language Chrome thinks you read, mixes languages, or loads content later (SPA). Use right‑click → Translate to [Language] or the address bar icon, or install the Google Translate extension.

How do I undo “Never translate this site/language”?

Desktop: chrome://settings/languages → Translate settings/exceptions → remove the entry. On a translated page, open settings and choose “Always translate [language]” to reverse behavior.

Is it safe to clear cookies and cache?

Yes, but you’ll be signed out. Prefer clearing the affected site first via the lock icon → Site settings → Clear data.

Does Chrome Translate work offline?

No. It requires internet access, and strict networks can block it.

An extension breaks Translate but I need it. What now?

Allowlist translation endpoints inside that extension (translate.googleapis.com, clients5.google.com, gstatic.com), or disable the extension only on specific sites.

Can I force Chrome to always translate a language?

Yes. When the translate bubble appears, open its settings and choose “Always translate [language].” You can undo this in Language settings later.

Resources

• Languages & Translate: chrome://settings/languages
• Manage extensions: chrome://extensions
• Clear browsing data: chrome://settings/clearBrowserData
• Reset settings: chrome://settings/reset
• Site data: chrome://settings/siteData

Related reading

If you also translate timed text, this guide covers safe SRT/WebVTT workflows: AI Subtitle Translator: Safe SRT/WebVTT Workflow

Conclusion and takeaways

• Start with updates and Language settings; trim your “read” list and remove “Never translate” rules.
• Use manual translation (right‑click/address bar) and the official extension for dynamic or stubborn pages.
• If Translate works in Incognito, isolate a blocking extension and allowlist Google translation endpoints.
• Clear site‑specific data before wiping everything. On managed devices, check policy.

Work through this sequence and you’ll restore click‑and‑translate for most sites—with privacy and readability in mind.