Published 2026-10-16 · Updated 2026-11-19 · PlexBeam
Dolby Atmos and DTS:X are object-based spatial audio formats that place sounds in three-dimensional space rather than assigning them to fixed channel positions. When working correctly through Plex, they produce a noticeably different listening experience compared to standard 5.1 or 7.1 surround sound. When not working correctly — which is the more common experience — they silently fall back to a flat stereo or basic surround mix, and most people never realize they are missing the spatial audio they paid for.
The core challenge is that spatial audio requires an unbroken chain from the file on disk through the Plex server, through the network, through the client device, through the HDMI cable, and into the AV receiver or soundbar. If any single link in that chain does not support passthrough, the audio gets transcoded to a lossy format and the spatial metadata is stripped out.
Dolby Atmos is not a standalone audio format. It is a metadata layer carried inside either Dolby TrueHD (lossless, used in Blu-ray rips and remuxes) or Dolby Digital Plus (lossy, used in streaming services). The Atmos spatial data is embedded within these container formats and can only be decoded by an Atmos-compatible receiver or soundbar.
DTS:X works similarly. It is carried inside DTS-HD Master Audio (lossless) or DTS Digital Surround (lossy). The spatial metadata rides alongside the standard surround channels.
This layered architecture means that any process that re-encodes the audio — including Plex transcoding — destroys the spatial metadata. A file with TrueHD Atmos that gets transcoded to AAC stereo has lost not just channels but the entire spatial dimension. Even transcoding to standard 5.1 AC3 destroys the Atmos objects while preserving a basic surround mix.
Every component in the playback chain must support passthrough. If any one fails, the whole chain falls back.
Not all Plex clients support audio passthrough equally. This is the single biggest source of spatial audio failures.
The Shield TV (both tube and pro models) is the gold standard for Plex audio passthrough. It supports TrueHD Atmos, DTS:X, DTS-HD MA, and every common lossy format. Enable passthrough in the Plex app under Settings, Advanced, Audio, and set the Audio Output to HDMI. Under Passthrough, enable all formats your receiver supports.
The Apple TV 4K supports Dolby Atmos through Dolby Digital Plus only, not through lossless TrueHD. If your files contain TrueHD Atmos, the Apple TV will transcode the audio to lossy DD+ with Atmos spatial metadata preserved — but the audio quality is reduced compared to the lossless original. For DTS formats, the Apple TV transcodes to multichannel PCM, losing the DTS:X spatial data entirely.
Fire TV devices support Dolby Digital Plus with Atmos but not TrueHD. DTS passthrough support varies by model and firmware version. The Fire TV Stick 4K Max has the best support in the Fire TV lineup.
Most Roku devices do not support TrueHD or DTS-HD passthrough. The Roku Ultra and Roku Streambar Pro support Dolby Atmos via DD+ only. Roku is not recommended if lossless audio passthrough is important to you.
The Plex app on Samsung, LG, and other smart TVs generally does not support audio passthrough. These apps decode the audio internally and output PCM or re-encoded lossy audio. If you are using a smart TV app and want Atmos, you need an external streaming device connected directly to your receiver.
A dedicated HTPC running Plex Media Player or Plex for Windows can pass through all audio formats including TrueHD Atmos and DTS:X, provided the graphics card and HDMI output support the format. This requires HDMI audio output configuration in the operating system and may require selecting the correct audio device in Plex settings.
When spatial audio is not working, Plex provides diagnostic information in the Now Playing dashboard. While a file is playing, check the stream info:
Common reasons audio transcodes even when passthrough is configured:
If your streaming device connects to your TV and the TV connects to your soundbar or receiver via HDMI ARC, you have a bandwidth limitation. Standard ARC supports a maximum of Dolby Digital Plus (lossy, up to 768 kbps). Lossless TrueHD Atmos requires eARC (Enhanced Audio Return Channel), which supports up to 37 Mbps.
Check whether your TV and receiver both support eARC. If either side only has ARC, you will only get lossy Atmos (DD+ Atmos), not lossless (TrueHD Atmos). The practical difference is audible on a good system but subtle — lossy DD+ Atmos still provides the spatial object positioning, just at reduced audio fidelity.
The recommended setup for lossless passthrough is to connect your streaming device directly to the receiver via HDMI, then connect the receiver to the TV. This bypasses the ARC/eARC limitation entirely.
On the server side, ensure these settings are not interfering with passthrough:
PlexBeam handles video transcoding on remote GPU infrastructure while preserving audio passthrough. When a remote user needs 4K video transcoded to 1080p but their client supports Atmos passthrough, PlexBeam transcodes only the video stream and passes the audio through untouched. This is the ideal configuration for users who want both remote streaming compatibility and lossless audio for local playback.
Why HDR tone mapping, color space conversion, and 10-bit encoding overwhelm most servers.
Set up NVENC, Quick Sync, or AMD VCN for hardware-accelerated transcoding in Plex.
CPU, GPU, RAM, and storage recommendations for every budget and use case.
Join the pre-beta waitlist and lock in 50% off for life.
Claim My Early-Adopter Spot →