
The short version of how to master for Spotify: aim for about -14 LUFS integrated with true peak at or below -1 dBTP, then confirm both numbers in a free volume normalizer before you upload. That is the whole target. Everything else here is about hitting those two numbers cleanly, and — just as important — not wrecking your mix chasing loudness Spotify is going to turn back down anyway.
This is a pre-upload checklist for a file you already have — a bounced stereo mix or a near-final master. It takes a couple of minutes, runs in your browser, and your audio never leaves your device.
Spotify plays every track through loudness normalization. By default (its Normal mode) it targets roughly -14 LUFS integrated — a measure of average perceived loudness across the whole song. If you deliver louder than that, Spotify turns your track down. If you deliver quieter, it leaves it alone in Normal mode. So the loudness of your master, past a point, is not something you get to control on the listener's end. That single fact changes how you should master. If you're new to the unit, what LUFS means for audio loudness is a two-minute primer.
The second number is a ceiling, not a target: true peak at or below -1 dBTP. True peak (dBTP) catches the inter-sample peaks that a normal sample-peak meter misses. Spotify encodes to lossy formats (Ogg Vorbis and AAC), and that transcoding can add peaks that weren't in your file — pushing a master that read -0.1 dBTP into audible clipping on playback. Leaving a decibel of headroom absorbs that. Spotify's own guidance goes further: if your master is louder than -14 LUFS, cap true peak at -2 dBTP for extra safety. What true peak (dBTP) is explains why it differs from sample peak.
Mastering for Spotify is really two jobs: shape tone and dynamics, then land the loudness and peak targets. Do them in that order.
Master tone and dynamics first (optional but recommended). If your file is a raw mix rather than a finished master, run it through the audio mastering tool to glue the mix, balance tone, and apply gentle limiting. This is where a real master gets its polish and controlled loudness — a normalizer alone can't do it. If you already have a finished master you're happy with, skip to step 2.
Open the volume normalizer and drop in your file. The free volume normalizer reads your file and shows a Before panel with its measured integrated LUFS and true peak (dBTP). This is your starting point — note both numbers.
Select the Spotify preset. In Loudness (LUFS) mode, click the Spotify target button. It sets the target to -14 LUFS. (YouTube is also -14 LUFS; Apple Music is -16.)
Keep Prevent clipping on. Leave the Prevent clipping (cap true peak at -1 dBTP) checkbox ticked. This stops the tool from pushing true peak above -1 dBTP even while it chases the loudness target — the exact ceiling Spotify asks for. If your master is already louder than -14 LUFS, switch to Peak mode and set the target-peak slider to -2 dBTP for the extra transcoding margin.
Preview and read the After panel. Click Preview after-LUFS. The After panel now shows the integrated LUFS and true peak your exported file will have. Confirm it lands near -14 LUFS with peak at or below -1 dBTP. The tool also displays the exact gain offset it applied, so you can see whether it turned the track up or down.
Export. Pick a format in the export selector — WAV (lossless, the safe default) is ideal for delivery; MP3, FLAC, M4A, and Opus are also available — and click Export WAV. That file is your Spotify-ready master. Your distributor handles delivery to Spotify from there.
For why the platform does this at all, how streaming loudness normalization works covers the full picture across services.
Here is the trap. Spotify has three playback loudness modes a listener can choose in settings: Loud (about -11 LUFS), Normal (about -14 LUFS, the default), and Quiet (about -19 LUFS). Only Loud turns quiet tracks up, and only Loud applies a limiter when it does — which can add its own distortion. Normal and Quiet only ever turn loud tracks down.
So mastering to -8 LUFS to sound "competitive" buys you nothing on Spotify: for the vast majority of listeners on Normal, your -8 master gets turned down to -14 anyway, and you've traded away all your dynamic range for a loudness the platform discards. That's the loudness war losing its own point. The fix is not to over-compress. Master to sound good at around -14 LUFS, let it breathe, and let normalization handle the rest.
Don't over-correct the other way either. Leaving a track very quiet isn't a safe way to "preserve dynamics" — a listener on Loud mode will have it turned up with a limiter, which is exactly the distortion you were trying to avoid. Landing near -14 LUFS is the sweet spot that behaves well in every mode. If you're unsure what to aim for on other platforms too, what LUFS you should master to has the per-service table.
One caveat: the normalizer applies a single gain offset and holds the true-peak ceiling — it is not a multiband limiter. If a mix is quiet and undynamic, normalizing it toward -14 will hit the -1 dBTP ceiling and stop rather than crush peaks to force more loudness. That's your signal to do the tonal work in the mastering tool first.
My track is quieter after normalizing. That's correct behavior if your master was already louder than -14 LUFS — the tool turned it down to match Spotify's target, which is exactly what Spotify would do on playback. You lose nothing: Normal-mode listeners hear the same loudness either way, and now your peaks are safe. If you genuinely need more perceived loudness, that comes from tonal and dynamic mastering in the audio mastering tool, not from pushing the number higher.
True peak is still over -1 dBTP after I convert to MP3. Lossy encoding can add inter-sample peaks after you export, so a file that read exactly -1.0 dBTP can nudge over once transcoded. Give yourself margin: re-run it in Peak mode with the slider at -2 dBTP, or master a touch quieter. Delivering a lossless WAV also avoids stacking your export encoding on top of Spotify's.
It sounds less punchy when I make it loud. That's the compression you added to reach a high loudness flattening the transients. Because Spotify normalizes anyway, that loudness is discarded on playback while the squashed dynamics remain — so you kept the downside and lost the upside. Back off the limiting, master nearer -14 LUFS, and let the punch return.
Landing loudness is the last step of a bigger workflow. Starting from a rough mix, how to master a song online for free walks the full chain, and the rest of our how-to guides cover the individual tools. Once your file measures near -14 LUFS at -1 dBTP, it's ready for your distributor.
What LUFS should I master to for Spotify? Aim for about -14 LUFS integrated, which matches Spotify's default Normal playback target. Keep true peak at or below -1 dBTP, or -2 dBTP if your master runs louder than -14 LUFS, to leave room for the inter-sample peaks lossy encoding can add. Mastering much louder than -14 LUFS gains nothing, because Spotify simply turns louder tracks back down.
Does Spotify master my track for me? No. Spotify applies loudness normalization on playback so tracks sit at a consistent level, but it does not master your audio — it won't fix tone, balance, or dynamics. You still deliver a finished master. Normalization only adjusts overall gain up or down toward its target; the creative and technical mastering is yours to do beforehand.
Should I master louder to compete on Spotify? No. Spotify turns any track louder than about -14 LUFS back down on playback, so extra loudness is discarded while the heavy compression you used to get it stays — you lose dynamic range for nothing. Master to sound good around -14 LUFS and let normalization equalize levels across every track a listener hears.
Do I need a special file format to upload to Spotify? Not from the mastering side. Prepare a clean master — a lossless WAV or FLAC is ideal — and your distributor handles delivery in whatever format Spotify requires. Playback loudness normalization is independent of the file you supply, so focus on hitting -14 LUFS and -1 dBTP rather than on a particular upload format.