A hotkey conflict happens when two applications are configured to listen for the same keyboard shortcut. Both apps want the same combination — say, Option-Space — and when you press it, macOS sends the keystroke to whichever app is currently in focus. That app gets first claim on the key. If it recognizes it, the other app never sees the press.
This is especially common for users setting up dictation on a Mac, where choosing the right hotkey is part of the initial setup, and conflicts with existing system shortcuts or other apps can frustrate initial configuration.
How the system decides which app wins
The order is:
- The app in focus. macOS sends every keystroke to the active application first. If that app has registered the hotkey, it fires.
- Global listeners. Some apps register to listen for a hotkey even when they're not in focus. If the foreground app doesn't use that key, a background listener can still intercept it.
- The system. If no app claims the key, macOS may have a system-level action for it (screenshot, spotlight, etc.).
This means a conflict is not symmetric. If both apps listen in the background, the one that registered first usually wins. If one listens only when active and the other listens globally, the global listener can steal the key from the focused app.
The layered approach is efficient for macOS, which needs to route thousands of possible key combinations to the right places, but it creates surprises for users when an app stops responding to its own hotkey after you install something else.
Where conflicts come from in practice
Hotkey conflicts are common because:
- Common shortcuts are popular. Option-Space, Command-Shift-D, and a few others are reused across multiple apps because they're easy to remember and ergonomic.
- Shortcut documentation is scattered. When you install an app, you might not discover its hotkeys until you've already assigned that key to something else.
- Apps don't warn you. There's no system-wide registry in macOS that tells a new app "that hotkey is taken"; most apps just register whatever is in their settings without checking for conflicts.
- Many apps ship with default hotkeys. A fresh install of a new app comes with a set of default shortcuts already in its settings, and if one of those conflicts with your existing setup, you don't know until you try to use it.
Dictation apps are particularly prone to conflicts because they often choose a fast, memorable key combination like Option-Space or Control-Shift-D, which other productivity apps may also want to use.
How to diagnose one
The most obvious sign is that a hotkey stops working in one of your apps after installing another. The workflow:
- Notice the key isn't working. You press the hotkey and nothing happens (or the wrong app's action fires).
- Narrow down which app lost the conflict. Try the key in the affected app in isolation, and test it in the newer app you just installed.
- Check both settings. Look at the preferences or settings of both applications and find the exact hotkey binding they're both using.
How to fix one
If a hotkey stops working:
- Identify which apps use the key. Check the settings of the apps you've recently added or the one that stopped responding.
- Change one of them. Pick a different hotkey in one app — or disable the feature if you're not using it. If you're using dictation, you might change your dictation hotkey rather than disabling the competing app's feature.
- Test. Press the key in both apps and make sure the one you wanted to keep still works.
If you're setting up a new app's hotkey, avoid well-known combinations (Command-S, Command-Z, Option-Space) or check your other apps' settings first. Choosing a less common key combination up front saves debugging time later.