Spell Check Not Working in ChatGPT on Chrome? What to Check First

The short answer

If Chrome is not underlining misspelled words in the ChatGPT prompt box, check these four things in order: (1) is 'Check for spelling errors when you type text on pages' turned on in Chrome's language settings, (2) is chatgpt.com in the list of sites not allowed to check spelling, (3) does a normal text field like Gmail compose show squiggles right now, and (4) does disabling your other extensions bring them back.

Step 3 is the one that actually tells you something. If Gmail compose underlines 'ths' and ChatGPT does not, Chrome is fine and the ChatGPT field is the variable. If neither underlines it, your browser setting is off and no amount of ChatGPT-side troubleshooting will help.

Why the prompt box behaves differently from a normal text field

ChatGPT's composer is not a simple textarea. Like most modern chat interfaces, it is a contenteditable element — a div that accepts typed text so the app can render mentions, formatting and multi-line input. Chrome's spell checker does support contenteditable elements, but support there is less consistent than in a plain input, and a site can turn it off for a specific element.

The mechanism is a single HTML attribute. A site can put spellcheck set to false on an element, and Chrome will not underline anything typed into it. Whether ChatGPT's composer carries that attribute has changed over time and may differ by account type, app version and rollout, so you should check your own browser rather than trust anyone's claim about it — including ours.

How to check it yourself in 30 seconds

1. 1

   Open chatgpt.com and click into the prompt box

   Type a few characters so the element is live in the DOM.

2. 2

   Right-click inside the box and choose Inspect

   DevTools opens with the element highlighted. If right-click does not offer Inspect, press F12 or Ctrl+Shift+I and use the arrow icon in the top-left of DevTools to pick the element.

3. 3

   Look at the highlighted element's attributes

   In the Elements panel, read the tag Chrome selected. You are looking for an attribute named spellcheck.

4. 4

   Interpret what you see

   If you see spellcheck set to false on that element or on a parent, the site has disabled spell check and Chrome cannot override it from settings. If you do not see the attribute at all, the field is not opting out and the cause is on the Chrome side.

   Attributes can sit on a parent element rather than the one you clicked. If you see nothing, click one or two levels up in the Elements tree and look again.

This is worth doing because it ends the guessing. If the attribute is there, the only fixes are browser-side workarounds or a correction tool. If it is not there, keep reading — the cause is in your settings.

The Chrome settings checks, in order

1. 1

   Turn on page spell check

   Go to chrome://settings/languages in the address bar. Under Spell check, make sure 'Check for spelling errors when you type text on pages' is switched on. If it was off, this is your answer — reload ChatGPT and test again.

   Chrome offers Basic and Enhanced spell check. Enhanced sends text you type to Google for better suggestions. If that is a concern for prompt content, Basic is the safer choice.

2. 2

   Check the language list

   On the same page, look at the list of languages. At least one must be enabled for spell check, and the language you are typing in must be among them. If you type in English but only another language is ticked, English words will not be checked.

3. 3

   Check the site exclusion list

   Still on chrome://settings/languages, scroll to the section listing sites that are not allowed to check spelling. If chatgpt.com appears there, remove it. Entries land in this list when someone clicks 'Never check spelling on this site' in the right-click menu, which is easy to do by accident.

4. 4

   Use the right-click menu on the field itself

   Right-click inside the ChatGPT prompt box. Look for a Spell check submenu. It should offer the enabled languages and an option to check spelling. If the submenu is missing entirely, the field has opted out via the attribute described above.

5. 5

   Reload the tab

   Spell-check setting changes do not always apply to an already-open single-page app. Reload chatgpt.com after any change before concluding that nothing worked.

6. 6

   Check the Chrome profile

   If you use more than one Chrome profile, settings are per-profile. The profile you configured may not be the one ChatGPT is open in. Look at the avatar in the top-right of the browser window.

Isolate the cause with a known-good field

This is the fastest diagnostic on the page and it takes about a minute.

Use Gmail compose because it is a plain contenteditable field with spell check enabled by the site, it is present for anyone with a Google account, and it is a close structural match to ChatGPT's composer. If Gmail works and ChatGPT does not, you have eliminated the browser as the cause.

Extension conflicts

Writing extensions are the most common non-obvious cause. Several popular grammar and AI assistants inject their own editor into text fields, and some set the spellcheck attribute to false so that Chrome's underlines do not compete with their own. The result is that installing a grammar tool removes your spell check.

1. Open chrome://extensions and turn off every extension except the one you are testing. Use the toggles, do not remove anything yet.
2. Reload chatgpt.com and type 'ths is a tst'. Note whether squiggles appear.
3. Re-enable extensions one at a time, reloading ChatGPT after each, until the squiggles disappear. The last one you enabled is the cause.
4. Decide whether you want that extension. Some have a setting to leave Chrome's native spell check alone; others do not.

The same checks on Edge and Firefox

One Shot Fix works in Chrome, Edge and Firefox, and so does this problem. The settings live in different places.

Firefox is the one that surprises people. If you have never installed an English dictionary in Firefox, spell check will silently do nothing on every site. Right-click in any textarea, choose Check Spelling, and confirm a dictionary is selected in the Languages submenu.

What spell check cannot catch in a prompt

Suppose you fix all of the above and squiggles appear. That is progress, but it is worth being clear about what you have actually gained. Spell check finds words that are not in its dictionary. Most prompt problems are not misspelled words.

A misspelled word in a prompt is usually survivable; the model infers what you meant. An ambiguous or ungrammatical instruction is the thing that produces the wrong output. That is the gap a correction pass fills and spell check does not.

A correction workflow that works regardless

If you would rather not depend on browser spell check at all, this workflow works everywhere and takes about the same time.

1. Write the prompt in your own words without self-editing. Get the task, the context and the constraints down.
2. Read it once for the constraint. Can a reader tell what must not change? If not, add it explicitly.
3. Run a correction pass. With One Shot Fix, click the toolbar icon, read the corrected text in the popup, and click Apply.
4. Compare the corrected prompt against your original for meaning. Check that 'might' did not become 'will', that no new instruction appeared, and that your technical terms survived.
5. Send it.

Step 4 is not optional for prompts. A prompt is an instruction, and instructions are where a well-meaning correction can silently change what you asked for.

Where this breaks down

Frequently asked questions