Chrome spell check failing — red squiggles missing on misspelled words, the right-click “Spelling” menu not offering suggestions, or autocorrect inside text fields silently ignored — usually comes down to one of two settings being off. Most people fix it in 30 seconds once they know where to look. For a broader walkthrough, our Google Chrome Errors is a good next read.
First check: chrome://settings/languages → “Spell check” section → make sure the toggle is on AND your language is listed below it as checked. If “Spell check” is enabled but no language is selected: the spell checker is running but has nothing to check against. Add your language (English, Spanish, whatever you write in), check the box next to it, and reload any open tabs. This alone resolves the most common cause.
Basic vs Enhanced spell check
Chrome offers two spell check engines. The Basic one runs entirely on your device and checks against a dictionary. The Enhanced one sends your text to Google’s servers and offers more accurate suggestions (the same engine Google Search uses) — useful for technical terms, proper nouns, and context-aware corrections.
Switch between them: chrome://settings/languages → Spell check section → choose “Basic spell check” or “Enhanced spell check.” If one isn’t working, the other often does. Enhanced needs internet; Basic doesn’t. Some workplaces block Enhanced for privacy reasons, so if it’s failing in an office environment specifically, Basic is the right choice.
Site permissions and rich-text editors
Not all websites use Chrome’s built-in spell check. Some, especially rich-text editors used by Gmail’s compose window, Google Docs, Notion, and most CMS editors, implement their own spell checking instead — overriding Chrome’s. If spell check works on plain comment boxes but not in Gmail or your blog editor, that’s why.
For Google Docs specifically: Tools → Spelling and grammar → Show spelling suggestions → must be on. For Gmail compose: the gear icon → See all settings → General tab → “Default text style” → confirm spell check isn’t off there. Each rich-text editor has its own setting buried somewhere — when in doubt, check the editor’s own preferences first.
Custom dictionary problems
Chrome maintains a custom dictionary of words you’ve added (right-click → “Add to dictionary”). Over time this can accumulate accidentally-added typos, which then never get flagged as misspellings.
Clean it up: chrome://settings/languages → “Custom spell check dictionary” → review the list → remove entries that look like typos. The path to this setting changed several times across Chrome versions; if you don’t see it in Languages, search “spell” in chrome://settings.
If the custom dictionary file itself is corrupted: navigate to %localappdata%GoogleChromeUser DataDefault → find Custom Dictionary.txt → close Chrome → delete the file → reopen Chrome. The file regenerates empty. You lose any actually-useful words you’d added, but spell check should work again.
Extensions interfering
Grammar/spelling extensions (Grammarly, LanguageTool, ProWritingAid) replace Chrome’s built-in spell check with their own. If you’ve installed one and then disabled it, sometimes the underlying state is left broken — neither the extension nor Chrome’s native checker works.
Quick test: chrome://extensions → toggle off all extensions → reload tab → test spell check. If it works: an extension was interfering. Re-enable extensions one at a time to find which. Common offenders: Grammarly, LanguageTool, and any “writing assistant” extension. Fix: either fully uninstall the broken extension (don’t just disable) and reload, or keep the extension and let it handle spell check entirely.
Our guide on Chrome page loading issues covers the broader Chrome troubleshooting flow that applies when multiple features stop working, and our Chrome crash diagnosis covers the underlying stability issues. For details on Chrome’s language and dictionary configuration, Google’s Chrome support documentation covers the language settings and how spell check interacts with multi-language profiles.
Multi-language profiles
Bilingual users hit this often. If you write in two languages and only one is enabled in spell check settings: the second language’s text appears as one giant string of misspellings, and Chrome may give up on spell-checking the page entirely.
Add all languages you actively write in: chrome://settings/languages → Languages section → Add languages → enable spell check for each by checking the box. Chrome will then auto-detect which language you’re typing per text field, mostly correctly. It’s not perfect — sometimes a mostly-English sentence with one Spanish word gets confused — but it’s the right configuration regardless.
Specific input types where spell check just won’t work
Some HTML inputs have spell check disabled by the website’s developers. Password fields are the obvious one. But also: email address fields, URL fields, code editors embedded in pages (like CodePen), and any text input with the spellcheck="false" HTML attribute.
You can’t override this from the browser side — the page explicitly told Chrome not to spell-check. If it matters (you’re writing in a code editor that should still spell-check comments, for instance), the workaround is to compose your text in a separate document with spell check working, then paste into the page.
For developers’ own custom inputs: this is sometimes a legitimate design choice (developer input shouldn’t be spell-checked), but on a content site like a blog comment box, it’s usually a bug. Worth reporting to the site owner.
Chrome update or profile reset
If everything looks configured correctly and spell check still doesn’t work, the next layer is Chrome itself. Two interventions:
Update Chrome: menu → Help → About Google Chrome. If an update was pending, this triggers it and relaunches. Sometimes spell check breaks in a specific Chrome release and gets fixed in the next.
Reset Chrome settings: chrome://settings/reset → “Restore settings to their original defaults.” This doesn’t delete bookmarks or saved passwords but does reset preferences, including spell check configuration that may be in a bad state. After reset: reconfigure language preferences as needed.
If resetting doesn’t help: test in a guest profile (Chrome menu → profile icon → Guest). If spell check works in guest mode, your main profile is corrupted. The cleanest fix is to create a new profile and sign in to Chrome Sync, which restores bookmarks and passwords to the fresh profile.
Windows-level language packs
Rare but real: Chrome falls back on Windows’ installed language packs for some spell-check functions. If you removed a language pack from Windows that Chrome was using, spell check for that language stops working.
Settings (Windows) → Time & language → Language & region → confirm your writing language has a language pack installed (look for “Language pack installed” under the language). If not: click the language → Options → download language pack and speech features. Restart Chrome after.
This usually only matters if you’re writing in less-common languages on Windows, but worth checking if standard fixes haven’t worked.
| Behaviour | Most likely cause | Fix |
| No squiggles anywhere | Spell check globally disabled | Enable in chrome://settings/languages |
| Works on some sites, not others | Site uses its own spell checker | Configure within that site’s editor |
| Wrong language flagged as misspellings | Wrong dictionary selected | Add the actual language to spell check list |
| Real typos no longer flagged | Accidentally added to custom dictionary | Review and clean custom dictionary |
| Works in incognito, not normal Chrome | Extension interfering | Disable extensions to identify offender |
| Stopped after Chrome update | Update-related regression | Wait for next update or reset Chrome settings |
For most users, the fix is genuinely as simple as toggling spell check on and selecting their language. The more involved scenarios (custom dictionary corruption, extension conflicts, language pack issues) are real but uncommon. Start with the basic toggle, work outward only if that doesn’t help.
When Grammarly takes over
Grammarly is the most commonly installed writing extension, and once installed, it intercepts text fields and provides its own checking — which is more sophisticated than Chrome’s native spell check but introduces its own behaviour. If you have Grammarly installed:
- Grammarly icon appears in the bottom-right of supported text fields → suggestions come through Grammarly, not Chrome
- Sign-out from Grammarly inside Chrome doesn’t disable it — you have to actually disable the extension
- Free Grammarly catches basic spelling; Premium catches grammar and style; if you have free, you may notice “missing” suggestions that are actually behind a paywall
If you want Chrome’s native spell check back: chrome://extensions → toggle off Grammarly → reload. Or use Grammarly’s own settings (gear icon in any text field) to disable it on specific sites where Chrome’s checker is enough.
Spell check and Chrome OS / Chromebooks
On Chromebooks, Chrome’s spell check uses the system-wide language settings instead of just Chrome’s. Configure spell check at: Chromebook settings → Languages and inputs → Inputs → check the languages you write in. Without the correct input methods installed, Chrome on Chromebook may not have access to the right dictionaries.
This is environment-specific to Chromebooks; the steps don’t apply to Windows or macOS users. But worth knowing if you’ve switched from Windows to a Chromebook and spell check behaviour changed unexpectedly.
The case for using site-native checkers
For longer or more important writing (job applications, formal emails, blog posts), it’s often better to use the site’s own checking rather than relying on Chrome’s. Gmail’s grammar and tone suggestions, Google Docs’ more sophisticated checking, WordPress’s editor checks — these are usually more capable than Chrome’s basic dictionary lookup. Chrome’s native spell check is best treated as a baseline for casual text input (comments, search boxes, simple forms) rather than the only checking layer on important text.
This isn’t a fix exactly — it’s a recommendation for how to think about spell checking on the web. Different tools for different writing contexts. Chrome’s spell check is the lightweight always-on layer; site-native checkers and Grammarly are heavier tools for when accuracy matters more.
Diagnosing intermittent failures
If spell check works most of the time but sometimes mysteriously fails, the cause is usually one of:
- The Enhanced spell check can’t reach Google’s server — temporary network blip, corporate firewall, or VPN interfering. Switch to Basic spell check to test if this is the issue
- The page reloads via JavaScript partway through typing, resetting the text field state and breaking spell check until you click out and back in. Common on heavily-interactive sites like Notion
- You typed in a textarea that just got dynamically replaced — common in chat apps and modern web frameworks. Spell check sees a brand-new element it hasn’t processed yet
For these, just clicking out of the text field and back in usually re-triggers spell check. Annoying but not really fixable from Chrome’s side; it’s a quirk of how modern web apps handle text inputs.
When you don’t want spell check
The opposite problem also exists: some users actively want to disable spell check on certain sites — developers working in code editors, foreign-language learners who want to see their actual unfiltered errors, people whose work involves typing technical terms that aren’t dictionary words and generate constant red squiggles.
Disable per-input: right-click in a text field → uncheck “Check the spelling of text fields” (label varies by Chrome version). This applies only to that specific input element, not the whole page. Useful for code editors embedded in web pages where every variable name appears as a misspelling.
Disable globally: chrome://settings/languages → Spell check toggle off. The simplest option when you don’t want spell check anywhere.
Most of the time, configuration scratches at the surface — fixing spell check is really about understanding which checker (Chrome’s, the website’s, Grammarly’s) is running in any given input, and configuring the right one. Once that’s clear, the actual fixes are quick.
One last note for users who write in non-English languages with diacritics (Spanish, French, German, Portuguese, etc.): Chrome’s spell check sometimes flags correctly-spelled words with accents as wrong, especially if you switched the keyboard layout but the dictionary is still set to a different language variant. Double-check that the spell check language matches not just the language but the regional variant — “English (UK)” and “English (US)” have different dictionaries; “Spanish (Spain)” and “Spanish (Mexico)” likewise. Adding both variants you encounter helps in mixed environments.
For everyday use, the practical truth is that Chrome’s spell check is fine for catching obvious typos, useless for catching anything subtle, and your real spell-checking workflow should involve site-native tools or Grammarly for content that matters. Setting expectations correctly avoids most frustration with what Chrome’s native checker can and can’t do.
To summarise the quick path through this issue: confirm spell check is enabled in chrome://settings/languages, confirm the right language is checked, test in incognito to rule out extensions, and check whether the site has its own spell checker overriding Chrome’s. Those four checks resolve the vast majority of spell check problems in under two minutes, and they correspond to the four most common causes: settings disabled, no language selected, extension conflict, and site-side override. If this sounds familiar, Chrome Dark Mode Not Working is worth a look.
