Suno's Download Limits Land 3 September: What Changes, and What to Do First

On 3 September 2026, Suno stops being a service you can freely export from and becomes one with a metered download counter. Free accounts get 7 downloads — not per month, but for the entire life of the account. Pro gets 20 a month. Premier gets 60.

We went through Suno's own announcement and FAQ rather than the secondhand coverage, and the numbers turn out to be the least interesting part of the story. Two details change how you should act, and most reporting carried neither.

The Limits, by Tier

Allowances reset on your billing date rather than the first of the calendar month, and unused downloads are gone rather than banked. If you hit the ceiling, Suno's FAQ confirms you will be able to purchase additional downloads — a detail almost nobody reported, and one that meaningfully softens the cap for an occasional heavy month.

The Retroactive Clause Everyone Missed

Here is the sentence that turns a policy announcement into a deadline, taken straight from Suno's own FAQ:

"Download limits apply to all music on Suno starting September 3, including songs created before that date."

A cap on future generation is a mild inconvenience. A cap on everything you have ever made is a different proposition entirely, and it is the second one Suno announced.

Work it through for a real library. Anyone generating regularly for a year or two has hundreds of tracks. Take a moderately active user with 400 songs sitting in Suno:

• On Free, they may export 7. Ever. And not commercially.
• On Pro at 20 a month, clearing the catalogue takes 20 months.
• On Premier at 60 a month, just under 7 months.
• Before 3 September, it takes an afternoon, because no counter is running.

That is the entire urgency compressed into four lines. The policy itself is defensible. But it converts an unlimited archive into a metered one, retroactively, with a few weeks of notice.

The Counting Rules Are Better Than You Think

The fine print barely got reported, and it materially changes how bad this is. All four of these are Suno's own wording:

• One song counts as one download, regardless of format. Pulling both the MP3 and the WAV is one download, not two.
• Re-downloading does not count again. Once a song is on your counter, pulling it again later is free. Lost a file? Re-download at no cost.
• All stems bundle into that single download. This is the big one — a full stem set does not multiply against your quota. For anyone finishing tracks in a DAW, that removes what would have been a crippling restriction.
• Failed or interrupted downloads do not count. A dropped connection costs you nothing.

Read together, this is a more carefully designed policy than the outrage suggests. It is aimed at catalogue volume, not at people working on individual tracks. Twenty distinct finished songs a month is a serious release schedule; twenty files would have been absurd. Suno picked the sane one.

The Pricing Maths Suno Didn't Advertise

Divide price by allowance and something falls out. At the reported $8 and $24 figures, Pro works out at $0.40 per download and Premier at $0.40 per download. Identical.

That is not how subscription tiers usually work. Higher tiers almost always offer a volume discount to reward commitment; Suno declined to give one. The unit price stays flat as you scale.

A flat unit price is precisely what you design when the goal is to make volume expensive in direct proportion to volume. Under the old model a streaming-farm operator paid a fixed fee and exported freely, so their per-track cost fell towards zero as they scaled. Now it is pinned at roughly 40 cents no matter how big they get — and against the fractions of a cent a fraudulent stream earns, that arithmetic stops working. Which is the point.

The unavoidable side effect is that legitimate high-volume producers pay the same 40 cents. Suno's sanctioned escape hatch is Studio, unlimited and included with Premier.

Who This Actually Hurts

The reaction has been broad and mostly imprecise. Sorted by who genuinely feels it:

• Streaming-farm operators — hit hardest, entirely by design. Generating thousands of tracks and botting the streams is exactly what the cap exists to kill. Legitimate target.
• Catalogue builders — hit hard, as collateral. Anyone building a large library for stock or production music now faces a ceiling of 720 a year on the top consumer tier. A real business model, run by people doing nothing wrong, constrained by a rule aimed at someone else.
• Free users with a back catalogue — worst in relative terms. Seven lifetime downloads against a library of hundreds, and no commercial rights regardless.
• Working producers releasing finished tracks — barely affected. Worth saying plainly, because the panic has been broad. Two to five polished songs a month sits comfortably inside 20.
• Hobbyists who never export — unaffected. Playback and sharing stay unlimited on every plan.

Why Suno Did It

Suno's stated reason is to make mass-export harder for bad actors and keep the platform used for "intentional music creation". Unusually for a corporate justification, the numbers support it.

Deezer has reported receiving around 90,000 fully AI-generated tracks per day — more than half its daily uploads — with a large majority of streams on those tracks judged fraudulent and filtered out of royalty payments. Spotify has removed tens of millions of spam-like uploads in a year. And the telling detail: fully AI-generated music accounts for only a low single-digit percentage of actual streams. The flood is enormous at upload and nearly invisible at listening.

That reframes the problem. Listeners are not being swamped. Royalty pools are being diluted by tracks nobody plays, uploaded purely to farm payouts. There is also legal pressure — the announcement followed closely on Suno's loss in GEMA v Suno at the Munich I Regional Court, with Universal and Sony actions ongoing. We covered the fallout in our piece on why HAVEN's "I Run" was removed.

What You Are Not Losing

Some of the reaction has been disproportionate, so it is worth being precise. Directly from Suno:

• Nothing is deleted. Everything you have made stays in your library.
• Playback and sharing stay unlimited on every plan, including free.
• Files you already downloaded remain yours, commercially if you pulled them on a paid plan.
• Covers and remixes continue. Existing songs can still seed new work on the platform.

This is a restriction on export, not on access, ownership or creation. The version circulating in places — that Suno is taking people's music away — is simply not accurate.

What to Do Before 3 September

Until the deadline there is no cap. Exporting your own catalogue right now uses no quota and breaks no rule. That is the single most useful fact here.

• Audit what you have. Most people have far more unexported material than they remember, and some of it is better than they recall.
• Export the keepers in the highest quality available. WAV over MP3. Re-generating is not the same thing — the model will not give you that take back.
• Pull stems for anything you might rework. Stems are the highest-value export because they are hardest to reconstruct later, and they cost nothing extra against the quota.
• Bulk export if your library is large. Several hundred tracks by hand is how this gets abandoned at song forty.
• Store it in two places you control. A drive and a cloud backup. Ordinary archival discipline; the deadline is a decent prompt to finally do it.
• Do not spin up extra accounts. The same announcement introduced tiered enforcement up to permanent bans. Risking the library you are trying to protect, to dodge a limit you can legitimately get ahead of this month, is a bad trade.

The Step After Exporting

Getting the files onto your drive solves the deadline. It does not solve what happens when you try to release them, and the two get conflated constantly.

Once a track leaves Suno, the thing that decides whether it earns anything is your distributor's AI screening, not Suno's download counter. That screening runs at the signal level — spectral artifacts, phase anomalies, embedded watermarks, C2PA metadata, noise-floor signatures — and it happens once, at upload, before a single listener hears the track. A flagged track does not come back with a warning; it does not go live.

That is the layer Undetectr is built for, and it is a genuinely different problem from bulk exporting. It strips those markers so the file clears intake and stays live. Two honest caveats worth stating: it does not change your composition, and it will not help with a rights dispute — if a track resembles an identifiable artist, no processing fixes that. We covered where that line falls in our ranking of AI music artifact removal tools.

Frequently Asked Questions

Our Verdict

Suno's download limits are a defensible policy with a real problem behind them. Ninety thousand AI tracks a day arriving at a single service, most of their streams judged fraudulent — that is an abuse pattern, and a flat per-export price is a sensible lever against it.

The fine print is more reasonable than the headline, too. One song is one download whatever the format, re-downloads are free, stems bundle, nothing is deleted, everything stays playable, and you can buy more if you need them. If you release a handful of finished tracks a month, you will barely notice this.

The genuine problem is the retroactive clause. Applying a cap to a back catalogue built under different rules, with a few weeks of notice, puts the cost on people who were never the target — and free-tier users with real libraries come off worst of all.

Which leaves exactly one action, and it expires. Until 3 September there is no counter. Export what you care about while that is still true, then worry about distribution screening after.

Figures in this article were checked against Suno's own downloads FAQ and its announcement post, with tier pricing as reported by Variety. Policies change — confirm current limits with Suno before making decisions about your plan.