You are not imagining it. DJ mixes uploaded to SoundCloud routinely sound worse than they did in your headphones moments earlier - quieter, flatter, sometimes muddy, sometimes harsh in the top end. The reasons are technical and consistent. SoundCloud does five specific things to your audio between upload and playback, and an unmastered mix is vulnerable to all of them. Here is each cause, and how to fix it - the long way, and the fast way.
The short answer
SoundCloud normalises every track to around -14 LUFS, transcodes your upload to a lossy streaming format, and does nothing to fix the level inconsistencies, low-end build-up, or true-peak clipping that an unmastered DJ mix typically carries. Your headphones played the raw file at full quality and full volume; SoundCloud does neither. The fix is to master the mix to the right target before you upload - either manually in a DAW, or with a tool that does it for you automatically.
Reason 1 - SoundCloud turns your mix down (or up) without telling you
SoundCloud measures the integrated loudness of every upload and adjusts playback so all tracks sit at roughly -14 LUFS. This is loudness normalisation, and it runs on everything - there is no setting to switch it off. It means the perceived loudness of your mix, against every other DJ on the platform, is decided by SoundCloud and not by you.
If you mastered to -8 LUFS to make your mix loud, SoundCloud pulls it back by around 6 dB to hit its target. You gain nothing in volume, and the pumping and squashed transients you introduced chasing loudness are still there, now playing quietly. If your mix sits at -20 LUFS because it was never mastered, SoundCloud does not turn it up - it just plays quiet and thin next to the mastered mixes around it.
Either way you lose. The only way to win is to master to the platform's target before upload, so the level SoundCloud plays back is the level you intended.
How to fix it
Master to -14 LUFS integrated with a -1 dBTP true-peak ceiling. A free LUFS meter plugin (multiple options exist for any DAW) or the free DJ Mix Analysis tool will tell you exactly where your current mix sits before you change anything.
Reason 2 - SoundCloud re-encodes your audio
Whatever you upload - WAV, FLAC, AIFF, or MP3 - SoundCloud does not stream that file to your listeners. It transcodes everything to a lossy format: 128 kbps MP3 for free listeners, 256 kbps AAC for Go+ subscribers. The file you carefully exported is not the file anyone hears.
This conversion is destructive by design. Lossy encoding throws away high-frequency detail and can add a swishy quality to cymbals, hi-hats, and reverb tails - the parts with the most fine detail. It can also clip, when inter-sample peaks sitting just under 0 dBFS get pushed over the line by the encoder.
The worst case is uploading an MP3: SoundCloud re-encodes it regardless, so you stack one lossy encode on another - double-encoding loss, audible as extra harshness and smearing. Give the platform the cleanest source you can, so the one unavoidable encode is the only one your audio goes through.
How to fix it
Always upload WAV, or 320 kbps MP3 as an absolute minimum. Master with a true-peak ceiling of -1 dBTP rather than 0 dBFS, so the encoder has the headroom it needs to work without clipping.
Reason 3 - Your mix has level inconsistencies you stopped noticing
When you record a live DJ set, the output level never holds still. One record is pressed slightly hotter than the next. You ride the trim through a transition and leave it there. A breakdown drops the energy, then a drop slams it back. Over an hour, these variations accumulate, so some sections sit at -8 dB peaks while others sit at -14 dB.
You stop hearing it, because you mixed it - your ears adapt as the set plays. But a fresh listener notices the energy dipping and swelling in ways that feel unintentional rather than musical. Uneven reads as amateur.
Track-focused automated mastering services do not fix this: they assume the input is a single song at one consistent level. A DJ mix is the opposite - dozens of tracks at slightly different levels, stitched together live. It needs broadband compression that smooths the inconsistencies across the whole mix, not loudness applied within one track.
How to fix it
Apply a gentle 2:1 broadband compressor across the whole mix, with a slow attack and moderate release. Two to three dB of gain reduction is plenty. The goal is invisible smoothing, not loudness - if you can hear it working, it is doing too much.
Reason 4 - Low-end rumble builds up over the length of the mix
A 60-minute mix is 60 minutes of kick drums, sub-bass, and low-end energy stacked back to back. Even with careful gain staging, content below 60 Hz accumulates - room rumble, vibration, and the inaudible bottom of every kick and bassline adding up across the recording.
Most listeners never hear it directly - phone speakers barely reproduce below 100 Hz, laptops struggle below 80 Hz. But the energy is still there, and it causes two problems. It eats limiter headroom, so the limiter clamps down on the music you want in order to control rumble nobody asked for. And it reads as muddy or heavy low end on systems that can reproduce it.
SoundCloud's lossy codecs make it worse. The encoder has a fixed bit budget, and it spends bits on that sub-bass rumble - bits then unavailable for the kick, the bassline, and the parts of the mix that matter.
How to fix it
Apply a high-pass filter at 30-40 Hz as the first stage of your mastering chain. It removes the inaudible sub-bass without changing the perceived weight or character of the bass you can actually hear.
Reason 5 - True peaks are clipping after upload
Your mix can peak at exactly 0 dBFS in your DAW and still clip after upload, because of inter-sample peaks. A file stores samples - snapshots of the waveform - but playback reconstructs a smooth curve between them, and that curve can overshoot the highest sample, rising above 0 dB in the gaps. Most meters show only sample peaks, so they never warn you.
It becomes audible when SoundCloud transcodes the file. The encoder works on the reconstructed waveform, and those overshoots become real clipping in the streaming file - harsh distortion on cymbals, sibilance, and high-frequency transients. Baked into the encode, it is permanent: every listener hears it, on every device.
It is subtle enough that listeners rarely name it as clipping. They just call the mix harsh, fizzy, or fatiguing - the sound you end up turning down, and one of the clearest tells of an unmastered upload.
How to fix it
Use a true-peak limiter - one that measures dBTP, not just sample peaks - with the ceiling set to -1 dBTP. A true-peak limiter plugin, commercial or free, or the mastering step in a tool like SetMaster Pro, handles this automatically.
The fast way to fix all five problems
The five problems are interdependent - fixing one without the others barely moves the needle. The manual route is a workflow in itself: a DAW and a mastering plugin chain, the hours to learn them, then 30 to 60 minutes mastering each mix by hand - and that is before you export, log in to SoundCloud to upload and tag it, then do the same again for Mixcloud and your social posts. Call it one to two hours of admin per mix, on top of the upfront investment.
SetMaster Pro collapses that into a single form. Choose your file, choose the Streaming profile (which targets streaming platforms), pick your destinations - SoundCloud, Mixcloud, Facebook, Instagram, in any combination - add your artwork and mix details, and click once. It masters to -14 LUFS integrated with a -1 dBTP ceiling, applies broadband compression, removes sub-bass below 30 Hz and limits true peaks before encoding, then publishes the finished master to each destination and emails you when it is live. Mastering is one automatic step inside it; you never download a file and upload it again.
If you want to see where your mix sits before committing to a fix, the free DJ Mix Analysis tool measures all five - integrated LUFS, true peak, dynamic range, low-end build-up, and level consistency - in your browser, with nothing uploaded anywhere.
Frequently asked questions
Why does my DJ mix sound quieter than other people's on SoundCloud?
SoundCloud normalises every track to roughly -14 LUFS integrated. If your mix is below that level, the platform doesn't turn it up - it just plays at the lower level, so it sounds quieter than mastered mixes in the same feed. Mastering to -14 LUFS before uploading is how to sit equal in playback volume.
Does SoundCloud reduce audio quality?
Yes. SoundCloud transcodes all uploads to lossy formats - 128 kbps MP3 for free listeners and 256 kbps AAC for Go+ subscribers. The original file you upload is not what listeners hear. This makes upload format (use WAV, not MP3) and true-peak headroom (-1 dBTP, not 0 dBFS) important before upload.
What LUFS should I master my DJ mix to for SoundCloud?
-14 LUFS integrated with a -1 dBTP true-peak ceiling. This matches SoundCloud's normalisation target and gives the streaming encoder enough headroom to avoid clipping. Going louder than -14 LUFS gains you nothing because the platform turns you back down.
Why does my DJ mix sound muddy after I upload it to SoundCloud?
Two reasons usually combine. First, accumulated sub-bass below 60 Hz that's inaudible on small speakers but eats up codec headroom. Second, SoundCloud's lossy codecs are particularly bad at handling unfocused low-end content. A high-pass filter at 30-40 Hz before upload solves both.
Should I upload WAV or MP3 to SoundCloud?
Always WAV. SoundCloud re-encodes everything you upload to its own streaming format, and starting from a lossless WAV gives the encoder the most to work with. Uploading an MP3 forces the platform to re-encode an already-encoded file, which causes audible quality loss.
Does SoundCloud sound better on Pro Plus accounts?
SoundCloud streams to Go+ subscribers at 256 kbps AAC instead of the free tier's 128 kbps MP3. The Pro Plus subscription is for uploaders (longer upload limits, no listener restrictions). The streaming quality difference is on the listener side - your subscribers hear higher-quality streams if they're Go+, regardless of your upload tier.
The bigger picture
None of this means SoundCloud is broken. It behaves like every modern streaming platform - Mixcloud, YouTube, Spotify, and Apple Music all normalise loudness and transcode to lossy formats. The mixes that sound great on SoundCloud are not getting special treatment; they were treated for these five conditions before upload, so that once normalisation and encoding have done their work, what is left still sounds the way the DJ intended. For the full mastering process - and the same advice for Mixcloud and YouTube - see The Complete Guide to Mastering Your DJ Mix for Streaming Platforms.
Related articles
- The Complete Guide to Mastering Your DJ Mix for Streaming Platforms - the full mastering process, every platform, start to finish.
- Inside the Free DJ Mix Analysis - what the in-browser analyser reads, and what to do with the report.
- Best DJ Mix Mastering Software in 2026 - a side-by-side comparison of the automated options (coming soon).