How to Master a Suno Song
Published · updated · by Loopin
A Suno export usually needs the same three fixes: clear out low-mid buildup, calm down a harsh top end, and bring the loudness up to something that survives Spotify without sounding squashed.
Start by identifying the mud
AI-generated exports tend to stack instruments without the natural gaps a human mix leaves between them, and that shows up as buildup in the 250–500 Hz range — the track sounds thick and undefined rather than punchy. A gentle cut of 1.5–2 dB somewhere in that range, wide rather than narrow, usually clears it without thinning the track out.
Sweep a narrow boost through 250–500 Hz and listen for where the mix sounds most congested — that's your cut frequency. If nothing in that range stands out and the track already sounds clear, skip this step. Not every export needs it.
Calm the top end before you add any brightness
The second common issue is harshness sitting around 4–7 kHz — a brittle, fatiguing edge on vocals and synths that gets worse the longer you listen. Before reaching for a limiter or an exciter, try a narrow dip of 2–3 dB in that range first. It almost always does more than any amount of “smoothing” compression.
If the harshness is specifically on the vocal and not the instrumental, a de-esser set to that same 4–7 kHz zone, rather than the usual 6–9 kHz sibilance range, is often the more targeted fix.
Bring the loudness up without losing the clarity you just built
Most raw Suno exports land quiet, often close to −18 LUFS, which is one reason they can sound thin next to a released track before you've even started mastering. Aim for −14 LUFS integrated with a −1 dBTP ceiling as a starting target for streaming — that matches what Spotify normalises to, so you're not leaving loudness on the table or forcing a limiter to work overtime.
Do the EQ work first, then bring up loudness last. If you master for loudness before fixing the mud and harshness, the limiter just makes both problems louder and harder to hear clearly.
Check the stereo width
Some AI exports come out unusually wide or, less often, nearly mono. Check mono compatibility before you finish — fold the track to mono and listen for anything that disappears or phases oddly. If the low end or vocal thins out in mono, narrow the stereo image below 200 Hz; almost nothing in that range should be wide anyway.
A too-wide master can sound impressive on headphones and fall apart on a single Bluetooth speaker, which is exactly where a lot of this music actually gets heard first.
Ready it for release
Once the mud is cleared, the top end is calm and you're sitting around −14 LUFS, export at 24-bit WAV before any platform-specific conversion — distributors and streaming services handle their own compression, and starting from a high-resolution file gives you the most headroom for that.
Listen back on the smallest, cheapest speaker you have access to as a final check. A lot of Suno tracks get discovered through short clips on a phone, not a studio monitor, and that's the environment the master actually has to survive in.
Frequently asked questions
Why does my Suno song sound muddy?
AI-generated exports often stack instruments without natural separation, which builds up in the 250-500 Hz range. A gentle, wide cut of 1.5-2 dB in that range usually clears it without thinning the track.
What LUFS should I master a Suno track to?
Around -14 LUFS integrated with a -1 dBTP ceiling matches what Spotify normalises to. Most raw Suno exports land quieter than that, often near -18 LUFS, so there's usually real headroom to bring up.
Why do Suno vocals sound harsh?
Harshness commonly sits around 4-7 kHz. Try a narrow 2-3 dB dip there before reaching for compression or an exciter -- it's usually the actual cause rather than something a limiter can smooth over.