Make volume keys follow the device you are actually listening to

Make the volume and mute keys adjust your monitor speakers when you select that output, then return to macOS handling when you switch to headphones. The setup uses a matching audio device to decide both when BetterDisplay listens and which display receives the adjustment.

Before you begin

Use a connected monitor with speakers and already working ranged hardware volume through DDC, plus headphones that macOS can adjust normally. Volume and mute need their own support. Working hardware brightness or sound over the display cable does not establish either. If the monitor’s BetterDisplay volume slider does not change its actual speaker level, start with the hardware volume connection tutorial before changing keyboard preferences.

This worked example keeps native audio association off so the display’s volume controller remains DDC. Use a monitor with ranged volume and stateful mute for the full procedure. An up/down-only controller does not enable the matching-name fields by itself. If your monitor lacks hardware volume, use its supported speaker or audio-device method. Keyboard settings cannot add hardware volume support.

Pause playback before changing outputs or trying mute. Set a quiet level on the actual monitor or headphones before resuming. The app’s slider may show a saved or default value rather than the current hardware level.

If existing synchronization or automation changes volume during the test, pause that rule temporarily.

BetterDisplay must be running, and native keys need its offered system permission. You can inspect and use menu volume separately from that permission. A listening message or on-screen display (OSD) is feedback, rather than proof of an audible change.

Verify the monitor output and volume method

  1. Pause sound. In System Settings > Sound > Output, choose the actual monitor output. Apple’s output-selection instructions explain the available devices. Selecting an output and changing its native volume are separate from DDC speaker volume.
  2. Open Settings > Displays > [monitor] > Device Control > Volume Control…. Under Feature Availability, check Volume control and Mute control, then Controller. For this example, verify ranged Enabled volume, supported stateful mute and DDC Control. Keep Associate this display with an audio device that has native volume controls off. If a different controller owns volume, investigate that method rather than assuming the slider is DDC.
  3. Use the monitor’s own audio settings to establish a quiet level and known mute state. With playback still paused, establish a suitably low app setting within the verified volume range and check the actual monitor level again. Unmuting or adjusting volume while muted can restore an earlier app volume. Check that level while sound is paused. Resume a quiet test only when the actual result is safe.
  4. Open App Menu > [monitor] and make a small volume-slider adjustment. Confirm the actual speaker level changes. Pause again and test mute/unmute separately, verifying the returned level before resuming sound. Keep the existing Mute Method, Unmute Method and When Volume Reaches 0%… choices unless this test reveals a specific issue.

DDC mute can combine a minimum-volume write with a mute command. Its default unmute method restores the remembered volume before unmuting, and clears that saved previous-mute value. The configured minimum is not necessarily silence, and an adjustment while muted may first restore that earlier level. See Which level returns after mute before changing these methods.

Match this display to its audio output

  1. With the monitor still selected in macOS Sound Output, reopen Settings > Displays > [monitor] > Device Control > Volume Control…. Find Matching audio device name.
  2. Select Copy Current Device Name without holding a modifier. Confirm the field contains the monitor output’s actual name, rather than headphones or the Mac’s speakers. This does not change the system output or enable native association. The copied value saves immediately. If you edit the text manually, press Return or move focus to another field to save. Escape cancels an unfinished edit.
  3. Open Settings > Displays > [monitor] > General Settings and check Keyboard control affects this display. It is on by default. Check other controllable displays for the same matching override so one output will not unintentionally match several displays.

A blank matching field uses the display’s original product name, which can differ from its renamed label in BetterDisplay. A nonempty value supports partial matching against the current output’s name or identifier. Use a distinctive value. Names differing only in digits or spacing can still match together.

For an ambiguous name, hold Option while selecting Copy Current Device Name to copy the current output’s UID, then retest both outputs. This can help distinguish devices, but a UID is not an unconditional guarantee of one exact target. Several eligible displays can match the same output. See matching without native association.

Listen only for a matching display output

  1. Open Settings > Keyboard and enable Listen to native audio keys if needed. It is on by default.
  2. If offered, open Set up Accessibility Permissions… on macOS 26, or Set up Device Control and Data Access… on macOS 27 and later. Follow BetterDisplay’s sheet. On macOS 26, Apple’s Accessibility instructions use System Settings > Privacy & Security > Accessibility. Restart BetterDisplay if it reports Accessibility Configured - App Restart Needed. See permission setup.
  3. Open Native Audio Key Settings…. Under App should assume control over native audio keys when, select Current audio device matches a controllable display's name. This default choice leaves a nonmatching headphone output to macOS even while the monitor stays connected.
  4. Keep Handle devices with native volume control on, its default. Keep Leave mute key under OS control off, its default, to use the monitor’s tested DDC mute. Preserve your existing fine-scale choice.

The engagement policy decides when BetterDisplay handles the keys. Handle devices with native volume control provides native-volume fallback when the app cannot handle a key through ranged display volume or stateful mute. It does not replace an already handled display command or fix a failed hardware write. Relative-only commands can also be followed by native fallback, so this example uses a verified ranged DDC controller.

Native Audio Key Settings configured for display-name matching, with native-volume devices handled and mute and fine-scale overrides off.

Configure native audio keys to engage when the audio device matches a controllable display. This session has no matching DDC audio output.

Send handled keys to the matching display

  1. Close Native Audio Key Settings. In Settings > Keyboard > Volume Control Affects:, select Display with the same name as current audio device. This is the default destination, separate from the listening policy above.
  2. With the monitor selected as the macOS output and a verified quiet unmuted level, press volume down once without modifiers, then up once. Check actual monitor sound. Test mute/unmute separately with playback paused around the transition and verify the returned quiet level before resuming. Avoid holding a key during the first test.
  3. Pause playback and select the actual headphones in System Settings > Sound > Output. Establish a quiet headphone level before resuming. Wait for the output change to settle. In BetterDisplay’s Keyboard pane, check that it is disengaged from native volume and mute keys because no controllable display matches that headphone output.
  4. Press volume down/up and mute/unmute individually. Check actual headphone sound and confirm the monitor’s hardware volume/mute remains unchanged. Repeat after returning to the monitor output.

Keyboard preferences save without Apply. Output changes refresh the listening policy. Wait for the change to settle before pressing keys. If a headphone name or UID also matches a configured display, the app may remain engaged, so correct that match before drawing conclusions about the fallback.

Keyboard Settings with all four Volume Control Affects choices and display-name matching selected.

Volume keys target the display matching the current audio device’s name. VIA USB Dongle is the nonmatching output in this session.

Check the result

Repeat the same quiet test in both directions. For the monitor output, BetterDisplay should handle keys for the matching hardware controller and actual monitor speakers should respond. For the nonmatching headphones, BetterDisplay should disengage from audio keys and the headphones should respond through macOS. Move the pointer to a different screen: with the matching destination selected, the output match should remain the deciding factor.

Check volume and mute independently, including the actual level after unmute. Check the actual sound and hardware settings. An OSD, moving slider or listening label alone does not confirm success. A disabled macOS output-volume slider can coexist with working DDC monitor volume because those are different adjustment paths.

Troubleshooting

When native audio association is appropriate

Associate this display with an audio device that has native volume controls replaces the display’s hardware volume/mute method with the named macOS device. It does not select that output in System Settings. Use it only when that actual device supports writable native volume. Native mute is a separate capability.

The field then becomes Associated audio device name. A Native label identifies the chosen method, even if the device is missing or cannot be adjusted. Native association resolves names before UIDs and does not reject ambiguous matches, so neither a copied UID nor an empty field guarantees the intended target. Use the native association reference for that separate workflow.

Undo the test setup

  1. Pause playback and release the keys. Set the system output and hardware volume to your preferred quiet levels.
  2. To leave native audio keys entirely with macOS, turn Listen to native audio keys off. BetterDisplay’s menu sliders remain available. To keep using BetterDisplay, choose your preferred engagement policy and Volume Control Affects: destination.
  3. Revert the matching-name field and native association if you no longer want them. Clear the matching field to use the monitor’s original product name. Re-enable any synchronization or automation you paused if you still use it.

Changing keyboard settings or removing permission does not restore hardware volume levels. Adjust the actual monitor or headphones separately.

Additional information

This section explains licensing and platform requirements for this workflow.

Features requiring Pro license

The native volume/mute-key policies, matching destination and shared Volume Control preferences used here do not require Pro. Other controller features or group synchronization retain their own requirements.

Platform compatibility

The documented app requires macOS 26.3 or later. All features described on this page are available on both Apple silicon and Intel Macs, subject to suitable monitor/audio capabilities, a working DDC transport and the offered native-key permission. Native audio volume and mute capabilities are separate. No Screen Recording permission is needed for this workflow.