Share what's playing on your Mac with two or more Bluetooth headphones at once — each with its own volume slider. No splitters, no dongles, no admin password.
It's 10pm. The baby is asleep in the same room. You both want to watch the movie.
MultiPods was built for that one warm, specific moment — and the dozen others like it. Working out together. Late-night gaming. Language learning. One pair of ears that needs it a little louder.
Open System Settings → Bluetooth and pair every set you want to use, like you normally would. MultiPods doesn't do the pairing — macOS does, the way it's meant to.
Click the MultiPods icon in the menu bar. Tick the headphones you want included in this session. Add the Mac's speakers too, if you like.
Each person gets their own slider. Adjust independently. The movie keeps playing — Apple TV, Netflix, VLC, anything that uses the system output.
Two people, two volume preferences, two sliders. The Mac's hardware volume keys step out of the way during a session — MultiPods's per-device sliders take over so nobody's volume gets clobbered by a stray F11.
MultiPods plots each device's reported total CoreAudio latency, live, and lets you nudge a per-device offset until lips and lines line up. There's also an Auto-sync button that anchors on the slowest device and lines the rest up to it.
No kernel extension. No virtual audio driver. No admin password. Just public CoreAudio APIs, a sandbox, and a hardened runtime — the same envelope every other app on your Mac runs inside.
Runs in macOS's app sandbox. Files, network, and devices are reachable only with explicit entitlements.
Code-signed and notarized by Apple. No injection, no debugger attach, no library swaps.
We don't install kexts or virtual audio drivers. Nothing to remove if you uninstall.
Never asks for elevated privileges. If something prompts you for one, it isn't us.
MultiPods sends audio out. It never asks for, opens, or records from any input device.
No usage analytics and no account. MultiPods does send anonymous crash reports to Sentry so we can fix what we can't reproduce — details on the privacy page.
Sticking to public APIs means a few things behave differently than they would in a dongle-and-driver setup. We surface every one of them in the app, and we'll surface them here too.
Most Bluetooth headphones — AirPods included — accept volume changes from the Mac just fine. A handful don't. When CoreAudio reports the property as unsettable, MultiPods locks the slider and shows a hint instead of pretending.
Adjust on the device, in Control Center, or in the source app. Every other slider in the session keeps working.
During a session, F10–F12 stop changing volume because there's no longer a single output to apply them to.
Per-device sliders take over. Stop the session and the keys snap back, instantly.
Two pairs of headphones rarely arrive at the same millisecond. AAC and AptX clocks aren't equally patient.
The live latency chart and per-device offset are exactly the dial you need.
With more than one Bluetooth output, macOS sometimes downgrades from AAC to SBC to keep both streams in sync.
It's a system-wide tradeoff that's outside any app's control. Reducing the number of active outputs usually restores AAC.
~/Library/Containers/com.appgineering.MultiPods, which holds your preferences (a few kilobytes). Delete that folder if you want a perfectly clean slate.
A small, App Store-safe Mac menu-bar app that does one thoughtful thing well.