You press the dictation shortcut on your Mac and nothing happens. Or worse — the microphone icon appears, you speak clearly, and it produces gibberish or nothing at all. Mac dictation failures are frustratingly common, and the causes range from simple permission issues to deeper system bugs. Here's a systematic approach to getting it working again.
Check Microphone Permissions
The most common cause of dictation failure is a permissions issue that happened silently. Go to System Settings → Privacy & Security → Microphone and verify that the apps you're trying to dictate into have microphone access. If you recently updated macOS, permissions can reset without warning. Also check System Settings → Privacy & Security → Speech Recognition — dictation requires this permission as well.
If permissions look correct, try toggling them off and on again. macOS occasionally gets into a state where the permission is listed as granted but isn't actually being honored by the system.
Reset the Dictation System
Open System Settings → Keyboard → Dictation and toggle it off. Wait ten seconds, then toggle it back on. When prompted, re-download the on-device speech recognition model. This forces macOS to reinitialize the entire dictation pipeline and often resolves issues caused by corrupted model files or stale caches.
If that doesn't work, try a more aggressive reset: in Terminal, run sudo killall speechsynthesisd followed by sudo killall assistantd. These services handle speech processing on macOS, and killing them forces a clean restart.
Audio Input Issues
Open System Settings → Sound → Input and confirm the correct microphone is selected. If you use external audio devices — Bluetooth headphones, USB microphones, audio interfaces — macOS sometimes routes input to an unexpected device. Speak while watching the input level meter to confirm your microphone is actually receiving audio.
Bluetooth microphones are a frequent culprit. The HFP (Hands-Free Profile) used for microphone input on Bluetooth headphones downgrades audio quality dramatically and can confuse the speech recognition engine. If possible, use a wired microphone or your Mac's built-in mic instead of Bluetooth for dictation.
Application Compatibility
Some applications don't properly implement the macOS text input APIs that dictation relies on. If dictation works in TextEdit but not in your target app, the issue is application-level compatibility, not a system problem. Electron-based apps (VS Code, Slack desktop, Discord) are notorious for spotty dictation support.
For apps with poor dictation compatibility, a system-level tool like Transcribo often works where Apple Dictation fails, because it uses a different text injection method that bypasses the standard input API limitations.
After macOS Updates
Major macOS updates frequently break dictation. If your dictation stopped working right after an update, you're not alone — this is a well-known pattern. The fix is usually a combination of: re-granting permissions, re-downloading the speech model, and restarting the relevant system services. In some cases, you may need to create a new user account and test dictation there to determine if the issue is system-wide or profile-specific.
When the Built-in Just Won't Cooperate
If you've exhausted these troubleshooting steps and Apple Dictation remains unreliable, consider it a sign to move to a dedicated dictation tool. Transcribo runs its own audio pipeline and speech recognition engine, independent of macOS dictation services. It's not affected by the system-level bugs that plague Apple Dictation, and it works consistently across macOS versions and updates.