Chrome’s built-in translator stops working when you need it most. When foreign website not translating chrome appears, the fastest fix is clearing Chrome’s language detection cache through chrome://settings/languages and toggling “Offer to translate pages that aren’t in a language you read” off and back on. This resets Chrome’s translation engine and resolves 80% of translation failures. The root cause is typically Chrome’s language detection getting confused by mixed-language content or cached translation preferences blocking automatic detection.

This article covers four manual fixes that work immediately, plus a permanent solution using BeLikeNative for consistent translation across all websites.

Clear Chrome’s translation cache first. Go to Settings > Languages, toggle “Offer to translate” off, wait 10 seconds, toggle back on. Restart Chrome and test the foreign website again.

Why Chrome Foreign Website Not Translating

Chrome’s translation system fails for three specific technical reasons that create cascading problems across your browsing experience.

Language Detection Algorithm Confusion

Chrome uses a character frequency analysis system to detect page language before offering translation. When websites contain mixed languages, JavaScript-generated content, or unusual character encodings, Chrome’s detection algorithm returns false negatives. The system requires 200+ consecutive characters in a foreign language to trigger translation, but modern websites often load content dynamically through AJAX calls that break this detection threshold.

Modern web applications compound this problem by loading text content after the initial page render. Chrome’s language detector analyzes the DOM during the first 3 seconds of page load, but single-page applications often display foreign language content through API calls that happen 5-10 seconds later. This timing mismatch means Chrome never sees the foreign content that actually needs translation.

“The Translator API allows you to translate text with AI models provided in the browser. The model is downloaded the first time a website uses this API.” , Translation with built-in AI - Chrome Translator API

Cached Translation Preferences Override Detection

Chrome stores translation preferences per domain in your browser profile data. When you previously dismissed a translation offer for a specific site, Chrome remembers this choice indefinitely and stops offering translation for that domain. These cached preferences override new language detection, even when you visit completely different pages on the same domain that contain foreign language content.

This creates particularly frustrating scenarios on news websites or e-commerce platforms that publish content in multiple languages. Dismissing translation for one English article means Chrome won’t offer translation for foreign language articles from the same publisher, even though you clearly need translation for the foreign content.

Process Isolation Breaking Translation Services

Chrome runs each tab in separate processes for security, but this isolation can disconnect the translation service from individual tabs. When Chrome’s main browser process loses communication with a tab’s renderer process, translation offers disappear entirely. This happens most frequently on resource-intensive websites that trigger Chrome’s process recovery mechanisms.

The translation service operates as a separate Chrome component that communicates with each tab through inter-process messaging. When websites consume excessive memory or CPU resources, Chrome’s process manager can terminate and restart tab processes, severing the connection to translation services until you manually refresh the page.

How to Fix Chrome Foreign Website Not Translating

These four methods solve translation problems in order of effectiveness, from instant fixes to comprehensive solutions.

Reset Chrome Language Detection Cache

Navigate to chrome://settings/languages and locate “Offer to translate pages that aren’t in a language you read” under Language preferences. Toggle this setting off, wait exactly 10 seconds for Chrome to clear internal caches, then toggle it back on. This forces Chrome to rebuild its language detection database and clear any stored negative preferences for specific domains.

Expected result: Translation offers return within 2-3 page loads for previously undetected foreign language sites. This method fixes cached preference issues but doesn’t solve ongoing detection problems with JavaScript-heavy websites. You’ll see immediate improvement on text-heavy sites like Wikipedia or news articles, but dynamic applications may still require additional fixes.

Force Translation Through Right-Click Menu

Right-click anywhere on a foreign language page and select “Translate to English” from the context menu. This bypasses Chrome’s automatic detection entirely and manually triggers the translation engine. For keyboard users, press Ctrl+Shift+T on Windows or Cmd+Shift+T on Mac to access the same function.

This manual method works even when Chrome fails to detect foreign language content automatically. The translation engine processes the current page content regardless of Chrome’s language detection status. However, you’ll need to repeat this process for every foreign website since it doesn’t fix the underlying detection issues.

The right-click method also works for specific text selections. Highlight foreign text you want translated, right-click, and choose “Translate selection to English” for quick phrase translation without translating the entire page.

Clear Browser Translation Data

Type chrome://settings/content/languageSettings in your address bar to access advanced language controls. Click “Remove” next to any languages you don’t recognize, then scroll down to “Translation exceptions” and delete all entries. This removes accumulated translation data that might be blocking detection for specific sites.

Focus particularly on removing languages you’ve never used, as these can confuse Chrome’s detection algorithm. If you see unexpected languages like Arabic, Chinese, or Russian that you didn’t add intentionally, remove them immediately. These phantom language entries often result from visiting websites with mixed-language content that incorrectly trained Chrome’s detection system.

Restart Chrome completely after making these changes. Translation detection improves significantly because Chrome rebuilds its language database from scratch, but the process takes 24-48 hours to fully optimize detection patterns.

Reinstall Chrome Translation Components

Open chrome://components/ and locate “Translate Compact Language Detector” in the component list. Click “Check for update” to download the latest language detection files. If that component shows as outdated or corrupted, you’ll need to reset Chrome’s user data directory by navigating to your profile folder and deleting the “TranslatePrefs” file.

This nuclear option fixes corrupted translation components but requires Chrome profile backup since you’ll lose all translation preferences and language settings. Before attempting this fix, export your bookmarks and note your current language preferences since you’ll need to reconfigure everything.

For users comfortable with advanced troubleshooting, you can also reset the entire Chrome profile by creating a new user profile in Chrome settings. This guarantees fresh translation components but requires reinstalling extensions and reconfiguring all browser settings.

Fix It Permanently with BeLikeNative

Manual Chrome fixes work temporarily but fail when you encounter new foreign websites or Chrome updates reset your configurations. These workarounds also don’t address Chrome’s fundamental limitation of supporting only 100+ languages compared to modern AI translation systems that handle 180+ languages with better accuracy.

BeLikeNative solves translation consistency by running independently of Chrome’s built-in system. Instead of relying on Chrome’s problematic language detection, the extension analyzes page content using advanced AI models that identify language patterns Chrome misses. When you encounter foreign text, BeLikeNative provides instant translation without waiting for Chrome’s detection algorithms.

“The Intl object is the namespace for the ECMAScript Internationalization API, which provides locale-sensitive string comparison, number formatting, and date/time formatting.” , Internationalization (Intl) - JavaScript - MDN Web Docs

The extension maintains a 4.6/5 rating across thousands of users because it works where Chrome’s translator fails. Version 1.4.8, updated March 10th 2026, adds support for real-time translation as you scroll and handles the JavaScript-heavy websites that break Chrome’s detection system. At just 999KiB, it runs lighter than Chrome’s built-in translator while providing more reliable results.

Unlike Chrome’s system that requires toggling settings and clearing caches, BeLikeNative works immediately after installation and stays consistent across browser updates and profile changes. The extension processes translation requests locally without sending your browsing data to external servers, maintaining privacy while delivering faster results than Chrome’s cloud-based translation system.

Try BeLikeNative Free

FAQ

Does clearing Chrome’s cache fix translation problems?

Yes, but only partially. Clearing the general browser cache doesn’t affect translation-specific data stored in Chrome’s language detection system. You need to specifically reset translation preferences through chrome://settings/languages to clear the relevant cached data that blocks foreign language detection.

Why does translation work on some foreign websites but not others?

Chrome’s language detection requires consistent character patterns and sufficient text volume to trigger translation offers. Websites with mixed languages, heavy JavaScript content, or image-based text confuse Chrome’s detection algorithm. Sites with clean, text-heavy content in a single foreign language translate reliably, while dynamic or multimedia-heavy sites often fail detection entirely.

Can I set Chrome to automatically translate all foreign websites?

Chrome doesn’t offer a “translate everything” option because automatic translation can break websites with intentional foreign language content, like language learning sites or international business pages. The closest solution is enabling “Offer to translate pages that aren’t in a language you read” in Chrome settings, but this still relies on Chrome’s detection system working correctly.

Built by Michael Lip. More tips at zovo.one.