Because they normalize loudness. Most major stores aim near −14 LUFS integrated (Apple Sound Check is often treated as closer to −16). A master at −8 LUFS is not played 6 dB louder than a −14 LUFS master. It is turned down until it matches.

The last decade of “make it competitive” advice assumed the listener’s volume knob was the only governor. That was true for CD. It is not true for a queue that has to survive a ballad, a podcast, and a club record without someone reaching for the phone. The store measures how loud the file feels over its duration, then applies a playback gain. That measurement is integrated LUFS, not the tallest sample on your clip lights.

If you spend the last 4 dB of the mix on a limiter, you have not bought volume on Spotify. You have bought less dynamic range at the same playback loudness, plus a worse chance of surviving the codec. The time you save is the time you stop arguing with a false loudness war and bounce at the lane the store already chose.

What “normalization” actually does

Integrated LUFS is a gated, K-weighted average. Short-term and momentary meters are useful while you work. The store mostly cares about the whole title. Two files at −14 LUFS can still feel different because crest, arrangement, and spectrum are not the same as loudness. That is the remaining art. The contract is the number.

Turn-up is real as well. A file at −20 LUFS may be gained up. That can make a noisy floor or a true-peak overshoot obvious. Quiet is not a free pass. Measure both directions.

Targets that show up in a delivery report

Sources: Spotify for Artists, “Loudness normalization” (tracks adjusted to −14 LUFS per ITU 1770); Apple Support, “Sound Check” (Apple describes the feature but does not publish a LUFS figure there, so ≈ −16 is the commonly reported value); AES TD1008, the AES recommendations for streaming loudness; ITU-R BS.1770, the loudness and true-peak measurement. The YouTube, Amazon Music and TIDAL rows are commonly reported figures; we did not find an official published target to link.

CoProducer’s analyze table treats −14 LUFS as the release target, with a 1.5 LU pass window. That is the same column you see next to “If repaired in CoProducer.” It is not a taste score. It is a distance.

A faster session

Do not print a new limiter preset until you have a number. Bounce. Measure integrated LUFS and true peak. If you are already inside the window, stop. If you are hot, take gain out of the chain before you add more compression. If you are quiet, ask whether the noise floor can survive a turn-up. That sequence is shorter than another hour of “one more dB.”

On the public A/B, Drippin starts at −11.92 LUFS and a +1.06 dBTP overshoot. After a conservative repair it sits at −14.12 LUFS. The arrangement did not change. The lane did.

Will a louder file beat the algorithm?

Not on loudness. Platforms already equalize integrated loudness. What remains is punch, tone, and whether the limiter ate the transients.

Is −14 mandatory?

No. It is the playback lane. Hotter files are turned down. Quieter files may be turned up, which can reveal noise and clip in the codec.