The Mac dictation shortcut.

Where to set it, why a double-press is the one that fails, and how to see what is really bound when the settings screen and your keyboard disagree. Written for macOS 26.

Where it lives

System Settings → Keyboard, in the Dictation section. The shortcut is a dropdown there, and it is the same screen that switches dictation on — if the switch is off, the shortcut does nothing no matter what it is set to, so check that first.

There is no single default across Macs. Which one your machine started with depends on whether the keyboard has a dedicated dictation key, and on what the globe key was set to do. This is worth knowing because most advice online names one specific default confidently, and then does not match your Mac.

Why the double-press is the option that fails

Several of the choices are “press this key twice”. A double-press has to be two presses inside a time window, and three ordinary things break it: a key that repeats because it was held a fraction too long, a remapping tool that swallows the first press, and any key that already does something on a single press — the single-press action fires first and the second press lands somewhere else.

If dictation starts sometimes, this is almost always why, and the fix is to switch to a single-key shortcut rather than to press more carefully.

Finding the app that took the key

A shortcut can be set correctly and still never reach dictation, because something else claimed the key first. The usual candidates are anything that runs in the menu bar and listens globally: clipboard managers, window managers, screenshot tools, remapping utilities, meeting apps that bind a push-to-talk key, and remote-desktop clients while they have focus.

The quickest test is not to hunt through each app’s settings. Quit them one at a time and try the shortcut after each. Whichever app brings dictation back is the one to rebind — and rebind that app, not dictation, if you would rather keep the dictation key where your hands expect it.

Reading what is actually bound

The settings pane shows what was chosen. It does not show what the system currently holds, and those come apart after a macOS upgrade or a restore from backup. You can read the real state in Terminal:

defaults read com.apple.symbolichotkeys AppleSymbolicHotKeys

That prints every system-wide shortcut as a numbered entry. Each has an enabled flag and a parameters triple of character, key code and modifier mask. Two things are worth recognising:

• enabled = 0 means the shortcut is off, whatever the dropdown says.
• 65535 in the first two slots is the value macOS writes for no key assigned. An entry reading enabled = 0 with (65535, 65535, 0) is an unset shortcut.

Rather than hunting for dictation’s entry by number, make the system tell you which one it is. Run the command and keep the output, change the dictation shortcut in System Settings, run it again, and compare the two. The entry that changed is yours — and that works regardless of which number your version of macOS uses.

If nothing changes between the two runs, the setting is not being written, and no amount of pressing the key will help. That is the point to log out and back in, which is what usually makes it stick.

When the shortcut is fine and dictation still is not

If the key is reaching dictation and nothing is transcribed, the shortcut is not your problem — microphone permission, the input device, or a missing language pack is. Those are the first three checks in the troubleshooting guide, and they take about a minute between them.

One thing that looks like a shortcut fault and is not: dictation that works at your desk and fails on a plane. Depending on your Mac and language, macOS may send audio to Apple to transcribe, so no connection means no dictation. macOS keeps a preference for using only offline dictation; where your language supports it, turning that on makes the behaviour predictable rather than dependent on the network.

If the built-in shortcut cannot do what you need

The macOS shortcut starts macOS dictation, and that is a fixed pairing. If what you actually want is a different key, a different behaviour on release, or dictation that keeps working in an app the system one behaves badly in, that is a different tool rather than a different setting. Uttrflow is ours; it holds its own shortcut and does not touch the one above, so both can exist on the same machine.