Short answer: Google Docs voice typing only works in Chrome and requires microphone permission for docs.google.com. The most common fixes are: switch to Chrome, allow mic access at the site and OS level, disable conflicting extensions, set the document language to a supported one, and restart the browser.
You click Tools, then Voice typing, the microphone icon appears, you click it, and... nothing. Or it lights up red and refuses to listen. Or it transcribes one sentence and then silently dies. Google Docs voice typing is a useful tool when it works, but when it breaks it gives almost no feedback about why. Below are the nine real reasons it stops working, in roughly the order you should check them.
1. You are not using Google Chrome
This is the single most common cause and Google has never made it obvious. Voice typing in Google Docs relies on Chrome's built-in Web Speech API and is not officially supported in Safari, Firefox, Edge, Brave, Arc, or any other browser. Sometimes Edge appears to load the feature because it shares the Chromium engine, but the speech back end is different and dictation will fail silently or after a few words.
If you are on Safari, Firefox, or any non-Chrome browser, the Tools menu may not even show "Voice typing" as an option, or it may show but refuse to start. The fix is simply to open the same document in Chrome. There is no workaround — the feature is bound to Chrome's speech engine.
2. Microphone permission is blocked for docs.google.com
Even in Chrome, voice typing only works if the site has been granted microphone permission. Chrome remembers your permission decisions per-site, and one accidental "Block" earlier in the year is enough to break voice typing forever until you reverse it.
To check and fix:
- With your Google Doc open, click the small icon to the left of the URL in the address bar (it usually looks like a tune slider or lock).
- Find the Microphone row.
- If it says Block or shows a red icon, change it to Allow.
- Reload the page.
If the microphone option is not listed at all, you may need to go into Chrome Settings, then Privacy and security, then Site settings, then Microphone, and remove docs.google.com from the Block list and add it to Allow.
3. macOS or Windows is blocking Chrome from using the mic
Browser permission is only half the picture. Your operating system has its own microphone permission layer. If you have ever clicked "Don't Allow" on a macOS mic prompt for Chrome, the browser will look like it is listening but no audio will reach the speech engine.
On macOS: open System Settings, click Privacy & Security, click Microphone, and make sure the toggle next to Google Chrome is on. If you toggle it on while Chrome is running, you will probably need to quit Chrome completely and reopen it.
On Windows: open Settings, click Privacy & security, click Microphone, make sure "Microphone access" is on and "Let apps access your microphone" is on. Scroll down to the list of desktop apps and confirm Chrome is allowed.
4. The wrong microphone is selected
This one is easy to miss. If you have a USB mic, AirPods, a webcam mic, and the built-in laptop mic all attached at once, your computer has multiple audio inputs and Chrome is using one of them — possibly not the one you want.
On macOS, go to System Settings, Sound, Input, and click the microphone you actually want to use. Watch the input level bar while you speak; if it does not move, that mic is dead or muted and you should choose another. On Windows, open Sound settings and set the correct device as the default input. Chrome inherits this default — there is no per-site mic selector inside Google Docs.
If you use a Bluetooth headset, also check that it is connected in the Headset profile (which enables the mic) and not the higher-quality A2DP-only profile, which disables the mic. Some headsets quietly drop the mic when paired to multiple devices.
5. The document language is not supported (or is set wrong)
Google Docs voice typing supports a wide range of languages, but the language is set inside the voice typing panel — not the document language. Above the microphone icon there is a small dropdown. If it is set to a language you do not speak, recognition will fail entirely or produce garbage.
Click the dropdown above the mic icon and pick the language you intend to speak. For accented English, choose the most matching variant — English (United States), English (United Kingdom), English (India), and so on. Recognition quality genuinely varies between variants, so it is worth experimenting.
Voice typing supports over 100 languages and dialects, but some niche regional variants and many less-resourced languages are not in the list. If your language is missing, voice typing is simply not available for that language and no troubleshooting will fix it.
6. A Chrome extension is breaking the speech API
Privacy extensions, ad blockers, script blockers, anti-tracking tools, and some VPN extensions can all interfere with Chrome's speech recognition. They can block the WebSocket connection the speech engine uses, strip the audio MediaStream, or simply hold so much CPU that the recognition session times out.
To isolate this:
- Open the document in an Incognito window (Chrome blocks extensions in incognito by default).
- Try voice typing. If it works in Incognito, an extension is the culprit.
- Disable extensions one by one in chrome://extensions/ until voice typing works in a normal window. Common offenders are uBlock Origin, Privacy Badger, AdBlock Plus, NoScript, Ghostery, and corporate-managed security extensions.
7. The document is in offline mode or has lost network
Google Docs voice typing is not on-device speech recognition. It streams your audio to Google's servers, transcribes it there, and streams the text back. That means it does not work offline, even if the rest of Google Docs has offline editing enabled.
If your connection is flaky, voice typing will work in bursts and then stop. If you are on a corporate or hotel network that blocks WebSockets or specific Google endpoints, voice typing may never start. Try the document on a different network — a phone hotspot is a quick test — to rule out network blocking.
8. Chrome itself needs an update or a restart
Speech recognition has been an unusually fragile feature inside Chrome for years. Long-running Chrome sessions sometimes drag a broken WebRTC or audio worker behind them, and only a full quit and relaunch will clear it.
The minimum first-aid sequence:
- Save your document.
- Quit Chrome completely (Cmd+Q on Mac, fully close all windows on Windows — not just close the tab).
- Reopen and try voice typing again.
- If that fails, go to chrome://settings/help and let Chrome install any pending updates, then restart.
9. The mic stops listening after a pause
This is not really a bug — it is the documented behaviour. If you stop speaking for more than a short window (roughly thirty seconds in practice), Google Docs voice typing turns the mic off and you have to click it again. The same thing happens if you switch tabs, click into another window, or change focus inside the document.
There is no setting to extend this timeout. If you are dictating a long document, you will end up clicking the mic icon dozens of times per session. This is the most common reason people give up on Google Docs voice typing entirely.
What to do if none of the above works
If you have worked through all nine fixes and voice typing still does not work, you are almost certainly hitting a Chrome speech engine bug that no amount of user-side tweaking will solve. Common signs that this is what you are seeing:
- The mic icon turns red but no text appears even though you can confirm the OS-level mic is capturing audio.
- The first one or two sentences transcribe and then it goes silent forever.
- Voice typing works on one document but not on another inside the same account.
- Voice typing works on one Google account but not another, on the same machine.
These are all symptoms of the underlying Web Speech API failing, not your configuration. A new Chrome profile sometimes clears it. A reinstall of Chrome sometimes clears it. A wait of a few days sometimes clears it. None of these are real solutions.
The real problem with Google Docs voice typing
Even when it works perfectly, Google Docs voice typing has structural limits that no troubleshooting can fix. It only works in Google Docs — not in Gmail, Slack, your code editor, your password manager, or any other app. It requires Chrome. It cuts off after pauses. It needs network. It cannot learn your voice. It cannot learn your vocabulary. It cannot rewrite messy speech into clean prose.
If you find yourself fighting Google Docs voice typing more than once a week, the honest answer is that you have outgrown what a free in-browser feature can do. A dedicated voice-to-text app solves all of the above with one architectural difference: it lives on your computer, not in a browser tab, and the text appears wherever your cursor is.
Voice Keyboard Pro is a native macOS menu bar app that does exactly this. You hold a hotkey, you speak, you release, and text appears at your cursor in any app — Docs, Gmail, Slack, Notion, your terminal, Cursor, Photoshop's text tool, anywhere. It uses Whisper-class AI transcription that is dramatically more accurate than the in-browser Web Speech API, and an offline Apple Speech mode for when you do not want anything leaving your machine.
It also fixes the things Google Docs voice typing cannot. A Voice Profile feature learns your voice so accuracy goes up over time. A custom vocabulary lets you teach it the names, acronyms, and jargon you use. Smart Rewrite cleans up filler words and run-on sentences after dictation. Voice Isolation strips background noise. And there is no thirty-second pause timeout, no Chrome dependency, and no scope limit to a single web app.
If you have spent more than an hour this month trying to make Google Docs voice typing behave, you have already paid more in time than a year of a real dictation app would cost.
Voice Keyboard Pro has a free tier with daily limits — enough to test whether voice dictation is genuinely faster than typing for the work you do. Pro is $4.99 per month or $34.99 per year, which removes the daily limit and unlocks Smart Rewrite and Voice Profile. On the privacy side, the server stores only operational pings; no audio and no transcript content are kept. There is also a fully offline Apple Speech mode for sensitive work that should never touch a network.
Try it on the same document you have been fighting Google over. The speed difference between a flaky browser feature and a real dictation app is not small — it is the difference between dictating that document once, end to end, and not having to click the mic icon ever again.