How to route an app to a USB audio interface on a Mac

The direct answer: a USB audio interface shows up on your Mac as an ordinary Core Audio output device, but macOS can only send all audio to one output at a time. Pick the interface in System Settings → Sound → Output and every app moves to it at once. To route a single app to the interface while everything else stays on your speakers or headphones, you need a per-app routing app such as SoundSource or Fader, which assigns an output device to each app on its own.

This is the setup behind a lot of home studios and desks: a Scarlett, a Volt, an SSL, a MOTU, some Behringer box feeding a pair of monitors, and you want one specific app — a DAW, a media player, a browser tab of reference tracks — running out of the interface while Slack pings, calls, and system alerts stay on the laptop speaker or your headphones. It sounds like it should be a checkbox somewhere. On a stock Mac, it isn't.

First, the good news: the interface is just another output

You almost never need special software to make a USB interface work on a Mac. The great majority of modern interfaces are class-compliant, meaning macOS drives them through its built-in Core Audio support (Apple's AppleUSBAudio driver) the moment you plug them in. No installer, no kernel extension — the device just appears in System Settings → Sound as an output (and an input) you can select like any other.

A few units still ship a vendor driver, but it's usually there for extra features — a software mixer, higher channel counts, lower-latency modes — not for basic playback. Audio out of the box works class-compliant on almost everything sold today. So the interface isn't the hard part. The hard part is that macOS treats it as the one place all sound goes.

Why choosing the interface moves everything

macOS has a single active output device. When you select the interface in the Sound menu, the system redirects the whole audio stream to it — Spotify, Zoom, notifications, YouTube, the works. There is no native panel that says "route Logic to the interface, keep everything else on the MacBook speakers." That single output rule is the same wall behind switching one app's output device without unplugging anything: the system moves in one block, per app is not a concept it exposes.

For some people that block move is fine — plug in the interface and everything comes out of the monitors, done. But the moment you want the interface reserved for one app while calls, chat, and alerts stay somewhere else, you've left what macOS can do on its own.

The free path, and exactly where it stops

There's a partial free route, and it's worth knowing so you don't buy something you don't need. A handful of pro apps carry their own output picker. DAWs are the big one: Logic, Ableton Live, Pro Tools, Reaper and friends let you choose an audio device inside the app's audio preferences, independent of the macOS system output. So a common studio split is genuinely free:

1. Connect the interface. 2. In your DAW's audio settings, set the output device to the interface. 3. Leave the Mac's system output on your speakers or headphones. The DAW now plays through the interface and monitors; everything else — browser, calls, alerts — stays on the system output. If your one app is a DAW, you may be done here with nothing installed.

The ceiling is obvious the second your "one app" isn't a pro tool. Spotify, Safari and Chrome, Apple Music, VLC, most media players, every conferencing app, and all system sounds have no output picker at all. They inherit the system default and go wherever it points. You can't send just Chrome, or just a media player, to the interface for free — there's no setting to do it. That gap is exactly what a per-app routing app fills.

The set-it-once path: a per-app routing app

A per-app routing app does at the OS audio layer what a DAW does for itself, but for any app: it assigns each app its own output device that holds regardless of the system default. You keep the system output on your everyday device, add one rule — this app → the interface — and leave it. Because the assignment lives with the app, it reapplies when the interface reconnects instead of snapping back to the system output.

SoundSource from Rogue Amoeba is the deep option. It routes individual apps to different output devices, adds per-app EQ and effects, and version 6 (December 2025) expanded its device handling with grouped outputs and an Audio Devices window. It's a one-time $49 for a single Mac ($25 to upgrade from an older version). Fader does the per-app output routing in a plain list — pick the interface as the output for a given app and it sticks across restarts and reconnects — for a one-time $19.99, and it rides per-app volume from your keyboard in the same app, so you can trim the app feeding your monitors without hunting for a slider. Background Music, the popular free and open-source option, is worth naming so you don't install it for the wrong job: as of 2026 it does per-app volume but keeps every app on one system output — it does not route an app to a separate device like your interface. Here's how the options line up for this exact task.

How to set it up with Fader

The steps are the same shape in any per-app router; here's the Fader version:

1. Plug in the interface and confirm it shows in System Settings → Sound as an output. 2. Leave the system output on your usual device — laptop speakers, headphones, desk monitors, whatever the rest of your Mac should use. 3. In Fader, find the app you want on the interface, and set its output device to the interface. 4. Play something from that app. It comes out of the interface; everything else keeps following the system output. The assignment persists, so unplugging the interface for the day and reconnecting it later re-applies the route instead of leaving the app stranded on the wrong device.

If you want the reverse — the interface as your main output and one chatty app peeled off onto the laptop speaker — the same tool does that too; you're just choosing which app carries the non-default device. And if you need two apps on two devices at the same time, that's the broader case covered in using two audio outputs at once, per app, on a Mac.

A note on latency and the interface's own controls

Routing an app to the interface changes where the audio goes, not the interface's job. If you're monitoring a live input — a mic or instrument through the interface — you'll still want the interface's own direct/low-latency monitoring for the input path; a routing app handles playback from apps, which is the part macOS won't split for you. And the interface's hardware volume knob still governs the analog output level; per-app volume in a mixer rides the digital level of each app before it reaches the device. The two stack cleanly: cap a loud app in software, set the room level on the knob.

Bottom line

A USB interface is easy — it's a standard Core Audio output the moment you plug it in. What macOS won't do is send only one app to it; choose it in Sound settings and the whole system follows. If your one app is a DAW, its built-in device picker gets you there for free. For anything without an output setting — media players, browsers, calls, alerts — you need a per-app routing app. SoundSource is the deep, effects-heavy choice at $49; Fader keeps it to a simple per-app device pick plus keyboard volume for $19.99 one-time. Either way, the interface stops being an all-or-nothing switch and becomes a destination you assign, app by app.