Does sample rate matter for per-app audio on Mac?

For per-app volume and routing, sample rate almost never matters. macOS Core Audio resamples every app to a single output-device rate before it mixes them together, and changing one app's volume is just a gain multiply — an operation that doesn't care whether the stream is 44.1 kHz or 48 kHz. Set the device rate once in Audio MIDI Setup, forget it, and control your apps. Sample rate only becomes a real concern in three narrow cases, none of which involve turning one app down.

It's a fair question to ask, because on Windows and in pro audio circles sample rate gets talked about a lot. So people installing a per-app mixer on a Mac reasonably wonder: do I need to match sample rates? Will resampling hurt quality? Does controlling Spotify separately from a call somehow degrade one of them? The short answer is no — and understanding why takes about two minutes.

What sample rate actually is

Digital audio is a stream of measurements, or samples, taken many thousands of times per second. The sample rate is how many per second: 44.1 kHz (44,100 samples per second) is the CD standard and what most music files use; 48 kHz is the standard for video, most Mac hardware, and conferencing. Higher rates like 96 kHz or 192 kHz exist for recording and mastering, where the extra headroom is useful before the audio is mixed down.

The key thing for a Mac user: your output device — headphones, speakers, an interface — runs at one sample rate at a time. Everything that reaches it has to be at that rate. That single fact is what makes per-app sample rate a non-issue.

How macOS handles it: one device rate, everything resampled to fit

macOS mixes audio at the system level through Core Audio. There is one active output device, and it has one current sample rate, which you can see and set in Audio MIDI Setup (Applications → Utilities). When several apps play at once — a 44.1 kHz song in Music, a 48 kHz video call, a browser tab somewhere in between — Core Audio resamples each stream on the fly to the device's rate, then sums them into one mix and sends that to the hardware.

In other words, macOS already does the sample-rate conversion for you, every time, whether or not you run a mixer. A per-app volume app doesn't add a conversion step or change which rate wins. It adjusts each app's level inside that existing pipeline. There's no "matching" for you to do and no mismatch to fix.

Notably, Apple's own Music app doesn't auto-switch the device rate to match each track, so a 44.1 kHz song played while the device sits at 48 kHz is resampled by macOS in real time. This is normal, it has been true for years, and for everyday listening it's transparent. It's the same mechanism a per-app mixer lives inside.

Why volume is sample-rate independent

Here's the part that settles the question. Changing an app's volume means multiplying every sample by a number between 0 (silence) and 1 (full). Set an app to 30% and each sample is scaled to 0.3 of its value. That math is identical at 44.1 kHz, 48 kHz, or 192 kHz — there are simply more or fewer samples per second getting the same treatment. Gain doesn't interact with sample rate at all.

The same holds for routing an app to a different output. Sending one app's stream to headphones and the rest to speakers changes where the audio goes, not how many samples per second it carries. If the two devices run at different rates, Core Audio resamples for each — exactly as it would without any routing tool. So a keyboard-driven mixer like Fader, which rides per-app gain and can route apps to different devices, sits entirely on top of the sample-rate handling macOS already does. It doesn't touch it, and it doesn't need to.

When sample rate genuinely does matter

To be fair, sample rate isn't meaningless — it just doesn't matter for the per-app volume and routing job. There are three real cases where it does, and it's worth knowing them so you can tell them apart from the everyday situation.

The one that trips people up in a per-app context is the Aggregate or Multi-Output Device. If you build a combined device to send audio to several outputs at once, every device inside it has to run at the same sample rate, or you get glitches, drift, or a device that won't assemble. That's a property of aggregate devices themselves, not of per-app volume — but since some routing setups lean on them, it's the place you'll actually meet a sample-rate rule. If you go that route, read what aggregate audio devices are and when you need one.

Does resampling hurt quality?

For normal listening, no — not in a way you'll hear on headphones or speakers during calls, music, and video. Core Audio's real-time sample-rate conversion is good, and the difference between, say, a 44.1 kHz song resampled to 48 kHz and the same song at its native rate is inaudible in ordinary use. The people who care are audiophiles chasing bit-perfect playback and engineers who want no conversion in a mastering chain; they set the device rate deliberately and use players that lock it. If that's you, you already manage sample rate by hand and a per-app mixer doesn't change your approach. For everyone else, it's a solved problem you never have to think about.

So what should you actually set?

Leave the output device at whatever it defaults to — usually 48 kHz on a Mac, or your interface's native rate. Open Audio MIDI Setup only if you have a concrete reason to change it (a recording session, or matching a high-resolution file). For per-app volume, muting, and routing, the rate is irrelevant: pick your apps, set their levels, and let macOS handle the conversion underneath. If the whole idea of a device-level "one rate for everything" is new to you, the background on why macOS works this way is in what a virtual audio device is and whether you need one.

Bottom line

Sample rate does not matter for per-app audio on a Mac. macOS resamples every app to one device rate before mixing, and adjusting an app's volume is a gain change that's identical at any rate. The only places sample rate bites are aggregate devices, bit-perfect playback, and DAW recording — none of which is the same job as turning one app down. So if you want per-app volume and routing, don't overthink the numbers. Set the device rate once, then control your apps. Fader is built to make that control instant — from the keyboard, without a menu — while macOS quietly handles the sample-rate math it was already doing.