Mac troubleshooting
Voice to text not working on your Mac?
Six verified fixes in the order I would actually try them, plus the one Apple does not publish.
Last updated: May 2026

When voice to text breaks on a Mac, the cause is almost one of six things: Dictation toggled off, missing microphone permission for the focused app, the wrong input device selected, Voice Control silently overriding Dictation, the macOS speech daemons hung, or, on Intel Macs only, NVRAM needing a reset. The toggle-off-toggle-on fix resolves most cases in under sixty seconds.
I have spent more evenings than I would like to admit making Mac Dictation behave. The first time it broke for me was a Tuesday: teacher email, Slack thread, permission slip all waiting, Microphone key doing nothing. Six fixes that night. Five worked at least once. The Terminal-daemon kill I now keep pinned in a sticky note.
Apple's official troubleshooting page lists ten steps for "Dictation on Mac doesn't work as expected". All ten are worth checking. The page omits three of the most common real-world causes: the Voice Control collision, the speech-daemon hang, and the fact that NVRAM resets only apply to Intel Macs. This walkthrough covers all of them in the order I would try them.
First check: is Dictation even turned on?
Dictation
Convert your voice to text
Before any other fix, confirm Dictation is enabled. Apple menu → System Settings → Keyboard → scroll to Dictation → check the toggle. If it is off, that is your whole problem. Toggle it on, accept the language download dialog if it appears, and try the shortcut again.
You start Dictation by pressing the Microphone key in the function row, by using the keyboard shortcut you configured, or by choosing Edit → Start Dictation from the menu bar. On 2021-and-newer MacBook keyboards the Microphone key is F5. On older keyboards the shortcut is a double-tap of Fn or the Globe key, changeable under System Settings → Keyboard → Dictation → Shortcut.
If Dictation is on and the shortcut does nothing, move to Fix 1.
Fix 1: Toggle Dictation off, wait 10 seconds, toggle it back on
The boring fix works on most Macs. Same panel, same toggle. Off, count to ten, back on. macOS re-initialises the speech subsystem and clears whatever state got stuck.
Why ten seconds? The Dictation daemon (corespeechd) needs a moment to shut down cleanly before it relaunches. Flip too fast and you land in the same hung state. After it is back on, test in Notes first. If Dictation works there but breaks in your browser or Word, the problem is permission, not Dictation. That is Fix 2.
Fix 2: Your microphone permission is the problem (not your mic)
Messages
Microsoft Word
Google Chrome
Slack
When Dictation works in Notes but breaks in Word, Chrome, Slack, or Messages, the issue is per-app microphone permission. macOS treats Dictation as a feature inside whichever app holds the cursor, so the focused app needs its own microphone access on top of the Dictation toggle.
System Settings → Privacy & Security → Microphone. You will see a list of every app that has asked for the microphone. If your target app is in the list with the toggle off, flip it on, quit and relaunch the app, and try again. If the app is not in the list, it has not requested microphone permission yet. Trigger any audio feature in the app (a voice memo, a video call), accept the prompt, then retry.
This single fix accounts for about half of the "Dictation stopped working" emails I see. The mic hardware is fine. The Dictation toggle is on. The app just was not granted permission.
Fix 3: macOS picked the wrong microphone again
Input level
Apple lists "external microphone connected" and "input volume sufficient" as separate steps. In practice they are the same problem worn two ways. macOS picks the wrong input device when a Bluetooth headset disconnects, when you plug in a USB mic, or when a video call grabs the default.
System Settings → Sound → Input. Pick the device you want from the dropdown. Below it is an input-level meter. Speak. The meter should bounce. If it sits flat at zero, the selected device is dead, so try another. If it bounces but Dictation hears nothing, drag the input volume to about 75 percent and try the shortcut again.
A side note: a twenty-dollar USB mic does more for Dictation accuracy than any software fix. The built-in mic is fine for short notes; for anything longer, a real microphone changes the experience.
Fix 4: Voice Control is on and disables Dictation without warning
Enable Voice Control
Almost never listed on third-party tutorials, and it took me the longest to find. Apple's own Dictation help page is plain: "When Voice Control is on, you use Voice Control to dictate text; standard macOS Dictation isn't available."
Voice Control is a separate accessibility feature introduced in macOS Catalina, and it lets you control the entire Mac by voice. It includes its own dictation, which is why enabling Voice Control disables Apple Dictation. The two cannot run side by side.
System Settings → Accessibility → Voice Control. If the toggle is on, that is why your shortcut does nothing. Turn Voice Control off. A common way to land here: you enabled it to dictate hands-free last month while making lunchboxes and never turned it off. That is how I lost an afternoon last year.
Fix 5: The kill-the-daemons Terminal command (when nothing else works)
user@MacBook ~ %
$ sudo killall -9 corespeechd assistantd
When the Dictation icon shows up but no text transcribes, or the icon hangs, the speech daemons (corespeechd, assistantd) have hung. Killing them forces macOS to relaunch them clean. This is not in Apple's documentation; it is a community remedy that has circulated on Apple Community threads and Mac troubleshooting sites for years.
Open Terminal (Spotlight → "Terminal") and run:
sudo killall -9 corespeechd assistantdEnter your password. macOS respawns both daemons within a few seconds. Test Dictation; most hangs resolve at once. Important caveat: this is a community fix, not Apple-recommended. The daemons are safe to kill, but if Terminal makes you nervous, skip this one. If you want to try the gentler form first, sudo killall corespeechd (single daemon, no -9) often clears a hung session on its own.
Fix 6: Reset NVRAM (Intel Macs only — skip if you have M1, M2, M3, or M4)
Hold during startup until you hear the chime twice
Intel Macs only
If you have an Apple Silicon Mac (anything M1, M2, M3, or M4), skip this fix. Apple Support is explicit: "The steps to reset NVRAM don't apply to Mac computers with Apple silicon, and aren't needed on those computers." Apple Silicon Macs rebuild NVRAM on startup. Nothing to press.
If you have an Intel Mac, an NVRAM reset can clear bad audio-routing state that Dictation depends on. Shut down. Power back on and immediately hold Option + Command + P + R. Keep holding for about twenty seconds. Release when you hear the startup chime a second time, or after the Apple logo appears and disappears twice. Log back in and try Dictation.
NVRAM resets are a 1998-era ritual that survives because it is harmless. They will not fix a permission problem or a Voice Control conflict. Try Fixes 1 through 5 first.
When the fixes don't stick: why Mac Dictation will keep breaking

After the second or third time you fix this, you notice the pattern: Dictation stays working for a week or two, then stops without warning. That is not your imagination. It is the architecture.
Apple Dictation in 2026 is layered on three things that drift underneath it: the macOS speech daemons (restarted by every system update), the per-app microphone permissions (which reset when apps are reinstalled or sandboxed under new rules), and the Voice Control / Dictation toggle pair. Throw in the Enhanced Dictation deprecation in macOS Catalina, where Apple moved offline speech into Voice Control in 2019 with no announcement, and the half-finished migration from dictationd to corespeechd, and you have a feature that breaks every few months because three different teams at Apple own pieces of it.
The fix sequence above will get you running again. It will not stop the breakage from coming back. That is why the section below this one exists.
Seeing the same silence inside a Google Docs tab rather than a native app? Here is how to fix Google Docs voice typing.
When to skip Apple Dictation outright (and what I'd reach for instead)
Apple Dictation is the right tool for short notes. For a thirty-word text or a one-line search query, it is free, on-device for most supported languages, and built in. We start being worth the install around the 200-word threshold, where Apple's accuracy and short-utterance behaviour start hurting and where you find yourself fixing the same breakage every other month.
If the fixes keep slipping and you want a free, on-device upgrade, our free Apple Dictation alternative for Mac walks through the exact swap, same short hotkey, every app.
Whisper by Remskill runs on-device on Apple Silicon using one of four English Whisper models (Base ~140 MB, Small ~480 MB, Medium ~1.5 GB, Turbo ~1.5 GB and six times faster than Large with ~99% of its accuracy), or any of four multilingual variants up to Large v3 (~3 GB) that handle 99 languages on Whisper multilingual. The English-only variants are locked to English. Parakeet TDT v3 (~600 MB) is the second local engine, 5–10× faster than Whisper on CPU, covering English plus 24 European languages. Apple Dictation supports about 40 region-specific variants by comparison.
The default macOS hotkey is the modifier-only push-to-talk combination ⌘ + ⌥ (Command + Option, either side of the keyboard): hold to record, release to paste at the cursor in any app. The full local pipeline (Whisper, Parakeet, Ollama AI enhancement, history, presets, hotwords) is free for any authenticated user, no card required at signup. Whisper Pro adds OpenAI Cloud transcription (gpt-4o-mini-transcribe is the default) and web-aware AI commands on top.
Mac is Apple Silicon only: M1, M2, M3, M4. On an Intel Mac, the Cloud path on any modern transcription tool is your route; the local-model path on Intel is closed across most of the category.
Try Whisper free on your Mac: same hotkey, every app, no Voice Control collision.
If you read this far and Dictation still does not work, the structural answer is in the section above the FAQ. The feature is layered on three subsystems that drift on their own schedules, and the toggle-off-on dance will keep coming back. I built Whisper by Remskill partly because I got tired of it. Use Apple Dictation for short notes (it is free and built in) and reach for something else when the breakage starts costing you the afternoon.
Further reading
Want to see it on your Mac?
Download Whisper, hold Command + Option, watch the transcript appear at your cursor.
Apple Silicon (M1, M2, M3, M4). Free local pipeline, no card at signup.
Tested on macOS Sonoma 14.x and Sequoia 15.x. Reviewed May 2026.



