What Is LUFS? A Standards-Based Guide to Loudness

LUFS is a way to describe programme loudness over time. It is useful because a sample peak alone does not tell you how loud a piece of speech, music, or video will feel across several seconds or an entire programme.

This guide separates the measurement standard from platform behavior. The standard defines how loudness and true peak are measured; each service decides whether, where, and how to normalize playback.

What LUFS means

LUFS means Loudness Units relative to Full Scale. The closely related term LKFS is used in some standards and workflows. For practical programme-loudness reporting, the numerical values are treated equivalently.

The current in-force reference is ITU-R BS.1770-5. It specifies algorithms for measuring audio programme loudness and true-peak level. The calculation applies frequency weighting and channel weighting, then integrates energy according to the defined method.

That does not make LUFS a perfect model of every listener. Room noise, hearing, speakers, headphones, frequency balance, dynamics, and duration still affect the experience. LUFS is a standardized engineering measurement, not a personal hearing test.

Integrated, short-term, and momentary loudness

The EBU loudness framework describes three useful time views:

• Momentary loudness uses a 400 ms window.
• Short-term loudness uses a 3 second window.
• Integrated loudness measures from the start to the stop of the programme, with the specified gating behavior.

Use integrated loudness to describe a whole song, episode, or programme. Use short-term and momentary readings to see how dialogue, music, effects, or individual passages vary inside it.

A single integrated number can hide a wide internal range. Two programmes may share the same integrated LUFS value while one stays dense and consistent and the other moves between quiet dialogue and loud effects.

LU, dBFS, and true peak are different

LU is a relative loudness difference. A change of 1 LU is numerically equivalent to a 1 dB change in level under the loudness framework, but that does not justify a universal claim about the smallest audible change for every signal and listener.

dBFS sample peak reports the largest digital sample relative to full scale. It can miss peaks between samples that appear during reconstruction or encoding.

dBTP true peak estimates those reconstructed peaks. ITU-R BS.1770 specifies true-peak measurement alongside programme loudness because loudness and peak headroom answer different questions.

Normalization is a service policy, not part of LUFS itself

Platforms can measure loudness and then apply playback gain, but their behavior differs by product, device, account setting, and content type.

Spotify currently documents the clearest public example. Its official loudness-normalization guide says the Normal setting adjusts tracks toward -14 dB LUFS under ITU 1770. It also says positive gain is limited by available headroom, and notes that its web player and some third-party devices do not use loudness normalization. The same page currently lists -11 LUFS for Loud and -19 LUFS for Quiet.

YouTube’s public documentation focuses on listener controls instead of publishing a universal LUFS target. YouTube Help says Stable volume continuously adjusts levels to reduce differences between quiet and loud passages, is not available on every video, and is disabled for YouTube Music and official music videos. It also documents Voice boost for eligible videos.

Those primary sources are why this guide does not present a simple “every platform targets this number” table. Such tables often mix mastering advice, third-party measurements, older behavior, and current playback policy as if they were the same thing.

A practical measurement workflow

1. Measure the entire programme for integrated LUFS.
2. Inspect short-term and momentary readings around the passages that matter.
3. Measure true peak separately.
4. Record the meter, standard/version, gating mode, channel layout, and file version.
5. Check the current delivery specification for the exact service and product.
6. Recheck an encoded deliverable when codec or distribution headroom matters.

For listening troubleshooting, also separate source loudness from playback limitations. A quiet browser tab can result from the programme, player, site-sound setting, operating-system mixer, selected output, speaker capability, or listening environment.

Where Hearably fits

Hearably processes supported browser-tab audio after capture begins. Gain, EQ, and compression can change the listener-side result, and a look-ahead limiter controls new sample peaks at its digital ceiling. The limiter’s narrow synthetic result and raw data are published in our browser-audio limiter benchmark.

That benchmark is not a LUFS-normalization study. Hearably does not currently measure a live tab to a guaranteed integrated-LUFS target, reconstruct missing source detail, or guarantee a safe acoustic level. Very large boosts can reveal source noise and distortion or overload speakers and headphones even when digital sample peaks remain controlled.

The reliable takeaway

LUFS describes programme loudness using a standardized algorithm. Momentary, short-term, and integrated measurements answer different time-scale questions; true peak answers a separate headroom question. Playback normalization is then a platform policy layered on top.

Use the current primary specification for measurement, the current platform documentation for delivery behavior, and a versioned, reproducible method for any product claim.