Mac dictation not working? Start with the 30-second rule

Most “Mac dictation not working” is one of three things: it is not broken and you have hit the silence rule; something else on the Mac has taken the microphone; or a toggle or permission got reset, usually by a macOS update. Work through them in that order and you will almost always be done inside five minutes.

Start with the one that is not a fault, because it is the most common and the most misdiagnosed.

The 30-second rule, and what Apple actually says

A lot of articles will tell you macOS caps a dictation session at 30 or 60 seconds. Apple's own documentation says the opposite: “You can dictate text of any length without a timeout.” What it does say is that dictation stops “when no speech is detected for 30 seconds.”¹

That distinction is the whole diagnosis. The clock is not on your speaking, it is on your silence — and composing is mostly silence. You say a sentence, stare out of the window working out the next one, and the session ends while you are still thinking. It looks exactly like a crash and it is a documented behaviour with no setting to change.

If that is your symptom, none of the fixes below will help, because nothing is broken. Your options are to keep talking, to re-trigger dictation each time, or to use something with press-to-talk, where a pause is just a pause because your finger is still on the key.

Eleven fixes, in the order worth trying them

1. Toggle Dictation off and on. System Settings → Keyboard → Dictation. Unglamorous, and it clears a surprising share of cases — particularly right after an update.
2. Turn Voice Control off. This is the single most-missed cause, and Apple states it plainly: “When Voice Control is on, you use Voice Control to dictate text; standard macOS Dictation isn't available.”² Voice Control can be switched on by an Accessibility shortcut without you meaning to. Look in System Settings → Accessibility → Voice Control.
3. Check which microphone is actually selected. System Settings → Sound → Input. AirPods that connect, become the default input, then wander out of range are a classic: dictation is listening to a microphone that is no longer there. So is a USB interface that has gone to sleep.
4. Check microphone permission. System Settings → Privacy & Security → Microphone. If you are dictating inside a specific app, that app needs the permission too.
5. Check the language is fully downloaded. A language that is listed but only half-downloaded produces exactly the “starts, then dies” symptom. Remove it and add it again to force a clean download.
6. Check the shortcut has not been reassigned. In Keyboard settings the fn key can be set to show emoji, change input source, or start dictation — one of those three, not all of them. If fn stopped triggering dictation, that menu is usually why.
7. Find out what else has the microphone. A FaceTime call, a screen recording, a browser tab that asked for the mic, Siri. macOS will hand audio to one of them and dictation collapses without an error message. Quit the obvious candidates and try again.
8. Try a different text field. Password fields and some secure inputs refuse dictated text by design. If dictation works in Notes and not in one specific app, the app is the variable, not macOS.
9. Restart the speech daemon rather than the Mac. If you are comfortable in Terminal, macOS runs speech recognition in a background daemon that it respawns immediately if you kill it — on current builds killall corespeechd, though process names do change between releases, so confirm with ps ax | grep -i speech first. Logging out and back in does the same job with no Terminal.
10. Re-check everything after a macOS update. Updates are the single biggest source of “it worked yesterday”: they can flip the Dictation toggle, drop a language download, and reset privacy permissions. Run steps 1, 4 and 5 again after every one.
11. Restart the Mac. Last, not first — it fixes things without telling you which thing, and you learn nothing.

If it is a third-party dictation app that stopped

The failure modes are different, because those apps need more than the microphone. Check the microphone permission, then Accessibility — that is the one that lets an app put text at your cursor, and without it you get a working transcription and nothing appearing on screen, which is a confusing way to fail.

The other classic is permission loss after an app update. macOS ties privacy grants to an app's code signature, so a badly-signed or hand-patched build can look like a different app to the system and silently lose everything you granted it. If you have re-granted Accessibility twice for the same app, that is the tell. A signed and notarized build should never do it.

When the fix is not a fix

Be honest with yourself about which problem you have. If dictation stops because a permission is off, fix the permission. If it stops because you paused to think, no setting will help — you have outgrown a feature designed for short bursts of text. That is the point at which people go looking for something else, and it is worth understanding what a dedicated app actually adds before you pay for one, and where your audio goes once you do.

For what it is worth, the design decision behind WrapScribe is exactly this: you hold a key while you speak and release it when you are done, so silence never ends anything, and the text arrives cleaned up rather than as a literal transcript of your umms. It needs macOS 26 (Tahoe) on Apple silicon — if you are on an older Mac, the eleven fixes above are the whole toolbox, and they are usually enough.