Why your Mac's volume keys have stopped working

Silent volume keys almost always come down to one of five things: a Multi-Output Device selected as your current output, a remapping tool like Karabiner-Elements intercepting the keys, a Bluetooth keyboard with a dropped low-latency connection, function-key behaviour toggled in System Settings, or a media-control app capturing the system media-key event.

None of these are hardware failures, and none of them need a restart to fix. Each one has a distinct symptom, so work through them in order below rather than guessing: the first two are the most common, and each section tells you exactly what to check.

Is a Multi-Output Device the reason your volume keys do nothing?

Check this first if the keys stopped working right after you set up a Multi-Output Device in Audio MIDI Setup, or if you have two speakers or a set of AirPods playing the same audio at once. A Multi-Output Device is not a real speaker with its own volume; it is a wrapper macOS builds to send one stream to several real outputs at the same time. Your volume keys, like the menu bar slider, need a single volume to change, and a Multi-Output Device does not have one. We cover the full mechanism, and the two free workarounds, in why your Mac's volume slider greys out on a multi-output device: the short version is that macOS disables the control rather than guess which of the grouped devices you meant.

Is a remapping tool like Karabiner-Elements intercepting the keys?

If your output is a single, normal speaker or your built-in Mac speakers, and the keys still do nothing, a key-remapping tool is the next most likely cause. Karabiner-Elements, BetterTouchTool, and similar utilities work by sitting between your keyboard and macOS, watching every keystroke before the system does anything with it. A rule that remaps F11 or F12 to something else, even one added months ago and forgotten, silently swallows the volume press.

Open System Settings, go to Keyboard, then Keyboard Shortcuts, and look through every category in the left-hand list for anything bound to F11 or F12. Then quit the remapping tool completely, not just close its window (these tools run as a background process that keeps working after the window closes), and test the keys again. If they work with the tool closed, go back into that tool's own settings and remove or change the conflicting rule.

Has your Bluetooth keyboard lost its low-latency HID connection?

This one has a specific symptom: you can still type normally, but the volume, brightness, or play/pause keys do nothing. A Bluetooth keyboard sends two separate kinds of signal, standard keystrokes on one connection and media-key presses as a separate consumer-control report, and the two can fall out of sync. The keyboard shows as connected because typing still works, but the media-key channel has quietly dropped.

Fix it by forcing both connections to re-establish. Open System Settings > Bluetooth, click the info button next to the keyboard, and choose Forget This Device. Turn the keyboard off and on, then pair it again from scratch. A plain disconnect-and-reconnect sometimes clears it too, but a full forget-and-re-pair is the more reliable fix if that does not hold.

Is the Fn or Globe key stuck, changing what F11 and F12 send?

System Settings > Keyboard > Keyboard Shortcuts has a toggle called Use F1, F2, etc. as standard function keys. With it off, which is the default on Apple keyboards, F11 and F12 send their printed volume glyph directly. Switch it on and every function key reverts to its plain F-key code, so you have to hold Fn and press F11 or F12 to get volume instead. If this setting changed, intentionally or by an accidental click, the keys will feel completely dead until you either flip it back or start holding Fn.

A physical cause produces the identical symptom: a Fn or Globe key that is mechanically sticking, common on keyboards that have collected dust or been through a spill, can hold the modifier down without you touching it. Every function-key press then behaves as though Fn is held, which flips F11 and F12 between volume and plain function-key output unpredictably. Press the Fn key firmly a few times and see if the behaviour becomes consistent again.

Are other apps capturing the media-key event before macOS does?

Volume, play/pause, and skip-track presses are broadcast as a system-wide event that any app with the right permission can listen for and act on, and only one listener gets to respond first. Remote-control apps, streaming-deck style utilities, and some browser extensions built for music services request exactly this permission so they can react to your media keys. If one of them is running in the background, it can quietly take the volume key press for itself and never pass it on to macOS.

Open System Settings > Privacy & Security > Accessibility and Input Monitoring, and look for anything you do not recognise or do not currently need. Quit any recently installed remote-control app or media-key utility one at a time, testing the volume keys after each, until you find the one responsible. Removing its permission, rather than just quitting it, stops it from grabbing the keys again after your next restart.

For every option available on a Mac, see Apple's own guide to sound output settings.

Frequently asked questions