You turn on spatial sound in Windows through Settings > System > Sound, by opening the output device's properties and choosing Windows Sonic, Dolby Atmos, or DTS Headphone:X under Spatial audio. Windows Sonic is built in and costs nothing. Dolby Atmos for Headphones and DTS Headphone:X need a separate app from the Microsoft Store, and both work over Bluetooth only after you disable the headset's own hands-free phone call profile.
The Three Formats You Can Actually Choose
Windows exposes exactly three spatial audio formats per output device, and each one comes from a different vendor. Windows Sonic for Headphones is Microsoft's own object-audio renderer and ships with Windows 10 and Windows 11 at no cost. Dolby Atmos for Headphones runs through the Dolby Access app, and DTS Headphone:X runs through the DTS Sound Unbound app, both distributed by the Microsoft Store.
The distinction that matters is virtualization versus object rendering. Windows Sonic renders height and position cues into ordinary stereo headphones through HRTF processing. Dolby Atmos and DTS Headphone:X do the same job but add their own tuning profiles, and some of those profiles are tied to specific licensed headset models rather than generic headphones.
Availability depends on the output endpoint, not the PC as a whole. A USB headset, a pair of wired earbuds in the 3.5 mm jack, and a Bluetooth headset each carry their own spatial audio dropdown. Selecting Dolby Atmos on your speakers does nothing for the headphones plugged into the front panel, because Windows tracks the setting per device.
Formats also fail independently. A PC that runs Windows Sonic flawlessly can show "not available" for Atmos because the Dolby Access app was never installed or because the Microsoft Store is blocked by a domain policy. Check the dropdown itself before assuming a driver fault.
Open the Right Settings Page for Your Windows Version
The path is identical in Windows 11 versions 22H2 through 25H2 and in Windows 10 version 22H2, the final feature update Microsoft shipped for Windows 10 before support ended on October 14, 2025. Settings > System > Sound lands you on the same page in both, but the layout differs enough that people describe the steps differently.
In Windows 11, Sound opens to a device list with a volume slider for each endpoint. Click the arrow beside your headset to reach its properties, and the Spatial audio dropdown sits in the middle of that page. The older Windows 10 Sound page uses a "Manage sound devices" link and a separate "Device properties" entry, which is why guides written before 2022 describe two or three more clicks.
If your headset appears grayed out on the Sound page, Windows has not assigned it as an active endpoint. Set it as the default output device first, either from the Sound page's device list or from the legacy mmsys.cpl control panel, and the spatial audio option will populate. Bluetooth headsets can take several seconds after pairing before the endpoint becomes selectable.
Laptop users sometimes find the Sound page shows only speakers even with a headset connected. That usually means the jack is a combo port that has not detected the plug, or the headset is paired to a phone instead of the PC. Re-pairing in Settings > Bluetooth & devices takes about thirty seconds and resolves most of these cases.
Step-by-Step: Switch On Spatial Audio for a Headset
Follow this sequence in order. Each step assumes the previous one completed successfully, so a failure early tells you where the problem lives rather than leaving you guessing at the end.
1: Connect the headset and confirm it appears under Settings > System > Sound as an output device. 2: Click the right-pointing arrow next to the headset name to open its properties page. 3: Find the Spatial audio dropdown, which defaults to Off. 4: Choose Windows Sonic for Headphones if you want the free option, or pick Dolby Atmos for Headphones or DTS Headphone:X if the matching app is installed. 5: If a chosen format shows "Not available", click the link beneath the dropdown to open the Microsoft Store page for Dolby Access or DTS Sound Unbound. 6: Install the app, reopen the Sound settings page, and reselect the format. 7: Play a known multichannel source, such as a film with a 5.1 or Atmos track, and confirm the dropdown still shows your format after playback begins.
Failure handling splits into two branches. If the dropdown is missing entirely, the endpoint is not active β set it as default and reopen the page. If the dropdown exists but the format refuses to stick after you leave the page, the app that owns the format is not licensed or signed in, and opening it once usually resolves the state.
Free Windows Sonic Versus Paid Dolby Atmos and DTS
Cost is the first dividing line. Windows Sonic is included with the operating system at no charge. Dolby Access and DTS Sound Unbound are free downloads that unlock a paid license for headphone use, typically sold as a one-time purchase or a longer trial, with pricing set inside the Store app and subject to regional variation. Confirm the current price on the Store listing rather than relying on any figure quoted elsewhere.
| Format | App required | Cost model | Best fit | Limitation |
|---|---|---|---|---|
| Windows Sonic for Headphones | None | Included with Windows | Free positional audio for games and video | Fewer tuning profiles than the paid options |
| Dolby Atmos for Headphones | Dolby Access | Paid license after trial | Film and game content mixed in Atmos | License tied to the Microsoft account, not the device |
| DTS Headphone:X | DTS Sound Unbound | Paid license after trial | Headsets with DTS-licensed profiles | Generic headphone tuning is thinner than on licensed models |
| Dolby Atmos for Home Theater | Dolby Access | Paid license | HDMI receivers and soundbars | Requires an Atmos-capable receiver over HDMI |
The verdict splits by use. If you play games casually and watch the occasional streaming film, Windows Sonic covers the job and costs nothing. If you have a library of Atmos-tagged films or play titles that ship an Atmos mix, the Dolby license is the one worth buying, since the renderer is tuned to that content. Skip DTS unless your headset carries a DTS license, because the generic profile adds little over Sonic on unlicensed hardware.
Bluetooth Headsets Need the Hands-Free Profile Disabled
This is where most people give up. A Bluetooth headset paired to Windows often appears twice in the device list: once as "Headphones" with stereo output, and once as "Headset" with a hands-free telephony profile. Spatial audio only works on the stereo endpoint, and Windows may default to the hands-free one the moment a call app grabs the microphone.
The fix lives in Control Panel, not Settings. Open the legacy sound panel by searching for "Change system sounds", select the stereo playback device, click Properties, then the Enhancements or Advanced tab depending on your audio driver, and disable the hands-free profile under the Bluetooth device's services. The exact tab name varies by driver vendor β Realtek, Intel, and Qualcomm layouts all differ β so read the labels rather than following a screenshot from another machine.
After disabling the hands-free endpoint, reconnect the headset. The spatial audio dropdown should now accept a format and keep it. If the headset re-enables hands-free after a reboot, the Bluetooth stack has restored the default service set, and you will need to disable it again or use a USB dongle instead.
Latency is the other Bluetooth wrinkle. Windows Sonic and both paid formats add processing delay measured in milliseconds, and Bluetooth itself adds transport delay. For films that is invisible because players compensate. For competitive games the combined delay can push audio behind the video enough to notice, which is why wired connections remain the safer choice for timing-sensitive play.
Receiver and Soundbar Setup Over HDMI
Spatial audio over HDMI works differently from the headphone path. The format becomes Dolby Atmos for Home Theater, and the renderer passes the bitstream to an external receiver or soundbar that decodes it. The PC does not virtualize anything in this mode β it hands off the object metadata and lets the receiver do the positional work.
Three conditions must hold. The HDMI output must be set as the default playback device, the receiver must advertise Atmos support in its EDID handshake, and the Windows sound format for that endpoint must be set to Dolby Atmos for Home Theater rather than stereo. Missing any one of the three leaves you with ordinary surround or plain stereo and no error message.
The Settings page shows the spatial audio dropdown for HDMI endpoints too, but selecting Atmos there without an Atmos-capable receiver produces silence or a fallback to stereo depending on the driver. Check the receiver's on-screen display for an "Atmos" indicator rather than trusting the Windows dropdown alone.
Cable quality matters more than people expect at this stage. Older High Speed HDMI cables rated for 1080p can choke on the bandwidth an Atmos bitstream demands alongside 4K video, producing dropouts that look like a software fault. A Premium High Speed or Ultra High Speed cable removes that variable cheaply.
Why the Dropdown Says Not Available
"Not available" is the single most common complaint, and it has four distinct causes that look identical on screen. The first is a missing app: Dolby Atmos and DTS Headphone:X cannot be selected until Dolby Access or DTS Sound Unbound is installed, even if the dropdown lists them by name.
The second is a driver that does not expose the endpoint as spatial-capable. Generic USB audio class drivers sometimes report no spatial support, and installing the headset maker's own driver package restores the option. Check Device Manager under Sound, video and game controllers for a generic "USB Audio Device" entry as the tell.
The third is a Windows update state. Spatial audio depends on components delivered through Windows Update, and a PC that has deferred updates for months can lack the renderer entirely. Running Windows Update once resolves this in most reported cases.
The fourth is a region or Store restriction. Corporate PCs with the Microsoft Store disabled by group policy cannot install Dolby Access or DTS Sound Unbound, which locks those formats out no matter what the user does locally. In that situation Windows Sonic remains the only usable option.
What Spatial Audio Does and Does Not Change
Spatial audio changes how existing stereo and surround content is rendered to your headphones. It does not remix your music library, and it does not add channels that were never in the source. A two-channel song played through Windows Sonic gets positional processing, which some listeners find wider and others find unnatural.
Games benefit most because they ship positional metadata that the renderer can place in three-dimensional space. Films with a 5.1 or Atmos mix benefit next, since the renderer has real surround information to fold into the headphone image. Plain stereo music is the weakest case, and many people switch spatial audio off for listening sessions.
The setting persists per device and survives reboots, so you do not need to re-enable it each session. Switching headsets switches the setting with them. If you alternate between a gaming headset and studio monitors, expect to toggle the format on the headset each time you swap back, because the speaker endpoint carries its own separate choice.
Battery life on wireless headsets takes a small hit when spatial processing runs on the PC side rather than in the headset. The renderer consumes CPU cycles continuously while active, and on a laptop that translates into a measurable but modest reduction in runtime. Wired headsets sidestep the question entirely.
Fixing Crackle, Dropouts, and Format Resets After Updates
Audio crackle after enabling spatial sound usually traces to sample rate mismatch. The headset endpoint may be set to 48 kHz while the format expects 44.1 kHz, and the resampling produces artifacts. Open the device's Advanced properties and set both the format and the spatial renderer to the same rate.
Dropouts during playback point at buffer size. Increasing the buffer in the audio driver's control panel β Realtek Audio Console and the Dolby Access settings both expose one β trades a few milliseconds of latency for stability. Do this only if the dropouts persist after a cable or pairing change.
Format resets after a Windows update are common enough to expect. Feature updates occasionally reset audio endpoint properties to defaults, which turns spatial audio back to Off. Re-selecting the format takes under a minute, and there is no permanent fix short of scripting the change through the audio endpoint API, which is beyond typical home use.
The Blu-ray and streaming app variable deserves a mention. Some players output their own decoded stereo rather than passing multichannel audio to Windows, which defeats the renderer. Check the player's audio output setting and set it to passthrough or "use system default" so Windows receives the full mix.
FAQ
Does spatial sound work with any pair of headphones?
Yes, Windows Sonic and the paid formats process output for ordinary stereo headphones, and no special hardware is required. The renderer applies HRTF processing to whatever stereo signal the endpoint receives. Licensed headsets get extra tuning profiles, but the base function works on earbuds that cost a few dollars.
Is Windows Sonic the same thing as Dolby Atmos?
No, they are separate renderers from separate companies, and Windows lists them as distinct choices in the same dropdown. Sonic is Microsoft's free object-audio engine, while Atmos is Dolby's licensed format delivered through the Dolby Access app. Both produce positional audio on headphones, but the tuning and content compatibility differ.
Why does my Bluetooth headset lose spatial audio when I join a call?
The hands-free telephony profile takes over the endpoint when a call app opens the microphone, and that profile does not support spatial rendering. Disable the hands-free service in the device's properties to keep the stereo endpoint in charge. Some headsets re-enable it after each reconnect.
Can I use spatial audio with speakers instead of headphones?
Only the home theater variant works on speakers, and only over HDMI to a receiver or soundbar that decodes Dolby Atmos. The headphone formats are designed for stereo endpoints and produce odd results on multi-speaker setups. Check the receiver's display for an Atmos indicator to confirm the handoff succeeded.
Does spatial audio slow down games?
The processing cost is small on modern CPUs, typically a few percent of one core, and frame rates are rarely affected. The bigger concern is added audio latency, which matters in competitive shooters. Wired connections keep that latency lower than Bluetooth.
Will my Dolby Atmos license transfer to a new PC?
The license binds to the Microsoft account used to buy it, not to the hardware, so signing in on a new PC restores it through the Dolby Access app. A PC without that account signed in will show the trial state instead. Confirm the license status inside the app after any hardware change.
What happens if I uninstall the Dolby or DTS app?
The spatial audio dropdown reverts those formats to unavailable, and Windows falls back to whatever was selected before, usually Off or Windows Sonic. Reinstalling the app restores the option without repurchasing, because the license stays with the account. Your per-device selection may need to be set again.
Does spatial audio work in Windows 10 after support ended?
The feature continues to function on Windows 10 version 22H2 as installed, since it is a local rendering component rather than a cloud service. Microsoft ended standard support for Windows 10 on October 14, 2025, so new fixes and driver updates no longer arrive for that version. Windows 11 is the supported path going forward.