How to route browser audio to a different speaker on Mac

macOS has one system output that every app shares, so there's no built-in way to send your browser to a different speaker while the rest of your Mac stays put. The fix is a per-app routing tool: it assigns Chrome, Safari, or Firefox its own output device — say, the desk speakers — while everything else keeps playing through the Mac speakers or your headphones. This guide covers the free workaround, exactly where it breaks down, and the two-click way to set it and forget it.

The reason this is harder than it should be is simple: Apple's Sound settings expose a single output selector. Pick "Desk Speakers" there and everything moves to the desk speakers — your music, your calls, your notification chimes, and your browser along with them. There's no per-app column, no "route this one app elsewhere" switch. If you've ever wanted YouTube on the big speakers while calls stay on your headset, you've hit the exact wall this article is about.

First, know what "browser audio" actually means to macOS

macOS routes sound per process, and to the system your browser is one process no matter how many tabs are open. That has one important consequence: when you route "the browser," you route all of it. Every tab — the YouTube video, the web call, the background music player — follows the same output device. You can't send one tab to the desk speakers and keep another on your headphones, because the system can't see individual tabs.

If a single tab is really what you're after, that's a different problem with a different answer, and it's worth reading how to control a browser tab vs the whole browser on Mac before you go further. For routing to a speaker, though, think in terms of "the browser as a whole" — that's the unit macOS gives you to work with.

Option 1 — The free route: a virtual device in Audio MIDI Setup

The zero-cost path uses a free virtual audio driver like BlackHole together with macOS's built-in Audio MIDI Setup. The idea is to build an Aggregate or Multi-Output Device that combines your speakers with the virtual driver, then push audio around with whatever tools can target the virtual device. It's genuinely free and it's the honest starting point.

The catch is that it doesn't actually do the thing you asked for. A Multi-Output Device mirrors the same audio to several outputs at once — it can't send your browser to one speaker and your music to another. Aggregate devices combine inputs and outputs but still don't split apps by app. BlackHole moves audio between apps, but it has no concept of "this is Chrome, send it there." To get true per-app-to-per-speaker routing you end up scripting it or layering another app on top. For a one-time, set-and-forget setup, the manual route is a lot of plumbing for a result that's fragile after a restart.

Option 2 — A per-app routing app (the real fix)

The clean answer is an app that sits at the audio layer and lets you assign each running app its own output device. You open the app, find your browser in the list, pick "Desk Speakers" as its output, and you're done — the browser plays there, everything else stays where it was, and the choice sticks. This is the only approach that does what the Sound settings won't: split one app off to its own speaker.

Three tools worth knowing, honestly compared:

SoundSource by Rogue Amoeba is the deep, mature option. It routes any app to any output — including grouped outputs and AirPlay devices like HomePods and Sonos in version 6 — and adds a full EQ and audio effects on top. It's excellent, and at $49 one-time you're paying for a lot of range you may or may not need. Background Music, the popular free open-source mixer, is great for per-app volume but isn't built to send different apps to different output devices, so it doesn't solve this particular problem. Fader focuses on the everyday version of the job: give the browser its own output, do it fast, keep it cheap.

How to route the browser with Fader, step by step

The flow is short. Install Fader, open it, and your running apps appear as channels — one of them is your browser. On the browser's channel, set the output device to the speaker you want (Desk Speakers, an HDMI display, a USB interface, whatever's connected). That's it: the browser now plays through that speaker while the rest of your Mac keeps using its normal output. The assignment is remembered, so it survives quitting the browser and coming back.

The reason to reach for Fader specifically is speed. Because it's keyboard-driven, the same channels you use to route are the ones you use to ride volume — you're not digging through a menu every time you want the browser louder on those speakers or muted while you take a call. If you want the general version of this beyond browsers, the walkthrough in how to send an app's audio to a different output on Mac covers the same idea for any app.

A note on the volume-goes-grey gotcha

Once an app is routed to a specific device, don't be surprised if the Mac's own volume keys stop affecting it — the system keys control the system output, and your browser is no longer on it. That's expected, not a bug. It's also the reason a routing app that also gives you a per-app volume slider is worth more than a pure router: you keep a way to ride the browser's level on its new speaker without hunting for a hardware knob. Fader keeps both on the same channel, which is the whole point of doing it from one place.

Bottom line

macOS gives you one output for the whole machine, so sending just your browser to a different speaker needs a per-app routing app — the built-in settings can't split one app off. The free BlackHole route exists but mirrors audio rather than splitting it, and takes real setup. SoundSource does it thoroughly for $49; Background Music doesn't route outputs at all. If you mainly want to point the browser at a speaker, keep the choice, and reach volume fast from your keyboard, that's exactly what Fader is built for — for $19.99 once.