Why Is My Mix Quieter Than Reference Tracks on Spotify?
18 August 2026 · 6 min read
Your mix probably isn't too quiet, it's likely hitting a different integrated LUFS than the reference tracks you're comparing it to. Streaming platforms don't play files at their native loudness. They measure the loudness of the whole track and turn playback up or down to match a fixed target. A track mastered hotter than that target gets turned down. A track mastered quieter gets turned up, which can expose noise floor and dynamics you didn't expect anyone to hear.
What LUFS actually measures
LUFS (Loudness Units Full Scale) measures perceived loudness across an entire track, not just the loudest peak. It's different from the peak meter in your DAW, which only tells you the highest single sample. Two tracks can hit the same peak level and still sound completely different in loudness, because LUFS accounts for how long a section stays loud, not just how loud it briefly gets.
This is why a heavily limited, brickwalled master doesn't automatically sound louder on Spotify than a dynamic one, the platform is normalizing both down to roughly the same perceived loudness anyway. The brickwalled version just loses more dynamic range for nothing.
Streaming loudness targets
Each platform normalizes to a different target. Mixing without knowing these numbers is why your track can sound perfectly competitive in your DAW and noticeably quieter the moment it goes live.
| Platform | Target LUFS | True Peak |
|---|---|---|
| Spotify | -14 LUFS | -1 dBTP |
| Apple Music | -16 LUFS | -1 dBTP |
| YouTube | -14 LUFS | -1 dBTP |
| Club / DJ sets | -6 to -9 LUFS | -0.3 dBTP |
Notice club and DJ contexts sit far hotter than streaming targets. If you're mixing for both a streaming release and a club edit, you likely need two separate masters, not one file trying to serve both.
Why your reference track sounds louder in your DAW
When you A/B a reference track against your own mix inside your DAW, you're comparing raw files, not normalized playback. Commercial reference tracks are usually already mastered close to streaming targets, so they can seem like they're "doing something" loudness-wise that your unmastered or early-stage mix isn't. That gap disappears once both files are normalized to the same LUFS target, the real question is whether your mix still holds up tonally and dynamically at that level, not whether it's loud enough.
Common mistakes that cause this
Judging loudness by ear against an already-mastered reference, instead of measuring integrated LUFS on both files.
Over-limiting to hit a peak target instead of an integrated loudness target, which sacrifices dynamics for no perceived loudness gain post-normalization.
Ignoring true peak and letting inter-sample peaks clip after lossy encoding (MP3/AAC), which some platforms then turn down further to compensate.
Mastering once and uploading the same file everywhere, when club, streaming, and YouTube all normalize differently.
How to fix it
Measure your integrated LUFS and true peak before you upload anywhere, and master to the target of the platform you're releasing on rather than to a peak number that feels loud in isolation. If your mix sounds thin or empty once it's normalized down to -14 LUFS, that's not a loudness problem, it's usually a sign the mix is leaning on limiting to feel full rather than on arrangement, low-end balance, and stereo width doing the work.
Run your mix through BetterMix to get an instant LUFS, true peak, and stereo width readout against genre-specific reference data for drum & bass, UK garage, and techno, so you know exactly where your mix sits before you release it.