What Is Apple Spatial Audio, and Why Does It Only Work in Apple's Own Apps?
What Is Apple Spatial Audio, and Why Does It Only Work in Apple's Own Apps?
Apple spatial audio is one of the few audio features in consumer tech that people notice immediately without being told what to listen for. Put AirPods in, play something in Apple Music, and the sound stops sitting between your ears. It's out in front of you, in a room, staying put when you turn your head.
Then you open Spotify on the same Mac with the same AirPods and it's gone.
Both halves of that experience have an explanation, and the second half is the more useful one to understand.
Table of Contents
- What Spatial Audio Actually Does
- The Three Parts That Make It Work
- Why It's Locked to Apple's Own Apps
- Why This Is Worse on Mac Than on iPhone
- Unlocking the Engine You Already Own
- Frequently Asked Questions
What Spatial Audio Actually Does
Ordinary headphone audio has a specific weakness. The left channel goes into your left ear, the right into your right, and nothing about that resembles how you hear anything in real life. In a room, sound from your left reaches your right ear too, slightly later and slightly muffled by your head. Your brain uses those differences to build a sense of where things are.
Headphones skip that step, which is why headphone sound feels like it's inside your head rather than around you.
Spatial audio puts the step back. It processes the audio so each ear receives what it would receive if the sound were coming from a speaker in a room, and your brain does the rest. The sound moves outward and forward. On a long listening session, that's usually less tiring, because your brain stops working to reconcile something that doesn't match physical experience.
The Three Parts That Make It Work
HRTF processing. A head-related transfer function describes how your head, shoulders, and ear shape change a sound before it reaches your eardrum. Apply that mathematically and you can place a sound at a specific point in space using only two channels. This is the core of the effect and Apple's implementation of it is very good.
Head tracking. The motion sensors in your AirPods report how you've moved. If the sound field stayed glued to your head, the illusion would break the moment you turned. Head tracking keeps the sound anchored to your device instead, so turning your head moves you within the scene rather than moving the scene with you.
A personalized profile. Everyone's ears are shaped differently, so a generic HRTF is a compromise. Apple's Personalized Spatial Audio uses an iPhone camera scan of your ears and head to tune the rendering to you. How much it improves things varies from person to person, but it's free and takes a few minutes.
None of these three exist in the third-party "3D sound" apps that use the same vocabulary. Those apply digital effects to widen or fake a surround image, without HRTF rendering, head tracking, or a personal profile.
Why It's Locked to Apple's Own Apps
Here's the part that gets asked constantly and answered badly.
Spatial audio on macOS isn't applied to everything your Mac plays. It's applied to audio that arrives through Apple's own media frameworks. An app has to hand its audio to the system in the specific way Apple's playback stack expects, and then macOS will spatialize it.
Apple Music does that. The TV app does that. Video in Safari, which runs on Apple's WebKit engine, does that.
Spotify's Mac app doesn't. Chrome, Edge, Brave, and Arc don't, because they run on Chromium, whose developers have an open request in their own public issue tracker acknowledging that Chromium lacks spatial audio support with AirPods on macOS. Most games don't. Most third-party players don't.
When you're in one of those apps, macOS has nothing to spatialize as far as it's concerned, so it greys the option out. It doesn't tell you why, which is why the internet is full of guesses about Intel chips, firmware, and Dolby Atmos content. None of those are it.
Whether Apple designed this as a moat or simply never built a system-wide path is a question only Apple can answer. What's observable is the result: one of the best audio features in consumer tech runs on a fraction of what you listen to.
Why This Is Worse on Mac Than on iPhone
Most people meet spatial audio on their iPhone, where it works in more places, including Spotify's iOS app. So the Mac experience reads as broken by comparison.
It isn't. On iPhone, apps largely use Apple's standard playback stack because that's the path of least resistance on iOS. On macOS, apps have far more freedom in how they output audio, and most take a route that never touches Apple's spatial pathway. Same AirPods, same song, different outcome. Which is exactly the complaint filling Spotify and Apple community threads for the last several years.
Unlocking the Engine You Already Own
Here's the reframe worth holding on to. Apple already built one of the best spatial audio engines in consumer tech, and you already own it. It's sitting in your Mac and in your AirPods right now. The problem was never quality or hardware. It's a question of which audio is allowed to reach it.
WaveCast exists for exactly that. It doesn't build a new spatializer, and it doesn't process your audio. It hands whatever is playing on your Mac to Apple's own engine, in the spot where an app like Apple Music would normally do it, so everything else on the machine gets treated like native Apple playback. Same HRTF processing, same head tracking, same personalized profile.
It works with the AirPods models that support Personalized Spatial Audio and head tracking: AirPods 3rd and 4th generation, AirPods Pro 2nd and 3rd generation, and AirPods Max.
Frequently Asked Questions
How does Apple spatial audio work?
It applies HRTF processing to place sounds at points in space using two channels, uses the motion sensors in your AirPods to keep that space anchored while you move, and can tune the rendering to your ear shape with a personalized profile.
Why does spatial audio only work in some apps on my Mac?
Because macOS only spatializes audio delivered through Apple's own media frameworks. Apple Music, the TV app, and Safari qualify. Spotify's desktop app, Chromium browsers, most games, and most other players don't, so the toggle is greyed out.
Is spatial audio the same as Dolby Atmos?
No. Dolby Atmos describes how audio was authored, as objects in three-dimensional space. Spatial audio describes how your device renders audio to headphones. Apple's engine can spatialize plain stereo too, which is what Spatialize Stereo does.
Do I need AirPods for spatial audio?
For the full experience with head tracking, yes, you need AirPods or Beats models that support it. Apple's spatial rendering can apply to other headphones in some contexts, but head tracking depends on Apple's own motion hardware.
Is Personalized Spatial Audio worth setting up?
It's free, takes a few minutes with your iPhone camera, and tunes the rendering to your ears. The size of the difference varies from person to person, but there's little reason to skip it.
Can I get Apple's spatial audio in apps that don't support it?
Not through the app itself, since the app would have to build the support. Routing your Mac's audio into Apple's spatial pipeline at the system level does it without the app's involvement, which is the approach WaveCast takes.
The Short Version
Apple spatial audio is HRTF rendering plus head tracking plus an optional personal profile, and it's one of the best-executed audio features in consumer tech. On macOS it only runs on audio that comes through Apple's own frameworks, which is a small slice of what you actually listen to.
The engine isn't the limitation. The door is. WaveCast opens it by handing your Mac's audio to Apple's engine directly.
If that sounds like your setup, drop your email in the waitlist below.