Is Your Suno Song Ready to Release? A Checklist
Published · updated · by Loopin
Before you submit a Suno export to a distributor, run through these five checks in order. Each one catches a specific, common problem that's easy to miss until it's already live.
1. Check integrated loudness first
Confirm your master sits close to −14 LUFS integrated. A raw Suno export is often much quieter, around −18 LUFS, and submitting it unmastered leaves it sounding thin next to properly mastered releases even after platform normalisation.
If you're significantly off that target either direction, go back and master before moving to the next check — everything after this assumes loudness is roughly right.
2. Confirm true peak has headroom
Check that true peak sits at or below −1 dBTP, not just that integrated loudness looks right. A file that clips during a distributor's format conversion, even if it played clean on your system, is a common and avoidable release-day surprise.
Most mastering tools display both numbers separately — check both, not just one.
3. Listen for mud and harshness specifically
Solo a section and listen for congestion in the 250–500 Hz range and harshness around 4–7 kHz — the two most common tonal issues in AI-generated exports. If either is present, address it before finalizing, since it's much easier to fix now than after distribution.
This check matters even if loudness already looks correct — a track can hit the right LUFS number and still have real tonal problems underneath.
4. Fold to mono and check stereo compatibility
Some AI exports come out unusually wide. Fold the track to mono and listen for anything — especially low end — that thins out or disappears. If it does, narrow the stereo image below roughly 200 Hz before finalizing.
This catches an issue that's invisible on headphones but very audible on a mono Bluetooth speaker, which is how a meaningful share of listeners will actually hear the track.
5. Confirm metadata matches across everything
Double-check artist name, track title and any featured artist credits are spelled identically across the file, the distributor submission form, and any social media you'll link from. Inconsistent metadata makes it harder for streaming platforms to group your catalogue under one artist profile.
This is the easiest check to skip and the most annoying to fix after the fact, since some corrections require another review cycle with the distributor.
Frequently asked questions
What's the most important thing to check before releasing a Suno song?
Integrated loudness first -- confirm it's close to -14 LUFS. Raw exports are often much quieter, around -18 LUFS, and everything else on the checklist assumes loudness is roughly correct before you check it.
Should I check mono compatibility before releasing an AI-generated track?
Yes. Some AI exports come out unusually wide in the stereo field, which can thin out on mono playback like a Bluetooth speaker. Fold to mono and check, especially the low end, before finalizing.
Why does metadata consistency matter for a Suno release?
Inconsistent artist name or title spelling across the file, distributor submission and social media makes it harder for streaming platforms to group your releases under one artist profile, and corrections after release often require another review cycle.