Productivity
The shortcut decides whether you keep dictating
A key your hands cannot find without looking will not survive a busy day. This is the least discussed and most decisive setting in any dictation app.
Last updated
Why this matters more than it sounds
Dictation competes with typing, and typing requires no preparation — your hands are already there. If invoking dictation requires looking down, moving your hand, or thinking about which key it was, you have added a cost that typing does not have, and you will stop using it within a fortnight.
The people who dictate daily all describe the same thing: they do not think about the shortcut. That is not a personality trait. It is a consequence of having chosen a key their hand already rests near.
What to avoid
| Avoid | Why |
|---|---|
| Anything with Cmd | Almost all taken, and Cmd+Enter sends in Gmail and many chat apps |
| Anything near Enter | You will send half a message. Everyone does this once |
| Single letter keys with one modifier | Your editor wants them. All of them |
| F1–F12 without a modifier | Media and brightness controls on most Macs |
| Anything your launcher uses | Raycast, Alfred and Spotlight claim the obvious ones |
| Anything your window manager uses | Rectangle, Amethyst and similar claim a lot |
| The same key as macOS dictation | Two dictation systems fighting. A surprisingly common cause of "nothing happens" |
What is usually free
- Right-hand modifiers on their own. Right Option or Right Command, if the app supports a bare modifier. Nothing else uses them and your hand is already there.
- The Globe (fn) key. On modern Macs this is a genuine modifier, it sits under your left little finger, and it is used by very little. macOS claims it by default, which a good dictation app can take over.
- F13 to F19. On a full-size keyboard, almost entirely unclaimed.
- Ctrl plus an unusual key. Ctrl is less contested than Cmd on macOS.
- A double-tap of a modifier. Double-tap Right Shift, for instance — fires nothing on a single press, so it collides with nothing.
Test it before committing
- Press the candidate in your editor With a file open. If anything happens, it is taken.
- Press it in your terminal Terminals pass many keys through to the shell, so a combination can be free in one app and taken in another.
- Press it in your browser Web apps register their own shortcuts. Gmail, Linear and Notion are the usual offenders.
- Press it in your chat app And check it is nowhere near Enter.
- Then set it, and restart the apps you tested Registration order matters; a stale claim can persist until a relaunch.
Push-to-talk, latched, or both
Most apps offer both and most people use both without thinking about it once the habit forms.
| Mode | Use it for | Watch out for |
|---|---|---|
| Hold to talk | Anything under about twenty seconds — replies, messages, notes | Holding a key for two minutes is genuinely uncomfortable |
| Double-tap to latch | Long dictations, prompts, drafts, brain dumps | Forgetting it is on. Some apps show an overlay for this reason |
A practical split: hold for anything you would type in one go, latch for anything you would have written a paragraph about. See push-to-talk vs always listening.
The habits around the shortcut
- Pause half a second after pressing before you speak. Voice activity detection needs a moment to decide speech has begun, and starting instantly clips your first word.
- Release a beat after you finish. The same problem at the other end, and it is why the last few words go missing.
- Click into the field first. Every time. The text goes where the cursor is.
- Keep your hand on the key. If you have to reach, the shortcut is wrong.
- Read it back before pressing anything else. Especially Enter.
When it stops working
| Symptom | Almost always |
|---|---|
| Nothing happens at all | Another app registered the shortcut first, or accessibility permission was not applied |
| It works everywhere except one app | That app claims the key |
| It stopped after an update | Something else took the key, or the permission needs the app relaunched |
| It fires when you did not mean it | The key is too close to something you press often |
| Text goes to the wrong window | The cursor was not where you thought |
The fix for the first four is the same: change the shortcut and relaunch. It takes thirty seconds and resolves most "dictation is unreliable" reports.
Questions
What is the best dictation shortcut on a Mac?
The Globe (fn) key, if your app can take it over — it is a dedicated modifier, sits where your hand already rests, and almost nothing else uses it. A bare right-hand modifier or F13–F19 are the next best options.
Why does my dictation shortcut do nothing?
Usually another app registered it first, or accessibility permission was granted while the app was running. Change the shortcut to something unusual, quit and relaunch, and try again before assuming anything is broken.
Should I use push-to-talk or a latch?
Both. Hold for anything under about twenty seconds, latch for long dictations. Holding a key for two minutes is uncomfortable, and a latch you forget about is its own problem — which is why apps show an overlay while it is on.
Can I use the same shortcut as macOS dictation?
You can set it, and you should not. Two dictation systems bound to the same key produce exactly the symptoms people report as a broken app. Give them different keys, or turn one off.