Suno v5 and v5.5 Are Retired: What to Use in 2026

If you have gone looking for Suno v5.5 in the last few weeks and could not find it, it is not hidden behind a setting. Suno retired every model before v6 on 9 September 2026, which means the roughly 390 searches a month for v5.5 now land on a first page of tutorials for a model nobody can select — and that the apps still selling a "V5.5" tier are selling something else. For this update we read Suno's own announcement, four of its help-centre articles on models, downloads and ownership, and the published terms of the best-known third-party app advertising V5.5, and we quote each of them rather than paraphrasing.

Two things fall out of that reading that are not on the first page of results for this query. The retirement is cleaner than the panic suggested — your library is genuinely untouched — and the real constraint on an old catalogue is the download allowance, not the model. The third-party apps are a separate problem with a separate answer, and it is a licensing answer rather than a detective story. Our methodology page sets out how we treat claims we can check against a primary source versus claims we cannot.

Is Suno v5.5 still available in 2026?

No. The sentence everything else follows from is in Suno's v6 announcement, dated 9 September 2026:

"As v6 rolls out, we will retire our previous models and move Suno entirely onto the v6 generation."

That was a forward-looking statement at the time, and a month later the v6 FAQ states it as finished fact: "All models prior to v6 have been retired, but your songs will still be in your library and remain unchanged." There is no legacy toggle, no archive tier and no paid route back.

What you can select now is three models, and the plan gating matters if you are deciding whether to resubscribe:

• v6 — Suno's most advanced model, available to Pro and Premier subscribers.
• v6-wild — "built for experimentation", also Pro and Premier.
• v6-mini — faster and lighter, "available for all users", which is what brings generation to the Free plan.

Suno's own definition of retirement is narrow and worth holding on to, because most of the alarm around this was about something that did not happen: "Retiring a model means you can't generate new songs with it. It doesn't affect anything you've already made." The loss is prospective. What each Suno tier includes is a separate decision from what happens to your archive, and the two got tangled together in September.

Every Suno model and its status

Here is the whole lineage in one place, with what you can and cannot do with each today. Release dates are Suno's; the status column is from Suno's v6 FAQ and its upcoming-changes FAQ.

One row deserves expanding, because it was the open question on this page until the v6 FAQ answered it. Custom models were tuned versions of v5.5, so retiring v5.5 might reasonably have taken them with it. It did not: "Any custom models you've created will automatically get upgraded so that v6 powers your model moving forward", and "songs created with your old v5.5 custom model will still be available, playable and unaffected by the v6 update."

Voices — the feature that captures your own singing voice — is not mentioned in that FAQ at all. That is silence, not a finding in either direction. If a Voice is load-bearing in how you work, it is a reason to keep your own recordings, not a reason to assume the worst.

Why Suno retired v5 and v5.5

Suno has not published a maintenance rationale, and the commercial one is not hard to trace. The v6 models were, in Suno's words, "developed with our industry partners, including Warner Music Group, BMG and Believe".

That partnership has a date, and it is earlier than most of the discussion assumes. Warner Music Group's settlement and partnership with Suno was announced on 25 November 2025, not in the autumn of 2026, and Suno's post that day said the deal "enables us to build a new generation of Suno models using high-quality licensed music". The same post is where the download changes came from: "a paid Suno account will be required to download songs from the product, with each paid tier enabling a specific number of downloads each month."

So the retirement, the download caps and the licensed models are one programme announced across ten months, not three unrelated shocks in September. It is also not a settled peace — two of the three majors went back to court against Suno days after v6 shipped. Our sister site has the chronology in why the models changed; this site's policy tracker keeps the dated sequence.

Read against that, a legacy v5.5 option was never likely. A model generation built with licensed catalogue is a different legal object from the models that preceded it, and keeping the predecessors selectable would have undercut the point of building it.

Suno v5.5 vs v6: what changed in the audio

Start with an honest limitation, because it governs everything written about this comparison from now on: v5.5 cannot be generated any more, so nobody can run a fresh A/B test. Any page published after 9 September claiming new listening comparisons is working from renders made before that date. So are we, and we are saying so.

The most rigorous measurement that exists was published in March 2026 by masterforge, which generated the same brief on v5 and v5.5 across five genres — piano ballad, indie rock, thrash metal, hard techno and dark hip-hop — with identical prompts and settings, then computed fifteen spectral metrics per pair with a mid-side decomposition. Its finding is more interesting than the marketing on either side: v5.5 was not uniformly cleaner. On the high-frequency shimmer artifact, two tracks improved and three got worse, and the model appeared to adapt its emphasis by genre rather than raising quality across the board.

The reception is its own story, told in our v6 review: better numbers, angrier users. One defect worth knowing before you plan an album is that v6's quality does not hold evenly across a track's length — our sister site documents the v6 defect that shows up after two minutes. Neither is a reason to chase v5.5. Both are reasons to audition v6-mini before paying for Pro.

What happens to the songs you already made on v5.5

Playback, sharing, remastering and covering all survive, and Suno has been consistent about it in two separate FAQs. The thing that does not survive untouched is getting the files out, and that is where people actually get hurt.

Download limits are not scoped to new work. Suno's wording is explicit: "Download limits apply to all music on Suno starting September 3, including songs created before that date." A back catalogue of four hundred v5.5 tracks is therefore governed by the same monthly allowance as a brand-new account.

Two details soften it: re-downloading a song you have already taken does not spend another download, and a song's stems come with that song rather than counting separately. Suno Studio was carved out of the caps from the start — the Warner post promised it would "remain untouched, including unlimited download functionality". Full mechanics in the download caps guide.

The honest framing for an old v5.5 catalogue, then: it is safe where it sits and expensive to move, and the sensible order is to export the tracks you would actually release first rather than attempting the archive. What happens after export is the part nobody has solved for most people — getting distributed is largely a solved problem now and being heard is not, which is why a storefront you own and a route into paid sync placements for TV, film, games and ads is worth more than another upload. played.fm exists for that half: pitch finished tracks for sync, and sell direct to listeners while keeping what you make.

The apps still advertising "V5.5" — how to evaluate them

This is the question that prompted this update. A widely-read r/SunoAI thread in late September found an app, Somio, offering models labelled "V3.5, V4, V4.5, V4.5+, V5, V5.5" — Suno's exact pre-v6 naming — and noted that its Android package identifier is com.aimusic.somio.suno. The poster's closing question was the honest one: are those Suno's old models, or a coincidence?

We cannot answer it, and neither can anyone else from outside the companies involved. What you can do is check what is published, which turns out to be more informative than the speculation. Here are the five tests, applied to Somio as published on 9 October 2026.

One claim needs separating out. That Somio is "built on Suno tech" is a real published statement, but it comes from somio.net, a site that says on its own page that it is "not the official Somio site". Somio's own site and store listing say Lyria 3. A package identifier is suggestive and is not evidence of what runs server-side.

So: a real product from a named company with a published licence, version naming that matches Suno's and is unexplained, and an engine question nobody outside can settle. If you want it settled, ask the vendor in writing before you release commercially — none of the five tests above requires installing anything.

If you are releasing: whose licence do you hold

This is where the choice stops being about audio and starts costing money, and it is the part no page on this query covers.

A track generated in a third-party app carries that app's licence, not Suno's. They are not equivalent documents.

That last row is the one to read twice. Somio's commercial licence agreement, effective 27 May 2026, states that "under no circumstances shall Commercial Use include registering, submitting, or delivering any Generated Content to any automated audio fingerprinting database, copyright identification system, or digital rights management tracking network (including, but not limited to, YouTube Content ID, Facebook Rights Manager, TikTok Music Content ID, and Shazam)". The stated penalty is "immediate, automatic, and retroactive revocation" of the commercial licence for that track, with the platform reserving the right to terminate the account without refund.

The stated reason is reasonable — generative models can produce acoustically similar output for different users, so one person fingerprinting a track generates false claims against everyone else's. The consequence is not: Content ID enrolment is a checkbox most distributors offer on YouTube monetisation. Tick it on a Somio track and you are in breach of the licence you are relying on. Suno imposes no equivalent restriction.

Suno's own documents are not perfectly consistent either, and this is a real conflict in primary sources rather than a reading error: its ownership article settles commercial rights by whether you were subscribed when the song was created, while its changes FAQ settles them by whether you downloaded it as a paying subscriber. For an undownloaded paid-plan back catalogue those are different answers, and we have no reconciliation to report. If that describes you, is Suno safe to use sorts the risks worth acting on from the rest.

What none of this changes about distributor screening

Model version does not determine whether a track clears a distributor's automated checks, and the belief that it does costs people real time.

Distributor classifiers read generation artifacts — spectral fingerprints, phase relationships, micro-timing distributions — at ingestion. Those are properties of how audio was synthesised, not of how good it sounds. A v6 render sounds better than a v5.5 render by most accounts and is not thereby less identifiable as machine-made. People rejected on a v4 track who assumed it was a quality problem regenerate on the newest model and fail the same screen.

It is also worth being precise about what that screening is, because the forums are not. Most distributors accept AI music openly — DistroKid, RouteNote, UnitedMasters, LANDR, Amuse and Symphonic among them, generally with a disclosure step at upload. What people actually report is individual uploads getting flagged and rejected by automated screening, which is a different problem from a ban and has a different fix. Nothing processed on your side changes how a platform labels a track as AI, either; that is disclosure-driven and provider-side.

Cleaning the artifact layer is a step you perform on the exported file, after generation and before upload. Undetectr is the tool this site reviews for that job, and our artifact removal ranking covers how the options compare. Whichever model produced the file — retired or current, Suno's or somebody else's — that step is the same.