What "system audio" really means on macOS

On a Mac, "system audio" usually means the combined output of every app you're playing at once — mixed into a single stream and sent to your chosen output device. But people use the same phrase for three other things: the alert "system sounds" category in Sound settings, the one master volume level, and the "System Audio Recording" permission that lets an app capture what your Mac is playing. They're related, but they are not the same, and confusing them is why so many audio problems on macOS feel unfixable.

The term gets thrown around in support threads, screen-recording tutorials, and app settings, and it rarely means quite the same thing twice. If you've ever tried to "record system audio" and gotten silence, or wondered why you can't turn down one app "in the system," the tangle is almost always which of these four things you're actually touching. Let's separate them.

1. System audio as the mixed output of every app

This is the meaning that matters most. When several apps play sound at once — a call, a music player, a browser video, a notification — macOS doesn't keep them separate on the way out. Its audio engine mixes them into one combined stream and sends that single stream to your selected output device (speakers, headphones, whatever). That mixed stream is what most people mean by "system audio": the sum of everything your Mac is currently making noise with.

Two consequences fall out of this design. First, there is exactly one master level for the whole mix — the volume keys and the menu-bar slider move all of it together. Second, once apps are mixed down, macOS offers no public way to reach back in and grab one app's level. The operating system knows which process is producing sound, but it doesn't hand you a control surface for it. That's the entire reason there's no native Windows-style panel with a slider per app — a gap covered in why there's no Windows-style volume mixer on macOS.

2. "System sounds" — the alert category, not everything

Here's the first place the word trips people. In System Settings > Sound there's a section for Sound Effects, sometimes called "system sounds" or "UI sounds": the startup chime, the Trash empty, the screenshot shutter, notification alerts. This category has its own alert-volume slider and can even be sent to a different output device than your main audio. Someone will say "turn down system audio" when they mean these beeps specifically.

But system sounds are just one small input into the big mix from section 1. Turning the alert slider down quiets the chimes and does nothing to your music or your call. If your actual problem is that alerts blast over quiet audio, that's a balance issue between two streams, not a system-audio setting at all. The takeaway: "system sounds" is a narrow category, not all of your Mac's audio.

3. System audio as the master output level

Casually, "system audio" often just means "the volume" — the single level the F-keys and the menu-bar slider control. This is the master fader on your current output device. It's genuinely system-wide: everything in the mix rides up and down with it, in lockstep, at the same ratio.

That lockstep is the friction people run into. Take a call and turn the system down, and your music, your browser, and your alerts all duck by the same amount. There's no built-in way to say "lower the music but keep the call where it is," because at this layer macOS only exposes the one combined level. Setting a relationship between apps — this one at 30%, that one at 100% — is a separate capability the master control simply doesn't offer.

4. The "System Audio Recording" permission

The newest meaning, and the one behind a lot of confusion, comes from recording. If you've tried to capture what your Mac is playing — a call, a video, a stream — you've probably hit the fact that macOS historically had no built-in way to record its own output. The microphone records the room; it does not record the audio going to your speakers. For years the workaround was a virtual audio device that reroutes the mix so it can be captured.

That changed in macOS 14.4, when Apple added Core Audio process taps — an API that lets an approved app read the audio a Mac is playing, per process or for the whole system, without a virtual driver. macOS gates it behind a dedicated "System Audio Recording" permission, so here "system audio" means literally the playback an app is allowed to capture. This is why screen recorders and meeting tools now ask for that specific permission. It's the same underlying idea as section 1 — the mixed output — viewed through the lens of "who's allowed to listen to it."

How the four meanings line up

Same two words, four different things. Here's the quick map so you can tell which one a setting, a tutorial, or an error message is really talking about.

Why none of this gives you per-app volume

Notice what's missing from all four. The mix is combined before you can touch it. System sounds are one narrow slice. The master level moves everything together. The recording permission is about capture, not control. At no point does macOS expose a knob for "this app, this loud, independent of the rest." That capability — a separate level per application — is what per-app volume control means, and macOS has never shipped it.

To get it, software has to insert itself into the audio path. The classic route uses a virtual audio device: the app installs a software "output," macOS sends the whole mix through it, and the tool adjusts each app on the way past. That's how Background Music works — free and open source, at the cost of a heavier install. The newer route uses the same macOS 14.4 audio-tap framework from section 4 to read and adjust audio per process without routing everything through a separate virtual device first. That's the framework Fader is built on, which is why it needs macOS 14.4 or later.

The apps that add per-app control, honestly compared

Several tools fill the gap. They all deliver per-app volume; they differ in price, in what else they do, and in how fast you can reach the controls. An honest snapshot as of 2026:

Background Music is the free, open-source pick and a good one if you don't mind the virtual-device install. SoundSource is Rogue Amoeba's deep, polished toolkit — per-app EQ, routing, and effects well beyond volume, at $49 one-time. eqMac leads with equalization and adds volume on top. All of them genuinely control per-app audio; which is "best" depends on what you're trying to do.

Where Fader fits

Fader's angle isn't "we have per-app volume and they don't" — they do too. It's speed. You hit a toggle hotkey and your keyboard becomes the mixer: one letter column per app, ride the levels with letter keys, never leave what you're doing. No hunting through a menu-bar list for the right row. For the apps you adjust twenty times a day, that's the difference between owning a mixer and actually using it. It's a one-time $19.99, with a 3-day free trial and no account, on macOS 14.4 or later.

Bottom line

"System audio" on a Mac is really four things wearing one name: the mixed output of every app, the narrow "system sounds" alert category, the single master volume, and the "System Audio Recording" permission. Once you know which one a setting means, most macOS audio confusion clears up fast. And once you notice that none of them lets you set one app's level on its own, it's obvious why per-app control needs a dedicated app — and, if reaching that control in a keystroke matters to you, why Fader exists.