Suno's custom models go shared. Who owns a model trained on your catalogue?

Suno spent the first half of October making its song generator behave more like a shared studio. On 15 Oct it added Shareable Workspaces and shareable custom models. A week earlier, on 8 Oct, Studio picked up tighter timing, clip stretching and curved fades. None of it is flashy. Together, it moves Suno from "type a prompt, get a song" towards several people working on the same material. That raises a question Suno's paperwork doesn't answer: when a model is tuned on one artist's catalogue and then handed to collaborators, who owns what?

What did Suno actually ship?

The collaboration release note has two parts. Workspaces let a team share a library of songs, and Suno says only the people you invite can get in. They're available on the Pro and Premier plans. Custom models can now be shared with collaborators, and the note adds "2x the inputs". It doesn't say what the old limit was, so we can't tell you what that doubles. Sharing custom models is Premier-only.

The Studio update is about editing:

• Downbeat detection. Suno says it now finds beat one more reliably in new clips, so clips and takes line up better on the timeline. It also says non-rhythmic material, such as an a cappella vocal, needs less manual alignment.
• Clip stretching. Shift-click and drag to time-stretch a clip, so samples and found sounds fit the project tempo.
• Fade curves. Fades used to be linear only. Dragging a node on the fade now gives exponential or logarithmic curves.
• Pop-out windows. The wavetable synth, the musical-typing keyboard and expanded plug-in views can float on a second monitor.

Studio is part of the Premier plan. Any DAW user will recognise these features. That's the point: Suno's browser DAW is still filling in basics. As we covered in September, it still doesn't load your own VST or AU plugins.

Are custom models new?

No, and the framing matters. Custom models arrived in March with v5.5. You upload at least six tracks from your catalogue to tune a personal version of the model. Suno's help article says Pro and Premier users can build up to three, and that you "must own the rights to all of the songs you upload". It also says custom models "are private and cannot be shared amongst users". The Custom Models page says that nobody but you can access them.

When we checked on 23 Oct, both pages still said that, even though the 15 Oct release now lets Premier users share models. That's a small lag in the docs. It also shows that the promise of privacy was a product setting Suno could change, not a commitment.

The base under your model has changed too. When v6 launched, Suno retired every earlier model. Its v6 FAQ says existing custom models were "automatically" upgraded so that v6 powers them. Songs already made with a v5.5 custom model stay playable. But the tool you tuned on your own music now sits on a base model you didn't choose. It didn't exist when you uploaded, and Suno trained it partly on what its community made.

What do Suno's terms say about a shared model?

Very little. Suno's Terms of Service (effective 3 Sep 2026) don't mention custom models or workspaces. They say you keep ownership of what you submit. They also say you give Suno a worldwide, sublicensable, "perpetual, irrevocable" licence to your content, and that licence covers improving its AI and machine-learning models. If you upload, you also promise that nobody else's permission or payment is needed for uses such as training. Suno's privacy notice says it uses content "to train and enhance the models that power our Services". It describes no way to opt out of training.

The terms say nothing about who owns a tuned model. They say the technology behind the service belongs to Suno and its licensors. On songs you make, Pro and Premier subscribers get Suno's rights in the output, but Suno makes no promise that any copyright exists in it. The only rule on co-ownership covers remixes: a remix is a joint work, owned "jointly and equally" by you and the remixer, and only for personal, non-commercial use. Nothing covers someone generating a track with a model built from your catalogue.

At v6's launch, Suno told Music Business Worldwide that the user data behind the model was preference data, not uploaded audio. That's the only public statement we found on uploads. The terms themselves would allow training on them. Suno now admits in court that v6 learned from users' "creations".

What we think

Shared custom models make Suno's ownership gaps a problem for artists' collaborators, not just for Suno. A private model tuned on your own songs was mostly a question between you and Suno. A shared one creates a third party: the collaborator who generates a track in your sound. Our reading of the terms is that the collaborator's output is theirs on a paid plan, as far as anyone owns it. You get no credit, no split and no note of which model made it. If a producer shares a model built on an artist's catalogue with a topliner, the artist's catalogue shaped the result and nothing on Suno records that. Before you share a model, agree splits and credits in writing, outside Suno.

The rights warranty also gets harder with a team. "You must own the rights to all of the songs you upload" sounds simple for a solo artist. A band's catalogue usually has co-writers, a publisher and often a label. One member uploading it to a shared model, and agreeing to a perpetual training licence on everyone's behalf, is exactly the kind of decision bands fall out over. We'd treat an upload as a licensing decision that needs every rights holder to agree.

The Studio work is real, but it doesn't change the deal. Downbeat detection, stretching and fade curves make Studio a better editor. Those tools make Suno a place you stay. They don't make it a place you control. Some tools take a different approach to making the track: Veena, for example, describes itself as an AI co-producer that builds a track with you layer by layer.

What Suno should publish is short: who owns a custom model, whether uploads used for custom models ever train the base model, and what a collaborator's output owes the person whose catalogue tuned it. Until then, treat a shared custom model as lending your sound to someone, on terms neither of you wrote.