Google Docs voice typing not working

Voice typing broke. Here is the 30-second triage.

Before you change a single setting, run this. It catches most cases faster than any deep fix.

If the triage did not fix it, work through the sections below in order. They are sorted by how often each one is the actual culprit.

Why Google Docs voice typing stops working

The microphone box has exactly one job: turn red when something is wrong, stay grey when it is fine. It will not tell you which of the four links in the chain broke. That is the annoying part.

Here is the chain. The browser has to support speech recognition. The OS has to route a working, un-muted microphone to that browser. The connection has to stay up long enough for Google's servers to send text back. And the Docs tab has to stay the active, focused tab. Voice typing is a relay race between four runners, and if any of them drops the baton, the box goes red and you lose the sentence.

Most guides online tell you to clear your cache first. I would not. Cache clearing fixes maybe one case in ten and logs you out of everything else. Start with the browser and the microphone, where eight of ten failures live.

You are in Firefox. Switch to Chrome, Edge, or Safari.

This is the single most common cause, and it is the one the rest of the internet keeps getting wrong. Google's own support page says voice typing works with the latest versions of Chrome, Edge, and Safari. Half the troubleshooting articles out there still say "Chrome only." That was never right, and it is wrong about Safari. Safari works fine.

What does not work is Firefox. Firefox does not support the speech-recognition piece that voice typing depends on, so the Tools then Voice typing option either does nothing or does not appear. If the menu item is greyed out or missing entirely, your browser is the reason ninety percent of the time.

The fix is the least technical one in this whole article: open the same document in Chrome, Edge, or Safari. One more thing: this is a desktop-web feature. On a phone or tablet you are using a different dictation path, so do not expect the Tools menu to look the same.

The browser blocked your mic. Fix it in site settings.

Your browser keeps its own list of which sites may use your microphone, separate from anything Google controls. If you clicked "Block" the first time docs.google.com asked, or your browser never asked, the box turns red the instant you click the microphone.

Look at the left end of the address bar. If there is a microphone icon with a small slash through it, the browser is blocking the mic for this site. Click it, choose "Always allow," and reload the tab. In Chrome you can also go straight to the site-permissions panel and flip the microphone toggle for docs.google.com to Allow.

This is standard browser behaviour, not a Google-documented step. Google's own page points you at the operating system, not the browser, for microphone settings. But the browser-level permission is the one that bites people most, so check it first. Then reload, click the microphone, and speak. If the box stays grey and the words land, you are done.

Your OS is sending the wrong microphone, or muting it.

The browser asks the OS for "the microphone," and the OS decides which one that is. If you have a webcam mic, a headset, and a laptop mic, the OS picks a default, and not always the one you are talking into.

Google's support page is direct about this: microphone settings live in System Settings on a Mac, or the Control Panel on a PC. Open your sound input settings and confirm three things. The right device is the default input. The level is not at zero. The mic is not muted at the hardware level, where some headsets hide a physical mute switch that is easy to knock (the inline button on the cable is the usual suspect — half a knee-bump away from silence).

While you are there, say a few words and watch the input meter move. If the meter is flat, no software fix here will help. The OS is not getting any audio, and Google Docs sits downstream of that. A flat meter usually means the wrong device, a muted device, or a $20 USB mic that came unplugged. Fix the hardware, then come back to the document.

Online Speech Recognition in Windows, and other long shots.

A lot of Windows guides tell you to turn on "Online speech recognition" under Settings, Privacy and security, Speech. I will be honest: this one is unproven for browser voice typing. Microsoft's documented scope for that toggle is its own cloud speech features (Cortana, Windows dictation, certain Store apps), not the browser's Web Speech API, which is what Google Docs uses. Some users report toggling it helps. I have flipped settings like this one for half an hour before realising the actual problem was a muted mic the whole time — I have a master's degree. Check it last, and do not expect much.

Two more long shots worth a quick look. Browser extensions can grab the microphone or block scripts on the page; try the same document in an incognito window with extensions off, and if voice typing suddenly works, an extension was the culprit. And the document language matters for one specific thing, more on that two sections down.

It stops mid-session, or the commands ignore you.

Two failures look like bugs but are not. First: voice typing stops when you click away from the Google Docs tab. Open a new tab to look something up, switch to email, click into another window, and the microphone box quietly stops listening.

It also stops after a stretch of silence — pause to think for a while and the session can time out on its own. Both are observed Web Speech API behaviour, not settings you can change, and together they are the most common "it just stopped" complaint.

The workaround is dull but reliable: keep the Docs tab in front, watch the box, and click it again when it goes grey-and-idle. If that babysitting sounds like it defeats the point of hands-free dictation — yes. That is the part to remember.

Second: dictation works, your words appear, but saying "select paragraph" or "bold" or "new line" as a command does nothing. That is by design. Google Docs voice editing and formatting commands are available only in English, and both your account language and your document language have to be set to English for them to fire. If your account is in French or your document is Polish, the commands silently do nothing while plain dictation keeps working in that language. Punctuation is the exception — spoken "period," "comma," "question mark," "new paragraph" works across many languages. So if "period" gives you a full stop but "bold" does nothing, your language settings are the reason, not your microphone. Switch both to English and the commands come back.

And if that kind of babysitting is the dealbreaker, the field of alternatives to Google voice typing is laid out in one guide.

Skip the browser: dictate straight into any app

Here is the opinion I will spend my one allowance on. A dictation feature that lives on someone else's server stops the moment that server cannot hear you: a dropped connection, a blurred tab, a browser Google did not bless. Google Docs voice typing requires a live internet connection because the audio is processed server-side. Every failure mode in this article traces back to that one design choice: the feature is a guest in your browser, and guests have a lot of ways to be turned away.

Whisper by Remskill takes the opposite approach. It is a system-wide desktop app, not a browser extension. You press a hotkey (Ctrl+Space on Windows, or hold Command+Option together on a Mac), speak, release either key, and the transcription lands at your cursor in whatever window is in front. That includes the Google Docs tab. It also includes your email, a chat box, a code comment, a spreadsheet cell, and the apps where Google's voice typing was never an option to begin with.

The local pipeline runs fully on your machine and works offline. No tab to keep in focus, no server to stay connected to, no supported-browser list. You pick the engine: NVIDIA Parakeet (~600 MB, English plus 24 European languages, 5 to 10 times faster than Whisper on a CPU), or a Whisper model covering 99 languages on the multilingual variants. There is a Cloud mode for OpenAI's latest models too, but the whole local side is free for any signed-in account.

Voice typing without the browser tab

In practice, it stops mattering where you are typing. Last week I answered a teacher's email, fixed a grocery list, and dropped a line into a document: three apps, one hotkey, no Tools menu in sight. None of those windows had to be a supported browser, and none had to stay in focus while I clicked around. The text just landed at the cursor. Take dictation out of the browser, and the browser's failure modes stop being your problem.

What the full app looks like

If you would rather see it than read about it, the app embed above is the real desktop frontend. You can click through the settings the same way you would after installing it: pick a transcription engine, set your hotkey, choose a language. Windows 10 and 11 and Apple Silicon Macs both ship today. The thing I would point at first is the hotkey setting: it is fully customizable, which matters because one of the few things more annoying than voice typing not working is a hotkey that fights your music software at 2am. You can see the full walkthrough in our guide to how Whisper works, and the platform-specific setups for voice to text on Windows and voice to text on Mac.

When Google Docs voice typing isn't the right tool anymore

Sometimes the honest answer is that Google's tool is fine. If you only dictate short bursts into a Google Doc, in Chrome, on a stable connection, voice typing is free and built in and works. No reason to install something to replace a thing already doing its job. Same for meetings: if you need multi-speaker transcription with a summary afterward, that is Otter's category, a paid monthly subscription, and a dictation tool is the wrong purchase entirely.

You outgrow Google Docs voice typing when the browser becomes the bottleneck — dictating into five apps a day, an unreliable connection, the tab-focus babysitting costing you sentences, or wanting the audio to never leave your laptop. That is when a system-wide, offline tool earns its place. Until then, fix the browser and the microphone and carry on.

If you want this everywhere — not just inside one browser tab — dictating straight into any app sidesteps the whole list above. And if the same trouble follows you outside Docs, the Windows and Mac fix guides cover the microphone and permission side in more depth.

And if it's Microsoft Word giving you grief instead, why Word's Dictate button is missing walks through the subscription requirement and the offline workaround.

I still keep voice typing on for quick notes in a doc, for what it is worth. But the day I stopped relying on a tab staying in focus was the day dictation finally felt like it was working for me instead of the other way around. My daughter would say that means it was never the computer's fault. She would be mostly right.