Mac keyboard shortcut conflicts: how to find what stole your keys
A shortcut you have pressed a thousand times does nothing. No error, no beep, no dialog — the key just falls into a hole. Nine times out of ten nothing is broken: a Mac keyboard shortcut conflict has quietly handed that combination to something else, and macOS will never tell you what.
This is the part Apple's own documentation skips. There is a warning badge in System Settings, but it only sees Apple's shortcuts, and almost every real collision involves an app Apple has never heard of. So the useful skill isn't "change a conflicting shortcut" — it's working out who is holding the key in the first place.
Why a Mac keyboard shortcut conflict is invisible
Keystrokes are offered to several layers in order, and the first layer that claims one consumes it. Everything downstream simply never hears the key — which is why nothing errors out.
| Layer | Examples | When it wins |
|---|---|---|
| System shortcuts | Spotlight, Mission Control, screenshots, input sources | Almost always, wherever you are |
| Global hotkeys registered by apps | Raycast, Alfred, CleanShot, clipboard managers, window tools | Anywhere, whichever app is in front |
| App menu shortcuts | ⌘S, ⌘W, an app's own bindings | Only while that app is frontmost |
| App Shortcuts you created | Your custom menu-command bindings | Only while that app is frontmost, and only if the menu title matches |
Two consequences fall out of this. First, a global hotkey beats a menu shortcut even inside the app that owns the menu — install a launcher on ⌘K and the ⌘K in your editor stops responding. Second, when two apps both register the same global hotkey, which one answers is not something you can rely on. That is why a shortcut can work for eight months and break the day you install an unrelated utility.
Step 1: rule out macOS itself
Open System Settings → Keyboard → Keyboard Shortcuts. Walk the sidebar categories — Mission Control, Spotlight, Input Sources, Services, Function Keys — and look for a warning icon, which macOS shows next to shortcuts that collide with each other. Double-click any shortcut to type a new one.
The classic here is Control-Space. It is Apple's default for Select the previous input source, and it is also what a long list of editors and IDEs expect for autocomplete. If you have ever added a second keyboard layout, that combination stopped belonging to your editor at that moment. Turn the input-source shortcut off in that pane and it comes back.
The Services category is worth a slow scroll too. Services inherit shortcuts from apps you installed years ago, they apply system-wide, and nobody ever looks at them.
If the pane has become a mess, Restore Defaults sits at the bottom left. It resets Apple's shortcuts only — your third-party hotkeys are untouched, which in this context is exactly what you want.
For a full dump you can read the same data from the command line:
defaults read com.apple.symbolichotkeys AppleSymbolicHotKeys
It is dense, keycode-based output, but it is authoritative when the UI and reality disagree.
Step 2: audit the apps that grab keys globally
If macOS is clean, the holder is a running app. There is no system-wide registry to consult, so this is a manual sweep — and it is short, because only a handful of categories register global hotkeys at all:
- Launchers — Raycast, Alfred, LaunchBar, Spotlight replacements
- Clipboard managers and snippet/text-expansion tools
- Screenshot and screen-recording apps
- Window managers and switchers
- Note-capture tools with a quick-entry panel
- Password managers with an autofill hotkey
- Meeting apps — Zoom, Teams and Slack all claim mute/screen-share chords
- Remappers — Karabiner-Elements, BetterTouchTool, Hammerspoon, which sit below everything above and can swallow a key before any app sees it
Open each one's preferences and write the hotkeys down. Do it once, keep the list, and you will diagnose the next conflict in thirty seconds instead of an hour.
A faster shortcut to the answer: quit suspects one at a time and retest. The moment the key comes back, you have your culprit. Start with whatever you installed or updated most recently — that is nearly always it.
Step 3: match the symptom to the layer
| What happens | Most likely owner | Where to look |
|---|---|---|
| Nothing at all, in every app | A global hotkey, or a remapper | Step 2 sweep |
| Nothing in one app, fine elsewhere | That app's own binding, or a menu-title mismatch | The app's settings; App Shortcuts |
| The wrong panel opens | Two global hotkeys on one chord | Step 2 sweep |
| Works, then stops after an update | A newly registered hotkey | Whatever you just updated |
| Only tiling/window keys fail | Fn/Globe key or Move & Resize | Tiling shortcuts not working |
| The menu item is greyed out | Not a conflict — the command is unavailable right now | Nothing to fix |
That last row matters. A greyed-out menu item is not a stolen shortcut, and people burn afternoons on it.
How to pick shortcuts that stay yours
Once you know how crowded the space is, the fix is mostly prevention:
- Leave the ⌘ range alone. Single-modifier Command chords are where every app's menus live. It's the densest neighbourhood on the Mac.
- Prefer Option. Bare ⌥ chords are used far less by apps, and macOS claims very few of them.
- Three modifiers, or one weird key. ⌃⌥⌘ combinations are almost never taken. So are ⌥ plus a key nothing else wants — Tab, backtick, Space.
- Register the important thing last. If two tools genuinely need the same key, the one you launch later tends to hold it — but treat that as a workaround, not a plan.
This is also why the apps we build lean on Option.
Let's Switch puts window switching on ⌥Tab and same-app
cycling on ⌥backtick, so it sits beside Cmd-Tab instead of fighting it,
and esc always backs out. Let's Tile summons its grid with a
single shortcut that is fully rebindable — one key to move somewhere
quiet if it ever collides, rather than a dozen per-layout chords each
with its own chance of clashing.
Frequently asked questions
Is there a tool that lists every shortcut on my Mac? Nothing built in. Third-party conflict scanners exist and can read running apps' menus plus your system shortcuts, but no tool sees every privately registered global hotkey, so the manual sweep in step 2 is still the reliable method.
Why does my shortcut work in some apps but not others? Because menu shortcuts are per-app and only apply while that app is frontmost. If it fails in exactly one app, that app has its own binding on the combination.
I changed a shortcut and the old one still fires. Some apps read their hotkeys once at launch. Quit and reopen the app — and, for macOS's own shortcuts, log out and back in.
Can two apps share one shortcut safely? Only if at most one of them registers it globally. Two global registrations on the same chord is a coin flip, and the coin gets re-tossed every reboot.