Why Your Song Sounds Quieter on Spotify (and the Real Fix)

Your song usually isn't quieter on Spotify because you mastered too quietly — commercial tracks are engineered to sound loud at −14 LUFS, the level Spotify normalizes everything toward. There are four common causes: a genuinely low master, an unfair comparison, low mastering density, or Spotify's limited boost for quiet masters. All four are diagnosable free.

Is your song actually quieter — or are you comparing it wrong?

Before changing anything, run a fair test. Ears reliably rate the louder of two tracks as "better," and a 1 dB difference is enough to bias you. So the comparison has to happen at matched loudness, in the same playback chain the listener uses.

Two traps to rule out first. One: as of July 2026, Spotify's web player and many third-party devices don't apply loudness normalization at all — if you compared there, you heard raw master levels, not what most app listeners hear. Two: Premium listeners can set normalization to Loud (−11 LUFS), Normal (−14), or Quiet (−19), so two people can hear the same pair of tracks differently. The clean way to test is to measure both tracks' integrated LUFS, or A/B them with playback gain-matched to the streaming level — TrackGleam's free master includes a volume-matched A/B at Spotify loudness, on your device, nothing uploaded.

Reason 1: your master really is below streaming loudness

This is the simple case. Spotify normalizes to −14 LUFS integrated (ITU-R BS.1770), and it can only boost a quiet track within the track's own peak headroom — more on that limit below. If your export sits several LU under −14 with peaks already near the ceiling, Spotify plays it quiet, full stop.

It's a common state for unmastered exports, and especially for AI-generated music. We measured 12 AI-generated music exports from our test library: median −15.2 LUFS integrated (range −16.4 to −12.3), with 8 of 12 sitting below the −14 LUFS streaming level, 3 of 12 exceeding the −1.0 dBTP true-peak ceiling, and a median loudness range of 6.6 LU. If that's your situation, the fix is ordinary mastering — see how to master AI-generated songs free in the browser.

Reason 2: Spotify turned the other song down — and you compared outside Spotify

Most commercial releases are mastered hotter than −14 LUFS. On Spotify, they get turned down to −14 at playback — Spotify adjusts the playback gain and never alters the file itself (as of July 2026). Crucially, turning a hot master down doesn't undo its limiting: all the density and sustain the mastering engineer packed in survives the gain reduction.

So if you compared your track against a commercial WAV in your DAW, or in a non-normalized player, the commercial file was playing 4–8 dB louder than it does on Spotify. Inside the app, at Normal volume, your −14 LUFS master and their turned-down −8 LUFS master play at the same average loudness. If yours still sounds smaller there, the difference isn't level — it's the next reason.

Reason 3: perceived loudness is density and tonal balance, not LUFS

Two tracks can both measure −14 LUFS integrated and sound very different in level. LUFS is a gated average; your ear responds to how consistently energy is present and where it sits in the spectrum. Tracks that "sound loud at −14" share traits: controlled dynamics (sustained energy rather than brief peaks over empty space), solid midrange around 1–5 kHz where hearing is most sensitive, and lows that are tight rather than bloated — sub energy eats headroom while adding little perceived loudness.

There's a measurement wrinkle too: BS.1770 doesn't low-pass the signal, so Spotify notes that inaudible high-frequency content can inflate a track's measured loudness — meaning a harsh or hissy master gets turned down for energy nobody hears. This is why "just push the limiter harder" disappoints: it raises LUFS, triggers more turn-down, and leaves density and tonal balance — the things that actually read as loud — unchanged.

Reason 4: the quiet-track penalty — Spotify won't fully boost quiet masters

Normalization is not symmetric. Loud masters are always turned down to the target, but quiet masters are only boosted as far as their own true-peak headroom allows, and Spotify keeps an extra 1 dB of headroom in reserve for lossy encoding. Spotify's own example (as of July 2026): a −20 LUFS track with peaks at −5 dBFS gets lifted only to −16 LUFS — still 2 LU under everything else. Here's how that plays out at the Normal (−14 LUFS) setting:

Verified July 2026 — we re-check these quarterly. Behavior per Spotify's artist documentation; the web player and some third-party devices skip normalization entirely.

Spotify also cautions that true peaks above −2 dBTP can distort during lossy encoding — one more reason the peak ceiling matters as much as the loudness number. If dBTP is new to you, true peak is explained here.

How do you actually fix it?

Work the reasons in order, with measurements instead of guesses:

1. Measure. Drop your track into the free browser masterer — it reports integrated LUFS (BS.1770-4 gated) and dBTP true peak on every master, computed on your device; the audio never uploads. If you're under −14 LUFS or over −1.0 dBTP, that's your diagnosis.

2. Master to the streaming target. −14 LUFS integrated with a −1.0 dBTP ceiling covers Spotify and travels well everywhere else — the full platform-by-platform numbers are in our LUFS streaming targets guide. Don't overshoot: anything hotter just gets turned back down with its limiter artifacts intact.

3. If it hits the target and still sounds small, work on density and tone. That's dynamics control, low-mid cleanup, and midrange presence — the free master applies a genre-aware chain, and the AI-Enhanced Master ($1.99 one-time, no subscription) pushes further on density and tonal balance for tracks that need it.

4. Judge at matched volume. Use the built-in A/B at Spotify loudness before downloading, so louder can't masquerade as better. If the master wins the fair test, it'll hold up in a playlist.

Master a track free — no signup, nothing uploads