you@macbook ~/blazing-transcribe $ cat blog/voice-typing-not-working.md

Voice Typing Not Working: Complete Guide (2026)

Alex ChristouMarch 12, 2026
troubleshootingvoice-typing
* * * * * * * * * * * * * * * * * * * * * * * *

Voice Typing Not Working: Complete Guide (2026)

Voice typing broke again. Maybe the cursor sits there blinking while you talk into the void, maybe the mic icon flashes and disappears, or maybe the feature just vanished from the menu entirely. The good news: most voice typing failures come from the same handful of causes, and most of them take under five minutes to fix.

This guide covers every major platform, the actual settings paths you need, and what to do when the real problem isn't a setting at all.

Quick diagnosis checklist

Before you troubleshoot anything platform-specific, run through this. These seven checks resolve about 70% of voice typing problems.

CheckWhat to doWhy
Microphone hardwareUnplug and replug, or switch to built-in micUSB disconnects and Bluetooth drops cause silent failures
Mic permissionsOpen system settings, confirm the app has microphone accessMost apps fail silently when permission is denied
Correct input deviceOpen sound settings, verify the right mic is selectedYour OS may have switched to a different device after sleep or dock changes
Input volumeSpeak and watch the level meter in sound settingsA mic can be "connected" but set to zero volume
Internet connectionRun a speed test or open a websiteCloud-based dictation (Google, Apple on Intel, Windows Voice Typing) dies without internet
Restart the appFully quit and reopenClears frozen audio sessions
Restart your deviceFull reboot, not sleep/wakeResets audio drivers and clears system-level audio locks

If none of those worked, find your platform below.

macOS: voice typing not working

Mac dictation breaks more often than it should, mostly because Apple scatters the relevant settings across three separate panes and silently denies access without telling you.

Enable Dictation

Open System Settings, go to Keyboard, scroll down to Dictation. If it's off, turn it on. If it's already on, toggle it off, wait 10 seconds, then toggle it back on. This forces macOS to reinitialize the speech engine.

While you're here, confirm two things:

  • The language is set correctly. A mismatched language pack produces garbage output or no output at all.
  • The microphone source below the Dictation toggle points to the device you're actually using.

The default shortcut is double-tap Fn. If you changed it and forgot what you set, it's shown right below the toggle.

For a deeper walkthrough of macOS dictation setup, see how to dictate on Mac.

Check microphone permissions

Go to System Settings, then Privacy & Security, then Microphone. Every app that uses your mic needs its own toggle here. If an app isn't listed, it hasn't requested access yet. Open the app, try to use voice typing, and the system prompt should appear.

If you accidentally dismissed the permission prompt, the app won't ask again. You can force it to re-request by running this in Terminal:

tccutil reset Microphone com.example.appname

Replace com.example.appname with the app's actual bundle identifier. Relaunch the app afterward.

Disable Voice Control

Voice Control and Dictation conflict with each other. If Voice Control is active, Dictation often stops working entirely, or you get duplicate words.

Go to System Settings, then Accessibility, then Voice Control. Turn it off. Try Dictation again.

Clear the speech recognition cache

If Dictation still won't respond and Siri is also broken, the speech engine itself is probably corrupted.

  1. Disable Dictation in System Settings
  2. Open Finder, press Cmd+Shift+G, and paste: ~/Library/Caches/com.apple.SpeechRecognitionCore
  3. Delete everything in that folder
  4. Restart your Mac
  5. Re-enable Dictation

This forces macOS to rebuild the language model from scratch.

Audio input device problems

Your Mac might be listening to the wrong microphone. Open System Settings, then Sound, then Input. If you have multiple devices (headset, external mic, built-in), macOS sometimes quietly switches between them after waking from sleep or connecting to a dock.

Click the correct device and speak. Watch the input level meter. If it doesn't move, the mic hardware is the problem.

If you want more detail on the macOS speech to text stack, check out how to use speech to text on Mac.

Windows: voice typing not working

Windows has two built-in voice typing systems with completely different failure modes. Windows Voice Typing (Win+H) and the older Windows Speech Recognition. Both break, just differently.

Fix Windows Voice Typing (Win+H)

  1. Press Win+H. If nothing happens, the feature might be disabled. Go to Settings, then Time & Language, then Speech. Make sure Online speech recognition is toggled on.
  2. Check your microphone: Settings, then System, then Sound. Under Input, confirm the correct mic is selected and the volume isn't at zero.
  3. Test the mic independently. Open Voice Recorder and try to record something. If recording fails, the problem is hardware or drivers, not voice typing.
  4. Run the built-in troubleshooter: Settings, then System, then Troubleshoot, then Other troubleshooters, then Recording Audio.

One thing that catches people off guard: Windows Voice Typing requires an active internet connection. It processes speech in the cloud. If your Wi-Fi drops, it fails with no error message. Verify your connection.

Fix Windows Speech Recognition

The older Speech Recognition system (open it by searching "Windows Speech Recognition" in the Start menu) has different requirements:

  1. It needs to be set up initially through the wizard. If you've never done this, search "Speech Recognition" and run the setup.
  2. It can work offline but requires language packs. Go to Settings, then Time & Language, then Language & Region. Click your language, then Language options, and download the Speech pack if it's not installed.
  3. Check that your microphone is configured: Settings, then System, then Sound, then Input. Select your device and verify the volume level.

Microphone permissions on Windows

Windows 11 has a global microphone permission gate. If it's off, nothing gets mic access.

Go to Settings, then Privacy & Security, then Microphone. Turn on Microphone access at the top. Then scroll down and make sure Let apps access your microphone and Let desktop apps access your microphone are both enabled.

This is the single most common cause of voice typing not working on Windows after a major update. Windows sometimes resets these toggles.

Google Docs: voice typing not working

Google Docs voice typing has its own set of quirks because it's browser-based and entirely cloud-dependent.

Browser requirements

Voice typing in Google Docs only works in Chromium-based browsers: Google Chrome and Microsoft Edge. It will not appear in Firefox, Safari, or Brave (unless Brave's shields are configured to allow it). If you don't see "Voice typing" under the Tools menu, switch to Chrome.

Grant microphone permission in Chrome

Two layers of permissions need to be correct:

Browser level: Click the three-dot menu in Chrome, go to Settings, then Privacy and security, then Site settings, then Microphone. Make sure docs.google.com is not in the "Not allowed" list. If it is, remove it.

System level: Your OS also needs to allow Chrome to use the mic. On macOS, check System Settings, then Privacy & Security, then Microphone, and confirm Google Chrome has access. On Windows, check Settings, then Privacy & Security, then Microphone.

Internet connection

Google Docs voice typing is 100% cloud-processed. If your internet cuts out for even a few seconds, the mic icon disappears and transcription stops. There's no offline fallback. If you're on flaky Wi-Fi, voice typing in Google Docs will be a frustrating experience.

Voice typing starts then stops

This is the most common complaint in Google's support forums. You start talking, it works for 30 seconds, then silently stops. The causes:

  • Chrome tab went to background. Voice typing pauses when the Docs tab loses focus. Don't switch tabs while dictating.
  • Microphone captured by another app. Close any other apps using the mic (Zoom, Teams, Discord, any recording software).
  • Chrome cache corruption. Clear cache: three-dot menu, then More tools, then Clear browsing data. Set time range to All time, select Cookies and Cached images and files, then clear.

Microsoft Word: voice typing not working

The Dictate button in Microsoft Word has its own failure modes. There are two versions of it, and they don't work the same way. For a full walkthrough of Word's dictation feature, see voice typing in Microsoft Word.

Microsoft 365 Dictate button

The Dictate button on the Home tab requires a Microsoft 365 subscription. If you're using a one-time purchase version of Office (Office 2021, etc.), the button either won't appear or will show an error when clicked.

If you have a valid subscription and it still doesn't work:

  1. Make sure you're signed in to your Microsoft account inside Word.
  2. Check for Office updates: File, then Account, then Update Options, then Update Now.
  3. Verify your internet connection. Word's dictation is cloud-based.
  4. Check microphone permissions at the OS level (see the Windows or macOS sections above).

"Oops, there was a problem with Dictation" error

This error usually means one of three things:

  • Your internet dropped during transcription
  • Microsoft's speech service is having an outage (check status.office.com)
  • Your Office installation is corrupted. Try running a Quick Repair: Windows Settings, then Apps, then Installed apps, find Microsoft 365, click Modify, then Quick Repair.

Windows Voice Typing as an alternative

If Word's Dictate button keeps failing, you can use Windows Voice Typing (Win+H) instead. It types into whatever text field has focus, including Word documents. It uses Microsoft's own speech service but through a different code path, so it often works when Word's built-in button doesn't.

iPhone and iPad: voice typing not working

iOS dictation breaks frequently after major updates. Apple has acknowledged several dictation bugs in iOS 18, including duplicate words and mid-sentence freezes.

Enable Dictation

Go to Settings, then General, then Keyboard. Scroll down and toggle Enable Dictation on. If it's already on, toggle it off, wait a few seconds, toggle it back on.

Check Siri & language settings

Dictation on iOS shares its engine with Siri. If Siri isn't working, Dictation won't work either.

Go to Settings, then Siri (or Siri & Search on older iOS versions). Make sure Siri is enabled and the language matches your dictation language.

Screen Time restrictions

This catches a lot of people. Screen Time can silently disable Dictation.

Go to Settings, then Screen Time, then Content & Privacy Restrictions. Tap Allowed Apps (or "Intelligence & Siri" on iOS 18+). Make sure the toggle for Siri & Dictation is turned on.

Microphone problems

If dictation produces no output at all, test the microphone separately. Open Voice Memos and record a few seconds of speech. If the recording is silent, the mic itself is the problem. Check for debris blocking the microphone grills on the bottom of the device, and remove any case that might be covering them.

Internet connection

On most iPhones, dictation requires an internet connection for cloud processing. Newer devices with Apple Silicon (iPhone 15 Pro and later) can process some dictation on-device, but the default behavior still sends audio to Apple's servers. If you're on weak Wi-Fi, switch to cellular or move closer to your router.

Known iOS 18 issues

iOS 18 introduced several dictation bugs that Apple has been patching through point releases:

  • Duplicate words: Often caused by having both Voice Control and Dictation active simultaneously. Turn off Voice Control in Settings, then Accessibility, then Voice Control.
  • Dictation stops mid-sentence: Update to the latest iOS version. Apple has fixed this in iOS 18.3 and later.
  • Wrong words consistently: Your on-device language model may be corrupted. Reset keyboard settings: Settings, then General, then Transfer or Reset iPhone, then Reset, then Reset Keyboard Dictionary.

Common causes across all platforms

After covering every platform, here are the patterns. The same handful of issues cause voice typing failures everywhere.

1. Microphone permissions

Every platform gates mic access behind permissions now. And nearly every platform fails silently when the permission is missing. No error dialog, no warning. Just nothing happens. Always check permissions first.

2. Wrong input device selected

If you use multiple audio devices (dock, headset, external mic, built-in), your OS will occasionally switch to the wrong one without telling you. This is the second most common cause of "my mic works but voice typing doesn't."

3. Internet dependency

Most built-in voice typing tools process speech in the cloud: Google Docs, Windows Voice Typing, Apple Dictation on older Macs, Microsoft Word Dictate, and iOS Dictation. If your internet connection drops, they all fail silently. No queuing, no retry. Just silence.

4. Software conflicts

Two apps can't use the same microphone simultaneously on most systems. If you have Zoom, Teams, Discord, or any other app actively using your mic, voice typing will fail. Close other audio-capturing apps before dictating.

5. Post-update breakage

Major OS updates (macOS, Windows, iOS) frequently reset permissions, change default settings, or introduce new bugs in speech engines. If voice typing stopped working right after an update, check your permissions and settings. They may have been reset.

When the real problem is the tool itself

Sometimes you've checked every setting, verified every permission, confirmed your mic works, and voice typing still fails. Or it works, just badly: dropped words, long delays, random stops mid-sentence, cloud timeouts on bad Wi-Fi.

At some point the question shifts from "how do I fix this?" to "why am I fighting this tool?" If you need a deeper look at common speech to text not working issues, that guide covers additional edge cases.

The fundamental problem with most built-in voice typing is architectural. Cloud-dependent speech recognition is fragile. It needs a stable internet connection, it's subject to server-side outages, and it introduces latency that makes real-time typing feel laggy. Add in the permissions juggling, input device switching, and post-update breakage, and you're spending more time maintaining the tool than using it.

Local speech recognition tools eliminate most of these failure modes entirely. No internet dependency means no cloud timeouts. No server means no outages. Processing on your own hardware means consistent latency regardless of network conditions.

Blazing Transcribe takes this further. It runs entirely on the Apple Neural Engine, so there's no internet connection to troubleshoot, no cloud service to go down, and no server-side processing to lag. The always-on voice activity detection means you don't have to press a button or remember a shortcut. You just talk, and text appears in whatever app has focus. At ~530ms latency and 2.5% word error rate, it sidesteps most of the problems in this guide by not depending on the infrastructure that causes them.

If you're evaluating your options, the best dictation software comparison breaks down how the major tools stack up on accuracy, latency, and reliability.

Summary

Voice typing failures almost always come from one of five causes: denied microphone permissions, wrong input device, no internet connection (for cloud-based tools), software conflicts with other audio apps, or broken settings after an OS update. The fixes are straightforward once you know where to look.

If you're tired of troubleshooting the same issues repeatedly, consider whether the tool itself is the bottleneck. Cloud-dependent voice typing will always be vulnerable to network issues and server-side problems. Local tools that process speech on your own hardware skip those failure modes entirely.

Voice Typing Not Working: Complete Guide (2026) — Blazing Transcribe