Per App Volume Control on Mac

Windows has a volume mixer built into the taskbar. macOS does not. Here is how to get individual app volume sliders on your Mac without overpaying.

Why Does macOS Lack a Per-App Volume Mixer?

macOS routes all application audio through a single system volume control with no native way to adjust individual app volumes. Apple's audio architecture treats all apps equally at the output stage, providing only a master volume slider. Windows introduced per-app volume mixing in Vista (2007), but macOS still lacks this feature in 2026.

The absence of a per-app volume mixer forces Mac users to adjust volume within each application individually. Spotify has its own slider, Discord has its own slider, and games have their own audio settings. Switching between apps to balance audio levels during a stream or voice call is tedious and breaks workflow.

Third-party developers have filled this gap with tools that intercept app audio at the system level. LitLink Pro uses Apple's Process Tap API to provide per-app volume sliders in a single interface, giving Mac users the volume mixer that macOS should have included years ago.

How Does LitLink Pro Compare to SoundSource and Background Music?

LitLink Pro ($29) offers per-app volume control with per-app EQ and output routing through the Process Tap API. SoundSource ($49) provides per-app volume sliders in a polished menu bar interface with system-wide EQ. Background Music is free and open-source but only handles volume, lacks EQ, and has not been updated regularly. LitLink Pro balances features and price.
LitLink Pro
$29 — volume, EQ, routing
SoundSource
$49 — volume, EQ, effects
Background Music
Free — volume only
LitLink Pro API
Process Tap (native)
SoundSource API
Audio driver extension
Background Music API
Virtual audio device

SoundSource comes from Rogue Amoeba, the same company behind Loopback and Audio Hijack. Users already invested in Rogue Amoeba's ecosystem may prefer SoundSource for consistency, but the $49 price is $20 more than LitLink Pro for comparable per-app volume and EQ features.

Background Music works well for basic volume control but relies on a virtual audio device that can conflict with other audio tools. Users running soundboard setups for Discord sometimes find that Background Music's virtual device competes with BlackHole or other routing tools, creating audio conflicts that LitLink Pro's Process Tap approach avoids entirely.

What Can You Do with Per-App Volume Control?

Per-app volume control lets users lower Discord notification sounds while keeping game audio loud, reduce Spotify during a podcast recording without pausing it, balance browser audio against a DAW, or mute individual apps without affecting others. The control applies in real time without switching between application windows.

Streamers benefit the most from centralized volume control. During a live stream, adjusting the balance between game audio, alert sounds, and music requires touching multiple app settings without per-app control. LitLink Pro consolidates these adjustments into a single panel, and the per-app audio routing capability lets streamers send each source to a different destination simultaneously.

Musicians working with DAWs and reference material can keep a YouTube tutorial at low volume while their DAW runs at full level, all without adjusting the master volume that affects both. The per-app EQ in LitLink Pro adds another layer, allowing users to shape each app's audio profile independently. LitLink Pro extends per-app control beyond volume to include frequency shaping through a parametric EQ for each application on Mac that adjusts tonal balance independently.

How Do You Set Up Per-App Volume Control on Mac?

LitLink Pro displays every running application that produces audio in a single list. Each app gets a volume slider, an EQ toggle, and an output device selector. Drag any slider to adjust that app's volume independently. Changes take effect instantly with no latency, no restart, and no Audio MIDI Setup configuration needed.

Background Music requires users to set it as the system output device in System Settings, then use its own interface to control individual app volumes. This virtual-device approach means all audio passes through Background Music first, which can introduce compatibility issues with professional audio interfaces.

LitLink Pro's Process Tap approach intercepts audio at the process level without rerouting the entire system output. Users keep their preferred audio device as the system default while LitLink Pro handles per-app adjustments transparently. The same technology powers the full LitLink Pro feature set including routing and EQ.

Does Per-App Volume Control Affect Audio Quality?

Per-app volume control through the Process Tap API introduces no measurable audio quality degradation. The volume adjustment happens digitally within the system audio pipeline before reaching the output device. Bit depth and sample rate remain unchanged. Virtual-device approaches can theoretically add latency from the extra routing hop, but Process Tap operates directly on the audio stream.

Audiophiles concerned about signal chain purity will appreciate that LitLink Pro does not insert a virtual audio device into the path. The audio flows from the application through the native macOS audio stack with only a volume coefficient applied at the process level. This differs from virtual-device tools that capture, process, and re-emit audio through a synthetic device.

Professional users working with high-sample-rate audio (96 kHz or 192 kHz) in DAWs can use LitLink Pro's per-app volume to manage other applications without affecting their DAW's audio pipeline configuration. The Mac volume mixer functionality remains independent of each application's internal audio processing.

Marcel Iseli DJing
Marcel Iseli

Indie Developer · DJ · Producer

LinkedIn

Marcel Iseli is an indie developer, DJ, and music producer with over 20 years behind the decks and in the studio. Rooted in hip hop culture, he collects drum machines, samplers, and vintage audio gear. LitPads grew out of that obsession: decades of triggering samples on hardware led him to build the software equivalent he always wanted.