Voice dictation hotkey setup — picking a key that doesn't break your apps

Your hotkey choice is the most consequential setting in any voice dictation app. You'll press it hundreds of times a day. If you pick wrong, you'll fight conflicts in VS Code, IntelliJ, Photoshop, or whatever else you live in — and the friction will make you stop using voice altogether.

Here's the framework for picking a hotkey that just works.

The four properties of a good hotkey

Single key when possible. Combos like Ctrl+Shift+Space require coordinating multiple fingers. Single keys like Right Alt are a single thumb press.
Easy to reach without looking. Your fingers should land on it without leaving the home row. F12 is far; Caps Lock is close.
Not used by any app you care about. Check your browser, your editor, your team chat, your design tool.
Distinct from "press and hold for repeat" behavior. If you accidentally hold a key meant for one-shot input, you don't want it to spam.

The best choices in 2026

Right Alt — the recommended default

Single key, sits under your right thumb. Used by basically no application as a standalone key. Some keyboards label it "AltGr" — same behavior in Pithflow.

Conflict to know: on non-US keyboard layouts (German, French, Spanish), Right Alt is the AltGr modifier used to type the @ symbol, €, etc. If you use one of those layouts, AltGr-as-hotkey will interfere with normal typing of those characters. Pick something else.

Caps Lock — second choice

Caps Lock as a normal key is mostly useless in 2026 (turn it on accidentally, type angry email, get embarrassed). Repurposing it for dictation is a strict upgrade.

Setup tip: use Microsoft PowerToys → Keyboard Manager to first remap Caps Lock to itself, which actually disables the Caps-Lock function. Otherwise tapping it as a dictation trigger ALSO accidentally enables Caps Lock, and you'll TYPE LIKE THIS until you notice.

F-key (F1-F12) — third choice

F12 or F11 are the popular picks. Single key, reachable. The reach is longer than Caps Lock or Right Alt, but acceptable.

Conflict to know: some browsers use F11 for fullscreen and F12 for DevTools. Some chat apps use F1 for help. Test in each app you use.

Hold-to-speak vs tap-to-toggle

These are two different ways the hotkey can behave:

Hold to speak: press and hold, dictate, release. The app records only while held. Default in most tools.
Tap to toggle (hands-free): tap once to start, tap again to stop. Records continuously between taps. Used for long-form.

Pithflow lets you bind separate hotkeys to each behavior. Common setup: Right Alt for hold-to-speak (short messages), Caps Lock for hands-free (long writing sessions).

The bad choices

Ctrl+Space — the default that conflicts

Many tools (Pithflow's own default, Wispr Flow's, etc.) ship with Ctrl+Space because it works on every keyboard layout. But VS Code, IntelliJ, and most IDEs use Ctrl+Space for autocomplete. If you do any coding, change this immediately to a non-conflicting key.

F-keys with modifiers

Ctrl+F8, Shift+F10, etc. require two-finger coordination AND a long reach. Worst of both worlds.

Windows key combos

Win+H, Win+S, etc. are OS-reserved. Some can be overridden but it's fragile across Windows updates. Skip.

Dedicated programmable keys on fancy keyboards

If you have a keyboard with a "macro 1" key (some Razer, Corsair, Elgato Stream Deck), use that. But don't pick it as your primary if you ever use other keyboards — your muscle memory will break the moment you switch.

Per-app conflict checklist

Quick test for any candidate hotkey:

Press it in VS Code with no extension active — does anything happen?
Press it in Chrome on a webpage — does anything happen?
Press it in Slack while a message is being composed.
Press it in Word or Google Docs.
Press it in your file manager (Explorer or Finder).

If any of these intercepts the keystroke, the hotkey is a bad choice for daily use. Pick a different one.

The foot pedal escape hatch

For severe RSI users (or people who just like the option), USB foot pedals exist. Cost: $25-50. They register as a keyboard event and you can program them to send any keystroke — including your Pithflow hotkey.

Genuine zero-hand-effort dictation: foot pedal + speak. Especially powerful when paired with hands-free mode for 20-minute writing sessions.

Three setups for three users

The developer

Primary hotkey: Right Alt
Hands-free hotkey: Caps Lock (after PowerToys disables Caps-Lock-function)
Default tone: Code comment

The salesperson

Primary hotkey: Right Alt
Hands-free hotkey: F12
Default tone: Email (90% of your day is messages)

The writer (RSI cautious)

Primary hotkey: Right Alt OR foot pedal
Hands-free hotkey: Caps Lock
Default tone: Casual for drafts, Professional for finished pieces

Once you've picked: don't change

The biggest factor in voice-dictation adoption isn't which hotkey you pick — it's whether you pick one and stay with it for two weeks. Muscle memory beats every "ideal" choice. If you've been using Right Alt for a month, don't switch to Caps Lock because of a blog post. Pick once, commit, iterate the rest.