How to Fix Punctuation and Grammar After Voice Typing in Chrome

The short answer

Dictate into a normal browser text field, finish speaking and let the transcription settle, then click into the field and click the One Shot Fix toolbar icon. Read the corrected text in the popup, and read the names, numbers and technical terms separately — those are the parts a grammar pass cannot verify. Apply only when both reads are done.

One Shot Fix does not record audio, does not transcribe speech and is not a dictation tool. It works on text that is already in the field. The dictation comes from Windows voice typing, Google Docs voice typing, your operating system's keyboard, or a dictation extension — and the cleanup afterwards is what this article is about.

Getting dictated text into a browser field

There are four routes, and they differ in one respect that matters a lot for cleanup: whether punctuation is added automatically.

For the rest of this article, assume the text has arrived in a normal browser field — a textarea, an input, or a contenteditable composer such as Gmail's. All three work with a correction pass.

A dictated draft, and what is wrong with it

The draft below is a simulation, written to reproduce the error patterns dictation actually produces, rather than a transcript captured with a microphone. We are labelling it as simulated deliberately: a fabricated transcript presented as real would be exactly the kind of untestable evidence this site avoids. The error categories in it are the ones you will see from Windows voice typing and from Google Docs voice typing.

so um the deploy went out on Tuesday night and it mostly worked
which is more than I can say for the last one the migration took
about 40 minutes which was longer than we thought but the roll back
didn't trigger so I think were fine Tomas wants to know if the
caching layer is actually helping or if its just making the logs
harder to read and honestly I don't no the answer to that yet we
should probably run a test with it off for an hour and compare the
numbers period also the client asked about the 15th of November
deadline and I told them it was fine but I didn't check with Anish
first so if that's wrong we need to say so soon because there's
three of them waiting on that answer

What the cleanup produces

The cleanup workflow

1. 1

   Turn on auto-punctuation before you dictate

   Windows voice typing has the toggle in its settings bar. Google Docs voice typing has it under its own settings. This one change removes most of the sentence-boundary and comma errors, and it costs nothing.

2. 2

   Dictate into a scratch field, not the destination

   A blank textarea you control. Raw dictation is messy enough that you want a place to work where nothing is watching and nothing is saved.

3. 3

   Wait for the transcription to finish

   Dictation engines write in chunks with a short delay. Correcting mid-write means the field changes underneath the correction.

4. 4

   Copy the raw text to a second scratch note

   There is no undo after Apply, and a dictated draft is expensive to reproduce. This is your fallback.

5. 5

   Click into the field and click the One Shot Fix toolbar icon

   Pin the icon first if it is not visible — the puzzle-piece menu in Chrome and Edge, Customize Toolbar in Firefox. The extension is invoked by a toolbar click only.

6. 6

   Read the popup for grammar, then read it again for facts

   Two separate passes. First: are the sentences now bounded correctly and the commas in the right places? Second: every name, number, date and technical term — is that what you actually said?

   The second pass is the one people skip, and it is the one that matters. Dictation errors are semantically valid words, so nothing looks wrong.

7. 7

   Delete filler and literal punctuation by hand

   'um', 'uh', 'like', and any spoken 'period' or 'comma' that survived. A corrector should not be deleting your words, so this is yours to do.

8. 8

   Apply, then paste into the destination

   If you dictated into a scratch field, copy the corrected text across. Check the destination field's character limit before you paste — see the limitations below.

What no grammar tool can fix

This is the section that determines whether voice typing saves you time or costs you a correction. Dictation errors are not like typing errors. A typing error usually produces something that is not a word — 'teh', 'recieved' — and those are trivially detectable. A dictation error almost always produces a real word in a plausible position, because the engine picks the most likely token given the audio.

The practical rule that follows from this table: after a dictation pass, read for content first and grammar second. If you only have time for one read, make it the content read. A run-on sentence is embarrassing. A dropped negation in a message to a client is a commitment you did not make.

Where this breaks down

Try it on your next dictated draft

Frequently asked questions