LUFS vs. RMS: What's the Difference and Which Number Should You Hand to a Mixer?

The Deliverable That Failed QC

A post-production sound editor delivered a television drama mix at -18 dBRMS, which is a reference level their facility had used for years on broadcast work. The broadcaster rejected the mix. Their QC check flagged it as too loud by approximately 5 LUFS. The editor had been monitoring in RMS and assumed RMS and LUFS were close enough to be interchangeable. They are not -- and the two-day re-mix cost the production its final payment deadline.

The problem was not the quality of the mix. It was delivering a number the platform did not use, for a target the platform did not specify.

This post explains how RMS and LUFS are calculated differently, why they produce different readings from the same audio file, and what to put in the handoff document when handing a mix to a re-recording mixer or delivering to a platform.

The loudness targets cited below are drawn from current platform specifications: EBU R128 (European Broadcasting Union), ATSC A/85 (US broadcast), Netflix Sound Mix Specifications (2025), and Spotify / YouTube / Apple Music loudness documentation as of early 2026.

How RMS and LUFS Are Calculated Differently

Both RMS and LUFS are ways of measuring the average level of an audio signal -- but they make different assumptions about what "average" means and what the signal represents.

RMS (Root Mean Square)

RMS measures the mathematical average power of the signal over a short time window. The calculation is: square all sample values, take their mean, then take the square root. The result is expressed in dBFS (decibels relative to full scale). The time window is typically 300ms, meaning RMS responds relatively quickly to transient changes in level. RMS applies no frequency weighting -- it treats a 50Hz bass rumble the same as a 3kHz speech frequency, despite the fact that human hearing perceives them very differently at equal power.

LUFS (Loudness Units relative to Full Scale)

LUFS is based on the ITU-R BS.1770 standard. It adds three key differences on top of the core RMS measurement. First, it applies K-weighting: a frequency curve that attenuates low frequencies and slightly boosts high-mids, mimicking the response of human hearing. Second, it uses a 400ms Momentary window, a 3-second Short-Term window, or a full-program Integrated measurement depending on which value you are reading. Third, the Integrated LUFS uses gating: silent or very quiet passages below -70 LUFS are excluded from the average, so a film with long quiet sections is not penalised for those passages.

The practical result: a mix heavy with low-frequency content (bass music, explosions, LFE) will measure quieter in LUFS than in RMS, because K-weighting reduces the contribution of bass energy to the perceived loudness reading. A mix with prominent mid-frequency speech will read similarly in both systems.

Three Real-World Handoff Examples

Example 1: Television Drama, EBU R128, -23 LUFS

A UK broadcaster requires all programme deliveries to meet EBU R128: Integrated LUFS of -23.0 LUFS with a maximum True Peak of -1 dBTP. The re-recording mixer receives a pre-mix from a dialogue editor at -20 dBRMS. The mixer runs the file through a BS.1770 loudness meter and reads -19.5 LUFS Integrated -- approximately 3.5 LUFS louder than the delivery target. The mixer attenuates the master fader by 3.5 LUFS, re-checks the Integrated measurement, and confirms the True Peak on music passages does not exceed -1 dBTP before delivery. The handoff document from the dialogue editor specifying "-20 dBRMS" was not actionable for this workflow -- a target of "-23 LUFS Integrated, EBU R128" would have been.

Example 2: Streaming Feature Film, Netflix, -27 LUFS

A feature film mix is delivered to Netflix. Current Netflix specifications require a Dialogue Norm of -27 LUFS Integrated and a maximum True Peak of -2 dBTP for stereo and surround mixes. The re-recording mixer monitors loudness in real time using a LUFS meter (Waves WLM Plus, iZotope Insight, or equivalent). The final Integrated reading across the full feature is confirmed at -27.2 LUFS -- within the ±1.0 LUFS tolerance Netflix permits. RMS is never referenced during this workflow because Netflix QC does not check it.

Example 3: Music Documentary, Streaming Audio, Multiple Platforms

A music documentary contains concert performance audio intended for both broadcast and music streaming platforms. The broadcast version requires -23 LUFS (EBU R128). The streaming music version on Spotify and YouTube will be normalised to -14 LUFS. The mixer delivers two separate versions: one mixed to -23 LUFS for broadcast with full dynamic range, and one mixed to -16 LUFS for streaming (knowing that -14 LUFS normalisation will bring it up slightly). Delivering both at -23 LUFS would result in the streaming version being turned up 9 LUFS by the platform's automatic normalisation, which would crush transients and degrade the listening experience.

LUFS Targets by Platform

The table below shows current Integrated LUFS targets and True Peak limits for major delivery platforms. These values reflect specifications current as of early 2026.

Netflix is significantly quieter than streaming music platforms because the -27 LUFS target preserves dynamic range for film dialogue and sound design. Music streaming platforms target -14 LUFS because listeners expect louder, more compressed music mixes. Delivering film audio at music streaming loudness levels destroys the dynamic range that makes the film sound mix work in a cinematic context.

How to Specify Loudness in a Handoff Document: Step by Step

Step 1: Identify the delivery destination for the project: broadcast (which country/standard), streaming video (which platform), streaming audio (which platforms), or theatrical. Each has a different target.

Step 2: Find the current loudness specification for that destination. Use the platform's published technical specifications rather than assuming the values have not changed. Netflix, Apple, and streaming services update their specs periodically.

Step 3: Write the handoff specification as Integrated LUFS target, True Peak limit, and applicable standard: for example, "Target -23.0 LUFS Integrated, max -1.0 dBTP (EBU R128)." Do not specify RMS unless the delivery spec explicitly requires it.

Step 4: If the project has multiple destinations, specify separate loudness targets for each version. A broadcast delivery and a streaming delivery from the same film should receive separate handoff documents -- or a single document with clearly labelled separate sections for each version.

Step 5: Use the LUFS Loudness Calculator to confirm your Integrated LUFS and True Peak readings before sending the handoff. A confirmed reading sent with the handoff document eliminates any ambiguity about what the mix currently measures and where the mixer needs to land.

At the end of this process the mixer has a single, unambiguous number to hit, specified in the standard the delivery platform actually uses.

Pro Tips and Common Mistakes

Pro Tip: The Integrated LUFS reading changes as the program plays -- it is the running average over everything from the start of the program to the current playhead position. Do not read it from the middle of the mix. A full-program Integrated LUFS reading must be taken by measuring from the first frame to the final frame with the loudness meter running throughout. Most loudness meters have a "Start / Reset" and a "Stop" function for exactly this workflow.

Pro Tip: Loudness targets for streaming music platforms are normalisation targets -- the platform will turn content up or down to hit them. Delivering at exactly -14 LUFS for Spotify means no normalisation is applied. Delivering significantly quieter than -14 LUFS means the platform turns your content up, which can reveal noise floor issues or introduce artefacts if the material was compressed or limited before delivery. For music mixes, targeting between -14 and -16 LUFS Integrated is the practical sweet spot across streaming platforms.

Pro Tip: True Peak and RMS peak are different measurements. True Peak uses inter-sample peak detection to catch clipping that occurs after digital-to-analogue conversion -- clipping that sample-peak meters miss. Always use a True Peak meter, not a standard peak meter, when checking compliance against a dBTP limit. Delivering a mix that passes sample-peak checks but fails True Peak is a common QC failure on content with heavily compressed or limited dynamics.

Common Mistake: Treating Short-Term or Momentary LUFS as the delivery target. Short-Term LUFS (3-second window) and Momentary LUFS (400ms window) are monitoring tools for tracking loudness during mixing. The delivery specification is almost always Integrated LUFS -- the program average from start to finish. Confusing a short-term reading of -22 LUFS during a loud scene with the Integrated program level is a frequent source of delivery errors.

Common Mistake: Applying a limiter to hit the True Peak target after mixing to loudness, without rechecking the Integrated LUFS afterwards. If your mix is at -23.1 LUFS Integrated and your True Peak is at -0.5 dBTP, applying a True Peak limiter to bring peaks to -1.0 dBTP may slightly reduce the Integrated LUFS reading (because limiting reduces average energy). The resulting Integrated value may now be -23.4 LUFS -- still within tolerance, but worth a final check rather than assuming the Integrated reading is unchanged after peak limiting.

Frequently Asked Questions

Can I convert an RMS reading to LUFS for the same file?

There is no fixed conversion factor because the difference between RMS and LUFS depends on the spectral content of the material. Speech-heavy content may show only 1 to 2 LUFS difference from RMS. Bass-heavy music may show 4 to 8 LUFS difference. The only reliable approach is to measure LUFS directly from the file using a BS.1770-compliant loudness meter.

Why does Netflix require -27 LUFS when broadcast requires -23 LUFS?

Netflix specifies -27 LUFS to preserve the full dynamic range of cinematic sound design. A -23 LUFS target for a feature film with wide dynamics (quiet dialogue at -40 LUFS, action sequences peaking near -10 LUFS) would result in louder average levels that compress the perceived dynamic range. The -27 LUFS target gives the mixer room to maintain natural dynamics while still hitting a measurable, QC-checkable delivery level.

What happens if I deliver to a streaming platform louder than the target?

For platforms that normalise (YouTube, Spotify, Apple Music), content louder than the normalisation target is turned down. Delivering at -12 LUFS to a platform targeting -14 LUFS means your content plays at a level 2 LUFS lower than if you had delivered at -14 LUFS -- the platform applies gain reduction, not gain increase, for content above target. The subjective result may also include compression artefacts from peak limiting applied to bring True Peaks into compliance before or after normalisation.

Is LUFS the same as LKFS?

Yes. LKFS (Loudness, K-weighted, relative to Full Scale) and LUFS are the same measurement. LKFS is the notation used in the ITU-R BS.1770 standard and in US broadcast documentation (ATSC A/85). LUFS is the notation adopted in EBU R128 and widely used in music production. Both describe loudness in 1 LU (Loudness Unit) increments where 1 LU = 1 dB in this context.

Related Tools

The LUFS Loudness Calculator measures Integrated, Short-Term, and Momentary LUFS along with True Peak for any audio file, providing a delivery-ready readout for any platform spec. For stem-level loudness management across a complex mix, the Audio Bitrate and Storage Calculator helps plan storage and bitrate requirements alongside loudness targets for different delivery formats.

For the downstream delivery workflow once loudness is confirmed, Audio Delivery Standards for Film and Television covers the full technical requirements for broadcast, streaming, and theatrical submission. For understanding sample rate and bit depth decisions that affect loudness measurement precision, Sample Rates in Film and Audio Post covers the foundational audio specifications.

One Standard for the Delivery Destination

RMS is useful for monitoring relative levels during a mix session. LUFS is the delivery currency. Every major broadcast network, streaming video platform, and streaming audio service specifies delivery in LUFS Integrated, not RMS. Handing a mixer an RMS target requires them to do a conversion that introduces inaccuracy. Handing them an Integrated LUFS target with a True Peak limit gives them a single, unambiguous number to hit against the same meter the QC process will use. The handoff document should always read in the unit the destination platform uses.

This post covers stereo and standard 5.1 surround deliveries. Dolby Atmos, Auro-3D, and spatial audio formats have additional loudness measurement considerations that differ from the ITU-R BS.1770 framework. What platform has the most stringent loudness QC you have encountered, and did you have to re-mix to pass it?