Netflix Spatial Audio on Mac: Why It Works in Safari but Not Chrome

Netflix Spatial Audio on Mac: Why It Works in Safari but Not Chrome

Open Netflix in Safari on your Mac, put your AirPods in, and spatial audio works. Open the exact same episode in Chrome and the toggle goes grey.

Same Mac. Same AirPods. Same show. The only thing that changed is the browser.

This trips people up because it looks like a Netflix problem, and Netflix gets blamed for it constantly. It isn't Netflix. The cause sits one layer down, in how macOS decides which audio is allowed near Apple's spatial engine at all, and it's the clearest working example of that rule anywhere on your Mac.

Table of Contents

The Cause: macOS Gatekeeps the Spatial Engine, Not Netflix

Apple built a spatial audio engine into macOS that is genuinely excellent. It's the same processing your AirPods use in Apple Music, with head tracking and your personalized profile applied. The catch is that it only activates for audio that arrives through Apple's own media frameworks.

Safari is built on WebKit, which is Apple's. Video playing in Safari qualifies. Chrome, Edge, Brave, Arc, and Opera are all built on Chromium, which is Google's. Video playing in those browsers does not qualify, so macOS treats it as ordinary stereo and greys the toggle out.

This isn't a theory. It's documented in Chromium's own issue tracker, in an open request titled "Add Support for Spatial Audio on MacOS + Airpods headphones" (issue #339678653). The report states plainly that Chromium lacks spatial audio support with AirPods on macOS, and that opening the same video in Safari lets the Mac apply the spatial audio effect. The people who maintain the browser engine agree with the diagnosis. It's a feature Chromium hasn't built, not a bug in your setup.

That's the part almost no troubleshooting article gets right. They'll tell you Netflix "supports" spatial audio, or that you need an Apple Silicon Mac, and stop there. Neither explains why the identical stream behaves differently in two windows on the same screen.

What Netflix Officially Requires on Mac

Netflix's own support documentation is consistent with all of this. For spatial audio on a Mac, Netflix requires Safari specifically. Chrome and Firefox are not supported paths. You also need compatible headphones and a title that carries a spatial mix, since not every show has one.

So the requirements stack up like this:

  • A Mac running Apple Silicon
  • Safari, not a Chromium browser
  • AirPods that support spatial audio
  • A Netflix title with a spatial audio track

Miss any one of those and the toggle stays grey. In practice, the browser is the one people miss, because nothing on screen tells you the browser is the reason.

Why the Usual Fixes Don't Work Here

If you searched this problem before landing here, you've probably already tried the standard list. It's worth naming why each one fails, because they're all solving a different problem.

Re-pairing your AirPods. Fixes genuine Bluetooth state bugs. Does nothing about which framework the audio came from.

Updating macOS or Netflix. There's no version of Chrome that changes this, because the gap is in Chromium's audio path, not in the Netflix web player.

Buying a newer Mac. The Intel-versus-Apple-Silicon story is the single most repeated wrong answer on this topic. Apple Silicon is a real requirement, but if you're already on an M-series Mac and Safari works while Chrome doesn't, the chip has already proven it isn't the blocker.

Looking for Dolby Atmos content. Netflix spatial audio does depend on the title having a spatial mix. But you can watch a spatial-mixed title in Chrome and still get nothing, which tells you content alone was never the gate.

If Safari works and Chrome doesn't, you have already run the only diagnostic that matters. The browser is the variable.

How to Get Netflix Spatial Audio in Any Browser

You have two options.

The free one is to watch Netflix in Safari. It works, and if Safari is a browser you're happy in, that's a real fix. The friction shows up when Safari isn't where the rest of your life lives, or when you want the same behavior from every other app on your Mac, which Safari can't help with.

The other option is to change where the audio goes instead of changing your browser. That's what WaveCast does.

WaveCast is a macOS menu bar app that sits underneath whatever is playing and hands your audio to Apple's spatial engine directly. It doesn't process the sound itself, and this is the important distinction. Apps that advertise "3D" or "surround" effects apply their own digital processing to imitate a spatial field, and that processing is audible. WaveCast doesn't imitate anything. It routes your audio into the same Apple pipeline Music and TV already use, so what you hear is native Apple spatial playback, not an approximation of it.

Because the routing happens at the system level, the browser stops mattering. Netflix in Chrome, Netflix in Arc, YouTube, Spotify, a game, a video call recording. If it makes sound on your Mac, it can go through the spatial engine.

WaveCast works with every AirPods model that supports Personalized Spatial Audio and head tracking: AirPods 3rd and 4th generation, AirPods Pro 2nd and 3rd generation, and AirPods Max.

Frequently Asked Questions

Does Netflix have spatial audio on Mac?

Yes, but only in Safari. Netflix supports spatial audio on Mac through the Safari browser on Apple Silicon Macs with compatible headphones, on titles that have a spatial mix. There is no Netflix desktop app on macOS, so the browser you choose is the whole story.

Why is Netflix spatial audio not working in Chrome?

Because Chromium, the engine behind Chrome, doesn't support Apple's spatial audio path on macOS. This is confirmed in Chromium's own public issue tracker. macOS only spatializes audio that comes through Apple's media frameworks, and Chrome's audio doesn't.

Why is spatial audio greyed out while I'm watching Netflix?

Either you're in a Chromium browser rather than Safari, or the title you're watching has no spatial audio track. Check Safari first. If the same title spatializes in Safari, the browser was the cause.

Does Netflix spatial audio work on an Intel Mac?

No. Apple's spatial audio on macOS requires an Apple Silicon Mac. That said, if you're on Apple Silicon and it still fails in Chrome, the chip isn't your problem and no hardware upgrade will change it.

Can I get Netflix spatial audio in Chrome without switching browsers?

Not through Chrome itself, since the support has to come from Chromium. Routing your Mac's audio through Apple's spatial engine at the system level, which is what WaveCast does, makes the browser irrelevant.

The Short Version

Netflix spatial audio on Mac works in Safari and fails in Chrome because macOS only spatializes audio that comes through Apple's own frameworks, and Chromium browsers don't use them. Netflix isn't withholding anything, and your Mac isn't broken.

You can live in Safari, or you can move the audio instead of the browser. WaveCast hands whatever is playing to Apple's spatial engine directly, so Netflix in any browser gets the same treatment Apple Music already gets.

If that sounds like your setup, drop your email in the waitlist below.

Join our waiting list

Get in line for the key.

WaveCast is pre-launch. Join the waitlist and you'll hear first when it ships — and you'll help decide how it's packaged and priced. One email at launch, nothing else.

This decides what we build first, so pick the closest.

$

Optional, and there's no wrong answer. We're still deciding, and this genuinely feeds into it.

macOS 14+·AirPods 3rd/4th gen·AirPods Pro 2nd/3rd gen·AirPods Max