Some links on this page are Amazon affiliate links. If you buy through them, we earn a small commission at no extra cost to you.

Overview
Loudness compliance is one of the few areas of production governed by actual regulation, and it is measured rather than judged, so a mix that sounds right can still fail. The good news is that the rules are simple once the units make sense, and meeting them does not require compressing the life out of a programme. This guide covers what the measurements mean, how to hit a target while preserving dynamics, and the specific mistakes that produce failures.
What You Need
- A loudness meter that measures to the standard your spec names
- The delivery specification, which states the target and tolerance
- A true peak limiter, used as a safety net rather than as a mixing tool
- The full programme, since loudness is measured across the whole thing
- Monitoring you trust at a consistent level
- A measurement report to accompany delivery, if required
Steps
Understand the target is an average over the programme
Programme loudness is measured across the entire piece, not moment to moment. That means quiet passages and loud passages both contribute, and a programme can contain considerable dynamic range while still averaging to the required value. This is the fact that makes compliance compatible with good mixing.
Mix for the programme, then normalise
Mix so the material sounds right, then measure the whole programme and apply a single gain offset to bring the average to target. This is the correct approach and it preserves your balance decisions entirely. Compressing sections to chase the meter during mixing is what produces flat, fatiguing programmes.
Treat true peak as a separate limit
True peak measures the actual analogue level a converter will reconstruct, which can exceed the highest digital sample. Specs set a ceiling below zero for this reason. Meeting it is a limiter placed last in the chain, set to the required ceiling, not something you mix toward.
Watch dialogue level within the loudness target
Two programmes can measure identically while one has clearly audible dialogue and the other buries it under music and effects. Some specifications address this explicitly. All audiences notice it. Check that speech sits at a consistent, intelligible level rather than only that the programme measures correctly.
Measure the final file, not the timeline
Export processing, format conversion, and downmixing can all change measured loudness. Measure the actual deliverable, in the channel configuration being delivered, and generate the report from that file. A timeline measurement is an estimate of what you are delivering.
Check the downmix if one will be made
If a surround programme will be downmixed for stereo playback, that downmix can measure differently and can suffer phase cancellation. Where the spec requires both, check both. Where it does not, check anyway, because a large share of your audience will hear the downmix.
Theatrical Film vs. Streaming Delivery & Automated QC
Understanding the distinction between room-calibrated theatrical mixing, web monitoring, and streaming platform QC prevents unwanted audio processing during distribution:
- Theatrical Room Calibration (85 dB SPL): Theatrical mixes are made to a calibrated room rather than to a loudness number. Netflix's sound mix spec sets no LKFS requirement for theatrical mixes and calibrates them to a reference of 85 dB SPL, and its near field mixes to 79 or 82 dB SPL, both from a -20 dBFS reference. ATSC A/85 uses 85 dB SPL, C-weighted and slow, only for rooms over 20,000 cubic feet, and steps down to 76 dB SPL for rooms under 1,500 cubic feet.
- Near Field Streaming (-27 LKFS) vs. Broadcast (-24 LKFS, -23 LUFS): Netflix's current spec asks for near field mixes at -27 LKFS ±2 LU, dialog-gated, measured to ITU-R BS.1770-1 across the whole programme. Where dialogue is under 15 percent of the programme, the whole mix is measured instead, at -24 LKFS ±2 LU. ATSC A/85, the recommended practice for US digital television, gives -24 LKFS. EBU R 128 sets -23.0 LUFS ±0.5 LU, or ±1.0 LU for live programmes. Other services publish their own figures, and the delivery spec you are given is the one that counts.
- Tolerance Is Not a Target: ATSC A/85 treats its ±2 dB as room for measurement variation and says content should not be aimed at the high or low side of it. EBU R 128 allows only ±0.5 LU. Aim at the number itself. What a platform does with a file outside tolerance, whether it rejects it or changes its gain, depends on the platform and is not set out in the documents read for this page.
- True Peak Safety (-2 dBTP to -5 dBTP): While nominal true peak specs specify -2 dBTP, many streaming automated processors crush peaks down to -5 dBTP. Setting your final limiter ceiling to -5 dBTP prevents unexpected distortion from automated platform limiters.
- Assembled Delivery Metering: Always measure the full, assembled final file (no reel breaks, 2-second heads/tails) using meters like iZotope Insight 2, Youlean Loudness Meter 2, or Waves WLM Plus before signing off on QC.
Pro Tips
- Mix first, normalise once. Chasing the meter while mixing produces flat programmes.
- Aim within ±1 LUFS of your target to pass automated streaming QC without aggressive gain-clipping.
- True peak limiting goes last in the chain and is a safety net, not a loudness tool. Set to -5 dBTP for safety against streaming platform gates.
- Measure the delivered file in the delivered channel configuration. Timeline measurements are estimates.
- Watch dialogue intelligibility separately from the loudness number. They are not the same thing.
- Keep the measurement report. It is evidence if a delivery is queried.
Tested: what integrated loudness counts, and what a gain change or a downmix does to it
We tested steps 1, 2, 5 and 6 on 2026-09-30 with FFmpeg 8.1.2's ebur128 filter, on synthetic band-limited noise programmes. This overlaps other guides' loudness tests and adds this page's own claims. The page's cinema and streaming target figures in the last section are not tested here. They were checked against the documents under Sources on 2026-10-05 and corrected on 2026-10-06.
| Programme | Integrated loudness | Loudness range |
|---|---|---|
| Loud programme alone, 60 s | -23.0 LUFS | 7.1 LU |
| The same followed by 60 s at about -50 LUFS | -23.2 LUFS | - |
| The loud programme with +6.02 dB of gain | -16.9 LUFS | 7.0 LU |
| A 5.1 programme, measured as 5.1 | -16.1 LUFS | - |
| The same downmixed to stereo by FFmpeg | -17.8 LUFS | - |
| Front pair with the surround pair in phase, downmixed | -16.0 LUFS | - |
| Front pair with the surround pair polarity inverted, downmixed | -31.3 LUFS | - |
Step 1 needs a limit. Adding a minute at about -50 LUFS to a minute at -23 LUFS left the integrated loudness at -23.2, unchanged, because the measurement gates out anything more than 10 LU below the running average. The page says quiet and loud passages both contribute. That holds for a passage a few LU down and not for very quiet ones, which is worth knowing when a programme has long near-silent stretches.
Step 2 holds. A gain of 6.02 dB moved integrated loudness by 6.10 LU, the small excess coming from the measurement's gate, and moved the loudness range from 7.1 to 7.0 LU, so a single offset keeps every balance decision, as the page says.
Steps 5 and 6 hold. The same 5.1 programme measured -16.1 LUFS as 5.1 and -17.8 after FFmpeg's stereo downmix, -1.7 LU apart, so a spec measured on one does not describe the other. With the front and surround pairs identical, the downmix measured -16.0 LUFS, and with the surround pair polarity inverted -31.3, a drop of 15.3 LU from phase cancellation alone. That is an extreme case, since the front and surround signals were identical, and real programmes fall somewhere between.
Validated for the measurements. Measured 2026-09-30 with FFmpeg 8.1.2 (ebur128) on synthetic noise, using its default downmix coefficients. Other downmix matrices and real programme material give other numbers. The delivery figures in the page's theatrical and streaming section come from the documents under Sources, not from this test.
Knowledge Base
What You'll Learn
Loudness regulation exists for a specific historical reason and the measurements were designed to match perception. Below: what the units mean, and why compliance does not require compression.
Why Loudness Is Regulated and What the Units Mean
Loudness regulation exists because of a real and widely experienced problem: advertisements and channel changes producing sudden jumps in volume, because broadcasters were normalising to peak level rather than to perceived loudness.
Peak level measures the highest sample value and correlates poorly with how loud something sounds. A heavily compressed advertisement and a dynamic drama can share the same peak while differing enormously in perceived loudness, which is precisely what produced the complaints.
Loudness units were designed to match perception. The measurement applies a frequency weighting approximating human hearing sensitivity and integrates over time, producing a number that tracks how loud something actually seems. Programme loudness is that measurement across the whole piece.
True peak addresses a separate technical problem: the analogue waveform reconstructed from digital samples can exceed the highest sample value, so a file that never reaches full scale digitally can still clip on playback. Specs therefore set a ceiling comfortably below zero.
Together these mean a compliant programme is one that sounds consistent with everything else on the channel and does not distort on any playback path.
Why Compliance Does Not Require Compression
The persistent misconception is that hitting a loudness target means compressing everything, producing flat and fatiguing audio. It follows from confusing an average with a ceiling.
Programme loudness is an average across the whole programme. A piece with quiet passages and loud ones averages out, and the target says nothing about how much variation is permitted around that average. A drama with whispered dialogue and loud action can comply perfectly while retaining its full dynamic range.
What compliance does require is that the average lands on target and no peak exceeds the true peak ceiling. Both are achieved by mixing normally, measuring the finished programme, applying a single gain offset, and placing a limiter as a final safety net.
The historical reason for the confusion is that the previous regime normalised to peak, which genuinely did reward compression, making something as loud as possible within a peak ceiling meant reducing dynamics. Loudness normalisation removed that incentive entirely, and heavily compressed material now simply gets turned down.
Where This Fits
Loudness is checked at the QC gates Broadcast Media Ingest places through the pipeline from ingest.
FAQ
Q: Does meeting a loudness target mean I have to compress everything?
A: No. Programme loudness is an average across the whole piece, so quiet and loud passages both contribute and considerable dynamic range is compatible with compliance. Mix normally, measure the finished programme, and apply a single gain offset. Compressing to chase the meter is what produces flat, fatiguing audio.
Q: What is the difference between peak and true peak?
A: Peak measures the highest digital sample. True peak estimates the actual analogue level reconstructed on playback, which can exceed the highest sample, so a file that never hits full scale digitally can still clip on a converter. Specs set a true peak ceiling below zero for exactly this reason.
Q: Where should the true peak limiter go?
A: Last in the chain, set to the ceiling the spec requires, functioning as a safety net rather than as a loudness tool. If it is doing substantial work, something earlier in the mix is too hot: the limiter should catch occasional transients, not shape the programme.
Q: Should I measure the timeline or the exported file?
A: The exported file, in the channel configuration being delivered. Export processing, format conversion, and downmixing can all change measured loudness, so a timeline measurement is an estimate of what you will deliver rather than a measurement of it.
Sources
Read 5 October 2026. These three documents give the targets and room levels in the theatrical and streaming section. No Dolby document giving a cinema reference level was reached, and no source was found for the -13 LUFS figure this page used to give for laptop listening, so both were removed.
- EBU R 128, Loudness normalisation and permitted maximum level of audio signals (V5, November 2023). Sets the target at -23.0 LUFS with a tolerance of ±0.5 LU, and ±1.0 LU for live programmes. Its supplement R 128 s4 (November 2023, cinematic content) also normalises to -23.0 LUFS and gives no -27 figure.
- ATSC A/85:2013, Techniques for Establishing and Maintaining Audio Loudness for Digital Television, with Corrigendum No. 1 (11 February 2021). Section 6 says content exchanged without metadata should have a target loudness of -24 LKFS, that ±2 dB is measurement uncertainty and not a range to aim at either side of, and that true peak should stay below -2 dBTP. Table 10.2 sets the monitoring level by room volume, from 85 dB SPL above 20,000 cubic feet down to 76 dB SPL under 1,500.
- Netflix, Sound Mix Specifications and Best Practices (branded content, version OC-1-6, 29 October 2024). Near field mixes at -27 LKFS ±2 LU, dialog-gated, to ITU-R BS.1770-1, true peak no higher than -2 dBTP, monitored at 79 or 82 dB SPL. Theatrical mixes at an 85 dB SPL reference with no LKFS requirement. The spec's first version is dated July 2018, but its 2018 text was not read. Licensed content falls under a separate delivery specification, also not read.
Translate this page
- Español
- 简体中文
- हिन्दी
- العربية
- Português
- Français
- Deutsch
- 日本語
- Русский
- Bahasa Indonesia
- 한국어
- Italiano
- Türkçe
- Tiếng Việt
- Polski
- Nederlands
Machine translation provided by Google Translate, on Google’s servers. We do not check these translations and they will get technical terms wrong. The English page is the authoritative one. Following a link sends this page’s address to Google. Your browser may also offer to translate this page itself, which keeps the request on your device.