What LUFS Should You Master to for Spotify? (2026): The Honest Answer

The short answer: Spotify normalizes playback to -14 LUFS integrated by default, and you should aim for a master near that target with true peak kept below -1 dBTP. But the more important answer, the one that changes how you master, is this: do not master to a number at all. Because Spotify turns the level up or down for you, a master crushed to -6 LUFS gets turned DOWN about 8 dB to hit -14, which means you destroyed your dynamics and transient punch and it still plays at the exact same volume as a well-mastered -14 track that kept its life. Louder does not win on streaming. It loses, for nothing. Below is the full verified platform table, the true-peak rule that actually protects your sound, an honest explanation of integrated LUFS versus true peak, and the reasonable landing zone. This is general guidance from Spotify and iZotope documentation as of July 2026, not measured audio testing.

What LUFS does Spotify actually target?

Spotify applies loudness normalization to every track by default so that songs play back at a consistent level, and its own documentation sets that default target at -14 LUFS integrated (Spotify loudness normalization). Anything louder than -14 gets negative gain applied on playback, and anything quieter gets turned up, within limits we will get to. Listeners can override the target in their app settings with three choices: Loud (-11 LUFS), Normal (-14 LUFS, the default), and Quiet (-19 LUFS). The overwhelming majority of listeners never touch this, so for practical purposes your track is heard at -14. There is one meaningful wrinkle: at the Loud -11 setting, Spotify applies a limiter to quieter masters as it pushes them up, which can subtly alter your sound in a way you did not choose. That is one more reason to deliver a master that already sits sensibly rather than a very quiet one that depends on the platform cranking it.

The full platform loudness table

Spotify is not the only destination, and the targets differ. If you distribute one master to every platform, which is what most independent artists do, aim for the cluster the majority sit in rather than optimizing for a single service. Here are the verified targets as of July 2026, compiled from Spotify's documentation and iZotope's streaming loudness guide.

Targets compiled from Spotify's documentation and iZotope's mastering for streaming platforms guide. Apple's -16 LUFS is a community and measured estimate, not an Apple-published spec.

Notice that the biggest platforms cluster at -14 LUFS (Spotify, YouTube, Amazon Music, Tidal), Deezer sits one dB quieter at -15, and the Audio Engineering Society reference for music streaming (AESTD1008) is -16. Apple Music's estimated -16 lines up with that industry reference, though Apple itself does not confirm a LUFS number (its Sound Check feature is a separate, non-LUFS system). The practical read is that a master somewhere around -14 satisfies the platforms that matter most, and going meaningfully louder than that buys you nothing on any of them except SoundCloud, which does not normalize at all.

Integrated LUFS vs true peak: what each one actually governs

These two numbers get confused constantly, and understanding the difference is what lets you stop chasing the wrong one. Integrated LUFS is the perceived loudness of your whole track, measured across its entire length with a K-weighting curve (which approximates how human hearing responds to different frequencies) and a gate that ignores near-silent passages. It is a single number describing how loud the song feels overall, and it is the number every streaming platform reads to decide whether to turn you up or down. When Spotify normalizes to -14, it is normalizing your integrated LUFS.

True peak is a completely different measurement. It is the highest actual output level your signal reaches, calculated with oversampling to catch inter-sample peaks (voltage spikes that occur between digital samples and can exceed 0 dBFS when the signal is reconstructed by a converter or a lossy codec). It is measured in dBTP, decibels true peak, and it governs clipping and distortion, not perceived loudness. A track can have a low integrated LUFS and still have true peaks over 0 dBTP that distort, or a high LUFS with well-controlled peaks. They are independent measures answering different questions: LUFS asks "how loud does this feel," true peak asks "will this clip."

This matters because when a platform turns your loud master DOWN, it does not save you from true-peak problems that were baked in when the master was created, and when a lossy codec (the compressed AAC or Ogg Vorbis file the platform actually streams) re-encodes your audio, it can push peaks even higher than your original file showed. That is why the true-peak ceiling is a real, protective rule rather than a formality.

Integrated LUFS is how loud your track feels and what the platform reads to turn you up or down. True peak is how close you are to distortion. Master the first with your ears, and hold the second under -1 dBTP so the codec cannot betray you.Spotify + iZotope loudness documentation

The true-peak rule that actually protects your sound

Spotify's own guidance is to keep true peak below -1 dBTP, and below -2 dBTP if your master is louder than -14 LUFS. The reason is the lossy codec. Streaming platforms do not send listeners your WAV; they send a compressed file, and the encoding process can introduce inter-sample peaks that push levels above where your original master sat. If your master is already brushing 0 dBTP, the encoded version can clip and distort audibly, especially in the low end and on transient-heavy material. Leaving a dBTP of headroom (two if you mastered hot) gives the codec room to do its work without turning your peaks into distortion. This single ceiling does more to protect how your track sounds on streaming than any amount of loudness chasing, and unlike the LUFS target, it is a hard rule worth honoring precisely.

Why mastering ultra-loud is self-defeating

Here is the payload, the thing almost no vendor page will tell you because louder sells software and services. Suppose you master a track to -6 LUFS, slamming a limiter to make it as loud as possible. You upload it to Spotify. Spotify reads its integrated loudness, sees it is 8 dB above the -14 target, and applies about -8 dB of gain on playback. Your -6 master now plays at -14. The listener hears it at exactly the same volume as a track someone else mastered thoughtfully to -14 while preserving its dynamic range and transient punch. You did not get louder. You gave up your dynamics, your transients, your sense of openness and impact, in exchange for a loudness the platform simply deletes before anyone hears it.

And it is worse than a wash, because the dynamic -14 master usually sounds better after normalization: more open, more punchy, more three-dimensional, because it kept the peaks and micro-dynamics that a loudness-maximized master flattens. The loudness war made sense in the era of CDs and radio, where a louder master genuinely played louder and grabbed attention. On normalized streaming, that entire logic inverts. The loud master is not just neutralized, it is actively handicapped against a dynamic one played at the same level. Chasing loudness for streaming is not a competitive edge, it is a self-inflicted wound.

So what should you actually do?

Stop optimizing for a target and start optimizing for how the track sounds. A reasonable landing zone for a streaming master is roughly -12 to -14 LUFS integrated with true peak at or below -1 dBTP, but treat that as a consequence of good decisions, not a goal you push toward. Different songs and genres want different things: a sparse acoustic ballad might sit naturally quieter and lose everything if you force it loud, while a dense electronic track might live comfortably nearer -10 before normalization pulls it back, and that is fine as long as you kept it sounding good and controlled the peaks. The discipline is simple. Master until it sounds as open, punchy, and finished as you can make it. Check that your integrated LUFS landed somewhere sane and that your true peak sits under the ceiling. Then leave it alone. The platform will set the playback level for you, and a master that sounds great and keeps its dynamics will beat a crushed one every single time, at the same volume.

A brief nuance on the extremes. If you deliver a very quiet master hoping the platform will crank it up, remember that on the Loud -11 setting Spotify applies a limiter as it pushes quiet tracks up, and even on the default it only raises quiet material as far as your peak headroom allows before risking distortion, so an excessively quiet master can end up sounding weak or getting processed in ways you did not intend. And if you master very loud, everything above applies: it gets turned down and loses its dynamics for nothing. The sweet spot is not an extreme, it is a well-controlled master near the target that you made sound good with your ears rather than a meter.

Tools that let you set a LUFS target

If you want direct control over your master's loudness, a few tools expose an explicit LUFS target rather than hiding it behind a preset. iZotope Ozone lets you set a specific integrated LUFS target and preview how lossy codecs will affect your peaks, which is exactly the workflow this guide argues for. Among free web tools, aimastering.com exposes an adjustable target loudness, and Bakuage offers loudness handling with reference matching. Online AI services like LANDR, eMastered, and Masterchannel optimize for streaming loudness internally without always showing you a number, which is fine as long as you understand that the number they land on matters far less than whether the result sounds good and keeps its dynamics. Whichever tool you use, the principle does not change: control the true peak, keep the dynamics, and do not chase loudness the platform will delete. For a full breakdown of which mastering tool fits your workflow, see our best AI mastering roundup, and for platform-specific picks, best AI mastering for Spotify.

Frequently asked questions

What LUFS should I master to for Spotify? Spotify normalizes to -14 LUFS integrated by default, so a master near that with true peak below -1 dBTP is a safe landing zone. But do not master TO the number: keep your dynamics and let normalization set the level, because a loud master just gets turned down to -14 anyway and loses its punch for nothing.

Is -14 LUFS a hard requirement? No. It is Spotify's default normalization target, not a submission rule. There is no minimum or maximum you must hit. Your master will play fine at any loudness; the platform simply adjusts the level. The real hard rule is the true-peak ceiling below -1 dBTP to avoid codec distortion.

What is the difference between LUFS and true peak? Integrated LUFS measures perceived loudness of the whole track (K-weighted and gated) and is what platforms read to normalize level. True peak (dBTP) measures the highest oversampled output level and governs clipping and distortion. They are independent: one tells you how loud it feels, the other tells you how close you are to distorting.

Should I master louder for a "competitive" streaming sound? No. Because playback is normalized, a louder master gets turned down to the platform target and plays at the same volume as a dynamic master, except you crushed your dynamics to get there. On streaming, a well-controlled dynamic master near -14 LUFS sounds better than a loud one at the same playback level.

What LUFS for Apple Music, YouTube, and the others? YouTube, Amazon, and Tidal target -14 LUFS like Spotify; Deezer targets -15; Apple Music is estimated around -16 (not officially published); SoundCloud does not normalize at all. One master near -14 with peaks under -1 dBTP serves the whole cluster well.

Bottom line

Spotify targets -14 LUFS integrated by default, with user options of Loud -11 and Quiet -19, and it recommends true peak below -1 dBTP (below -2 if you master louder than -14). Most other major platforms cluster at -14 as well, so one sensible master serves them all. But the number is not the point. Because streaming normalizes playback, mastering ultra-loud is self-defeating: a -6 LUFS master gets turned down about 8 dB to -14 and plays at the same volume as a dynamic -14 master that kept its punch, so you crushed your dynamics for nothing. Do not master to a number. Make the track sound as good and as open as you can, keep its dynamics, hold true peak under the ceiling, land somewhere around -12 to -14 LUFS integrated as a consequence rather than a goal, and trust your ears. On streaming, the dynamic master wins. This is general guidance from Spotify and iZotope documentation as of July 2026, not measured audio testing.