LUFS, dBFS, and Loudness Normalization: What Filmmakers Need to Know

The Mix That Sounded Right and Got Rejected Anyway

Your re-recording mixer finishes the final pass on a 94-minute drama. You play it in the studio and the dynamics are exactly what you wanted: intimate dialogue scenes at roughly -35 LUFS short-term, the third-act confrontation peaking near -12 LUFS, score sitting confidently underneath. Everyone signs off. The mix gets exported and sent to the broadcaster. QC comes back two days later: the program loudness reads -19.8 LUFS integrated against a -23.0 LUFS requirement. The broadcaster will not air it without correction.

The mixer didn't make an error. You both just forgot to set up the integrated LUFS meter before the session started. Fixing it now means going back into the session, pulling down the master fader by 3.2 dB, checking that the true peak still clears -1 dBTP, and re-exporting the final file. That takes four hours. The two-day re-mix cost the production its delivery bonus.

Loudness compliance failures are almost entirely avoidable once you understand how LUFS, dBFS, and true peak work as separate measurements with separate functions. This post covers that distinction and gives you the step-by-step metering workflow to hit spec on the first export.

The standards in this post are drawn directly from EBU R128 (the European Broadcasting Union's loudness recommendation), ITU-R BS.1770-4 (the international algorithm that defines how loudness is calculated), and ATSC A/85 (the US broadcast standard). These are the documents your broadcast QC teams are measuring against.

How Loudness Measurement Works

Digital audio has three distinct ways of measuring level, and they describe completely different things.

dBFS (decibels Full Scale) measures the digital signal level relative to the maximum the system can represent. 0 dBFS is the absolute ceiling. Everything below it is negative: -6 dBFS, -18 dBFS, -40 dBFS. It measures peak amplitude of the waveform, not perceived loudness. A 1kHz sine wave at -18 dBFS and a broadband noise signal at -18 dBFS are at identical dBFS levels but the noise sounds perceptually louder because it excites more of the auditory range simultaneously.

True Peak (dBTP) is a variant of dBFS that accounts for inter-sample peaks: momentary amplitude values that occur between digital samples during playback reconstruction in the digital-to-analog converter. A standard peak meter misses these. A true peak meter interpolates between samples to find the actual peak the playback system will produce. This is why the delivery limit is -1 dBTP rather than 0 dBFS. That 1 dB of headroom absorbs the inter-sample excursions that standard peak metering doesn't detect.

LUFS (Loudness Units Full Scale) is a perceptual loudness measurement defined by ITU-R BS.1770. It applies K-weighting to the frequency spectrum: a filter that attenuates low frequencies and slightly boosts high-mids to approximate how human hearing perceives loudness. LUFS comes in three time windows: momentary (400ms), short-term (3 seconds), and integrated (the full program from start to finish). Delivery specifications always reference integrated LUFS. The integrated measurement is also called Program Loudness or I-LUFS in some DAW displays.

Why dBFS and LUFS Are Independent

A signal can be quiet on a dBFS meter but loud in LUFS if it contains dense mid-frequency content. A signal can peak high on dBFS but measure quietly in LUFS if it's a short transient with minimal average energy. This independence is exactly why loudness normalization exists. Streaming platforms normalize to a target integrated LUFS value so all content plays back at comparable perceived loudness, regardless of how aggressively the mix was limited.

A mix mastered to -9 LUFS integrated gets turned down by YouTube's normalization to -14 LUFS and will still sound compressed and lifeless, because the limiting that achieved -9 LUFS removed the dynamic range permanently. A mix mastered to -14 LUFS with real dynamics sounds better at the same normalized level. Louder delivery numbers do not produce louder playback on any major platform.

Platform Loudness Normalization Reference

The table below shows current integrated LUFS targets across major delivery destinations as of July 2026, per each platform's published technical specifications.

Content louder than the platform target gets normalized downward. Content quieter is typically left as-is. That asymmetry means there is no benefit to mixing louder than the delivery target. You'll only be turned down, and the dynamic range you compressed away to hit a loud number is gone permanently.

Three Real-World Loudness Scenarios

Example 1: Short Film, Festival and Streaming Delivery

A 28-minute drama short with wide dynamic range. Intimate dialogue scenes average -35 LUFS short-term; the climactic sequence averages -18 LUFS short-term. The mixer exports the full program and measures it: -22.4 LUFS integrated, -1.2 dBTP true peak.

Target: Sundance and SXSW technical specs require -24 LUFS integrated, -1 dBTP. The mix is 1.6 LU too loud.

Correction: The mixer applied a -1.6 LU gain adjustment in iZotope RX Loudness Control with the true peak limiter set to -1 dBTP. No dynamic range was affected - a uniform gain change moves the integrated measurement without touching the dynamic relationships between scenes. The re-export measured -24.0 LUFS, -1.8 dBTP. Compliant with no audible change to the mix character.

Decision: The same corrected master covered both festival submission and VOD delivery. The short-term variation from -35 LUFS in quiet scenes to -18 LUFS at the climax remained fully intact.

Example 2: Corporate Video, YouTube Delivery

A 4-minute brand film with a heavily limited score. The mixer targets -10 LUFS integrated for maximum apparent loudness, applying aggressive limiting across the mix bus.

Result: YouTube normalizes the video down to -14 LUFS. The 4 LU reduction exposes the pumping artifacts from the limiting that were inaudible at the original level. The client hears a worse-sounding mix than the unlimiter version would have produced at the same normalized target.

Fix: The mixer rebuilt the session targeting -14 LUFS integrated from the start without the bus limiter. The result was a louder-sounding video on YouTube at the same normalized level, because dynamics were preserved rather than compressed away. The LUFS Loudness Calculator calculates what gain correction a post-mix fix would require before committing to a full remix.

Example 3: Feature Film, Netflix Delivery

A 98-minute narrative feature delivering to Netflix. The spec: -27 LUFS integrated, -2 dBTP true peak, tolerance ±2 LU.

Challenge: The re-recording mixer has spent years mixing broadcast at -23 LUFS. At -27 LUFS, the mix sounds too quiet on studio monitors during the final sign-off session.

Solution: The mixer recalibrated the monitoring level per Netflix's specification, raising monitor gain by approximately 4 dB to compensate for the lower output. At the correct monitoring calibration, -27 LUFS sounds equivalent to -23 LUFS on broadcast-calibrated monitors. The perceived loudness in the room stayed the same. The mix retained 4 additional dB of headroom, which the delivery system uses to maintain theatrical dynamic range on home playback.

Outcome: Final deliverable measured -26.8 LUFS integrated, -2.2 dBTP. Within tolerance on both counts. Netflix QC accepted without correction.

How to Meter and Hit Compliance: Step by Step

Step 1: Set up integrated LUFS metering before any mixing work begins. In DaVinci Resolve Fairlight, enable the Loudness Meter in the master bus panel and set the target to your delivery spec. In Pro Tools, use Waves WLM Plus or Avid Pro Limiter on the master bus. In Logic Pro X, enable the Loudness Meter in the master channel. In Adobe Audition, use the Amplitude Statistics panel. Not after the mix - before.

Step 2: Calibrate your monitoring level for the delivery target. For every 1 LU of loudness target reduction from -23 LUFS, raise monitor gain by 1 dB. Mixing for Netflix at -27 LUFS means your monitors should be 4 dB louder than a broadcast session. Mixing at the wrong monitor level produces the reflex to push faders higher than the spec allows.

Step 3: Keep the integrated LUFS meter visible throughout the session. The short-term LUFS display (3-second window) is your real-time reference. The integrated value accumulates from the session start. If it's trending 3 or more LU off-target at the 30-minute mark of a 90-minute film, adjust gain staging mid-session rather than applying a correction to the final export.

Step 4: Apply a true peak limiter as the last processor in the master bus chain. Set it to the platform's true peak limit: -1 dBTP for broadcast and most streaming, -2 dBTP for Netflix and theatrical. The limiter should catch occasional transients, not continuously reduce gain. If it's working harder than 2 to 3 dB of reduction on a regular basis, the mix level is too high for the target.

Step 5: Export and re-measure the bounced file before submission. Some DAW plugins accumulate minor discrepancies over a long program. Export the final file and measure it using a standalone loudness tool: iZotope RX, Nugen Audio VisLM, or the free Orban Loudness Meter. Confirm integrated LUFS, true peak, and loudness range (LRA) against the spec.

Step 6: If the integrated measurement is off by more than 1 LU, apply a uniform gain correction. Import the final bounce into a new session, apply a single gain plugin set to the correction value (for example, -1.8 dB to bring -22.2 LUFS to -24.0 LUFS), re-apply the true peak limiter, and export again. A gain-only correction moves loudness without altering the dynamic relationships within the mix.

Pro Tips and Common Mistakes

Pro Tip: Loudness Range (LRA), measured in LU, describes the variation between the quietest and loudest program sections. Broadcasters don't mandate a specific LRA value, but programs with LRA above 20 LU will sound inconsistent on consumer playback systems with dynamic normalization enabled. A dialogue-heavy documentary typically lands between 12 and 18 LU. A feature film with action sequences may hit 18 to 22 LU. If your LRA exceeds 25 LU, check whether the quiet sections are genuinely too quiet or whether a few unusually loud moments are skewing the measurement upward.

Pro Tip: When a film delivers to both broadcast (-23 LUFS) and streaming (-27 LUFS), mix to -23 LUFS with a true peak of -1 dBTP. The broadcast version is the reference master. The streaming version comes from a -4 LU gain reduction with the true peak limiter re-applied. That's a 10-minute operation with no remixing required. Don't try to split the difference with a single master at -25 LUFS. Neither version will comply.

Pro Tip: For documentaries that include archival audio - telephone recordings, news clips, archival footage - integrate those sections into the overall LUFS measurement. Archive audio often has radically different dynamic characteristics. Don't treat archive sections as isolated islands. Measure the complete program from first frame to last, including every archive segment.

Common Mistake: Using a peak meter to judge compliance and assuming -6 dBFS peak means -24 LUFS integrated. There is no fixed relationship between peak level and LUFS. A heavily compressed program can peak at -6 dBFS and measure -10 LUFS integrated. A dynamically mixed orchestral program can peak at -3 dBFS and measure -28 LUFS integrated. Peak meters catch clipping. They tell you nothing about loudness compliance.

Common Mistake: Applying heavy bus compression to raise integrated LUFS quickly rather than adjusting gain staging. Bus compression increases integrated LUFS by reducing dynamic range: the quieter sections get brought up closer to the louder ones. This achieves numerical compliance but destroys the dynamic character of the mix. A gain adjustment achieves the same LUFS change with zero impact on dynamics. Use compression as a mix tool, not a compliance shortcut.

Frequently Asked Questions

What is the difference between LUFS and LKFS?

They're the same measurement. LKFS (Loudness, K-weighted, relative to Full Scale) is the original term from ITU-R BS.1770 when the standard was first published. EBU R128 adopted LUFS as a more intuitive label for the identical algorithm. LKFS still 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.

Why does my mix sound louder than the LUFS number suggests?

Perceived loudness depends on frequency content as well as level. Mixes with dense upper-midrange energy (2 to 5kHz) sound louder than their LUFS number relative to bass-heavy or high-frequency material. The BS.1770 K-weighting filter approximates human hearing but doesn't perfectly model individual perception. Loudness range also plays a role. A highly compressed mix at -18 LUFS can sound louder than a wide-dynamic mix at -16 LUFS because the compressed version has no quiet moments to contrast against.

How do I measure LUFS in DaVinci Resolve?

In the Fairlight page, open the Meters panel and select the Loudness Meter from the panel options. Set the target to your delivery spec. The meter shows momentary, short-term, and integrated loudness simultaneously. To measure an existing file, import it into a Fairlight timeline, add the Loudness Meter to the master bus output, and play the file from start to finish. The integrated value at the end of playback is your program loudness.

Does loudness normalization affect true peak levels?

Yes. When a platform normalizes your program down from -14 LUFS to -27 LUFS, it applies a -13 LU gain reduction to the entire signal. If your original true peak was -1 dBTP, after normalization it drops to approximately -14 dBTP - well under any limit. The risk runs the other direction: if a platform applies upward normalization (rare - most platforms don't boost quiet content), the true peak rises. Netflix and most video streaming services normalize downward only, which is why the true peak concern at delivery is about your original file, not the normalized version.

What loudness target should I use if I don't know where the film will be distributed?

Use -24 LUFS integrated and -1 dBTP true peak as your default master. This matches the ATSC A/85 broadcast standard and sits within the tolerance of every major streaming platform. From that master, you can create a Netflix-specific version (-27 LUFS, a 3 LU reduction) or a YouTube-specific version (-14 LUFS, a 10 LU increase worth re-checking for peak compliance) without a full remix.

Related Tools

The LUFS Loudness Calculator takes your measured integrated loudness and delivery target and returns the exact gain correction needed for compliance. For the full audio delivery picture including channel configuration, sample rate, and bit depth, audio delivery standards for film and television covers every major platform and broadcaster in one reference. If your mix includes a scored picture, music and picture lock: how to sync score to your edit covers the composer-to-mixer handoff and how the score's loudness feeds into your final program measurement. The Audio Bitrate Storage Calculator helps plan file sizes for the multiple audio deliverables most platforms require.

For the authoritative technical standards behind this post: the EBU R128 specification and ITU-R BS.1770-4 are the primary sources. ATSC A/85 is available through the Advanced Television Systems Committee's technical documentation library.

Conclusion

LUFS is the measurement that determines whether a platform plays your mix at the level you intended. dBFS tells you whether you're clipping. True peak tells you whether the playback system will distort during reconstruction. All three measurements are necessary, but only integrated LUFS is what QC checks against a delivery spec.

This guide covers stereo and 5.1 integrated loudness targeting. Dolby Atmos and immersive audio delivery involve additional dialog normalization metadata (dialnorm) that operates outside the scope of a single integrated LUFS target and requires the platform's Atmos-specific delivery specification.

What's the widest loudness range you've managed on a mix that still held together on consumer speakers - and did you end up applying dialogue normalization or leave the dynamics intact?