Why does voice typing type the word 'period' instead of adding a period?

Voice commands, including spoken punctuation, are available only in English in Google Docs, and both your account language and the document language must be set to English. If either is not English, the command word is transcribed literally instead of being applied. A dictation tool that adds punctuation automatically avoids spoken commands entirely.

Google Docs Voice Typing Not Working? Why It Stops and How to Fix It (2026)

Q: Why is Google Docs voice typing not working?

The most common cause is a blocked microphone permission for docs.google.com in your browser or operating system. Other frequent causes are using an unsupported browser (Google supports only the latest Chrome, Edge, and Safari, not Firefox), the wrong microphone being selected or muted, no internet connection because the recognition is server-based by default, or a language setting that does not match what you are speaking. Fix the permission first, then work down the list.

Q: Does Google Docs voice typing work in Firefox?

No. Google's support page lists voice typing as working only in the latest Chrome, Edge, and Safari, and Firefox is not on it. The technical reason is that release Firefox does not expose the Web Speech API speech recognition interface that the feature needs, which Mozilla's own bug tracker records as an open issue. To dictate into Docs on Firefox, use a browser dictation extension that does not rely on that feature.

Q: How do I fix a blocked microphone for Google Docs in Chrome?

In Chrome, go to Settings, then Privacy and security, then Site settings, then Microphone. Under the not-allowed list, select docs.google.com and change the microphone permission to Allow. Then confirm your operating system lets the browser use the microphone: on Windows 11 in Settings, Privacy and security, Microphone, and on macOS in System Settings, Privacy and Security, Microphone.

Q: Why does Google Docs voice typing keep stopping?

Voice typing listens only while the microphone box is active. If you click into another window or tab, or stop speaking for a while, it can stop listening, and you click the microphone again to resume. It also stops if your connection drops or the speech service is blocked, because the recognition is server-based by default and needs a live connection.

Q: Can I voice type in Google Docs without the built-in feature?

Yes. A browser dictation extension types into the Google Docs editor, and into any other web text field, in both Chrome and Firefox, with automatic punctuation and your exact words. Because it does not depend on the Docs voice typing feature, it also works where that feature does not, such as Firefox.

By the Voxtyper team·Updated June 2026·9 min read

A document editor with a dictated paragraph that has commas, periods, and capital letters added automatically, showing dictation working in a Google Docs style page

TLDR

Fix the microphone permission first. The most common cause is docs.google.com being blocked from the mic - reset it in Chrome's Site settings > Microphone (Chrome Help), then check your OS mic privacy on Windows 11 and macOS.
It does not work in Firefox. Google supports voice typing only in the latest Chrome, Edge, and Safari (Google); release Firefox does not expose the speech recognition the feature needs (Mozilla bug 1456885).
It needs a live connection. Browser speech recognition is server-based by default, so it "won't work offline" (MDN).
Spoken punctuation is English-only. Voice commands need both your account and document language set to English, or the command word is typed literally (Google).
The durable fix is a dictation extension that types into Docs and any web field, with automatic punctuation, in Chrome and Firefox - including where Docs voice typing cannot run.

When Google Docs voice typing stops working, the official advice ("move to a quiet room, plug in a microphone, restart") rarely touches the real problem, which is almost always in the browser, not the room. Here are the actual in-browser causes and how to fix each one.

Voice typing in Docs is a real, free feature: open Tools, then Voice typing, and a microphone box appears that you click to start (Google). When it fails, it is usually one of a handful of specific things. Work down this list in order.

Fix 1: your microphone permission is blocked

This is the cause for most "not working" reports. Voice typing needs the browser to have microphone access for the Docs site, and one earlier "Block" disables it until you reverse it:

Reset the site permission in Chrome. Go to Settings > Privacy and security > Site settings > Microphone; under the not-allowed list, select docs.google.com and change it to Allow (Chrome Help).
Then unblock the mic at the OS level. On Windows 11, open Settings > Privacy & security > Microphone and turn on Microphone access, "Let apps access your microphone", and "Let desktop apps access your microphone" (Microsoft).
On a Mac, open System Settings > Privacy & Security > Microphone and turn access on for your browser (Apple).

If the mic was the problem, voice typing starts transcribing the moment you click the box again. If not, keep going.

Fix 2: the wrong microphone is selected, muted, or busy

Google's own checklist is hardware-focused, and it is worth a quick pass before the deeper causes:

Confirm the mic works at all. Google says "your computer microphone needs to be on and working," and to check it is plugged in and not being used by another application (a video call holding the mic is a classic culprit), then restart if needed (Google).
Pick the right input device on Windows. In Sound settings > Input, select the microphone, open its properties, and use Start test to confirm it hears you (Microsoft); if nothing registers, Microsoft's mic troubleshooter walks the same access and device checks (Microsoft).
Pick the right input device on Mac. In System Settings > Sound > Input, choose the device you are actually speaking into, since a Mac can list several (Apple).

Voxtyper for Chrome Voxtyper for Firefox

Fix 3: you are on Firefox (or another unsupported browser)

If voice typing is greyed out or simply does nothing, the browser may be the reason, and this one is not a setting you can flip:

Only three browsers are supported. Google states the feature "works with the latest versions of: Chrome, Edge, Safari" - Firefox is not on the list (Google).
Why Firefox cannot run it. Voice typing relies on the browser's built-in Web Speech API speech recognition (MDN), and release Firefox does not expose that recognition interface to users by default. Mozilla's own bug tracker records the Docs case as an open issue, "Not able to use Voice for Google Docs Integration due to missing SpeechRecognition support" (Mozilla bug 1456885), and MDN's compatibility data lists the SpeechRecognition interface as not available in Firefox.
The fix is a different tool, not a different setting. A dictation extension that does its own transcription, rather than calling the Docs feature, types into the Docs editor on Firefox just as it does on Chrome.

Fix 4: you are offline or the speech service is blocked

Browser dictation is not local by default, so anything that cuts the connection to the recognition service breaks it:

It needs the internet. As MDN puts it, in Chrome "using Speech Recognition on a web page involves a server-based recognition engine. Your audio is sent to a web service for recognition processing, so it won't work offline" (MDN; MDN guide).
Check the obvious connection issues. A dropped network, a VPN or firewall blocking the speech service, or a corporate proxy can all stop transcription even when the page itself loads.
This also explains "it just stops." Recognition starts listening when you click the mic (MDN), and a flaky connection mid-session ends it, so you click the box to start again.

Fix 5: spoken punctuation is being typed as words (language)

If "period" and "comma" appear as text instead of marks, the cause is language settings, not your microphone:

Voice commands are English-only. Google states plainly: "Voice commands are available only in English. The account language and document language must both be English" (Google). Transcription itself works in many languages, but the commands do not.
Set both languages. Change your account language to English (Google account language) and set the document's language to match, so the spoken marks are applied instead of typed.
Recognition follows a language too. The underlying speech recognition has a language setting that decides how your speech is interpreted (MDN); a mismatch between what you speak and what is set yields garbled results.
Or skip commands entirely. A dictation tool with automatic punctuation adds commas, periods, and capitals from context, so there are no command words to memorize and no English-only requirement to satisfy.

Why it "keeps stopping" mid-sentence

A recurring complaint is that voice typing quits on its own. A few things make that happen, and most are by design:

It listens only while the box is active. Voice typing runs while the microphone box is open and focused; if you click into another window or tab, it can stop, and you click the mic to resume.
Long pauses end the session. After a stretch of silence the recognition can close, which is why a slow, thinking-heavy draft feels like it keeps dropping out.
Connection blips cut it off. Because the recognition is server-based by default (MDN), a brief network drop ends the session even if the page stays open.

Voice typing's exact focus and silence behavior is not spelled out in Google's documentation; the points above reflect how the browser speech feature behaves in practice, not a published limit.

The durable fix: dictation that does not depend on the Docs feature

Most of the failures above come from voice typing leaning on the browser's own speech recognition: it is Chrome-family only, server-only, English-only for commands, and easy to block. A browser dictation extension does its own transcription, which sidesteps all of that:

It works where Docs voice typing cannot. Because it does not call the unsupported feature, it dictates into the Docs editor on Firefox as well as Chrome (Mozilla bug 1456885).
It works in every web field, not just Docs. The same setup types into Gmail, Slack, Notion, and any text field, each at the live cursor.
Automatic punctuation, no command words. Commas, periods, and capitals are added from context (here is the full automatic punctuation guide), so the English-only command rule never applies.
Your exact words. Punctuation and capitalization are added, but the text is never rewritten, so a draft still sounds like you.

Our pick is Voxtyper, which does this in Chrome and Firefox. It is free to start: 20 minutes a month without an account, or 60 minutes signed in, no card. If you need more, there is a plan for unlimited usage.

For the record: we make Voxtyper, so treat this as the maker's view. Google Docs voice typing is real and free, and the fixes above are the genuine ones; the point here is that an independent dictation tool removes the browser, connection, and language constraints the built-in feature carries.

Dictation is also an accessibility tool

For many people, getting dictation working in Docs is not about convenience, it is about access:

Some people rely on it. The W3C lists speech recognition as relied on by "people with physical disabilities who cannot use the keyboard or mouse" and people with repetitive stress injuries (RSI) who need to limit keyboard use (W3C Web Accessibility Initiative).
A broken feature is a real barrier. When the built-in tool quietly fails, the people who most need it are the ones stuck, which is why a dictation method that works across browsers and fields matters.

This is general information, not medical advice. Dictation can reduce keyboard strain; it is not a treatment.

Frequently asked questions

Why is Google Docs voice typing not working?

Most often a blocked microphone permission for docs.google.com (Chrome Help). Other causes: an unsupported browser like Firefox (Google), the wrong or busy microphone, no connection, or a non-English language for commands. Fix the permission first.

Does Google Docs voice typing work in Firefox?

No. Google supports only the latest Chrome, Edge, and Safari (Google), and release Firefox does not expose the speech recognition the feature needs, an open Mozilla issue (Mozilla bug 1456885). Use a dictation extension that works in Firefox.

How do I fix a blocked microphone for Google Docs in Chrome?

Chrome Settings > Privacy and security > Site settings > Microphone; set docs.google.com to Allow (Chrome Help). Then confirm the OS allows it: Windows 11 and macOS.

Why does voice typing type "period" instead of adding a period?

Voice commands are English-only, and both account and document language must be English, or the command word is typed literally (Google). A tool with automatic punctuation avoids spoken commands.

Why does Google Docs voice typing keep stopping?

It listens only while the mic box is active, so clicking away, a long pause, or a connection blip ends it, and you click the mic to resume. The recognition is server-based by default and needs a live connection (MDN).

Can I voice type in Google Docs without the built-in feature?

Yes. A browser dictation extension types into the Docs editor and any other field, in Chrome and Firefox, with automatic punctuation, so it works even where Docs voice typing does not.

Conclusion

When Google Docs voice typing is not working, the fix is rarely "a quieter room." It is almost always the browser: a blocked microphone permission (Chrome Help), an unsupported browser like Firefox (Google; Mozilla bug 1456885), a dropped connection to the server-based recognition (MDN), or an English-only command setting. Work the list and most cases clear. And if you would rather not fight the feature's limits at all, a dictation extension that does its own transcription works in Chrome and Firefox, in any field, with automatic punctuation and your exact words. Voxtyper is our pick, free to start.

Sources

"Type with your voice" (enable via Tools > Voice typing; supported browsers Chrome/Edge/Safari; English-only voice commands; microphone troubleshooting), Google Docs Editors Help - support.google.com
"Use your camera & microphone" (Site settings > Microphone; reset a blocked site to Allow), Google Chrome Help - support.google.com
"Change the language of your Google Account," Google Account Help - support.google.com
"Not able to use Voice for Google Docs Integration due to missing SpeechRecognition support" (open bug), Mozilla Bugzilla 1456885 - bugzilla.mozilla.org
"Web Speech API" (the API behind browser voice typing; two parts, SpeechRecognition + SpeechSynthesis), MDN - developer.mozilla.org
"SpeechRecognition" (the recognition controller interface; server-based, "won't work offline"; Firefox not supported), MDN - developer.mozilla.org
"Using the Web Speech API" (server-based recognition by default; offline note; on-device alternative), MDN - developer.mozilla.org
"SpeechRecognition: lang property" (sets the language of recognition), MDN - developer.mozilla.org
"SpeechRecognition: start() method" (starts listening to incoming audio), MDN - developer.mozilla.org
"Turn on app permissions for your microphone in Windows" (Let apps / Let desktop apps access your microphone), Microsoft - support.microsoft.com
"How to set up and test microphones in Windows" (Sound > Input; Start test), Microsoft - support.microsoft.com
"Fix microphone problems" (microphone access; choose the input device), Microsoft - support.microsoft.com
"Control access to the microphone on Mac" (System Settings > Privacy & Security > Microphone), Apple - support.apple.com
"Change the sound input settings on Mac" (System Settings > Sound > Input; choose the device), Apple - support.apple.com
"Speech Recognition" (who relies on it: cannot use keyboard/mouse, RSI), W3C Web Accessibility Initiative - w3.org

Voxtyper is free to use in Chrome and Firefox, dictating into Google Docs and every other web text field with punctuation and capitalization handled for you, even where the built-in voice typing cannot run.

Voxtyper for Chrome Voxtyper for Firefox