Why Streaming Turns Your Song Down
Published · updated · by Loopin
Streaming platforms turn loud songs down so listeners don't get blasted switching between a quiet acoustic track and a loud pop single. It's not a penalty — it's the whole point of normalisation.
The problem normalisation actually solves
Before loudness normalisation was standard, playlists mixing songs from different eras and mastering philosophies created jarring volume jumps — a quiet 1970s recording followed by a maximally-loud modern master. Normalisation targets a consistent perceived loudness across everything, regardless of how the source was mastered.
This is a listener-experience feature, and it works the same way whether your track happens to be louder or quieter than the target — it's not specifically targeting loud masters as a punishment.
Why chasing extra loudness stopped paying off
Before normalisation was widespread, mastering louder than everyone else genuinely made a track stand out more in a shuffled playlist — the so-called loudness war had a real, if crude, incentive behind it. Normalisation removed that incentive: an aggressively loud master just gets turned down to match everything else.
The practical result is that mastering to a reasonable target with real dynamics intact costs you nothing competitively anymore, while preserving more of the track's actual dynamic quality.
It's a relative adjustment, not a quality judgment
Normalisation doesn't evaluate whether your mastering is good or bad — it purely measures loudness and adjusts gain to hit a target. A poorly mastered but appropriately-loud track and a beautifully mastered but appropriately-loud track get treated identically by the normalisation system itself.
This means normalisation isn't something to blame for a track sounding unimpressive — that's down to the actual mastering quality, which normalisation neither helps nor hurts directly.
You can work with it instead of against it
Since fighting normalisation with extreme loudness accomplishes nothing, the practical move is mastering to somewhere near the platform's target — roughly −14 LUFS for most major services — so the normalisation system has the least amount of adjusting to do.
A master close to the target translates most predictably and consistently across different platforms and listening contexts, since it's not relying on normalisation to do heavy corrective work.
What actually still matters
With loudness effectively equalised by the platform, tonal balance, clarity and how a track's dynamics are shaped become the things that actually differentiate one master from another in a listener's ears. That's where mastering effort is genuinely well spent now, rather than in a loudness arms race that platforms have already neutralized.
This is arguably a healthier situation for music overall — the incentive has shifted from "as loud as possible" to "as good as possible," which normalisation didn't create but does reinforce.
Frequently asked questions
Why does Spotify turn down my loud song?
Loudness normalisation targets a consistent perceived volume across every track, roughly -14 LUFS, so listeners don't get jarring volume jumps switching between songs. It applies to every track, not specifically as a penalty for loud masters.
Does mastering louder still help my song stand out on streaming?
No, not anymore. Before normalisation was widespread, louder masters stood out in playlists. Normalisation removed that advantage -- an aggressively loud master just gets turned down to match everything else.
What should I focus on now that loudness doesn't give a competitive edge?
Tonal balance, clarity and how dynamics are shaped. With loudness effectively equalised by normalisation, those qualities are what actually differentiate one master from another to a listener.