I built this service partly because I got tired of watching great Suno songs get killed by their own loudness. Here is the complete workflow as of 2026 — export settings, the numbers that matter when you upload to a distributor, and honest opinions on where mastering fits (and where it doesn't). Written by a solo developer who ships this product, not a content team: if something below is an opinion, I say so.
Step 1 — Export from Suno in the right format
Suno lets you download songs as MP3, and on paid plans also as high-quality WAV (plus video; stems/MIDI on the top tier). For mastering, use WAV when your plan allows it — an already-lossy-encoded source gives the master nothing to work with that a clean export would. If you are on free or capped access:
- Suno introduced download caps in late August 2026 (announced ~Aug 25): free accounts get 7 downloads total, Pro ($8/mo) 20/month, Premier ($24/mo) 60/month — per Variety's coverage of the announcement. That means every export should go to a file you will actually release, not another re-roll audition.
- When exporting stems (Premier), master the final stereo mix, not the individual stems — stem mastering is a different, more expensive discipline that this page (and this service) does not pretend to cover.
Practical tip from the r/SunoAI threads I read while building this: most "it sounds worse than in Suno" complaints are loudness and peak problems, not generation problems. The raw export often sits quieter or spikier than what streaming services expect — which is exactly the gap a master closes.
Step 2 — Know the two numbers your distributor cares about
Streaming platforms normalize playback to an integrated-loudness target, and they punish peaks that cross their true-peak ceiling:
| What | Target for a stream-ready master (2026) | Why it matters |
|---|---|---|
| Integrated loudness | ≈ −14 LUFS (the Spotify-family norm; some platforms sit slightly lower) | Files louder than the pack get turned down to match — you lose nothing by hitting target, and you gain headroom for encoders |
| True peak ceiling | ≤ −1 dBTP, −2 dBTP if your master is louder than −14 LUFS (Spotify's own guidance) | AAC/MP3 encoding can add ~1 dB of intersample peaks; without headroom that becomes audible clipping in the file the listener actually hears. See what true peak is and why sample-peak lies |
You do not need a $2,000 meter to check these — our free browser LUFS meter & normalizer computes integrated LUFS + true peak locally in your browser (nothing uploaded), and it is the fastest sanity check I know. If you only remember one page: what LUFS actually measures.
A useful rule of thumb for Suno output specifically: measure first, then decide. Some exports are already near −14 with peaks under ceiling — in that case you need tonal shaping and gentle limiting, not a loudness rescue. Others are 3–6 LU quieter than the pack or peaky at the top end; those benefit from a full master more than any genre tag would suggest.
Step 3 — Master (this is where choices fork)
Your realistic options in late 2026:
| Option | Cost (verified Aug 28, 2026) | When it's the right one |
|---|---|---|
| DistroKid's built-in Mixea mastering | $99/year for unlimited tracks; first mastered track free (official distrokid.com/mixea page). A separate optional "Loudness Normalization" upload extra auto-adjusts audio to Spotify-recommended −14 LUFS / −1 dBTP — and is not charged if your release already meets the target | You are all-in on DistroKid, release often, and want zero context-switching. Note it is a per-distributor feature: the master is tied to that upload flow |
| BandLab mastering | Free, unlimited (3 presets) | Quick and dirty; no reference targets, no loudness spec shown — fine for demos |
| Per-track web mastering (this service) | $5 one-time per variant's 24-bit WAV, 3 free processing passes/day, up to 3 variants per upload in parallel | You want a master aimed at a specific style (11 patterns, each with reference targets), you A/B the results before committing, or your output is AI-generated and you don't want an ecosystem deciding your terms — LANDR's pricing page now states monthly limits apply to high volumes of AI-generated audio, which makes this relevant beyond snark |
| Human indie engineer | Typically $50–150/track (higher for specialists) | The record genuinely matters and the mix needs editorial fixes mastering cannot invent |
Why "up to 3 variants per upload" deserves a line here: Suno gives you 2 candidate songs per generation; most people keep both if they're close. A human would master them twice at twice the price. Here, one pattern with up to three sub-style targets runs in a single queue pass and you pick — which is also how you keep two tracks from the same EP sounding like a set rather than strangers (match both to the same pattern).
Step 4 — Deliver: WAV first, metadata second
- Send your distributor the 24-bit WAV, not an MP3 re-upload. DistroKid's own help center frames loudness normalization as fixing files that are not already at target — the cleaner your input master, the less any pipeline touches it.
- If you use DistroKid's optional Loudness Normalization extra, know what it does (their words): "automatically adjust the level and headroom of your audio to Spotify's recommended settings: -14dB integrated LUFS with -1dB true peak maximum." A master that already sits there costs you nothing because the service skips it — but a spiky −8 LUFS file gets processed by their pipeline instead of one you auditioned.
- Keep the MP3 preview for sharing (it's free from any completed track here); keep the WAV as your archival delivery file.
A realistic budget example: 4-track EP from Suno, Premier plan
| Step | Cost |
|---|---|
| Suno generation (Premier $24/mo) — assume one month of it | ~$24 |
| Export 4 final songs as WAV (within the 60/month cap) | included |
| Mastering, per-track: 4 × $5 (WAV variants) + free MP3 previews | $20 |
| DistroKid Musician plan for distribution | ~$24.99/yr |
| Total to have a stream-ready EP | ~$70 one month, no recurring mastering subscription |
Compare that against a $15–39/month eMastered-style bundle you'd be paying for months between releases, or $36+ if the same four tracks went through LANDR's $10 one-off WAVs. The per-track math only loses when your monthly output crosses roughly 8–10 paid masters — beyond that a subscription legitimately wins, and I will tell you so rather than oversell (see our LANDR alternative page for the crossover analysis).
What mastering does NOT fix in Suno songs
Honesty section, because "AI mastering" marketing lies by omission:
- A broken vocal performance or an off-key hook stays broken. No chain rescues a melody you didn't like at generation time — regenerate instead.
- Structural problems (muddy 808s fighting the kick, a chorus that never opens up) are mix problems. If your export has them, mastering will polish around them, not remove them. Suno's stem tools + a DAW session is the real fix when you need it.
- Loudness wars within your own catalog still need discipline. Mastering to target doesn't stop you from uploading three tracks with wildly different tonal characters — that's why pattern-matching an EP (step 3) beats "loudest preset wins."
- Time-based effects left on a wrong grid stay off-grid. Suno occasionally renders delay/reverb tails that don't sit exactly on the song's tempo, and no amount of limiting will re-align them — check what you're getting first: read the actual tempo with the free BPM & key analyzer, then convert it to exact effect times in the BPM → delay & reverb time calculator before deciding whether a full master is even worth it.
Frequently Asked Questions
Is it legal / allowed to master AI-generated music and release it?
Releasing AI-generated music is a per-platform question (DistroKid, Spotify etc. have their own AI policies — check current terms), not a mastering question: our service has no separate restriction on generated audio, which is unusual among online masters in 2026. Your responsibility is the distributor's rules about disclosure and ownership, not your loudness meter.
Suno export sounds fine in my player but bad on Spotify — why?
Your player probably normalizes (or plays it hot). Streaming encoders are harsher: a master that clips after AAC conversion will crackle on phones specifically. True-peak headroom of at least 1 dB is the fix; measure your export in the free browser tool to see if you need it at all — details at /blog/true-peak.
Do I need a different master for Spotify vs Apple Music?
Not anymore. Both converge on roughly −14 LUFS integrated with a −1 dBTP ceiling, so one stream-ready master serves the major platforms. Club/EDM contexts that want hotter files are where you might keep a separate loud take — see what -9/-14/-16 LUFS presets mean.
How long does mastering take here?
Minutes per track in practice (queue + engine pass), which is the whole point of doing it between "Suno export" and "DistroKid upload." For comparison, DistroKid's Mixea is similar speed but locked to their ecosystem — see mastering before DistroKid for that decision.
Should I master every song or only the good ones?
Only what you release. The per-track model exists so that audition tracks cost $0 (free daily passes, free MP3s) and finished ones cost $5 each — there is no monthly fee paying for your rejects.