Dolby Atmos Bitrate, Codecs & Loudness: Film to Streaming

Updated October 2026: a Dolby Atmos bitrate table by service and encoder, which streaming services and broadcasters carry Atmos in 2026, and the current loudness and ADM standards (ITU-R BS.1770-5, BS.2076-3).

Why this matters

If you build or operate a product that delivers video or audio — streaming, OTT/Internet TV, e-learning, telemedicine, or AR/VR — a client or a product manager will eventually say the word "Atmos," and what they mean by it depends entirely on which costume they have seen. The marketing person means "the immersive thing Apple Music advertises"; the broadcast engineer means "AC-4 or E-AC-3 with object metadata"; the cinema person means "64 speakers." This article gives a non-technical reader the full mental model — what Atmos stores, how it is carried on each platform, what it costs in bitrate, and what loudness target applies — so you can scope an immersive-audio feature, write a sane storage and CDN budget, and talk to audio engineers without guessing. It builds on the channel-vs-object-vs-scene taxonomy but assumes you have not read it; every term is defined before it is used.

What bitrate does Dolby Atmos use?

Streaming Dolby Atmos typically runs at 448–768 kbps (encoders allow 384–1,024 kbps) when it is carried as Dolby Digital Plus with Joint Object Coding (DD+ JOC), which is how Netflix, Apple Music and Amazon Music deliver it in 2026. Dolby AC-4 carries a 7.1.4 Atmos mix at about 192–320 kbps. Lossless Atmos exists only as Dolby TrueHD on Blu-ray, at several Mbps, and inside the cinema DCP. The studio master is uncompressed PCM: 128 inputs at 48 kHz and 24 bits would need about 147 Mbps, which is why no service streams it.

Table 1. Dolby Atmos bitrates by delivery path, October 2026. Streaming figures are what services and encoders publish; cinema and disc are the lossless exceptions.

Two practical rules follow. First, Apple's HLS Authoring Specification says Dolby Atmos content "SHOULD be restricted to a single bit rate", so an Atmos track is one rendition next to the video ladder, not a ladder of its own. Second, the bitrate depends on the element count, not on the speaker layout at home: a 16-element stream costs the same whether the viewer has a soundbar or a 9.1.6 room. The rest of this article explains where those numbers come from.

Atmos is object-based audio with a channel bed

Before the four costumes, the body underneath them. Dolby Atmos is object-based audio, which means the file does not say "play this signal out of the left-rear speaker." It says "here is the sound of a helicopter, and here is its position in the room — up, behind you, drifting left." The sound is called an audio object, and the position-over-time is metadata: data about the sound. A piece of software called the renderer reads the position and works out, at playback time, which of your actual speakers should play how much of that object to put it in the right place. That is the whole trick, and it is why one Atmos master can play correctly on headphones, a soundbar, a 5.1 system, or a 64-speaker cinema with no separate mix for each.

But Atmos is not pure objects. It is a hybrid, and the hybrid is the part most people get wrong. An Atmos mix has two layers. The first is a bed: a set of ordinary channel-based audio — fixed speaker feeds — used for ambience, music, and anything that does not need to move with precision. Beds are written in a three-number notation we will decode shortly, often 7.1.2 in the home renderer. The second layer is the objects: individual sounds with positional metadata that the renderer places dynamically. A door slam, a passing car, a single line of dialogue — these become objects.

The Dolby Atmos Renderer, the software studios use to author the mix, accepts up to 128 inputs in total, where each channel of a bed counts as one input and each object counts as one input. Within that budget the renderer supports up to 118 object paths, with the remainder going to the bed. That single constraint — 128 inputs, of which up to 118 can be roaming objects — turns up again and again, because every Atmos costume is built from the same 128-input master.

Figure 1. The anatomy of an Atmos mix: a channel-based bed plus up to 118 positional objects, 128 inputs in total, feeding one master.

A useful analogy holds the whole article together. A channel-based mix is a stack of pre-addressed envelopes — "left-rear speaker" written on the outside, the sound sealed inside, delivered perfectly only if your room has a left-rear speaker in the right spot. An object-based mix is a stack of GPS addresses — "this sound lives at these coordinates" — and the renderer is the local driver who knows your neighbourhood, your exact speakers, and delivers each sound to the right spot regardless of how your room is laid out. The bed is the handful of envelopes you keep for the background; the objects are the GPS-addressed packages that need to land precisely.

Costume 1: Atmos in the cinema

The cinema is where Atmos started in 2012, with the release of Brave, and it is the costume closest to the raw master. Understanding why Dolby built it the way they did explains the rest of the format. Before Atmos, cinema sound was channel-based: a fixed number of speaker feeds (5.1, then 7.1) that every auditorium wired up identically. The problem was that a small screening room and a thousand-seat hall got the same small number of feeds, so the big room simply ran more speakers off each feed — the back-left "channel" might drive a dozen physical speakers all playing the same thing. A sound could not travel smoothly across that wall of speakers, because they were all one channel. Atmos broke each speaker out into its own addressable zone and let the mix describe sounds as objects that the room places, so a sound can travel smoothly from the screen to the back of a 64-speaker hall. That is the origin of the object idea, and every downstream costume inherits it. A cinema Atmos package carries up to 128 audio tracks — a 9.1 bed plus up to 118 audio objects — and the auditorium can drive up to 64 independent speaker feeds, where every speaker is its own addressable zone rather than part of a wired-together surround array. The same single package, shipped inside the Digital Cinema Package (the DCP, the file a projection booth actually receives), adapts to whatever the room has, "from 5.1 and 7.1 up to 64 channels."

The adaptation happens live. The in-theatre Dolby Atmos cinema processor reads the bed and the 118 object paths and renders them, in real time, against the known positions of that specific cinema's speakers. That is why the identical Atmos master sounds correct in a room with 24 speakers and a room with 64: the creative intent ("the helicopter is up and behind, moving left") is preserved, and each cinema solves the placement problem for its own geometry.

Two cautions matter here for anyone reasoning about Atmos in a product. First, Dolby describes the cinema package as carrying its audio losslessly — that is true of the DCP, and it is the only place "lossless Atmos" routinely applies. The streaming costumes in the next section are lossy. Do not carry the word "lossless" from the cinema description over to a streaming pipeline. Second, the cinema's 118-object figure and the home renderer's 118-object figure are the same architectural number — 128 inputs minus a 10-channel bed — not two independent facts. State it once and reuse it.

Costume 2: Atmos at home and in streaming

Shipping 128 separate channels of audio to a living room is not practical; at 48 kHz and 24 bits per sample, uncompressed, one channel costs:

48,000 samples/s × 24 bits/sample = 1,152,000 bits/s = 1.152 Mbps per channel
128 channels × 1.152 Mbps         = 147.5 Mbps

About 147 Mbps for audio alone is absurd for home delivery — it would dwarf the video. So Atmos for the home does two things: it spatially codes the scene down to a handful of elements, then carries those elements inside a normal codec.

Spatial coding: 128 elements down to ~16

Spatial coding is the algorithm that groups the 128 beds and objects into 12, 14, or 16 perceptually distinct elements, often called clusters: objects that sit close together in space, or that the ear cannot separate anyway, are merged into one carried element, and the metadata records how to expand them again. This is the single most important number to remember about delivery Atmos: the studio authors with up to 128 elements, but only ~12–16 elements are actually transmitted. You are not streaming 128 channels. A vendor or a colleague who says "Atmos is 128 channels of audio over the wire" has confused the studio format with the delivery format.

Figure 2. The home-delivery chain: 128 studio inputs spatially coded to ~16 elements, then carried in E-AC-3 JOC or AC-4 — a reduction of about two orders of magnitude.

The carriage codec: Dolby Digital Plus with Joint Object Coding

The most common way streaming Atmos reaches a home in 2026 is Dolby Digital Plus — technically Enhanced AC-3, or E-AC-3 — carrying a feature called Joint Object Coding (JOC). The controlling standard for E-AC-3 is ETSI TS 102 366 (the published revision is still V1.4.1, 2017-09, as of October 2026), where Enhanced AC-3 lives in Annex E; the US equivalent is ATSC A/52, also Annex E. E-AC-3's data-rate envelope runs from 32 kbit/s up to 6.144 Mbit/s.

The clever part of JOC is backward compatibility. A DD+ JOC stream is a normal 5.1 (or 7.1) Dolby Digital Plus core plus a side payload — the JOC data and the Object Audio Metadata (OAMD) — that lets a modern decoder reconstruct the object scene. A device that has never heard of Atmos simply decodes the 5.1 core and ignores the side data. So one stream serves both an old soundbar and a new Atmos receiver. This is exactly the "graceful degradation" property a streaming product wants: one rendition, two audiences.

The practical bitrates are where studio-versus-delivery thinking pays off. Dolby's own encoder defines minimums of 384 kbps for a 12-element spatial coding and 448 kbps for 16 elements. Services publish higher working rates: Netflix streams Atmos at 448–768 kbps and Amazon Music at 448 or 768 kbps (Table 1). Compare 768 kbps against the naive 147.5 Mbps from the worked example above and you have a reduction of two orders of magnitude (about 190-to-1 at 768 kbps): that gap is the entire reason "studio Atmos" and "streaming Atmos" must never be treated as the same bitstream. (A side benefit: DD+ JOC at the usual 768 kbps or less fits within HDMI ARC's roughly 1 Mbps return path, which is why Atmos from a TV app can reach a soundbar over plain ARC without the newer eARC connector.)

The next-generation carriage codec: Dolby AC-4

The successor codec is Dolby AC-4, governed by ETSI TS 103 190-1 (the core codec, current revision V1.4.1, 2025-07) and ETSI TS 103 190-2 (immersive and personalized audio, current revision V1.3.1, 2025-07), with its reference renderer in ETSI TS 103 448. AC-4 carries immersive/object Atmos at roughly half the bitrate of DD+ for comparable quality, using a more advanced object-coding scheme Dolby calls A-JOC (Advanced Joint Object Coding).

Dolby's white paper puts numbers on the efficiency: an immersive 7.1.4 mix is characterized as "good" at about 192 kbps and "excellent" at about 320 kbps, and a two-channel Immersive Stereo (IMS) variant is near-transparent at 256 kbps, good at 112 kbps, and acceptable from as low as 64 kbps. Treat these as Dolby's own quality characterizations rather than hard spec limits. As of October 2026, AC-4 on streaming is still early. Tidal uses it for Atmos music, Peacock announced at CES in January 2026 that it would adopt AC-4 during the year (no launch confirmed as of October), and US NextGen TV (ATSC 3.0) stations broadcast in it, but most film and series Atmos still ships as DD+ JOC. For a product targeting the broadest device base today, DD+ JOC remains the safe default and AC-4 the forward-looking option.

The lossless exception: TrueHD on disc

There is one consumer place where Atmos is genuinely lossless: Dolby TrueHD on Blu-ray and 4K UHD Blu-ray. TrueHD uses Meridian Lossless Packing (MLP) and embeds the Atmos object metadata inside the lossless stream. This is disc-only; no streaming service delivers TrueHD Atmos, because the bitrate would be many megabits per second. If a requirement says "lossless Atmos," it means physical media, not a stream.

Table 2. The three Atmos carriage paths a product person meets, with the controlling spec and where each one actually appears. Tinted cells mark each codec's standout property.

Which streaming services support Dolby Atmos in 2026?

Netflix, Disney+, Prime Video, Apple TV, HBO Max and Peacock stream films and series in Dolby Atmos; Apple Music, Amazon Music and Tidal stream Atmos music. Spotify and YouTube do not: Spotify added lossless stereo in September 2025 but no Atmos, and YouTube's immersive format is Google's own Eclipsa Audio, built on the open IAMF codec. Almost every service carries Atmos as DD+ JOC; Tidal uses AC-4 for Atmos music, according to Dolby.

Table 3. Dolby Atmos support by service, October 2026, from each service's or Dolby's own documentation.

Dolby Atmos on broadcast channels

Broadcast Atmos is on air in three forms in 2026: US NextGen TV (ATSC 3.0) stations carry it in Dolby AC-4, pay-TV operators carry it in DD+ JOC on premium sports feeds, and in April 2026 TV Azteca brought Atmos to Mexican free-to-air TV over the older ATSC 1.0 standard, whose audio layer is AC-3 and E-AC-3. Live sport drives almost all of it.

The recent examples show the pattern. NBC streamed the Milan Cortina 2026 Winter Olympics on Peacock in 4K HDR with Atmos, and its NextGen TV stations in selected cities carried the same coverage over the air in 1080p Dolby Vision and Atmos. Comcast's Xfinity delivered all 104 FIFA World Cup 2026 matches from Fox and FS1, plus a Telemundo match of the day, with Dolby Vision and Atmos (June 2026). In the UK, BT Sport (now TNT Sports) has broadcast Premier League matches in Atmos since 2017. Outside the Dolby world, South Korea's ATSC 3.0 service uses MPEG-H 3D Audio, and Brazil made MPEG-H the mandatory audio codec of its TV 3.0 (DTV+) system by presidential decree in August 2025.

Atmos fits into an existing broadcast chain at the encoder, not in the studio. A live sports mix is usually a channel-based immersive layout such as 5.1.4 or 7.1.4, because there is no time to automate free-moving objects. AWS Elemental MediaLive, for example, takes up to 16 PCM channels in a fixed order (L R C LFE Ls Rs Lb Rb Tfl Tfr Tsl Tsr Tbl Tbr Lw Rw), encodes Dolby Digital Plus with Atmos as 5.1.4, 7.1.4 or 9.1.6, or passes an Atmos stream through untouched, and signals it in HLS as CHANNELS="12/JOC" or "16/JOC". Everything after the encoder (playout, multiplexer, CDN, set-top box) carries one more audio track, and a legacy receiver simply decodes the 5.1 core. The work is in the encode settings, the dialnorm value and the loudness QC on that track, which is the part our custom video and audio processing team builds into live and VOD pipelines.

Costume 3: Atmos in music

Atmos crossed from film into music when Apple launched Spatial Audio on Apple Music in 2021, and the music costume has its own rules — different from video in two ways that catch people out: a different delivery split and, critically, a different loudness target.

On the delivery side, Apple Music and Amazon Music deliver Atmos as DD+ JOC (Amazon's developer documentation lists 448 and 768 kbps variants with 16 elements), while Tidal streams Atmos music in AC-4, according to Dolby. Music Atmos rides the same two carriage codecs as video Atmos.

The loudness rule is the one to memorise. Atmos music must not exceed −18 LKFS integrated loudness, measured per ITU-R BS.1770 (Apple's spec cites revision 4; the current revision is BS.1770-5, November 2023), with a true peak no higher than −1 dBTP, and albums are measured per track rather than aggregated. (LKFS and LUFS are the same scale for our purposes; broadcast and ATSC documents say LKFS, streaming and music documents tend to say LUFS.) That −18 LUFS target is deliberately quieter than a typical stereo master, which often sits around −10 to −14 LUFS after loudness-war mastering. The consequence is real and worth flagging to anyone shipping music: an Atmos mix played next to its stereo counterpart can sound softer, and engineers who do not account for this complain that the Atmos version feels "dull." It is not dull — it is correctly mastered to a quieter, more dynamic target.

Pitfall — using the wrong loudness target. Atmos music targets −18 LUFS integrated (per-track). Streaming video Atmos uses a different reference entirely: Netflix and Dolby specify roughly −27 LKFS dialogue-gated for home/streaming mixes (a dialogue-gated measurement, not the same method as integrated music loudness). These are different numbers measured in different ways for different content. Applying the music −18 to a film mix, or the video −27 to a music master, produces a deliverable that fails QC. Match the target to the domain.

One more music-specific detail catches engineers out. Because most Atmos music is heard on headphones, the Dolby Atmos Renderer lets the mixer set a Binaural Render Mode — Off, Near, Mid, or Far — for each bed channel and each object, controlling how "distant" that element sounds in Dolby's binaural render. Apple renders headphone playback with its own engine rather than Dolby's (Costume 4), so the same master can sound different on AirPods in Apple Music and on headphones in another app. For a product handling music ingest, the lesson is to listen to a master through both renderers before sign-off and never to strip the object metadata, because every headphone render is computed from it.

The production master for music — and for everything else — is the same file format, covered next.

Costume 4: Apple Spatial Audio (the binaural render)

The fourth costume is the one most consumers actually hear: Apple Spatial Audio, the head-tracked Atmos you get on AirPods. The distinction to hold firmly is that the Atmos master is object-based and speaker-agnostic, while what reaches your ears on headphones is a binaural render — a two-channel signal engineered so your two ears perceive full 3D placement. Binaural audio is not a production format; it is the output of a renderer.

Apple produces that render on-device, in real time. According to Apple's delivery documentation, the path is to downmix the Atmos master to 7.1.4, then virtualise that 7.1.4 to binaural — meaning Apple uses its own renderer rather than Dolby's binaural engine. Two extra features ride on top. Head tracking uses the headphone's motion sensors so that when you turn your head, the sound field stays anchored to the device, which is the same head-rotation idea that makes scene-based audio attractive for VR — but here it is applied to an object render. Personalised Spatial Audio captures the shape of your head and ears with the iPhone's TrueDepth camera (iOS 16 and later) to build a personalised model of how your anatomy colours sound from each direction — a head-related transfer function, covered in our ambisonics, HRTF, and binaural rendering article.

Figure 3. Apple Spatial Audio: the Atmos master is downmixed to 7.1.4, then virtualised to a head-tracked, optionally personalized binaural pair for headphones.

The thing all four share: the ADM BWF master

Cinema, home, music, and binaural are four deliveries of one source. That source is the Dolby Atmos master, and it exists in two equivalent forms. The first is a Dolby-specific trio of files — a .atmos metadata header, a .atmos.audio PCM payload, and a .atmos.metadata file holding the object positions and automation. The second, increasingly the interchange standard, is a single ADM BWF .wav file: a Broadcast Wave File whose embedded metadata follows the Audio Definition Model, the vocabulary specified in ITU-R BS.2076 (the in-force revision is BS.2076-3, February 2025), with the EBU's Tech 3364 as a companion. Dolby publishes a "Dolby Atmos Master ADM Profile" that pins down exactly how an Atmos master uses the ADM.

The technical baseline of that master is simple to remember: 24-bit linear PCM at 48 kHz, with 24 fps timecode. Since September 2026 Apple Music also accepts 96 kHz ADM masters and converts them to 48 kHz on ingest. Every costume in this article is rendered from that one file. When an engineer says "send me the ADM," they want this — the speaker-agnostic, object-based source, not a 5.1 downmix and not a binaural render.

This is also where the "real Atmos versus fake Atmos" question lives. Apple's music delivery rules are explicit that a stereo mix merely placed in the sound field with added ambience or reverb is not allowed — a genuine Atmos master requires authored object-based mixing, where a human (or a deliberate process) has placed sounds as objects with intent. An automated stereo-to-Atmos upmix that just sprinkles reverb around a flat mix is not a true Atmos master, and platforms that police it will reject it. For a product decision, the takeaway is that "we support Atmos" should mean "we ingest and deliver authored object masters," not "we run an upmixer."

How loudness works across the Atmos costumes

Loudness deserves its own short section because it is the most common place Atmos deliverables fail QC, and because the numbers differ by domain. Three references matter:

The music reference is −18 LUFS integrated, −1 dBTP true peak, measured per ITU-R BS.1770, per track. The streaming and home video reference is roughly −27 LKFS dialogue-gated (the value Dolby's professional encoder defaults its dialogue-normalisation, or "dialnorm," to for movie soundtracks, and that Netflix mandates for Atmos home mixes). The dialnorm value itself is metadata: it tells the decoder how loud the dialogue was authored to be, so the playback device can normalise different programs to a consistent level without re-encoding the audio.

The product-level lesson is that "what LUFS should Atmos be?" has no single answer — it depends on whether you are shipping music or video, and which measurement method (integrated versus dialogue-gated) the platform specifies. Get this wrong and the asset is rejected; get the measurement method wrong and you can hit the right number by the wrong route and still fail.

Decoding the speaker-layout notation

The three-number notation appears throughout Atmos documentation, and decoding it once removes most of the confusion. The pattern is floor . LFE . height:

• The first number counts the full-range, ear-level speakers around the listener.
• The second number counts the Low-Frequency Effects channel — the "LFE," the deep-bass channel your subwoofer plays. It is "point one" by convention: it is a band-limited channel (roughly 20–120 Hz) rather than a full-range one, so it is counted separately.
• The third number counts the overhead (ceiling) speakers — the height layer that makes Atmos "immersive."

So 5.1.2 is five ear-level speakers, one subwoofer, two overhead; 7.1.4 (Dolby's home reference layout) is seven ear-level, one sub, four overhead — twelve speakers; and 9.1.6, the largest named home layout Dolby publishes setup guides for, is sixteen. The same Atmos stream auto-adapts across all of them, because the renderer places the objects against whatever layout it finds. Note the domain split clearly: home layouts top out at the named 9.1.6 (and most consumer receivers cap at 7.1.4, 11 amplified channels plus a subwoofer output, a hardware limit rather than a format limit), while cinema scales to 64 independent feeds. Cinema and home are different worlds; do not quote a cinema speaker count when scoping a home or streaming feature.

The production pipeline, end to end

It helps to walk the chain once in order, because the four costumes are really four exits from a single road. The road starts in a digital audio workstation — Pro Tools, Nuendo, Logic, or similar — where a mixer assigns each sound either to a bed channel or to an object. Assigning to an object means giving that sound a position and, usually, automation: a path it travels over time. The DAW feeds the Dolby Atmos Renderer, which is the piece of software that monitors the mix (so the engineer can hear it on whatever local speaker layout or on binaural headphones) and, when the mix is finished, writes out the master — the ADM BWF .wav or the .atmos file trio described above. Nothing downstream sees the DAW session; everything downstream sees the master.

From that one master, each exit applies a different transform. The cinema exit packages the bed and objects into a DCP that the auditorium's processor renders live. The streaming exit runs spatial coding to reduce the scene to ~12–16 elements and then encodes them as E-AC-3 JOC or AC-4, producing the few-hundred-kbps stream a CDN actually serves. The music exit applies the −18 LUFS loudness pass and delivers the ADM BWF to Apple, Tidal, or Amazon, who encode it for their apps. The binaural exit — which can happen on the consumer's device rather than in the studio — downmixes to 7.1.4 and virtualises to a head-tracked stereo pair. The discipline that keeps all four consistent is that they all derive from the same authored master; an organisation that re-mixes per platform, rather than re-rendering from one master, multiplies its cost and its chances of drift between versions.

A second pipeline detail worth knowing is dialnorm, the dialogue-normalisation metadata mentioned in the loudness section. It is not audio; it is a number the encoder embeds that tells every playback device how loud the program's dialogue was authored to be. The device then attenuates so that a quiet documentary and a loud action film play back at a consistent dialogue level without anyone re-encoding the audio. For a streaming product, dialnorm is the lever that lets a catalogue of titles, mastered by different studios, present a uniform loudness to the viewer — set it wrong and viewers reach for the volume control on every title change.

A storage and CDN budget for Atmos

Product people need a number, so here is how to build one. The headline is that Atmos is cheap on the wire relative to video, because spatial coding has already done the heavy lifting. Take a premium film delivered with Atmos at 768 kbps and a two-hour runtime:

768 kbps × 7,200 s = 5,529,600 kbits = 5,529.6 Mbit
5,529.6 Mbit ÷ 8   = 691.2 MB per title for the Atmos audio rendition

Under 700 MB of audio for a two-hour film, against perhaps 8–20 GB for the 4K video of the same title — the Atmos track is a single-digit percentage of the total. If you also store separate 5.1 and stereo renditions, as many services do for players that cannot handle the JOC track, the math stays modest: a 5.1 E-AC-3 fallback at 384 kbps adds about 346 MB, and a stereo AAC fallback at 128 kbps adds about 115 MB. The three audio renditions together come to roughly 1.15 GB, still small beside the video. Switch the carriage to AC-4 at 320 kbps for the immersive track and the Atmos rendition alone drops to about 288 MB — the "half the bitrate" claim made concrete.

Pitfall — budgeting Atmos like it is 128 channels. The naive mistake is to size storage and egress as though you were carrying the studio's 128 inputs. As the worked example at the top of the streaming section showed, that would be ~147 Mbps and over 130 GB per two-hour title — two orders of magnitude too high. Always budget the delivery bitrate (a few hundred kbps), never the studio element count.

The CDN egress story follows directly: at 768 kbps, one hour of Atmos streamed to one viewer moves about 346 MB; at the AC-4 320 kbps figure, about 144 MB. Multiply by your concurrent-viewer peak and your average session length, and the audio component of egress is almost always dominated by the video component. The honest product takeaway is that adding Atmos to an existing video service is a small bandwidth cost; the real costs are authoring (you need genuine object masters, not upmixes), QC (loudness and the no-fake-Atmos rule), and device testing (making sure the JOC fallback actually degrades gracefully on the long tail of older hardware).

Where Atmos sits next to its rivals

For completeness, two adjacent formats come up whenever Atmos does. DTS:X is Dolby's main rival — also object-based, also layout-flexible, competing on ecosystem and licensing rather than on a different underlying philosophy; for a product decision, treat DTS:X and Atmos as the same category. MPEG-H 3D Audio, specified as ISO/IEC 23008-3, is the open ISO immersive standard that carries channel, object, and scene-based audio in one bitstream (up to 64 loudspeaker channels and 128 codec core channels) and is the broadcast-world alternative — the audio system of South Korea's ATSC 3.0 service and the mandatory codec of Brazil's TV 3.0, and one of two options (alongside Dolby AC-4) in the US ATSC 3.0 audio standard A/342. Atmos is not MPEG-H; when a broadcast target requires MPEG-H, that is a different authoring and carriage path, covered in MPEG-H 3D Audio: the ISO immersive standard.

Google's Eclipsa Audio is the newest contender: an open immersive format built on IAMF from the Alliance for Open Media, announced in January 2025 with YouTube support. It matters for products that publish to YouTube; it does not replace Atmos on Netflix-class services or in cinemas.

How Dolby licensing works for a streaming product

Dolby earns about 93% of its revenue from licensing, according to its fiscal 2025 annual report: device makers pay per-unit royalties for the decoders in TVs, phones, soundbars and cars, and much of its patent income comes through patent pools. A streaming service normally does not license the decoder, because the viewer's device already has one. It pays for Atmos-capable encoding and mastering tools through their vendors, so check the current terms of your encoder before you price an Atmos tier.

Quick answers

What bitrate does Netflix use for Dolby Atmos?

Netflix streams Atmos as DD+ JOC at 448–768 kbps, a range it introduced in May 2019, and only on its Premium plan.

Is streaming Dolby Atmos lossless?

No. Every streaming service delivers lossy Atmos (DD+ JOC or AC-4) at a few hundred kbps; lossless Atmos exists only as Dolby TrueHD on Blu-ray and in the cinema DCP.

Which TV broadcasts are in Dolby Atmos?

In 2026, NBC's Winter Olympics coverage on Peacock and NextGen TV, Xfinity's FIFA World Cup feeds, TNT Sports Premier League football, and TV Azteca free-to-air broadcasts in Mexico were all in Atmos.

Does Spotify support Dolby Atmos?

No. Spotify added lossless stereo in September 2025 but offers no Atmos or spatial audio; Apple Music, Amazon Music and Tidal do.

What loudness should a Dolby Atmos mix hit?

Atmos music must be no louder than −18 LUFS integrated, with true peak no higher than −1 dBTP (Apple), while streaming film and series Atmos uses about −27 LKFS dialogue-gated (Netflix).

How does Dolby Atmos fit into an existing broadcast system?

At the encoder: an Atmos-capable encoder takes a 5.1.4 or 7.1.4 mix (up to 16 PCM channels), outputs DD+ JOC or AC-4 as one more audio track, and legacy receivers decode its 5.1 core.

How much storage and CDN does Atmos add?

About 690 MB per two-hour title at 768 kbps, or about 346 MB of egress per viewer-hour, which is a single-digit percentage of the 4K video it ships with.

Does Dolby Atmos work over HDMI ARC?

Streaming Atmos in DD+ JOC at the usual 768 kbps or less does, because it fits within ARC's roughly 1 Mbps return path; lossless TrueHD Atmos from a Blu-ray player needs eARC.

Where Fora Soft fits in

Fora Soft has built video products since 2005 across streaming, OTT/Internet TV, video conferencing, e-learning, telemedicine, video surveillance, and AR/VR, and immersive audio is the part of those pipelines that users notice first when it is wrong. In OTT and streaming work we wire up Atmos delivery as E-AC-3 JOC — the broadly compatible default — with AC-4 where a target device base supports it, and we keep channel-based stereo and 5.1 fallbacks so a title plays correctly from a phone to a home cinema. We treat the ADM BWF master as the single source of truth and render the costumes from it, rather than upmixing stereo. In AR/VR projects, where the sound field must track the headset, we lean on the head-tracked rendering ideas that Apple's Spatial Audio popularised. The point of knowing all four costumes is practical: it is how you scope an Atmos feature that ships on the devices, and at the bitrates and loudness targets, your users and platforms actually require. Atmos delivery is built into the platforms our OTT and Internet TV development team ships, and music products with immersive playback come from our music software development practice.

The book

Audio for Video: A Complete Guide to Sound in Video Products: From Jitter Buffers and Lip Sync to Atmos, Quality Metrics, and Neural Codecs

Volume 5 of the handbook takes Atmos past the four costumes: how the renderer places beds and objects on real speakers and on head-tracked headphones, where DD+ JOC, AC-4 and MPEG-H differ once you have to ship them, and how to keep an immersive track in sync with the picture after it crosses the network. It also covers the loudness passes and the listening tests (MUSHRA, POLQA, ViSQOL) you need to prove an Atmos encode still sounds right. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

See our case studies

References

1. ETSI TS 102 366 V1.4.1 (2017-09), "Digital Audio Compression (AC-3, Enhanced AC-3) Standard." Controlling spec for E-AC-3 (Dolby Digital Plus); Enhanced AC-3 in Annex E; basis for the DD+ JOC streaming carriage and the 32 kbit/s–6.144 Mbit/s data-rate envelope. Tier 1 (official standard). https://www.etsi.org/deliver/etsi_ts/102300_102399/102366/01.04.01_60/ts_102366v010401p.pdf
2. ETSI TS 103 190-2 V1.3.1 (2025-07), "Digital Audio Compression (AC-4) Standard; Part 2: Immersive and personalized audio." Controlling spec for AC-4 immersive audio and Advanced Joint Object Coding (A-JOC); current 2025 revision; reference renderer in ETSI TS 103 448. Tier 1. https://www.etsi.org/deliver/etsi_ts/103100_103199/10319002/01.03.01_60/ts_10319002v010301p.pdf
3. ETSI TS 103 190-1 V1.4.1 (2025-07), "Digital Audio Compression (AC-4) Standard; Part 1: Channel based coding." AC-4 core codec specification. Tier 1. https://www.etsi.org/deliver/etsi_ts/103100_103199/10319001/01.04.01_60/ts_10319001v010401p.pdf
4. Recommendation ITU-R BS.2076-3 (02/2025), "Audio Definition Model." The ADM metadata model underlying the Dolby Atmos master ADM/BWF deliverable (the speaker-agnostic interchange master). Tier 1. https://www.itu.int/rec/R-REC-BS.2076/en
5. Recommendation ITU-R BS.1770-5 (11/2023), "Algorithms to measure audio programme loudness and true-peak audio level." Current revision; Apple's Atmos music spec still cites revision 4. Loudness-measurement method underlying the −18 LKFS music target, the −1 dBTP true-peak limit, and the dialogue-gated video reference. Tier 1. https://www.itu.int/rec/R-REC-BS.1770-5-202311-I
6. ISO/IEC 23008-3, "MPEG-H 3D Audio" (Part 3). The open ISO immersive standard used for comparison; carries channel/object/HOA in one bitstream, up to 64 loudspeaker channels and 128 codec core channels. Tier 1 (MPEG overview page; normative text sold by ISO). https://www.mpeg.org/standards/MPEG-H/3/
7. Dolby Laboratories, "Dolby Atmos Renderer Guide." Source for the 128-input renderer limit (beds + objects), the up-to-118-object cap, the 7.1.2 home bed, and the Atmos master file formats. Tier 4 (first-party vendor). https://professional.dolby.com/siteassets/content-creation/dolby-atmos/dolby_atmos_renderer_guide.pdf
8. Dolby Laboratories, "Dolby Atmos Cinema Sound." Source for cinema figures: up to 64 independent speaker feeds, a 9.1 bed plus up to 118 objects (up to 128 tracks), single-DCP real-time rendering, and the cinema "lossless" carriage. Tier 4. https://professional.dolby.com/cinema/dolby-atmos/
9. Dolby Laboratories, "Dolby AC-4: Audio Delivery for Next-Generation Entertainment Services" (white paper). Source for AC-4 immersive 7.1.4 bitrates (~192–320 kbps) and Immersive Stereo (64–256 kbps), and the "~half the bitrate of DD+" efficiency claim. Tier 4 (vendor characterization, not a hard spec limit). https://professional.dolby.com/siteassets/technologies/dolby_atmos_ac-4_whitepaper.pdf
10. Dolby Laboratories, "Dolby Atmos encoding" (Hybrik documentation). Source for spatial coding to 12/14/16 elements, the DD+ JOC minimum data rates (384 kbps for 12 elements, 448 kbps for 16), and the JOC backward-compatibility model. Tier 4. https://docs.hybrik.com/tutorials/dolby_atmos/
11. Apple, "Delivering Dolby Atmos audio" (Apple Music Provider Support). Source for the music master format (ADM BWF, 24-bit/48 kHz), the −18 LKFS / −1 dBTP music loudness target, the 7.1.4-downmix-then-binaural render path, and the no-upmix ("not allowed") rule. Tier 4. https://itunespartner.apple.com/music/support/5216-delivering-dolby-atmos-audio
12. Netflix, "Dolby Atmos Home Mix Deliverable Requirements v2.3." Source for the ~−27 LKFS dialogue-gated home/streaming loudness reference. Tier 4. https://partnerhelp.netflixstudios.com/hc/en-us/articles/115001539991
13. Netflix, "Bringing Studio Quality Sound to Netflix" (May 2019). Source for Atmos at 448–768 kbps on the Premium plan. Tier 4. https://about.netflix.com/en/news/bringing-studio-quality-sound-to-netflix
14. Amazon Music for Developers, "Audio formats." Source for Atmos as DD+ JOC at 448 and 768 kbps (16 elements) and 360RA as MPEG-H. Tier 4. https://developer.amazon.com/docs/music/audio-formats.html
15. AWS, "Eac3AtmosSettings" (Elemental MediaConvert API). Source for the DD+ JOC bitrate presets 384–1,024 kbps. Tier 4. https://docs.aws.amazon.com/sdk-for-ruby/v3/api/Aws/MediaConvert/Types/Eac3AtmosSettings.html
16. AWS, "Working with Dolby Digital Plus with Dolby Atmos" (Elemental MediaLive User Guide). Source for the 16-channel live input order, 5.1.4/7.1.4/9.1.6 outputs, passthrough and HLS JOC signalling. Tier 4. https://docs.aws.amazon.com/medialive/latest/ug/feature-dolbyatmos.html
17. Apple, "HLS Authoring Specification for Apple Devices." Source for the single-bitrate rule for Atmos and the JOC value in the CHANNELS attribute. Tier 4. https://developer.apple.com/streaming/hls-authoring-specification-for-apple-devices.html
18. Apple, "Apple Video and Audio Asset Guide" (updated September 2026). Source for 48/96 kHz ADM BWF Atmos music masters. Tier 4. https://help.apple.com/itc/videoaudioassetguide/en.lproj/static.html
19. Dolby, "Dolby AC-4 on TIDAL." Source for Tidal delivering Atmos music in AC-4. Tier 4. https://professional.dolby.com/en-gb/technologies/ac-4/tidal/
20. Dolby, "Dolby Sets the New Standard for Premium Entertainment at CES 2026" (6 January 2026). Source for Peacock's Atmos on live sports and planned AC-4 adoption. Tier 4. https://s27.q4cdn.com/365963565/files/doc_news/Dolby-Sets-the-New-Standard-for-Premium-Entertainment-at-CES-2026-2026.pdf
21. HBO Max Help Center, Dolby Atmos availability. Source for Atmos on the Premium plan. Tier 4. https://help.hbomax.com/us/Answer/Detail/000002549
22. NBC Olympics, "Video and audio quality" (Milan Cortina 2026). Source for Peacock 4K HDR with Atmos and NextGen TV 1080p Dolby Vision and Atmos. Tier 4. https://nbcolympics.com/video-audio-quality
23. TV Technology, "Comcast Xfinity to deliver 4K coverage of FIFA World Cup 2026" (June 2026). Source for 104 matches with Dolby Vision and Atmos. Tier 5 (trade press reporting Comcast). https://www.tvtechnology.com/business/comcast-xfinity-to-deliver-4k-coverage-of-fifa-world-cup-2026
24. Sports Video Group, "NAB 2026: Dolby and TV Azteca deploy Dolby Atmos for free-to-air broadcast" (21 April 2026). Tier 5 (trade press). https://www.sportsvideo.org/2026/04/21/nab-2026-dolby-and-tv-azteca-deploy-dolby-atmos-for-free-to-air-broadcast/
25. What Hi-Fi?, "BT to broadcast Premier League matches with Dolby Atmos sound" (2017). Tier 5 (trade press). https://www.whathifi.com/news/bt-to-broadcast-premier-league-matches-dolby-atmos-sound
26. ATSC, "A/342 Part 2: AC-4 System" (revised July 2025). Tier 1. https://www.atsc.org/atsc-documents/a342-part-2-ac-4-system/
27. Fraunhofer IIS, "Brazil signs decree for DTV+ (TV 3.0)" (2025). Source for MPEG-H as the mandatory DTV+ audio codec; vendor source (Fraunhofer develops MPEG-H). Tier 4. https://www.audioblog.iis.fraunhofer.com/dtv_decree
28. Spotify Newsroom, "Lossless listening arrives on Spotify Premium" (10 September 2025). Tier 4. https://newsroom.spotify.com/2025-09-10/lossless-listening-arrives-on-spotify-premium-with-a-richer-more-detailed-listening-experience/
29. Google Open Source Blog, "Introducing Eclipsa Audio" (January 2025). Source for the IAMF-based format and YouTube support. Tier 4. https://opensource.googleblog.com/2025/01/introducing-eclipsa-audio-immersive-audio-for-everyone.html
30. Dolby Laboratories, Form 10-K for the fiscal year ended 26 September 2025 (SEC EDGAR). Source for the licensing model: per-unit royalties from device makers and patent-pool income. Tier 4.

Note on source hierarchy (per our research standard): where a vendor description and a controlling standard disagree, the article follows the standard. Codec-carriage facts are anchored to the ETSI and ITU-R standards above; Dolby and Apple documents are cited for deployment specifics (renderer limits, encoder minimums, platform loudness targets) that the standards do not fix. The per-platform music codec split is now anchored to first-party documents (Amazon Music developer docs for DD+ JOC, Dolby for Tidal on AC-4); broadcast and service-support facts were checked against the broadcaster, service or Dolby pages on 17 October 2026.