The remote-work
audio checklist, 2026.

Most bad call audio on a Mac is not a hardware problem. It is five or six settings, spread across macOS and the conferencing app, that nobody ever went through in order — so people fix the symptom with the volume key, over and over, for years.

This is that list, in the order that actually helps. The first four sections cost nothing. The last one is the only place a third-party tool is genuinely required, and it says exactly why.

1. Lock your devices, and split input from output

macOS lets you pick input and output independently, in System Settings → Sound. Use that.

• Output: whatever you actually want to listen through. Wired headphones or a USB interface if you have them; built-in speakers are fine if you are not also using the built-in microphone.
• Input: a dedicated microphone if you own one. The long-standing catch with Bluetooth headsets is that using their microphone switches the whole link into a low-bandwidth mode, and everything you hear gets noticeably worse for the duration of the call. Output on AirPods, input on a USB mic, sidesteps it.
• Check the app, not just the system. Zoom, Teams and Meet each keep their own device selection. macOS switching to a new device does not always mean the call app followed.

If you use speakers rather than headphones, echo cancellation is doing real work and it does it better when the speaker level is moderate. Turning your output up to compensate for a quiet caller makes the far end's experience worse, not better — fix it at the source instead, which is the next section.

2. Set the call app's own level — stop riding the system volume

This is the single change most worth making. Every major conferencing app has an output level of its own, separate from the macOS volume:

• Zoom: Settings → Audio → Speaker, with a test button and a level meter.
• Teams: Settings → Devices → Speaker.
• Google Meet: in-call settings, per device.

Set those so a normal speaking voice is comfortable with your system volume at roughly two-thirds. Now the system volume key is a master control you rarely touch, and "the caller is quiet" has a place to be fixed that does not also make your music louder.

This is also the setting to check when the reverse happens — a call that is painfully loud when everything else on the Mac is fine. There is a dedicated walkthrough for that in the Zoom levels article.

3. Noise suppression: on, but at the lowest setting that works

Every major app has free, built-in suppression, and macOS has its own Mic Mode on top:

• macOS Mic Mode — open Control Center while you are in a call and you get Standard, Voice Isolation and Wide Spectrum. Voice Isolation aggressively strips everything that isn't your voice. Wide Spectrum does the opposite and lets the room through, which is what you want if you are playing an instrument.
• Zoom — Settings → Audio → Suppress background noise, with Auto, Low, Medium and High.
• Teams — Settings → Devices → Noise suppression, with Auto, Low, High and Off.

Do not stack them at maximum. Aggressive suppression is a gate plus a model deciding what counts as speech, and the failure mode is your first syllable getting clipped, or your voice going underwater when you speak quietly. Start at Auto, raise it only if someone actually complains, and record a test call to hear what you sound like rather than guessing.

If keyboard clatter is the specific complaint, there is more detail in the keyboard noise article — including why buying a subscription noise-removal app is usually unnecessary in 2026.

4. Silence the interruptions you can silence for free

• A Focus for meetings. System Settings → Focus. Set it to turn on automatically when you share your screen, which is the moment notifications become genuinely expensive.
• The Alert volume slider. System Settings → Sound has an alert level separate from your main output. Most people have never touched it, and pulling it to a third makes every system sound stop being startling without affecting anything else.
• Per-app notification sounds. System Settings → Notifications lets you turn off the sound for one app while keeping its banners. Slack and Mail are the usual candidates — see the Slack article for the distinction between an app's own audio and a system notification sound, which are handled in different places and confuse a lot of people.

5. The one thing macOS still cannot do

Work through everything above and one problem is left standing: while a call is running, macOS gives you no way to turn Spotify down and leave the call alone. There is one volume, it is global, and it moves the call with everything else.

This is the gap a per-app mixer fills, and it is worth understanding what changed recently. Until 2024 the only way to do it was to install a virtual audio driver — a system-level component, an admin password, a restart, and on Apple silicon often a trip through Recovery Mode. Apple then shipped Core Audio process taps as a public API, which lets a signed app capture and adjust a specific process's audio entirely in user space. That is what modern tools in this category are built on, MixPill included.

Practically, for a remote-work setup, that means:

• Free: a fader, mute and a real dBFS meter for every app that is making sound, for unlimited apps, permanently. Drop the browser and Spotify, leave the call app alone.
• Pro: Auto-Ducking, which does that automatically whenever any app takes hold of an audio input; per-app EQ, which is genuinely useful for making a thin caller intelligible without touching your music; and per-app output routing.

The install requirement is one macOS permission — System Audio Recording, which is what process taps require — plus Accessibility only if you want global hotkeys. No driver, no restart, and your default output device stays exactly where it was. The setup, in full.

The five-minute version

1. System Settings → Sound: set output and input deliberately, and pull Alert volume down.
2. In your call app: set its own speaker level so a normal voice is comfortable at ~65% system volume.
3. Turn on noise suppression at Auto, not High. Record a test call.
4. Make a Meetings Focus and have it trigger on screen sharing.
5. Add a per-app mixer for the background apps, and set ducking to run automatically if you take more than a couple of calls a day.

Common questions