Voice typing not working in Chrome? 7 fixes

Troubleshooting · LK Forge · Updated 22 June 2026

When voice typing suddenly stops working in Chrome, it is almost always one of a handful of causes: a blocked microphone permission, the wrong browser, another app holding the mic, an operating-system privacy setting, or a dropped internet connection. Browser dictation relies on the Web Speech API, and in Chrome and Edge that engine streams your audio to the browser's speech service to transcribe it — so a single broken link in that chain stops the words from appearing. This guide walks through the fixes in the order that resolves the most cases fastest, whether you are using Google Docs voice typing, an in-browser dictation tool, or VoiceFlow.

1. Allow the microphone permission for the site

The most common cause is a blocked or never-granted mic permission. In Chrome, click the icon at the left of the address bar (a padlock, tune slider, or "View site information" button), find Microphone, and set it to Allow. Reload the page and start dictation again. If you accidentally clicked "Block" the first time, the browser will not ask again until you change it here. On Chrome you can also visit Settings → Privacy and security → Site settings → Microphone to see which sites are blocked and remove the bad entry.

2. Make sure you are using a supported browser

Live voice typing only works in browsers that ship the Web Speech recognition API. In practice that means Google Chrome and Microsoft Edge on desktop, plus other Chromium browsers such as Brave and Opera. Safari has partial, inconsistent support, and Firefox has speech recognition disabled by default — so dictation may silently fail to start there. If nothing happens when you press the mic and there is no error, switching to Chrome or Edge resolves it immediately.

3. Check the right microphone is selected and free

If the browser is listening but no words appear, the wrong input device may be active, or another program is holding the microphone. Close other apps that capture audio — Zoom, Teams, Discord, OBS, or another browser tab already recording — since most systems give the mic to one app at a time. Then confirm the correct device is chosen in Chrome Settings → Privacy and security → Site settings → Microphone (there is a default-device dropdown). A quick hardware check: open your OS sound settings and watch the input level move when you speak. If it does not, the issue is the mic or its connection, not the website. Our microphone guide for dictation covers picking and placing a mic that the engine hears clearly.

4. Fix the "no-speech" error

A no-speech error means the engine started but heard nothing it could transcribe. Usual culprits are a muted mic, an input level that is too low, or simply too long a pause before you started talking. Unmute the mic, move a little closer, speak within a few seconds of pressing the button, and avoid very noisy surroundings. Some tools (VoiceFlow included) automatically restart listening after a silence so a natural pause does not end the session — but if dictation keeps cutting out the moment you stop talking, that restart behaviour is what you want to look for.

5. Clear OS-level microphone privacy blocks

Even with the browser permission granted, your operating system can block the mic for the whole app. On macOS, open System Settings → Privacy & Security → Microphone and make sure Google Chrome is toggled on. On Windows, go to Settings → Privacy & security → Microphone and confirm both "Microphone access" and "Let desktop apps access your microphone" are on. After changing an OS setting, fully quit and reopen Chrome so it picks up the new permission.

6. Try without extensions or in a clean window

Privacy and ad-blocking extensions occasionally interfere with the speech API or the connection it uses. Open an Incognito window (extensions are off by default there) and test dictation. If it works in Incognito, re-enable your extensions one at a time to find the culprit. While you are at it, make sure Chrome itself is up to date via Settings → About Chrome, since speech support has improved across versions.

7. Confirm you are online

This surprises people: in Chrome and Edge, browser dictation is not on-device. The audio is sent to the browser vendor's cloud speech service to be transcribed, so a dropped or flaky connection produces a network error and stops dictation. On a train, in a café, or on a captive-portal Wi-Fi that has not been signed into, voice typing will stutter or fail. Reconnect and try again. VoiceFlow has no offline mode; if you need to dictate without a connection, use your operating system's built-in dictation.

Google Docs voice typing specifically

If the problem is narrowly with Google Docs → Tools → Voice typing, the same checks apply, with two extras: Google Docs voice typing only runs in Chrome (not other browsers), and it lives inside a document, so you need a Google account and an open Doc to use it. If you would rather dictate without opening Docs or signing in, a standalone browser tool avoids both requirements.

When you have tried everything

If you have allowed the mic at both the site and OS level, confirmed you are on Chrome or Edge, freed the microphone from other apps, and verified you are online, voice typing will work in the vast majority of cases. The quickest way to test a clean setup is a tool that is just a dictation box: open the VoiceFlow dictation demo, press the mic, click Allow, and speak — it is free for 2,000 words a day with nothing to install. For a walkthrough of dictating from scratch, read how to use voice dictation in your browser, or browse the VoiceFlow blog for more on speech-to-text.