How to Correct Selected Text in Chrome Without Copying It Into Another App

The short answer

Chrome has three levels of correction available, and they are not interchangeable. Word-level correction comes from the browser's own right-click spelling suggestions and only works on words Chrome has already underlined. Field-level correction comes from an extension and rewrites the whole input. True sentence-level correction — select one sentence of a paragraph and fix only that — is not something Chrome offers natively, and One Shot Fix does not do it either.

If your actual goal is 'fix this one bad sentence in a long draft without opening another app', there is a clean method that stays on the page. It is described below. If your goal is 'correct what I am about to send', field-level correction is faster and you should skip the selection step entirely.

Three levels of correction, and what each is good for

Most of the time the field level is what you want. The reason people ask for sentence-level correction is that they have a long document open and they do not want the rest of it touched. That is a reasonable concern, and the answer is usually that field-level correction on a well-written document changes very little — but you should still read the result before you apply it.

Word-level correction with Chrome's built-in tools

This is genuinely selection-aware, and it is already installed. It is also narrower than people expect.

1. 1

   Make sure page spell check is on

   Open chrome://settings/languages and enable 'Check for spelling errors when you type text on pages'. On Edge the equivalent is edge://settings/languages. On Firefox, right-click in the field and choose Check Spelling, and confirm an English dictionary is installed.

2. 2

   Right-click the underlined word

   Chrome shows a list of suggested replacements at the top of the context menu. Click one to replace just that word.

3. 3

   Use the submenu for anything not underlined

   If the word you selected is not underlined, Chrome will not offer spelling suggestions for it. There is no way to force a suggestion for a word Chrome considers correctly spelled.

The in-page method for one sentence

This is the answer to the title of this article. You can correct a single sentence of a long draft without copying it into another application, because almost every page has more than one text field on it.

1. 1

   Select the sentence you want corrected

   Double-click a word and drag, or click at the start and shift-click at the end. Select the whole sentence including its final punctuation.

2. 2

   Cut it

   Ctrl+X. The sentence leaves the draft, so make a mental note of where the gap is. If the draft is important, copy the full text somewhere first — there is no undo once you start moving pieces around.

3. 3

   Find another empty text field on the same page

   A search box, a comment field, a reply composer, a filter input. Any editable field on the page you are already on will do. If the page genuinely has only one field, open a new browser tab and use its address bar as a scratch space, or any site with a search box.

   Stay on the same page where you can. Switching tabs risks losing focus on the original field, and some single-page apps clear a draft when the composer loses focus.

4. 4

   Paste and correct

   Ctrl+V into the scratch field, then click the One Shot Fix toolbar icon. The extension corrects the focused field, which is now just your one sentence. Read the popup and click Apply.

5. 5

   Copy the corrected sentence

   Select all inside the scratch field with Ctrl+A and copy with Ctrl+C.

6. 6

   Go back and paste it into the gap

   Click into the original field at the position where you cut, then Ctrl+V. Clear the scratch field so you do not accidentally submit it.

A worked example

Suppose you are writing a long comment on a product page. Two paragraphs are fine. The third has a problem.

The 3rd option seems better because it dont require a migration and the team have already used it in production twice

Notice what did not happen. The two good paragraphs were never sent anywhere, which is the whole point of isolating a sentence. If you had corrected the entire comment field instead, they would have been processed too — and the corrected output would have been longer and harder to review.

Toolbar, right-click and keyboard shortcut, compared honestly

A lot of extension marketing leads with keyboard shortcuts. Here is what each invocation route actually gives you, including what One Shot Fix does not have.

If a keyboard shortcut is essential to your workflow, that is a legitimate reason to pick a different extension. The honest trade-off with a toolbar click is one mouse movement per correction, in exchange for never colliding with a web app's own key bindings.

Fields where none of this works

Selection-level correction assumes the text is editable. Plenty of text on a web page is not.

• Rendered page text — articles, comments you did not write, product descriptions. There is no field to focus, so no correction tool can write back to it.
• PDFs opened in the browser. Chrome's PDF viewer is not a text field.
• Text inside images, canvas elements and video captions.
• Read-only inputs, which some forms use for calculated or prefilled values.
• Custom editor components that do not expose a real input, textarea or contenteditable element. These are rare but they exist, and nothing in the browser can reach them.
• Native desktop applications. Slack Desktop, Discord Desktop, WhatsApp Desktop, Microsoft Word and your IDE are not browser tabs.

For rendered text, the only route is to copy it into an editable field first — at which point you are back to the standard workflow.

Where this breaks down

What to read next

Frequently asked questions