> ## Documentation Index > Fetch the complete documentation index at: https://docs.openwhispr.com/llms.txt > Use this file to discover all available pages before exploring further. # Hotkeys by platform > What you can bind on macOS, Windows and Linux, what each refuses, and the one-time setup some need. Each operating system lets apps see different keys, so what OpenWhispr can accept as a shortcut changes from one machine to the next. The default on every platform is the safe choice β€” it types nothing if it slips through β€” and if dictation is working there's no reason to change it. This page is the full map for when you want something else, or you've moved between machines and wonder why a key that worked on one is refused on the other. Every shortcut lives under **Settings** β†’ **Hotkeys** under **App**. ## At a glance A *modifier* is a key that changes what other keys do β€” Ctrl, Alt, Shift, Cmd, Option, Win and Super. Most shortcuts combine one with something else; the interesting cases are the ones that don't. | What you want to bind | macOS | Windows | Linux | | -------------------------------------------------------------------------------------- | --------------------------------- | ------------------------------- | ------------------ | | **Globe alone**
🌐 fn | **Yes** β€” the default | No | No | | **One right-side modifier**
Right Option Right Ctrl | **Yes** β€” Right Option | **Yes** β€” Right Ctrl | No | | **Two modifiers, no other key**
Ctrl + Win | No | **Yes** β€” the default | Varies β€” see Linux | | **Modifier + F-key**
Alt + F7 | Yes | Yes | Yes | | **Modifier + letter**
Ctrl + Shift + K | Yes | Yes | Yes | | **An F-key alone**
F8 | Yes β€” tap only | Yes | Yes | | **A mouse side-button**
Mouse 4 Mouse 5 | Needs setup | No | No | | **Caps Lock**
β‡ͺ Caps Lock | No | No | No | | **Several keys, one shortcut**
F8 and Ctrl + Win | Yes | Yes | Varies β€” see Linux | Everything marked No is refused when you try to set it, with a message saying why β€” never bound silently to a key that will never fire. ## macOS A Mac has the most ways to start dictation without typing anything: the **Globe** key, a right-side modifier on its own, or a side-button on your mouse. All three go through a small helper bundled with the app, because the normal shortcut system can't see them. **Globe is handled for you.** macOS has its own idea of what Globe should do β€” switch input source, show emoji. While OpenWhispr owns the key it sets that system option (**Press Globe key to**, under **System Settings β†’ Keyboard**) to do nothing, and puts your original choice back when it quits. You don't need to change it by hand, and if you change it yourself while the app is running, your choice wins. **Right-side keys work alone.** Right Option, Right Ctrl, Right Shift or Right Cmd on their own each make a good dictation key. Right Option is what setup suggests, and it's the fix for the one thing a Mac refuses (below). **Mouse side-buttons.** If your mouse has buttons 4 and 5 β€” the two on the side, on most mice β€” you can bind either by clicking it while the hotkey field reads **Listening…**. They need the **Accessibility** permission, which you've already granted if pasting works. ### What a Mac refuses A combination made only of modifiers β€” Control+Option, Command+Shift β€” is refused here and nowhere else: *"Two-modifier shortcuts are not supported on macOS. Use a right-side modifier on its own (e.g. RightOption), or add a regular key."* Do what it says: use **Right Option** on its own, or add a regular key so the combination becomes something like Control+Space. Globe can't be combined with anything else either β€” *"The Globe/Fn key can only be used by itself."* β€” and neither can a mouse button. ### Hold on a Mac Hold works with Globe, a right-side key, a mouse button and any combination that includes a modifier. The one shape it can't do is a single ordinary key such as F8 on its own, because macOS doesn't tell the app when a key like that is released. Pick one and switch to Hold and you'll see: *"Hold-to-talk needs a key macOS can see you release: Globe, a right-side key like Right Option, or a shortcut with a modifier. Tap works with any key."* ### Reserved on macOS The combinations you're most likely to bump into: **Cmd+Space** (Spotlight), **Cmd+Q**, **Cmd+W**, **Cmd+H**, **Cmd+M**, **Cmd+Shift+3**, **Cmd+Shift+4** and **Cmd+Shift+5** (screenshots), and **Cmd+Option+Esc** (Force Quit). The app refuses these with *"\[key] is reserved by the system"*. ### If Globe stops responding **Globe Hotkey Unavailable** means the helper that watches for Globe couldn't start. Your other shortcuts keep working. The helper restarts itself after your Mac wakes from sleep; if the message stays, quitting and reopening OpenWhispr gives it another try. ## Windows Windows is the most permissive platform. The default **Ctrl+Win**, any other two-modifier combination, and a right-side key on its own β€” Right Ctrl, Right Alt, Right Shift, Right Win β€” all work, because a small keyboard helper bundled with the app watches for keys the normal shortcut system can't see. Combinations with a letter or an F-key go through the normal route and work too. During setup OpenWhispr suggests **Right Ctrl** first, then Ctrl+Win. **If your keyboard uses Right Alt for accents or symbols** β€” the key is labelled AltGr on many layouts β€” you *can* bind Right Alt and it will work, but every accented character or symbol you type with it would also start or stop dictation. Use Right Ctrl instead. ### Hold on Windows Hold works with any dictation key. If the helper that watches for key presses is missing or fails, you'll see **Push-to-Talk native listener not available** and dictation runs in Tap until it's back. ### Reserved on Windows **Alt+Tab**, **Alt+F4**, **Ctrl+Alt+Delete**, **Ctrl+Shift+Esc**, **Win+L**, **Win+D**, **Win+E**, **Win+R**, **Win+S**, **Win+X**, **F5**, **F11**, **Home**, **End** and **Print Screen** are refused as reserved. **Win+H** is *not* refused β€” it's Windows' own voice typing shortcut, and binding it puts two dictation systems on one key. Avoid it anyway. ### If a key is already taken *"\[key] is already registered by another application."* means something else on your PC claimed it first. *"Could not register \[key]. It may be in use by another application."* is the same thing when Windows didn't say who. Pick another key, or quit the other app to find out which. ## Linux Linux is really four platforms, because OpenWhispr hands shortcut registration to your desktop when it recognises one β€” GNOME, KDE or Hyprland β€” and each has its own rules. Everything else goes through the normal shortcut system, with limits of its own. Two things are the same on all four: a right-side key on its own is refused (*"Right-side single modifier hotkeys are not supported on Linux."*), and the Globe key and mouse buttons are macOS-only. **Default: F8.** GNOME only accepts a shortcut that includes a regular key, so the usual Ctrl+Super can't be registered here and the app uses F8 instead β€” on Wayland and X11 alike. Shortcuts are registered as GNOME's own custom shortcuts, so they appear under **Settings β†’ Keyboard**, and GNOME refuses a key that's already used by one of your other custom shortcuts. Each OpenWhispr shortcut takes one key; **Add another hotkey** isn't offered. **Hold** works on GNOME 48 or newer with no setup, because those versions can tell the app when you release the key. Older GNOME can't, so Hold there needs the `input` group β€” see **Everything else** for the command. **Default: Ctrl+Super on Wayland, F8 on X11.** A modifier-only combination like Ctrl+Super works on Wayland, but only in Tap. On X11 it's refused β€” *"\[key] may be reserved by your desktop environment"* β€” so pick a combination with a regular key. F-keys work from F1 to F12 only. Each OpenWhispr shortcut takes one key. KDE tells you why a key was refused: *"already registered by another application"* when another program owns it, *"may be reserved by your desktop environment"* for a modifier-only combination. **Hold** works with any combination that includes a regular key. **Default: Ctrl+Super.** OpenWhispr writes its binds into your Hyprland config, so `hyprctl` must be on your PATH. It **claims** the combination you choose β€” any existing Hyprland bind on the same keys is unbound when it registers, and the settings page says so under the field. If the app can't write to your config you'll see **Hyprland keybinds will not persist**: they work now but won't survive a config reload. Make sure the file exists and is writable. A modifier-only combination works in Tap only. Each OpenWhispr shortcut takes one key. **Hold** works with any combination that includes a regular key. Plain X11 desktops, and Wayland desktops OpenWhispr doesn't recognise β€” Sway, Niri, COSMIC and the like. **Default: F8 in practice.** The app tries Ctrl+Super first, but a modifier-only combination can't be grabbed here, so it falls back to F8 and tells you. Super combinations are usually taken by the desktop too β€” *"\[key] may be reserved by your desktop environment"*. Pick a combination with a regular key. Unlike the three desktops above, each shortcut can hold several keys here. **Hold needs one-time setup.** For Hold the app reads the keyboard directly, which needs your user in the `input` group. You'll see **Hold to Speak needs setup** with the command: ```bash theme={null} sudo usermod -aG input $USER ``` Log out and back in afterwards β€” the change isn't picked up until you do. **On these Wayland desktops the shortcut only works while you're in an app running through XWayland.** XWayland is the compatibility layer that lets older-style apps run on a Wayland desktop. OpenWhispr runs through it itself, and a Wayland desktop only passes keystrokes to that layer while one of its windows has focus β€” so the hotkey works while you're in another XWayland app and goes quiet in a native Wayland app. Hold isn't affected, because it reads the keyboard directly. ## True everywhere * **Hold is for dictation only.** The voice assistant, translation and meeting shortcuts are always Tap, whatever key they're on. * **Hold gives up after five minutes** if it never sees you release the key, so a missed release can't leave a recording running forever. * **If your key can't be registered when the app starts** β€” another app got there first, or your desktop refused it β€” OpenWhispr tries **F8**, then **F9**, then **Ctrl+Shift+Space**, uses the first that works, and tells you: *Hotkey changed β€” "X" was unavailable. Using "Y" instead.* Your chosen key is kept and tried again at every launch, so once the conflict is gone it comes back on its own. A **Reset to \[key]** link under the field takes you back to the platform default whenever you've strayed from it. * **If you'd saved Hold and your current key can't do it**, the app quietly puts you back on Tap the next time it starts. The rules that apply to every shortcut on every platform β€” three keys at most, a letter or digit never on its own, one key per OpenWhispr shortcut β€” are in [Choosing a shortcut that works](/help/dictation/choosing-a-shortcut). ## Related * [Your hotkeys](/help/dictation/hotkeys) * [Hold or tap](/help/dictation/hold-or-tap) * [Choosing a shortcut that works](/help/dictation/choosing-a-shortcut) * [My hotkey doesn't work](/help/fix/hotkey-not-working) * [macOS](/platform/macos) * [Windows](/platform/windows) * [Linux](/platform/linux)