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

The Handoff Document That Crashed the Delivery

A post-production sound editor finishes the dialogue edit on a half-hour television drama. They send the pre-mix to the re-recording mixer with a note: "targeting -18 dBRMS, which is what the facility has used for broadcast for years." The mixer uses the RMS target as a guide and hits it. The mix gets delivered to the broadcaster. QC flags it as 5 LUFS over their -23 LUFS integrated requirement. The show's first air date is in six days. The re-mix runs two days and costs the facility its delivery bonus.

Nobody made an error in the mix itself. The error was in the handoff spec. The broadcaster's QC team measures integrated LUFS per EBU R128. Delivering an RMS number to a LUFS standard is not a translation problem -- it is delivering the wrong metric entirely.

This post explains how RMS and LUFS are calculated differently, why they produce different readings from the same file, and exactly what to write in a handoff document so your mixer has a single unambiguous number to hit.

The loudness targets in this post are drawn from EBU R128 (European Broadcasting Union), ITU-R BS.1770-4 (the international loudness algorithm), ATSC A/85 (US broadcast standard), and current Netflix, Spotify, YouTube, and Apple Music delivery specifications as of July 2026.

How RMS and LUFS Are Calculated Differently

Both RMS and LUFS measure average audio level, but they make different assumptions about what "average" means.

RMS (Root Mean Square) measures the mathematical average power of the signal over a short time window, typically 300ms. The formula: square all sample values, take their mean, take the square root. Result expressed in dBFS. RMS applies no frequency weighting. A 50Hz bass rumble and a 3kHz speech frequency at the same RMS level sound very different in perceived loudness because human hearing responds differently at those frequencies. RMS has no mechanism to account for that difference.

LUFS (Loudness Units Full Scale) builds on the core RMS calculation but adds three things. First: K-weighting, a frequency curve that attenuates low frequencies and slightly boosts high-mids, designed to approximate human hearing response. Second: three separate time windows -- momentary (400ms), short-term (3 seconds), and integrated (full program duration). Third: gating for the integrated measurement, which excludes very quiet passages below -70 LUFS from the running average. A feature film's long silences don't pull the integrated loudness down, which would create an artificially quiet reading that doesn't reflect the perceived loudness of the program.

The practical result is that a mix heavy with bass content (LFE, action effects, kick drums) reads quieter in LUFS than in RMS, because K-weighting reduces the contribution of those frequencies. A dialogue-heavy mix with minimal bass reads more similarly in both systems. For any mix, the difference between RMS and LUFS is not a fixed conversion factor -- it depends entirely on the spectral content of the material.

Three Real-World Handoff Scenarios

Example 1: Television Drama, EBU R128, UK Broadcast

A UK broadcaster requires EBU R128 compliance: -23.0 LUFS integrated, -1 dBTP true peak. The re-recording mixer receives a pre-mix from the dialogue editor specified at -20 dBRMS. The mixer runs the file through an iZotope Insight 2 loudness meter and reads -19.5 LUFS integrated: approximately 3.5 LU over the delivery target. The mixer pulls the master fader down by 3.5 dB, re-checks that the true peak on music passages doesn't exceed -1 dBTP, and delivers. The pre-mix RMS spec was unusable for this workflow. A spec of "-23 LUFS integrated, EBU R128, max -1 dBTP" would have sent the mixer directly to the correct measurement without a conversion step.

Example 2: Feature Film, Netflix, -27 LUFS

A narrative feature delivers to Netflix. The spec requires -27 LUFS integrated dialogue norm, -2 dBTP true peak, for stereo and surround mixes. The re-recording mixer uses Waves WLM Plus on the master bus throughout the session. The final integrated reading across the full 102-minute feature lands at -27.2 LUFS, within Netflix's ±1 LU tolerance. RMS is never referenced during the session. Netflix QC does not check RMS. The handoff document the production sent the mix stage specified LUFS throughout; no translation was required.

Example 3: Music Documentary, Dual Delivery, Broadcast and Streaming

A feature documentary with concert performance audio delivers to both a European broadcaster (EBU R128, -23 LUFS) and a music streaming catalog (Spotify and YouTube, -14 LUFS normalization target). The mixer delivers two separate masters: the broadcast version mixed to -23 LUFS with full dynamic range, and a streaming version mixed to -16 LUFS. At -16 LUFS, Spotify's normalization applies a small upward correction to -14 LUFS, preserving more dynamics than a mix delivered directly at -14 LUFS with limiting. Delivering both platforms from a single -23 LUFS master would send the streaming version 9 LU quieter than the normalization target, which the platform would boost upward -- amplifying noise floor and exposing compression artifacts.

LUFS Targets by Platform

The table below shows current delivery specifications. These figures are per published technical requirements from each platform and standard as of July 2026. Platform specs update periodically; confirm against each platform's current technical documentation before delivery.

Netflix targets -27 LUFS to preserve the dynamic range that cinematic dialogue and sound design require. Music streaming targets -14 LUFS because listeners expect louder, more compressed music. Delivering a film audio mix at music streaming loudness levels compresses the dynamic range that gives the mix its dramatic impact.

How to Write a Loudness Handoff Document: Step by Step

Step 1: Identify the delivery destination. Broadcast (which country, which standard), streaming video (which platform), streaming audio (which services), or theatrical. Each destination uses a different loudness spec. If the film delivers to multiple destinations, you need a separate loudness target for each version.

Step 2: Find the current spec for that destination. Use the platform's published technical documentation directly -- not a third-party summary. Netflix, Apple, and YouTube update their specs. The LUFS target you used two years ago for the same platform may not be current.

Step 3: Write the handoff specification as: Integrated LUFS target, True Peak limit, and the applicable standard. Example: "Target -23.0 LUFS Integrated, max -1.0 dBTP (EBU R128)." Do not specify RMS unless the delivery spec explicitly requires it. No major broadcast or streaming platform checks RMS on delivery.

Step 4: If the project delivers to multiple platforms, write separate sections in the handoff document for each version. Label them clearly: Broadcast Master, Netflix Master, Streaming Master. One mixer, one film, three different LUFS targets requires three clearly labelled export workflows.

Step 5: Run the [LUFS Loudness Calculator](/tools/lufs-loudness) to confirm your current Integrated LUFS and True Peak before sending the handoff. Including a confirmed reading in the handoff document ("current integrated LUFS on the pre-mix measures -20.3 LUFS; target is -23.0 LUFS; correction required: -2.7 LU") tells the mixer exactly where they are starting from and where they need to land.

At the end of this process, the mixer has one unambiguous number per version, specified in the same unit the QC process will use to evaluate it.

Pro Tips and Common Mistakes

Pro Tip: Integrated LUFS builds as the program plays. It is the running average from the session start to the current playhead position. Never read it at the 30-minute mark of a 90-minute film and treat that as your delivery reading. A full-program integrated LUFS measurement requires the meter to run continuously from the first frame to the last frame. Most loudness meters have a Reset function for exactly this workflow. Reset it, play the full program, read the integrated value at the end.

Pro Tip: For music mixes targeting streaming platforms, deliver between -14 LUFS and -16 LUFS integrated. At -14 LUFS, Spotify and YouTube apply no normalization -- your mix plays exactly as delivered. Delivering significantly quieter than -14 LUFS means the platform boosts your content, which can expose noise floor issues and amplify compression artifacts. The practical ceiling for streaming music is -14 LUFS; the practical floor where upward normalization starts causing problems is around -18 LUFS.

Pro Tip: True Peak and RMS peak are different measurements with different failure modes. True Peak uses inter-sample peak detection to catch clipping that occurs after digital-to-analog conversion. Sample-peak meters miss these inter-sample excursions. A mix that passes a standard peak meter at -0.5 dBFS can still fail true peak compliance at -1 dBTP. Always use a true peak meter when checking against a dBTP delivery limit.

Common Mistake: Reading short-term or momentary LUFS and treating it as the delivery level. Short-term LUFS (3-second window) reads the loudness of the current program section. Momentary LUFS (400ms window) reads the loudness of the current moment. Neither equals integrated LUFS, which is the only measurement delivery specs reference. A loud action scene short-term reading of -12 LUFS during mixing does not mean your program will deliver at -12 LUFS integrated.

Common Mistake: Applying the true peak limiter and not re-checking integrated LUFS afterward. A true peak limiter reduces transients that exceed the target, which lowers average energy across the program. If your integrated measurement was -23.1 LUFS before peak limiting and the limiter is working heavily on loud passages, the post-limiter integrated reading may shift to -23.6 LUFS. Still compliant -- but worth a verification pass rather than assuming the integrated level is unchanged.

Frequently Asked Questions

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

There is no reliable conversion factor. The difference between RMS and LUFS depends entirely on the spectral content of the material. Speech-heavy content may show 1 to 2 LU difference between RMS and integrated LUFS. Bass-heavy music or action effects may show 4 to 8 LU difference. The only accurate approach is to measure integrated LUFS directly using a BS.1770-4 compliant loudness meter. Estimating LUFS from an RMS reading introduces enough error to cause a delivery failure.

Why does Netflix specify -27 LUFS when broadcast uses -23 LUFS?

Netflix chose -27 LUFS to preserve the full dynamic range that a cinematic sound mix requires. At -23 LUFS, a feature film with wide dynamics -- quiet dialogue scenes at -40 LUFS short-term, action sequences near -10 LUFS -- has a louder average level that compresses the perceived dynamic range on home playback. The -27 LUFS target gives re-recording mixers room to maintain natural dynamics while still hitting a measurable, QC-verifiable delivery number.

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

For platforms that normalize (YouTube, Spotify, Apple Music), content louder than the target gets turned down. Delivering at -12 LUFS to a YouTube target of -14 LUFS means your content plays 2 LU quieter than a mix delivered at -14 LUFS. The platform applies gain reduction, not gain increase, for over-target content. If the mix was heavily limited to achieve -12 LUFS, the limiting artifacts that were masked at high playback levels become audible after normalization applies that 2 LU reduction.

Is LUFS the same as LKFS?

Yes. LKFS (Loudness, K-weighted, relative to Full Scale) is the original notation from ITU-R BS.1770. LUFS is the notation adopted in EBU R128 for the same algorithm. LKFS appears in US broadcast documentation (ATSC A/85 uses LKFS). EBU R128 and most streaming platform specs use LUFS. The numerical values are identical: -23 LUFS equals -23 LKFS. The only difference is the label, and which standards body's documentation you are reading.

Related Tools

The LUFS Loudness Calculator measures integrated, short-term, and momentary LUFS along with true peak for any audio file and returns a delivery-ready readout against any platform spec. For the full audio delivery workflow including channel configuration, sample rate, and codec requirements alongside LUFS, Audio Delivery Standards for Film and Television covers every major platform and broadcaster. For sample rate and bit depth decisions that affect the precision of loudness measurement in long-program sessions, Sample Rates in Film and Audio Post covers the foundational specifications.

For the authoritative technical sources: the EBU R128 loudness specification and ITU-R BS.1770-4 are the primary references for every number in this post.

One Standard for the Delivery Destination

RMS is useful for setting relative levels within a mix session. LUFS is the delivery currency. Every major broadcast network, streaming video platform, and music streaming service specifies delivery in integrated LUFS, not RMS. Giving a mixer an RMS target requires a spectral-content-dependent conversion that introduces inaccuracy. Giving them an integrated LUFS target with a true peak limit gives them one number to hit against the same meter the QC process will use. The handoff document always reads in the unit the destination platform checks.

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've encountered, and did you have to remix to pass it?