The Mac dictation shortcut, and the two reasons it stops working
By Andrey ChmerevI build Kekoso, a dictation app with its own hotkey, which is why I know more than I would like about why hotkeys stop working on macOS. The Apple settings are quoted from Apple's guide; the language table and the Secure Input behaviour I checked on this machine, macOS 26.5.2, and the commands are in the text so you can check yours.

The shortcut for dictation on a Mac is where most people meet the feature, and it is also where it most often fails — quietly, with nothing on screen to explain it.
Setting it takes ten seconds. The two failure modes take longer to explain, and neither is documented anywhere you would look.
Setting it
The dictation shortcut Mac ships with is off until you turn it on, and the MacBook dictation shortcut is the same setting on the same pane. Apple’s guide is direct: “On your Mac, choose Apple menu > System Settings, then click Keyboard in the sidebar. Go to Dictation, then turn it on or off.”
The speech to text shortcut on a Mac lives in that same pane, under the switch. There is no single factory default to memorise — you pick one from the Shortcut pop-up menu, or, in Apple’s words, “choose Customize, then press the keys you want to use. For example, you could press Option-Z.”
Three ways to start dictating, from the same page: “Press and release the Microphone key if available in the row of function keys on your Mac, use the Dictation keyboard shortcut, or choose Edit > Start Dictation.”
That is the whole setup. Now the parts that go wrong.
Failure one: Secure Input, which explains nothing
You press the shortcut and nothing happens. No error, no menu bar change, no beep. Press it again in a different app and it works.
The cause is almost always Secure Input — a macOS mode any application can turn on to stop other software from reading the keyboard. It exists for good reasons: while it is active, a keylogger cannot see what you type. The side effect is that everything else watching the keyboard goes blind too.
What matters, and what is easy to get wrong: Secure Input blocks the reception of keys, not the typing of text. While it is on, key-down and key-up events stop reaching apps that watch for them. Modifier events — the ones that fire when you press or release Command, Control, Option or Shift on their own — keep arriving.
That distinction has a practical consequence. A shortcut built on a held modifier keeps working under Secure Input. A shortcut that is a modifier plus a letter does not, and it fails silently, because the app never learns the key was pressed. I know this in detail because it is the same problem for any app with its own hotkey, mine included, and the fix is to explain rather than fail quietly.
Where it comes from. Any password field turns Secure Input on for as long as it is focused — a fraction of a second, usually harmless. The lasting cases are apps that hold it: Terminal has a Secure Keyboard Entry option that keeps it on the whole time Terminal is in front, and some password managers do the same. Check Terminal’s setting with:
defaults read com.apple.Terminal SecureKeyboardEntry
A 1 means it is on. Occasionally an app crashes while holding Secure Input and the mode stays on until you log out — which is what people are describing when they say the fix was a restart.
Failure two: the language you dictate in
The speech to text Mac shortcut is bound to one language at a time, and this is where that bites.
The second failure is not silent, but it is confusing: dictation works, then stops after a while, or works on one Mac and not on another, or refuses to work at all with the network off.
That behaviour is governed by a table macOS keeps on your own disk, and you can read it:
defaults read com.apple.assistant.support "Offline Dictation Status"
On this machine, macOS 26.5.2, that returned 54 language variants — 33 languages, counting regional pairs like de-AT, de-CH and de-DE once — and each carries seven flags:
| Flag | What it appears to govern |
|---|---|
Installed |
The offline model is downloaded on this Mac |
Continuous Listening |
Dictation is not cut off after a short window |
Auto Punctuation |
Commas and full stops are inserted for you |
Emoji Recognition |
Saying “heart emoji” produces one |
On Device Search |
Search terms are handled locally |
High Quality |
The better model exists for this language |
Voice Commands |
Spoken editing commands |
And here is what the numbers looked like on my Mac:
- Installed: 2 of 54. Only
en-USandru-RU, the two languages I actually use. The other 52 are listed but not downloaded. - Continuous Listening: the same 2. This is the mechanism behind “dictation stops after a minute”. It travels with the downloaded model.
- Auto Punctuation: 1. Only
en-US. Russian has its model installed and still does not punctuate for me. - Emoji Recognition: 1. Also
en-USonly. - Voice Commands: 0 of 54.
- High Quality: 53 of 54. The single exception was
vi-VN.
Two things follow. First, “does Mac dictation work offline” has no general answer — it is a per-language fact about your machine, and the command above gives you yours in a second. Second, the features people assume come with dictation, like automatic punctuation, are narrower than dictation itself: a language can be fully supported and still hand you an unbroken wall of text.
What no shortcut will fix
Once the shortcut for dictation on Mac works, two limits remain that no key combination touches.
The shortcut starts the system feature, so it inherits everything the feature does not do.
It types where the cursor is, and only there. There is no shortcut that dictates into an app that is not focused.
It stops at the password field. Dictation into a secure field is not a shortcut problem and not a bug — it is the same Secure Input above, working as designed.
It has no vocabulary of your own. Names, drug names, part numbers and internal jargon come out as whatever the model thought it heard, every time, in every app.
Its language list is Apple’s. The table above is the whole world of what it can do offline, and adding to it is not something a shortcut reaches. The same boundary shows up in Voice Memos transcription, which draws on the same ten-language set.
When you end up wanting your own hotkey
If the built-in shortcut does the job, use it — it is free, it is there, and nothing here is an argument against it.
The reasons people go looking for something else are usually one of three: a language outside Apple’s list, a vocabulary that has to come out right, or the silent failure above happening often enough to stop trusting it. Kekoso, which I build, exists for those cases — recognition on the device, up to 99 languages, a custom dictionary, and a hotkey that tells you when Secure Input has taken the keyboard rather than doing nothing. Files rather than live speech go through a separate screen.
The wider comparison, including the built-in feature’s other limits, is in voice to text on a Mac.
Apple’s settings quoted here come from Apple’s own guide. The language table and the Secure Input behaviour were checked on macOS 26.5.2 on 4 September 2026 — both commands are above, so you can check yours rather than take mine.
Questions people ask
What is the keyboard shortcut for dictation on a Mac?
There is no single fixed one. Apple's guide has you pick it: System Settings, Keyboard, Dictation, then the Shortcut pop-up menu, where you can also choose Customize and press whatever keys you want — Apple's own example is Option-Z. Besides the shortcut, dictation starts from the microphone key in the function row if your keyboard has one, or from Edit, then Start Dictation, inside the app.
How do I turn on dictation on a Mac?
Apple's instruction is: choose Apple menu, System Settings, click Keyboard in the sidebar, go to Dictation, then turn it on. The shortcut is set in the same pane, directly under the switch.
Why does my Mac dictation shortcut suddenly do nothing?
The usual cause is Secure Input, a macOS mode that any app can hold to stop other software reading the keyboard. While it is on, key-down events never reach apps that watch for shortcuts, and nothing is displayed to explain it — the shortcut simply does nothing. Password fields turn it on for a moment; Terminal with Secure Keyboard Entry enabled holds it the whole time it is focused.
Does Mac dictation work offline?
Only for languages whose model has been downloaded. macOS keeps a table of 54 language variants and marks which ones are installed on your machine; on mine two of the 54 were. You can read the same table for your Mac with: defaults read com.apple.assistant.support "Offline Dictation Status". A language that is not installed needs a network connection.
Why does dictation stop after a minute for some languages?
That limit is tied to the same table. Continuous Listening is a per-language flag, and on my machine it was set only for the two languages whose models were installed. Without the downloaded model, dictation runs as a cloud feature with a time limit; with it, that limit goes away.
Which languages get automatic punctuation?
Fewer than support dictation. In the table on my Mac, 54 variants were listed, two had models installed, and only one — en-US — had Auto Punctuation and Emoji Recognition switched on. So a language can be fully supported for dictation and still not add commas and full stops for you.
Can I use a single modifier key as a dictation shortcut?
Apple's Customize option lets you record a combination, and a modifier held on its own behaves differently from a combination in one specific way that matters: while Secure Input is active, modifier events still reach apps but ordinary key presses do not. That is why push-to-talk on a held modifier keeps working in places where a letter-based shortcut goes quiet.