Audio

Loudness, LUFS and streaming audio normalization

A peak meter swears your track sits at −0.1 dBFS, and yet it still sounds quieter than the next one in the same player. The reason is simple and rarely stated: peak measures the single loudest sample in the file, and the ear does not hear samples, it hears energy spread across time and the spectrum. LUFS was built to measure exactly that. This guide opens the ITU-R BS.1770 algorithm (K-weighting, gating, per-channel summation), separates true peak from sample peak, compares the broadcast and streaming targets, and explains why platform normalization took the point out of squeezing a master. Measure the loudness and true peak of your own files in the [volume normalizer](tool:normalizar-volume-audio) as you read.

J-Kit15 min readIntermediate
  • Audio
  • Loudness
  • LUFS
  • Mastering
  • Streaming

Key takeaways

  • Peak (dBFS) measures the loudest sample; loudness (LUFS) measures the perceived energy of the whole programme, with K-weighting and gating. They are different quantities.
  • Broadcast uses fixed targets, −23 LUFS in EBU R128, −24 LKFS in ATSC A/85; streaming normalizes playback to a target (on Spotify, −14 LUFS in Normal mode).
  • The loudness war ended because of normalization: a hyper-compressed track is turned down to the same LUFS as a dynamic one. Squeezing buys no loudness, it only costs transients.
  • Master with true peak at −1 dBTP: inter-sample peaks can exceed 0 dBFS and clip in the converter or the lossy codec.

Why peak says nothing about how loud something sounds

dBFS (decibels relative to full scale) is an amplitude measure: 0 dBFS is the loudest sample the format can represent, and everything else is negative. It is a logarithmic scale, like almost any decibel relation, the same ratio-between-quantities idea covered in the unit conversion guide. The trouble is that peak only looks at one instant: the single loudest sample in the file. It has no idea whether that peak lasted a click or the whole record, nor whether the energy is concentrated in a high whistle or spread across the entire spectrum. The ear cares about exactly those two things.

A worked example lays the difference bare. A 997 Hz sine tone hitting 0 dBFS, fed to a single channel (left, centre or right), measures exactly −3.01 LKFS, that is how BS.1770 calibrates itself. Put the same tone in both channels of a stereo pair and the weighted sum doubles: the meter now reads 0.0 LUFS, with the peak untouched. Now take a dense pop master that also peaks at 0 dBFS: it integrates far louder, because it fills the whole spectrum and sustains that energy for minutes. Same peak, completely different loudness. Normalizing by the loudest sample equalizes the number nobody hears and leaves unequal the thing everybody hears.

Normalize by peak

  • Raises the gain until the highest peak touches a ceiling (e.g. −1 dBFS).
  • Equalizes the maximum amplitude, not the perceived volume.
  • Ignores frequency and duration, a thin tone and a dense mix at the same peak read "equal" on the meter.
  • Good for not clipping. Useless for evening out loudness.

Normalize by loudness

  • Adjusts the gain to hit an integrated LUFS target (e.g. −14).
  • Equalizes the perceived volume of the whole programme, with K-weighting and gating.
  • It is what platforms do at playback, turning up quiet tracks and turning down loud ones.
  • Must respect the true-peak ceiling so the gain change does not clip.

What LUFS actually measures

The recipe lives in ITU-R BS.1770, the recommendation that defines how to measure loudness and true peak, now at revision BS.1770-5, November 2023, but stable in essence since the first version in 2006. The first step is K-weighting, a two-stage filter that approximates how we hear: a shelving pre-filter that lifts the highs by about +4 dB, modelling the effect of the head, followed by an RLB high-pass filter that cuts the very low frequencies. It is not the perfect audibility curve, but it is simple, reproducible and good enough to govern all professional audio. If you want to feel how differently bass and treble weigh on perception, play with the bass and treble equalizer.

After the filter, the algorithm squares the signal and averages it (the mean square) over 400 ms windows with 75% overlap. Each channel is measured separately and summed with a weight: this per-channel weighted sum is the heart of the measure.

L_K = −0.691 + 10 · log₁₀( Σ Gᵢ · zᵢ ) [LKFS]
L_K
K-weighted loudness, in LKFS (identical to LUFS).
zᵢ
mean square of the K-weighted signal of channel i over the measured window.
Gᵢ
channel weight: 1.0 for left, right and center; 1.41 for the surround channels; the LFE channel is not counted.
−0.691
calibration offset: it cancels the K-weighting gain at 997 Hz, making a 997 Hz tone at 0 dBFS on a single channel read exactly −3.01 LKFS.
BS.1770 K-weighted loudness: a linear sum of the per-channel mean squares, then converted to decibels.

The −0.691 constant is not magic: it cancels the K-filter gain at 997 Hz, anchoring the scale. The larger weights for the surround channels (1.41, about +1.5 dB) reflect that sound arriving from behind is perceived as slightly louder. Before going on, it helps to pin down the vocabulary, below, each acronym with its exact meaning.

dBFS
Decibels relative to digital full scale. 0 dBFS is the loudest representable sample; everything below is negative. Measures sample amplitude, not loudness.
dBTP
Decibels true peak: the peak of the reconstructed signal between samples, estimated by oversampling. It can exceed 0 dBFS even with no sample at 0.
LUFS
Loudness Units relative to Full Scale: the absolute BS.1770 loudness scale (K-weighting + gating).
LKFS
Loudness, K-weighted, relative to Full Scale: the name ATSC and ITU give to the SAME scale as LUFS. 1 LKFS = 1 LUFS.
LU
Loudness Unit: the same magnitude as 1 dB, but used relatively, the distance between two loudness values or to a target.
LRA
Loudness Range: the loudness variation of the programme (95th percentile minus 10th of the short-term blocks), in LU. High = dynamic; low = compressed.
gating
Discarding silent stretches before computing integrated loudness: an absolute gate at −70 LUFS and a relative gate 10 LU below the already-gated level.
Momentary / Short-term / Integrated
The three EBU Mode windows: momentary (400 ms), short-term (3 s) and integrated (the whole programme, gated).

The three windows, gating and LRA

A serious loudness meter shows three numbers, defined by EBU Tech 3341 as "EBU Mode". Each answers a different question about the same track.

  • Momentary (M): a 400 ms window. Catches instantaneous loudness spikes, useful for spotting a one-off overshoot.
  • Short-term (S): a 3 s window. Follows the mix as you work, tracking how the music evolves.
  • Integrated (I): the whole programme, gated. This is the number you compare to a target like −14 or −23 LUFS.

Gating exists because a silence or a long pause would drag the average down and make a track look quieter than it sounds. BS.1770 applies two gates before computing integrated loudness: an absolute gate at −70 LUFS, which throws away what is essentially silence, and a relative gate placed 10 LU below the level already measured with the absolute gate. Only the blocks above that second gate enter the final average. Without gating, a podcast with long stretches of quiet speech and a shouted commercial could register the same integrated value, which would defeat the whole measure.

LRA (Loudness Range), defined in EBU Tech 3342, sums up how dynamic the track is: it takes the short-term blocks and measures the distance between the 10th and 95th percentiles, ignoring the extremes. It is a distribution measure, not an average, the same statistical logic of looking at the spread of the data that appears in the correlation and regression guide. A high LRA means strong contrasts between quiet and intense passages; a low LRA betrays heavy compression, where everything was flattened to the same volume.

True peak: the peak the sample meter never sees

Sample peak is the loudest sample in the file. True peak (dBTP) is the highest value the signal reaches once reconstructed as a continuous waveform, and the two almost never coincide. Between two samples that sit just under 0 dBFS, the curve the converter draws can rise higher than any existing sample. That is the inter-sample peak, and it is treacherous precisely because it is invisible to an ordinary peak meter. Seeing the waveform helps you understand where it approaches the ceiling: you can generate and inspect that in the waveform generator.

Why a signal exceeds 0 dBFS with no sample at 0

Digital audio stores discrete points; the converter joins them with a smooth (sinc) interpolation to reconstruct the analog wave. When two consecutive samples are high and on opposite sides of a steep curve, common in high-frequency content, the reconstructed wave between them overshoots the samples themselves. That overshoot can reach roughly +3 dB above the highest sample peak.

Why to master at −1 dBTP (or lower)

Leaving 1 dB of headroom guarantees the reconstruction does not overflow the converter. And there is a second reason: lossy codecs (AAC, MP3, Ogg) reshape the waveform and can push peaks up during transcoding, the same kind of destructive re-encoding the image formats guide describes in the visual world. Spotify recommends true peak below −1 dBTP, and below −2 dBTP for very loud masters.

Oversampling: how the meter sees the real peak

To estimate true peak, BS.1770 oversamples the signal by at least 4×: between each pair of real samples it computes three interpolated points and measures the highest. That is why the dBTP value is usually higher than the sample peak: it already sees the wave the converter will actually produce.

The broadcast standards: one ruler, two rules

BS.1770 is only the ruler, how to measure. The rules of how much are built on top of it. In Europe, EBU R 128 fixed the target at −23 integrated LUFS for programmes, with a ±0.5 LU tolerance (±1 LU for less predictable live material) and a maximum true peak of −1 dBTP. In the United States, ATSC A/85, which the CALM Act made mandatory for commercials, uses −24 LKFS, with a ±2 LU margin. Worth burning in: LKFS and LUFS are the same scale under different names; the 1 LU gap between the two targets is real, but small.

Broadcast targets, tolerance and true-peak ceiling.
StandardIntegrated targetToleranceMax true peak
EBU R 128 (Europe)−23 LUFS±0.5 LU (±1 live)−1 dBTP
ATSC A/85 (US)−24 LKFS±2 LU−2 dBTP (recommended)
  1. 2006ITU-R BS.1770

    The ITU publishes the algorithm defining K-weighting and true peak, the common ruler for the whole industry.

  2. 2010EBU R 128

    The European Broadcasting Union sets the −23 LUFS target and the EBU Mode (Momentary, Short-term, Integrated, LRA).

  3. Dec. 2010CALM Act signed

    In the US, the law (Public Law 111-311) directs the FCC to require loudness control of commercials.

  4. Dec. 2012FCC rules in force

    The CALM Act rules take effect, adopting ATSC A/85 (−24 LKFS) as the mandatory reference.

  5. 2010sStreaming adopts normalization

    One by one, music and video platforms begin normalizing playback by loudness, each with its own target.

  6. 2023BS.1770-5

    The latest revision of the algorithm keeps the core intact and refines measurement details.

Streaming and the end of the loudness war

Streaming borrowed the idea from broadcast, but with a higher target. Spotify normalizes playback to −14 LUFS in Normal mode, with −11 LUFS (Loud) and −19 LUFS (Quiet) options for subscribers. Important: it does not alter your file, it applies a gain only at play time, down on loud tracks and up on quiet ones. And it respects true peak: per the official documentation, a track at −20 LUFS whose true peak sits at −5 dBFS is only raised to −16 LUFS, not −14, because +6 dB would push the peak to +1 dBFS and clip. The platform leaves 1 dB of headroom and stops short.

ATSC A/85 (US broadcast)24 LU
EBU R 128 (EU broadcast)23 LU
Spotify "Quiet"19 LU
Spotify "Normal"14 LU
Spotify "Loud"11 LU
All targets are negative in LUFS; the chart plots the magnitude (how many LU below 0 LUFS). A taller bar = a lower/quieter target. Only officially published values are shown.
View the data
CategoryValue
ATSC A/85 (US broadcast)24 LU
EBU R 128 (EU broadcast)23 LU
Spotify "Quiet"19 LU
Spotify "Normal"14 LU
Spotify "Loud"11 LU

Here is how the loudness war ends. For decades, masters were compressed and limited ever louder to "win" on radio and CD: whoever played louder grabbed more attention. Loudness normalization retired that logic. Suppose you master at −6 LUFS, brickwalled; when it plays on Spotify in Normal mode, the track takes −8 dB of gain to drop to the very same −14 LUFS as a dynamic master sitting at −14. The two arrive equally loud, but yours lost its transients and its breathing room on the way. Squeezing no longer buys loudness; it only costs quality.

When every track is leveled to the same LUFS, squeezing the dynamics buys no loudness at all, it only costs the transients.

Communities like the Dynamic Range Database and campaigns like "Turn Me Up!" had been documenting this loss of dynamics long before the platforms acted. Today the economic incentive has flipped: a master that keeps its dynamics sounds equally loud as the rest and better in quality. The practice comes down to mixing with your ears, checking the integrated value and true peak at the end, and not mastering to a number louder than the destination target. Close the production loop with other audio tools, like the BPM detector.

  • Measure the track’s integrated loudness (LUFS), not just the peak, use the volume normalizer or a meter with EBU Mode.
  • Cap the true peak at −1 dBTP (−2 dBTP if the master is loud), with a true-peak limiter, not just a sample-peak one.
  • Do not master above the destination target hoping for "loudness": platforms turn the track back down to their target.
  • Preserve dynamics (watch the LRA): heavy compression gives no advantage after normalization.
  • Check the whole album together, many platforms normalize per album to keep the relationships between tracks.
  • Keep a more dynamic master as the source; it is easier to turn down later than to recover lost transients.

Frequently asked questions

What is the difference between LUFS and dBFS?
dBFS measures amplitude, how loud a sample is relative to digital full scale (0 dBFS is the max). LUFS measures the perceived loudness of the whole programme, applying K-weighting (which mimics the ear) and gating (which discards silences). Two tracks with the same dBFS peak can have very different LUFS.
Are LUFS and LKFS the same thing?
Yes. They are different names for the same BS.1770 scale: 1 LKFS = 1 LUFS. "LKFS" (Loudness, K-weighted, Full Scale) is the term preferred by the ITU and ATSC; "LUFS" is the EBU term and the more common one in the music world. Both are absolute, referred to full scale.
What LUFS should I master to for Spotify?
Spotify normalizes playback to −14 integrated LUFS (Normal mode) and recommends delivering around that value with true peak below −1 dBTP. Since the platform adjusts gain at play time, mastering much louder brings no loudness, it only loses dynamics. Prioritize preserving transients and respecting the true-peak ceiling.
What is true peak and why does it matter?
True peak (dBTP) is the peak of the signal reconstructed between samples, measured by oversampling (at least 4× in BS.1770). It can exceed 0 dBFS even when no sample reaches it, because the continuous wave rises higher than the discrete points. If true peak crosses the ceiling, the converter or the lossy codec clips and distorts, which is why you master at −1 dBTP.
Did the loudness war really end?
The incentive ended. Because platforms normalize playback by loudness, a hyper-compressed track is turned down to the same LUFS as a dynamic one, both sound equally loud, but the compressed one lost its transients. There is no longer any loudness gain in squeezing a master; only the cost in quality remains. Nothing stops someone from over-compressing, but the advantage that drove the race is gone.

Peak protects the signal from clipping; LUFS describes how loud it sounds. Measure integrated loudness with K-weighting and gating, cap the true peak at −1 dBTP and deliver near the destination target, without squeezing. Because broadcast (−23/−24) and streaming (−14 on Spotify) normalize everything to one level, preserved dynamics sound equally loud and better in quality.

Sources & references

  1. ITU-R BS.1770-5, Algorithms to measure audio programme loudness and true-peak audio level (2023)
  2. EBU R 128, Loudness normalisation and permitted maximum level of audio signals
  3. EBU Tech 3341, Loudness Metering (EBU Mode)
  4. EBU Tech 3342, Loudness Range (LRA)
  5. ATSC A/85, Techniques for Establishing and Maintaining Audio Loudness for Digital Television
  6. FCC, Sound Volume Requirements for Commercials (CALM Act)
  7. Spotify for Artists, Loudness normalization