Louder masters used to win. On CD, on MP3 downloads, on SoundCloud — the louder file felt punchier in an A/B. So producers pushed limiters until the master hit −6, −5, even −3 LUFS integrated. It worked, until streaming platforms decided to fix it.
What normalization actually does
Spotify, Apple Music, YouTube, and Tidal all apply loudness normalization — they measure every track at upload and store a gain offset. At playback, they apply that offset so all tracks hit roughly the same perceived volume. If your master is louder than the target, they turn it down. If it's quieter, some platforms turn it up.
The problem with over-limiting
Suppose you master your track at −7 LUFS. Spotify normalizes to −14, so it pulls your track down by 7 dB. You don't just lose volume — you lose the transient punch that was holding your mix together. The kick, the snare attack, the vocal clarity — all attenuated equally.
Meanwhile, a producer who mastered at −14 LUFS preserves full dynamics. On Spotify, their track hits the same perceived volume as yours — but their transients are intact. Their mix sounds more alive.
The loudness war is over. The platform won.
What PRISM measures
PRISM calculates integrated LUFS using EBU R128 K-weighting with gating (blocks below −70 dBFS and blocks more than 10 LU below the relative gate are excluded). This is the same spec Spotify uses. If your integrated LUFS sits above the genre target, PRISM flags it as a priority fix.
For genre context: hip-hop and pop typically target −13 to −14 LUFS. Techno and DnB masters run hotter, around −9 to −10 LUFS, because those genres historically push dynamics hard — and their audience often listens loud enough that the normalization hit is acceptable.
How to fix it in your DAW
- Ableton: Use the Glue Compressor on the Master with a 2–4 dB ceiling, then add a Limiter set to −0.3 dBTP true peak. A/B your LUFS reading with a LUFS meter on the master chain (Youlean Loudness Meter is free and accurate).
- FL Studio: Peak Controller → Fruity Peak Controller routed to the master mixer, then Maximus for limiting. Set the ceiling to −1 dBTP. Aim for −14 LUFS on the integrated meter.
- Logic Pro: Add the Loudness Meter in Metering mode → set to EBU R128 → use the Adaptive Limiter at the end of the master chain. Logic's built-in Loudness meter tracks integrated LUFS in real time.
The target: −14 LUFS integrated, −1.0 dBTP true peak maximum. This gives you headroom for Spotify's encoding process without audible squashing.
A dedicated loudness meter and a quality limiter make this straightforward. These are the tools PRISM users most often pair with the loudness issue fix.
After the fix
Re-scan your track in PRISM. If the loudness issue disappears, your LUFS is inside the streaming target for your genre. If the score improves but the issue persists, your master is still slightly above the threshold — ease the limiter input by 1–2 dB and re-scan.