Spotify Loudness Normalization: What −14 LUFS Really Does

Spotify normalizes playback to −14 LUFS. A louder master is turned down by clean gain, which adds no distortion. A quieter master is turned up only as far as its true-peak headroom allows, so a quiet, peaky master can land short of −14. None of it changes your file. Preview the result on BeamTracer's Loudness tab.

Hi, I'm Trina with BeamTracer.com, and this post walks through what Spotify's normalization actually does to your master — with the arithmetic.

"Master to −14 LUFS or Spotify will destroy your track." You've read that sentence, or one of its cousins, a hundred times. It's folklore built around a real number: Spotify does normalize playback to −14 LUFS, and says so on its own artist pages — one of the very few platforms that publishes its behaviour at all.

But what Spotify actually does at −14 is gentler, stranger, and more interesting than the folklore — and once you understand it, most of the loudness anxiety in your mastering session evaporates.

CLICK TO ENLARGE

What does Spotify's −14 LUFS normalization actually do?

• Louder than −14 LUFS? Spotify turns the whole track down by the difference. Clean gain. Nothing else changes.
• Quieter than −14? Spotify turns it up — but only as far as your true-peak headroom allows, and a limiter stands by for what doesn't fit.
• It's on by default in the app, normalizes albums as albums, and the listener can switch it off — or to Loud (−11) or Quiet (−19).
• None of it touches your file. It's playback gain, applied at the listener's end.

Now the parts folklore gets wrong.

Does Spotify turning your track down cause clipping or distortion?

No. Attenuation is a clean, lossless gain change — the same thing that happens when the listener nudges the volume knob — and Spotify's own documentation says lowering the volume relative to the master introduces no additional distortion.

The most persistent myth in this subject says that when Spotify turns your loud master down, something bad happens to it — clipping, distortion, "penalty". It's repeated by blogs that should know better, and it's backwards.

Your −8 LUFS master plays back 6 dB quieter and otherwise completely intact. The "penalty" isn't damage — it's that you gave up dynamic range to be loud, and then the loudness got taken away. The distortion risk lives entirely on the other side of the target.

Does Spotify turn a quiet track all the way up to −14 LUFS?

Not always. Spotify raises a quiet master, but it refuses to push your true peaks into distortion, so the boost is capped by your own headroom below the −1 dBTP ceiling. A quiet master that also peaks low lands short of −14 and stays there.

This is the genuinely underreported part, and it's worth doing the arithmetic once:

• Your master: −20 LUFS integrated, peaking at −5 dBTP
• The boost it "should" get: +6 dB, to reach −14
• The headroom available before the −1 dBTP ceiling: from −5 up to −1 is +4 dB
• Where it actually lands: ≈ −16 LUFS. Not −14. Two dB short, forever.

Most loudness calculators — including the popular target-slider pages — will tell you that quiet track plays at −14. It doesn't, and no amount of wishing moves it. If you master very quiet and very peaky, you've chosen your playback level whether you meant to or not.

One more wrinkle on the loud side: the listener's Loud setting (−11) can demand more level than a dynamic master has, and there Spotify does engage a limiter. If your master is dynamic and someone plays it on Loud, it gets squeezed in ways you never approved. You can't control listener settings — but it's one more reason the "louder master wins" theory doesn't survive contact with how playback actually works.

Should you master to −14 LUFS for Spotify?

No — and this is the position the best-sourced people in the field have converged on. −14 is a playback reference, not a mastering target. Analyses of hundreds of thousands of released tracks find that most commercial masters exceed it, sometimes by a lot, and they all get turned down, and nobody dies.

Master the music at the loudness it wants to be. The one number that is a rule is true peak: ≤ −1 dBTP, or −2 dBTP if your master is well above −14 — because lossy encoding pushes peaks up, and a limiter you didn't choose is waiting on the other side of 0.

If the terms in that paragraph are fuzzy, the plain-language LUFS guide covers them all in ten minutes.

What do the other streaming platforms normalize to?

Spotify publishes its behaviour. Most platforms don't, which is worth knowing when you read a confident LUFS chart — as of this writing:

Two honest footnotes to that table. YouTube's normalization is server-side and always on — you can see it yourself under right-click → Stats for nerds. And the social platforms publish nothing at all: the "−10 to −13 LUFS for TikTok" numbers that circulate have no traceable source. Mastering louder for a platform that never told anyone its rules is optimizing for a rumor.

How do you check what Spotify will do to your track?

Select Spotify in the TARGET card of BeamTracer's Loudness tab and drop your master onto it. The normalization preview does Spotify's arithmetic on your measured numbers — turn down, turn up, or capped by true peak — and AUDITION plays the predicted level so you can hear it before you upload.

The METER view judging live against the −14 target — one bar per LU, green below the line, red above it, with the exact short-term and integrated values in the middle.

Next

• LUFS in plain language — every number on the meter, without a manual
• How dynamic is your master? PSR, PLR and LRA — what survives after everyone plays at the same loudness
• Level a multi-person livestream in the browser — the same meter pointed at live voices
• Make a music visualizer from the same MP3 — what the rest of the app does with your track

That's the whole trick — beamtracer.com. See you in the next one.