What Is Loudness Normalization?
Updated July 2026 · by Loopin
Loudness normalization is how streaming platforms play every track at roughly the same perceived volume. It’s the single biggest reason that mastering louder than the target gains you nothing.
The problem normalization solves
Before normalization, a quiet jazz record followed by a brick-walled pop single meant lunging for the volume knob every few minutes. To stop that, platforms measure each track’s loudness and turn it up or down on playback so everything lands at a consistent level — no manual riding required.
The measurement they use is LUFS (Loudness Units relative to Full Scale), which tracks perceived loudness over the whole song rather than instantaneous peaks. A track’s integrated LUFS is compared to the platform’s target, and the difference becomes a simple gain change applied at play time.
How each platform does it
Spotify, YouTube and Amazon normalise to around −14 LUFS; Apple Music targets nearer −16 LUFS; TikTok sits around −14 to −13. If your master is louder than the target, it gets turned down to match. If it’s quieter, most platforms turn it up (within limits), though some only attenuate and never boost.
Critically, this is one gain move applied to the whole track — it doesn’t re-compress or re-limit your audio. It just changes the playback level. The internal dynamics you mastered into the song are preserved; only the overall volume shifts to meet the target. See loudness targets by platform for the full list.
Why louder masters stop helping
Here’s the key consequence. If you crush your master to −8 LUFS chasing loudness, the platform turns it back down to its target anyway — so it ends up no louder than a track mastered at −14. You squashed the dynamics for nothing, and now your loud-but-flat master plays at the same volume as everyone else’s, only with less punch.
After normalization, the dynamic track often sounds bigger than the crushed one at matched loudness, because its transients still hit. That’s the loudness war turned on its head: restraint wins. More on the mechanics in why a master sounds quiet on Spotify.
Mastering for a normalised world
The practical recipe is simple: master to around −14 LUFS integrated with a −1 dBTP true-peak ceiling, and you sit at a competitive level everywhere without fighting the normalizer. You don’t need a separate file per platform — one well-targeted master translates across all of them.
Most listeners leave normalization on by default, so design for it. Chasing the meter past the target just trades dynamics for a loudness the platform will quietly undo. Aim for the target, keep your punch, and let normalization do the level-matching for you — the full picture is in how loud a master should be.
Hitting the target without a meter
You don’t need a metering plugin to land on the target. Loopin’s free online mastering measures your track’s integrated loudness and true peak, targets streaming levels automatically, and lets you A/B the result loudness-matched so you judge the tone honestly rather than falling for ‘louder sounds better’.
Run your mix through, listen on a couple of systems, and trust the LUFS target over the instinct to pin the meter. In a normalised world, a clean master at the right loudness beats a loud one every time — try it with the free mastering tool.
Frequently asked questions
What is loudness normalization?
It's the process streaming platforms use to play every track at a similar perceived loudness. Each track's integrated LUFS is measured and compared to the platform's target (around -14 LUFS for Spotify), then a single gain change is applied on playback to bring it to that level. It doesn't re-compress your audio.
Does loudness normalization ruin my master?
No. It only changes the overall playback level — it doesn't re-limit or re-compress your audio, so your internal dynamics are preserved. The only downside is for over-crushed masters: they get turned down to the target anyway, so the squashing gained nothing.
Can I turn loudness normalization off?
Listeners can usually disable it in their app settings, but most leave it on by default, so you should master as if it's always active. Target around -14 LUFS integrated with a -1 dBTP ceiling and your track sits at a competitive level whether normalization is on or off.