{
"title": "Chrome’s Red Underlines Disappeared? Here’s How to Restore Spell Check on Windows, Mac, and Mobile",
"content": "Chrome’s red squiggly underline is a subtle but critical writing aid. When it vanishes mid-sentence, the result isn’t just a typo — it’s an erosion of trust in your browser. On July 23, 2026, Technobezz published a detailed walkthrough confirming what many users already suspected: most spell check failures in Chrome aren’t bugs. They’re configuration issues a user can fix in under two minutes without reinstalling anything.
The problem might be a disabled language, the wrong spell check mode, an extension that intercepts keystrokes, or even a policy set by your IT department. The solution is almost always simpler than a full browser reset.
Figure Out Exactly What Stopped Working
“Spell check not working” covers a lot of ground. Before you change any setting, clarify what you’re seeing:
- No red underlines at all, anywhere.
- Right-clicking a mistake doesn’t show suggestions.
- Spell check works for English but not Spanish.
- It fails only on specific websites, like your work email or a blog editor.
- It works in a normal window but not in Incognito mode — or vice versa.
- Your Android phone ignores typos but your desktop flags them.
The Two Settings Inside Chrome That Control Everything
Open a new tab and go directly to chrome://settings/languages. That address cuts through the menus and lands you on the page that governs spelling.
First, make sure the master switch is on: under “Spell check,” enable Check for spelling errors when you type text on web pages. If that toggle is off, Chrome stops checking entirely. It’s the most common cause of a suddenly silent spell checker.
Next, scroll down to Use spell check for. You’ll see a list of languages. Make sure the language you’re typing in is toggled on. If you write in U.S. English but only U.K. English is enabled, Chrome may not flag words like “color” even though it’s correct for your variant. If the right language is missing, add it via Windows or macOS language settings first, then return here and enable it.
A surprisingly effective trick when a language is enabled but still not checking: toggle the language off, restart Chrome, then toggle it back on. This forces Chrome to reload the local dictionary. According to the Technobezz guide, this quick refresh fixes many “stuck” language issues.
Basic vs. Enhanced Spell Check: A Trade-Off Worth Understanding
Chrome gives you two spell check engines, and picking the wrong one can break suggestions or even prevent underlines from appearing.
| Mode | What It Does | Privacy Impact |
|---|---|---|
| Basic spell check | Uses a local dictionary stored on your device. No text is sent to Google. | Private. Best for confidential work or restrictive networks. |
| Enhanced spell check | Sends the text you type in browser fields to Google’s servers for more sophisticated suggestions. | Higher quality corrections, but your typed content leaves your device. |
But don’t just flip the switch blindly. Enhanced spell check won’t work if your network blocks Google services (common on corporate VPNs or with strict firewall rules). If you’re on a managed device, your admin may have disabled it entirely via policy.
Extensions: The Silent Killers
The most maddening cause of spell check failure is a well-meaning extension. Writing assistants (Grammarly, ProWritingAid), AI drafters, privacy tools, password managers with form overlays, and even translation extensions can hijack the typing flow and suppress Chrome’s native red underlines.
The fastest way to test this: open an Incognito window (Ctrl+Shift+N on Windows, Command+Shift+N on Mac). By default, extensions are disabled in Incognito. Type a misspelled word. If spell check works, an extension in your normal profile is the culprit.
Next, return to your normal window and go to chrome://extensions. Disable all extensions, then re-enable them one by one, testing spell check after each. The moment the underlines disappear, you’ve found the conflict. Remove that extension if you don’t need it, or check its settings for a spell check override. Some writing tools have their own spelling engines and deliberately suppress Chrome’s.
When the Website Is the Culprit
Some websites instruct the browser not to spell-check specific fields. Password boxes, search bars, code editors, terminal-style interfaces, and custom rich-text editors (like those in Confluence, Slack, or modern webmail) often disable native spell check by design. If Chrome underlines mistakes on a simple site but not on your company’s web app, the website is making that call.
Test in a known working environment: open a plain text area on a site like a public forum or a basic HTML <textarea>. If spell check thrives there, you can stop tweaking Chrome. Look instead for an in-app proofreading toggle on the problematic site, or accept that it’s a deliberate design choice.
Windows Users: Your Typing Settings Matter Too
On Windows 10 and 11, Chrome leans on the operating system’s typing infrastructure for some spell check functions. If Windows-level spelling correction is turned off, Chrome’s own spell check may behave erratically.
Windows 11: Go to Settings → Time & language → Typing. Under “Spelling,” turn on Highlight misspelled words and Autocorrect misspelled words.
Windows 10: Go to Settings → Devices → Typing. Enable the same two switches under “Spelling.”
Additionally, if you write in a language other than your system display language, make sure that language is fully installed with proofreading tools. Head to Settings → Time & language → Language & region (Windows 11) or Time & language → Language (Windows 10). Under “Preferred languages,” add the language and select all optional features, including “Handwriting” and “Basic typing,” but especially “Spell checking.” Without those, Chrome may not have a complete dictionary.
Mac Users: Keyboard Spelling Controls
On macOS, Chrome can draw on the system’s keyboard spelling settings. If spell check is broken across multiple apps, the fix might lie in System Settings. Go to System Settings → Keyboard → Text Input → Edit. Ensure Correct spelling automatically is enabled. Under the Spelling dropdown, choose the language you’re writing in, or select “Set Up…” to add languages and enable automatic language detection.
But if Chrome is the only app suffering, focus on the Chrome-specific steps first: extensions, language toggle, and spell check mode. macOS settings are secondary.
Mobile: It’s All About the Keyboard, Not Chrome
Chrome on Android and iOS doesn’t use its own spell checker at all. Google explicitly states that mobile Chrome relies on the keyboard app’s spelling features.
Android: Open your keyboard settings (Gboard, Samsung Keyboard, SwiftKey, etc.). For Gboard, tap the settings gear on the keyboard, then Text correction, and enable Auto-correction, Spell check, and Show suggestion strip. If spell check works in other apps but not Chrome, try switching temporarily to another keyboard (like the default Gboard) to isolate the issue.
iPhone/iPad: Go to Settings → General → Keyboard and turn on Auto-Correction. To bring back predictive text suggestions, make sure Predictive is enabled. If you use a third-party keyboard, test with Apple’s default keyboard to rule out a keyboard-specific bug.
Chromebooks require a two-layer check. First, verify Chrome’s spell check settings as described for desktop. Then, inspect ChromeOS input settings: click the time in the lower-right → Settings → Device → Keyboard and inputs (or search for “keyboard” in settings). Confirm the input method matches your writing language and that any available autocorrect or spell check toggles are on.
Managed Devices: When IT Holds the Keys
If you use a work or school account in Chrome, your organization might have disabled spell check entirely or locked it to a specific language. Type chrome://policy into the address bar. Look for policies named SpellcheckEnabled, SpellcheckLanguage, SpellcheckLanguageBlocklist, or SpellCheckServiceEnabled. If any are marked “True” or enforce a value, your admin controls that feature.
Don’t try to bypass these policies with registry hacks or flag overrides. Doing so can violate workplace rules and cause support headaches. Instead, ask your IT department if they can adjust the policy or explain why it’s necessary.
Last Resorts: Reset, New Profile, Reinstall
If you’ve exhausted all the above and Chrome still won’t underline anything, it’s time for heavier but still reversible steps.
Reset Chrome settings. Go to Settings → Reset settings → Restore settings to their original defaults and confirm. This disables all extensions, resets your startup page, new tab page, search engine, and pinned tabs, and clears temporary data. It does not delete your bookmarks, history, or saved passwords. After the reset, test spell check immediately, before reinstalling any extensions.
Create a new Chrome profile. If a reset doesn’t help, your user profile might be corrupt. Click your profile icon in the top-right, select Add (or Manage people → Add person), and create a local profile (don’t sign in yet). If spell check works in the new profile, your old profile is the problem. You can then migrate your bookmarks and data, or simply start fresh.
Only as a final measure should you reinstall Chrome. Download the installer only from Google’s official site. Uninstall Chrome first through your OS (Windows: Settings → Apps; Mac: drag to Trash), then install fresh and test before restoring any extensions or signing into a syncing account.