Why Does My Master Clip on Spotify?
Published · updated · by Loopin
A track that sounded clean during mastering but distorts specifically on Spotify usually traces to a well-understood interaction between an already-hot master and the platform's own loudness normalisation.
Understand what Spotify's normalisation actually does
When Spotify normalises a track that's louder than its target, it applies gain reduction to bring the level down. But some implementations of loudness normalisation apply this as a straightforward gain change without additional peak limiting, which means a file with insufficient true-peak headroom can clip during or after this adjustment.
This is why a file that measured clean on your own system, at your own playback level, can still exhibit clipping-like artifacts once processed through a platform's normalisation.
The root cause is almost always insufficient true-peak headroom
If your master's true peak is right at or very close to 0 dBTP, rather than the recommended −1 dBTP or lower, there's no safety margin left for any additional processing — including the platform's own normalisation and any subsequent format conversion.
Check your delivered file's true-peak reading specifically, not just its standard peak level, since these measure genuinely different things and only true peak reliably predicts this kind of issue.
The fix: proper true-peak ceiling before delivery
Re-master or re-limit with a genuine −1 dBTP true-peak ceiling, using a limiter with true-peak detection or oversampling enabled, rather than relying on a standard peak meter that might miss inter-sample peaks entirely.
This single correction resolves the large majority of platform-specific clipping complaints, since it's addressing the actual root cause rather than a symptom specific to any one platform's processing.
Confirm the issue is genuinely on Spotify's end, not elsewhere
Before concluding it's specifically a Spotify normalisation issue, confirm the distortion isn't present in your original master file itself — play the actual delivered file directly, not through Spotify, to rule out an issue that existed before the file even reached the platform.
If the file is clean on direct playback but distorts specifically through Spotify, that confirms the normalisation-interaction diagnosis above rather than a more basic mastering error.
This is worth checking even if you haven't noticed a problem yet
Not every listener or listening context reveals this kind of subtle clipping clearly — it's worth proactively checking true-peak headroom on any already-released masters, especially older ones mastered before this specific issue was well understood, even if no one has reported a problem.
A proactive check and, if needed, a corrected re-upload is a reasonable step for protecting the listening experience of any release still actively being streamed.
Frequently asked questions
Why does my track distort on Spotify but not when I play it directly?
This typically happens when a master has insufficient true-peak headroom (right at or near 0 dBTP). Spotify's normalisation applies gain adjustment that can expose or worsen clipping that wasn't audible before that processing.
How do I fix a master that clips after Spotify's normalisation?
Re-master or re-limit with a genuine -1 dBTP true-peak ceiling, using a limiter with true-peak detection or oversampling enabled, rather than relying on a standard peak meter that can miss inter-sample peaks.
Should I check older releases for this issue even without complaints?
Yes, it's worth a proactive check, especially for releases mastered before true-peak headroom was well understood as a specific issue. Not every listening context reveals subtle clipping clearly, so absence of complaints isn't proof of absence of the problem.