Why Your Song Sounds Different After Uploading
Published · updated · by Loopin
If your song sounds different after uploading, two things are almost always at work: the platform’s loudness normalization shifts your perceived level, and lossy transcoding to AAC, Opus or MP3 nudges your tone and can push true peaks into clipping. The fix is to master to about −14 LUFS so normalization barely acts, and to leave true-peak headroom so the codec has room to work. You can do both, free, in Loopin’s browser mastering.
Why your song changes after you upload it
The file you bounced and the file a listener hears are not the same file. Streaming platforms run every upload through two processes that alter how it sounds — loudness normalization and lossy transcoding. Neither is a bug; both are standard, and both are predictable once you know what they do.
The good news is that a master built for these processes barely changes at all. When you hit the right loudness target and leave the right headroom, normalization has almost nothing to adjust and the codec has room to breathe. The difference between a track that survives upload and one that doesn’t comes down to those two numbers.
- Loudness normalization: the platform re-levels your track toward about −14 LUFS
- Lossy transcoding: your WAV is re-encoded to AAC, Opus or MP3
- Both happen automatically — you never see the file the listener gets
- A master built for both survives the trip nearly unchanged
Cause 1: loudness normalization
Streaming platforms play everything back toward a common loudness, around −14 LUFS, so listeners don’t have to ride the volume knob between songs. If your master is louder than that target, the platform turns it down on playback; if it’s quieter, the platform may turn it up. Either way, the perceived level you carefully dialed in shifts.
This is why a master that felt punchy and loud on your system can sound flatter or smaller after upload — it was hotter than the reference, so it got pulled down. Matching the target instead of fighting it keeps your playback level exactly where you intended.
- Platforms normalize by integrated LUFS, around −14 LUFS
- A master hotter than −14 LUFS gets negative gain on playback
- That’s why ‘loud’ masters can sound quieter after upload
- Master to about −14 LUFS and normalization barely touches you
Cause 2: lossy transcoding
Platforms don’t stream your WAV — they re-encode it to a lossy format like AAC, Opus or MP3 to save bandwidth. That re-encoding can shift your tone slightly, and it can push your true peaks higher than they were in the original file. A master that peaked right up at the ceiling can end up clipping after the codec is done with it.
This is the sneaky one, because it doesn’t show up until after upload. The file measured clean on your machine, but the encoder’s reconstruction overshot the ceiling and introduced distortion. The cure is headroom — give the codec somewhere to put those overshoots.
- Your WAV is re-encoded to AAC / Opus / MP3 for streaming
- Transcoding can shift tone and raise true peaks
- Peaks that sat at the ceiling can clip after encoding
- Leaving true-peak headroom prevents codec clipping
The fix: target −14 LUFS with true-peak headroom
Both causes have the same two-number cure. Master to about −14 LUFS so normalization has almost nothing to adjust, and leave true-peak headroom so the codec can re-encode without clipping. A true-peak limiter set to −1 dBTP gives most platforms the room they need; for Amazon, leave a little more at −2 dBTP.
Hit those targets and the file a listener streams sounds essentially like the file you bounced — same level, same tone, no surprise distortion.
- Integrated loudness: about −14 LUFS
- True-peak ceiling: −1 dBTP for most platforms
- Amazon: leave more headroom at −2 dBTP
- Both numbers together defeat both causes at once
Make your song survive upload step by step
Here’s the fastest reliable path from a finished mix to a master that sounds the same after upload:
- Bounce your mix to WAV with headroom — peaks near −6 dB and no mix-bus limiter.
- Open Loopin’s free mastering tool and drop the file in.
- Let the chain drive loudness toward about −14 LUFS integrated with a −1 dBTP true-peak ceiling.
- A/B against your original — it should sound fuller and controlled, not squashed.
- Confirm the true peak lands at −1 dBTP (or −2 dBTP if you’re targeting Amazon).
- Download the 16-bit WAV and upload that — not an MP3 or a hotter bounce.
Common mistakes
- Mastering way hotter than −14 LUFS — the platform just turns it back down, so it sounds quieter, not louder.
- Peaking at 0 dBFS — the codec pushes true peaks over the top and clips after upload.
- Uploading an MP3 instead of a WAV — that stacks a second round of lossy encoding on top of the platform’s own.
- Judging your master only on your own system — check the actual streamed version before deciding what changed.
- Blaming the master for a mix issue — mastering acts on the whole stereo file, so tone problems baked into the mix travel with it.
Is it a mix problem or a master problem?
Normalization and transcoding are master-stage concerns — they act on the finished stereo file, and hitting the right loudness and headroom targets is exactly the master’s job. If your track sounds different after upload in level or shows new clipping, that’s the master, and the two numbers above fix it.
But if the track sounded thin, muddy or unbalanced before upload and simply still sounds that way after, that’s a mix issue that the codec merely revealed. Mastering acts on the whole stereo file and can’t un-bake a balance problem. Fix the mix first, then let Loopin’s mastering tool handle the loudness-and-headroom stage so the upload stays faithful.
Fix it free
Loopin’s online mastering drives your track toward about −14 LUFS integrated with a −1 dBTP true-peak ceiling, all in your browser — free, no signup, nothing uploaded, no watermark. Drop in your mix, A/B it against the original, and download a 16-bit WAV that sounds the same after you upload it.
Frequently asked questions
Why does my song sound different after uploading?
Two things happen at upload: the platform normalizes loudness toward about −14 LUFS, which shifts your perceived level, and it transcodes your file to a lossy format like AAC, Opus or MP3, which can shift tone and push true peaks into clipping. Mastering to −14 LUFS with true-peak headroom minimizes both.
How do I stop normalization from changing my level?
Master to about −14 LUFS integrated. That matches the level platforms normalize toward, so they apply almost no gain and your playback level stays where you intended.
Why does my song clip or distort only after upload?
Lossy transcoding can push true peaks higher than they were in your original file. If your master peaked right at the ceiling, the codec overshoots and clips. Leave true-peak headroom — −1 dBTP for most platforms, −2 dBTP for Amazon.
Should I upload a WAV or an MP3?
Upload a WAV if you can. Uploading an MP3 stacks a second round of lossy encoding on top of the platform’s own transcoding, compounding the tone shift. Master and export to WAV, then upload that.
Can I fix this for free?
Yes. Loopin’s free browser mastering drives your track toward about −14 LUFS with a −1 dBTP ceiling, runs entirely in your browser with nothing uploaded, and exports a 16-bit WAV built to survive upload.