How to Fix Grammar in Gmail Without Changing the Tone of Your Email
Gmail's composer is a rich-text field, which makes it one of the better places to correct an email and one of the easier places to lose your formatting. Here is how to do both safely.
Tested October 2026 on Chrome, Edge and Firefox (Windows 11)
Free · works in Chrome, Edge and Firefox
On this page
- The short answer
- What Gmail already does, and why it is not enough
- What we tested in Gmail
- Three emails where tone is the point
- A warm follow-up
- An uncertain estimate
- A polite refusal
- The steps
- Protecting formatting in a rich-text composer
- Where this breaks down
- Before you send the next one
- Frequently asked questions
The short answer
Write the email in Gmail, click the One Shot Fix icon in your browser toolbar, read the corrected version in the popup, and click Apply. Then do the part that actually protects your tone: read the corrected email and put back anything that made it more formal, more certain or less like you than the draft you wrote.
Gmail is a good place to do this because the composer is a standard rich-text field in a browser tab. It is also a risky place, because that same composer holds formatting — bold, links, lists, quoted replies — that a text-level correction can disturb. This guide covers both halves.
What Gmail already does, and why it is not enough
Gmail has three built-in writing features. Knowing what each one covers tells you whether you need anything else.
| Feature | What it does | Where the controls are |
|---|---|---|
| Spell check | Underlines misspelled words and offers replacements on right-click | Settings → General → Spelling. Also affected by your browser's own language settings. |
| Grammar suggestions | Flags some grammatical issues with a blue underline and offers a fix | Settings → General → Grammar. Availability depends on your account type and language. |
| Smart Compose | Predicts and completes phrases as you type, shown in grey | Settings → General → Smart Compose. Also has a separate Smart Compose Personalization toggle. |
Menu paths verified October 2026 on current stable Chrome, Edge and Firefox, Windows 11. Gmail moves these settings between releases, so treat the labels as approximate.
Two of these work against tone preservation rather than for it. Smart Compose suggests phrases that are statistically common, which means generically polite — it is a plausible-phrase generator, not a voice preserver. And Gmail's grammar suggestions, like most built-in assistants, are tuned toward standard formal English, so they will offer to expand your contractions and formalise your openings.
What we tested in Gmail
Compose and reply are not the same field even though they look alike. Each was tested separately in October 2026 on current stable Chrome, Edge and Firefox under Windows 11.
| Field | Works | Notes |
|---|---|---|
| New message body | Yes | Contenteditable rich-text field. |
| Reply and Reply-all body | Yes | Same composer. The quoted original below your reply is rendered content, not part of the editable field. |
| Forward body | Yes | Same composer. |
| Subject line | Yes | A separate single-line text input. Correct it separately from the body. |
| To, Cc, Bcc | Technically yes | Do not. These are contact fields and autocorrect tokens, not prose. |
| Inline reply inside quoted text | Yes | Works, but be careful: the quoted portion is someone else's wording and should not be corrected. |
| Chat and Meet side panel messages | Yes | Standard composer in the Gmail interface. |
| Gmail mobile app | No | Not a browser. |
| Gmail in a mobile browser | Impractical | The composer is too small to work in comfortably. |
Tested October 2026 on current stable Chrome, Edge and Firefox, Windows 11.
Three emails where tone is the point
Grammar is easy. These three are the cases where a correction can quietly change what the email does.
A warm follow-up
Following up with someone you know well
Hi Dana, hope you're doing well! Just wanted to circle back on the design review from last week — i know things got busy. whenever you have a moment id love to hear what you thought about the onboarding flow. no rush at all
Hi Dana, hope you're doing well! Just wanted to circle back on the design review from last week — I know things got busy. Whenever you have a moment I'd love to hear what you thought about the onboarding flow. No rush at all
What changed. Three capitalisations and one apostrophe. The exclamation mark, the em dash, 'circle back', 'whenever you have a moment' and 'no rush at all' are all preserved. Every one of those is a warmth signal, and a tool that removed them would have turned a friendly nudge into a formal request. Note that 'circle back' is a cliché and a style checker would flag it — correctly, by its own standards, and wrongly for this email.
An uncertain estimate
Giving a client a timeline you are not sure about
Hi Tomas, we've looked at the scope and i think we could probably get the first milestone done in around 3 weeks, assuming the API access comes through on time. Its hard to be more precise than that untill we see the sandbox. I'll send a proper estimate by friday
Hi Tomas, we've looked at the scope and I think we could probably get the first milestone done in around 3 weeks, assuming the API access comes through on time. It's hard to be more precise than that until we see the sandbox. I'll send a proper estimate by Friday
What changed. Fixed the its/it's error, the spelling of 'until', the capitalised pronoun and the day. Left completely alone: 'I think', 'could probably', 'around 3 weeks', 'assuming', 'hard to be more precise'. That stack of hedges is not sloppy writing — it is the entire substance of the email. Removing any one of them converts an estimate into a commitment you did not agree to.
A polite refusal
Declining a request without damaging the relationship
Hi Amira, thanks for thinking of us for this. unfortunately we cant take on the migration work this quarter — the team is commited to the 2.4 release untill the end of november and i dont want to promise you something we cant deliver properly. Could we revisit it in january? id be happy to introduce you to someone who has capacity now
Hi Amira, thanks for thinking of us for this. Unfortunately we can't take on the migration work this quarter — the team is committed to the 2.4 release until the end of November and I don't want to promise you something we can't deliver properly. Could we revisit it in January? I'd be happy to introduce you to someone who has capacity now
What changed. Capitalisation, the spelling of 'committed' and 'until', and the apostrophes in the contractions. The refusal itself is untouched: 'we can't', 'I don't want to promise you something we can't deliver properly', and the counter-offer. A rewrite would have softened this into 'we may not have capacity', which is worse — it leaves the door open and guarantees the same conversation in three weeks.
The steps
Write the whole email first
Greeting, body, sign-off. Do not correct as you go — you will interrupt your own thinking and end up writing to the tool rather than to the person.
Check the subject line separately
The subject is its own input field. Click into it and correct it as a separate pass if it needs one. Subjects are short enough that most do not.
Click into the body and click the toolbar icon
One Shot Fix corrects the focused field, so make sure the cursor is in the body and not in the subject or a recipient field before you click.
Invocation is a toolbar click only. Gmail's own right-click menu is controlled by Gmail, so there is no extension item in it.
Read the popup against the draft
The popup shows corrected plain text with no diff highlighting. Read for the four tone risks: expanded contractions, removed hedges, formalised greetings, and deleted softeners like 'just', 'probably' or 'when you have a moment'.
Apply, then check formatting
After Apply, look at your bold text, links and lists. If any formatting was lost, this is the moment to find out — before you send.
Verify the facts
Every name, date, amount, deadline and attachment reference. This takes ten seconds and it is the check that prevents the email you have to send twice.
Protecting formatting in a rich-text composer
Gmail's body is not plain text. It is HTML, and the composer maintains that HTML while you type. Any tool that operates on the text content of that field is operating on a projection of the HTML, and writing back is where formatting can be lost.
- Plain-text emails are the safe case. If your message has no bold, no links and no lists, there is nothing to lose.
- Links are the most fragile element, because the visible text and the href are stored separately. After Apply, hover your links and confirm they still point where you set them.
- Bulleted and numbered lists depend on HTML structure rather than characters, so they can be flattened into plain lines.
- Quoted replies are the highest-risk case, because the quote is part of the same document.
- Signatures are usually outside the editable region, but confirm yours is intact before sending anything important.
The reliable habit is to correct the prose before you add the formatting. Write the email as plain text, run the correction, read it, and then apply bold, links and lists. That ordering removes the entire category of risk, and it also produces better emails, because you are not tempted to use formatting to compensate for unclear prose.
Where this breaks down
Where this breaks down
Rich-text formatting can be lost when corrected text is written back into the composer. Bold, links and lists are the elements at risk.
Workaround: Correct the prose first and add formatting afterwards. Or test the workflow on a throwaway draft before trusting it with a formatted email.
Inline replies put your words and the sender's words in one editable region, so a whole-field correction processes both.
Workaround: Write your reply above the quoted text rather than inside it.
The Gmail mobile app cannot use any browser extension. If you send most email from a phone, this workflow does not reach it.
Workaround: Use the phone keyboard's own suggestions, or draft important email on a desktop.
There is no undo after Apply, and Gmail's autosave may already have stored the corrected version by the time you notice a problem.
Workaround: Select all and copy the draft before correcting. Ten seconds of insurance.
It cannot tell you whether the email should be sent. A grammatically clean email that promises the wrong deadline is still a problem, and no correction tool can see the deadline.
Workaround: Do the fact pass separately: names, dates, amounts, commitments, attachments.
English only, and text is sent to our backend API. Client email frequently contains personal data and commercially sensitive detail.
Workaround: Do not correct emails containing personal data, credentials, pricing you have not agreed to disclose, or anything under NDA.
Before you send the next one
Frequently asked questions
Does Gmail have a built-in grammar checker?
Yes. Gmail has spell check and separate grammar suggestions, both toggled under Settings → General. Availability depends on your account type and language. The grammar suggestions lean toward standard formal English, so they will offer to expand contractions and formalise casual openings.
Will correcting my email remove the bold text and links?
It can, because the Gmail composer holds HTML rather than plain text. Test the workflow on a throwaway draft containing bold text, a link and a list before you rely on it. The safe habit is to correct the prose first and add formatting afterwards.
Does it work on replies and forwards?
Yes. Reply, Reply-all and Forward all use the same composer. Be careful with inline replies inside quoted text, because your words and the sender's words end up in the same editable region.
How do I stop my emails sounding formal after a correction?
Reject the specific changes that raise formality: expanded contractions, removed hedges such as 'I think' or 'probably', deleted softeners such as 'just' or 'when you have a moment', and formalised greetings. Fix agreement, spelling and punctuation and leave those alone.
Can I correct only part of a long email?
No. Correction applies to the whole focused field. For a long email, draft it in a scratch tab and correct it section by section before pasting it into Gmail.
Can I undo after applying a correction?
Not reliably. There is no undo in the extension, and Gmail's continuous draft autosave may have already captured the corrected version. Copy the draft to your clipboard before you Apply.
Related guides
Platform guides · 11 min read
How to Check Grammar in Slack on Chrome: Browser vs Desktop Options
Slack's browser version is a normal web page, so its composer can be corrected. The desktop app is not, and that single distinction explains most of the confusion in this search.
Correction basics · 7 min read
What to Do When Grammarly Changes Your Tone
A careful look at tone-preserving correction for people who do not want every sentence rewritten.
Correction basics · 7 min read
How to Fix Grammar Without Changing Meaning
A practical guide to cleaning up grammar while keeping the original idea intact.
Written by Raheel Ashraf, builds and maintains one shot fix. Tested October 2026 on Chrome, Edge and Firefox (Windows 11). Last updated 7 October 2026.
Write naturally. Send clean.
Correct prompts, emails and messages in the browser field you are already typing in. Free to install.