top of page

Suno Copyright Lawsuit Targets Its Licensed v6 Models

Sep 28
13 min read

Suno faces a second copyright lawsuit despite launching v6 with licensed industry partners only nine days earlier. Universal Music Group and Sony Music Entertainment filed the complaint on September 18, 2026.

The Suno copyright lawsuit alleges that licensing new training material did not erase the influence of earlier, disputed recordings. The labels claim Suno carried that influence into v6 through generated songs, user preference data, and model-development methods.

Suno disputes those allegations and calls them flawed on both the facts and the law. Its defense matters far beyond one Cambridge startup. The case tests whether rebuilding an AI model creates a clean legal boundary from its predecessors.

That question divides a music business already pursuing two paths at once. Warner Music Group, BMG, and Believe helped Suno develop v6, while Universal and Sony returned to court.

The conflict is therefore larger than labels against AI. It is a fight over whether licensed models can inherit legal exposure from systems built before licensing agreements existed.

What the New Suno Copyright Lawsuit Alleges

Universal and Sony are challenging the lineage of Suno v6, not merely the recordings placed directly inside its newest training dataset.

Twelve record companies affiliated with Universal and Sony filed the federal complaint in Massachusetts. The public court docket identifies Suno and unnamed defendants as the targets.

The plaintiffs assert rights in 60,202 sound recordings named in the action. That scale makes the new filing considerably broader than a dispute over several recognizable outputs.

The complaint followed an earlier case filed against Suno in June 2024. Universal, Sony, and Warner participated in that first action, alleging unauthorized copying during model training.

Suno acknowledged in its response to the earlier case that its neural networks learned from recordings available online. However, it argued that this training constituted fair use under U.S. copyright law.

The second case arrives after the relationships between Suno and those original plaintiffs diverged. Warner settled with Suno and became a business partner, while Universal and Sony continued litigating.

Universal and Sony now allege that Suno used stream ripping to acquire recordings from YouTube. Stream ripping means extracting downloadable audio from an online stream, often outside the service’s intended playback process.

According to Bloomberg Law, the complaint says that process circumvented technological protections. Suno has not conceded that allegation.

The labels also target how Suno reportedly developed v6. Their theory reaches beyond direct ingestion of Universal or Sony recordings into the final model.

Suno says v6 was trained from scratch using licensed partner material and other authorized inputs. The plaintiffs argue that starting new model weights does not necessarily eliminate knowledge derived from older models.

One disputed path involves synthetic data, meaning songs generated by a previous AI model and reused as training material. If older models reflected protected recordings, plaintiffs argue that their outputs could carry some of that influence forward.

Another path involves preference data. Suno generates alternative versions of a song, then observes which version a user selects or continues editing.

Those choices can become signals about which musical structures, sounds, or arrangements users prefer. The lawsuit alleges that such signals originated partly from outputs created by the disputed earlier systems.

A third issue is knowledge distillation. This method transfers capabilities from one model into another by using the older system’s outputs or behavior as teaching material.

The labels describe v6 as the product of the same allegedly unlawful foundation. Their claim does not become true simply because the complaint uses a vivid metaphor.

The court will need evidence showing what data, outputs, and development processes actually entered v6. It must then decide whether those connections amount to legally significant copying.

That is what changed with this filing. The argument now concerns AI model ancestry, rather than only a static list of training files.

Suno v6 Was Supposed to Mark a Clean Break

Suno presented v6 as the beginning of a licensed operating model, but the lawsuit challenges whether that transition was technically and legally complete.

Suno launched v6 on September 9, 2026, with Warner Music Group, BMG, and Believe named as industry partners. The company called the release a new chapter for music creation.

The company’s v6 announcement described three models aimed at different uses. Its flagship model emphasized control, while v6-wild focused on experimentation and v6-mini offered broader access.

Suno also introduced editing tools that can change individual parts of a generated song. Users can combine song elements or provide text, images, video, and audio as creative references.

These capabilities make model provenance more consequential. A system that edits, extends, and combines material can sit closer to professional production workflows than a novelty song generator.

Suno said the new family was developed with its music-industry partners. Reporting around the release said the company planned to retire its earlier models.

That retirement served two purposes. It supported Suno’s claim that its future products would operate within licensed relationships, and it answered pressure created by ongoing litigation.

The shift followed Warner’s November 2025 agreement with Suno. Their deal contemplated licensed models and new artist-controlled experiences, alongside the retirement of earlier technology.

BMG later reached an agreement with the startup. Believe, which owns the TuneCore distribution platform, also participated in the v6 development program.

Suno says partner agreements include revenue sharing with rights holders. However, the financial terms and detailed allocation methods have not been publicly disclosed.

Warner CEO Robert Kyncl framed the arrangement as a source of creation-based revenue. That would pay participating artists and songwriters for authorized AI creation, not only traditional listening.

The model differs from the standard streaming economy. Streaming rewards consumption after a recording exists, while creation-based licensing can compensate rights holders when users generate new material.

Suno says more than 100 million people have used its platform. That company-supplied figure helps explain why labels see both risk and opportunity in its technology.

A platform with that reach can become a new licensing channel. It can also multiply unauthorized imitations or confusingly similar recordings if its controls fail.

The new Suno copyright lawsuit attacks the boundary between those two eras. Universal and Sony argue that v6 cannot become clean merely because its direct catalog partners changed.

Suno’s position rests on a narrower account of the rebuild. If v6 began with new weights and authorized material, the company argues, allegations against earlier models should not automatically transfer.

Those accounts are not mutually exclusive at the technical level. A model can be trained from scratch while its development process still uses outputs or evaluations influenced by earlier systems.

The legal question is even less settled. Copyright law does not offer a simple rule for measuring inherited influence across successive generative models.

A conventional software rewrite can avoid copying earlier code. Machine-learning systems are harder to compare because behavior can transfer through generated examples, rankings, and teacher-student training.

Therefore, “trained from scratch” is an important factual statement, but it is not a complete legal answer. The surrounding data pipeline matters just as much as the final training run.

Licensed AI Music Now Has Competing Rulebooks

Warner’s partnership and the Universal-Sony lawsuit reveal two competing approaches to the same technology: negotiated access and continued enforcement.

Warner chose to settle its claims and help shape Suno’s next model family. Universal and Sony chose to test Suno’s new architecture in court.

This split does not mean Warner supports every past Suno practice. A settlement can resolve disputed claims without deciding which side would have prevailed at trial.

It also does not mean Universal and Sony reject licensed AI music. Both companies have explored partnerships and rights-management systems involving generative technology.

The disagreement concerns leverage and acceptable remediation. Warner accepted a negotiated transition, while Universal and Sony are demanding accountability for alleged copying that preceded such deals.

Suno’s rival Udio offers a useful comparison. Udio reached agreements with Universal and Warner in 2025 after facing similar copyright allegations.

Those deals envisioned a licensed creation service and changed how users could access or export generated material. The transition showed that litigation can lead to commercial integration.

Yet licensing one service does not establish an industry-wide technical standard. Each agreement can define different catalogs, artist controls, revenue terms, and model restrictions.

BMG and Believe also do not represent every right attached to every song. A single recording can involve a label, publisher, songwriter, performer, producer, and collecting society.

That layered ownership makes AI music licensing unusually complex. Permission for a sound recording does not automatically include the underlying musical composition.

Artist identity creates another layer. A model might avoid copying a recording while still generating a voice, persona, or style that listeners associate with a specific performer.

Suno says it blocks direct prompts requesting a known artist or song. Such filters can reduce obvious imitation, but they cannot settle disputes about the model’s underlying development.

The technology also creates enforcement problems after generation. Users can distribute AI songs through services that were designed for human artists and conventional recordings.

Streaming platforms then need reliable information about origin, ownership, and authorization. Without it, an AI-generated upload can compete for attention and royalties before anyone resolves its provenance.

The industry is responding with labels, detection systems, and distribution policies. However, detection remains imperfect, and metadata can disappear when files move between services.

Suno has discussed watermarking generated audio. A watermark is a machine-readable signal intended to identify content as AI-generated, even when ordinary listeners cannot detect it.

Watermarking helps with disclosure, but it does not determine whether training was lawful. It also does not prove that every contributor received consent or compensation.

The licensing path nevertheless has practical advantages. It creates contracts, access controls, payment channels, and defined processes for participating artists.

Litigation offers a different form of clarity. A court can establish whether certain training or transfer practices require permission, even when companies cannot reach an agreement.

The two approaches will continue in parallel. Suno is simultaneously a partner to some music companies and a defendant facing others.

That dual status is the central reversal in this story. The same v6 release promoted as evidence of cooperation immediately became the subject of another major copyright case.

The Case Turns on Model Lineage, Not Marketing Language

The decisive evidence will come from Suno’s development records, because neither “licensed” nor “poisoned” explains the complete model lineage.

The plaintiffs must support their allegations with evidence linking protected recordings to legally relevant acts by Suno. A large catalog list alone does not explain every stage of model development.

Suno will need to show how it separated v6 from earlier systems. That likely includes dataset records, training procedures, generated examples, evaluation criteria, and internal access controls.

Model lineage describes how data, code, outputs, evaluations, and human decisions connect one system generation to another. It is becoming the AI equivalent of a manufacturing supply chain.

For enterprise buyers, lineage answers basic questions. They need to know what entered a model, who authorized it, and which earlier systems influenced the resulting product.

The labels’ synthetic-data argument illustrates the difficulty. Training on AI-generated songs can reduce reliance on directly collected recordings, but it introduces questions about those songs’ origins.

Synthetic data is not automatically infringing. It is also not automatically free from claims connected to the model that produced it.

The relevant analysis depends on what each generated example contains. It also depends on how Suno selected that example and what information the next model learned from it.

Preference data presents a similar problem. A user choosing one generated track over another creates a behavioral signal, not a copy of a conventional recording.

However, the plaintiffs can argue that the signal rewarded outputs containing qualities learned from their catalogs. Suno can answer that musical preferences and abstract qualities are not protected expression.

Knowledge distillation adds another technical layer. A student model can learn to reproduce a teacher model’s general behavior without receiving the teacher’s original training files.

Courts will need to distinguish transferable capabilities from protectable expression. Copyright generally protects original expression, not broad ideas, methods, genres, or stylistic conventions.

Music makes that distinction difficult. Melody, lyrics, and particular recorded performances can be protected, while rhythm patterns, instrumentation choices, and genre traits often receive narrower protection.

A system can therefore sound highly familiar without reproducing a legally protected portion. It can also conceal meaningful copying inside outputs that differ superficially.

Technical testing will matter. Experts may compare outputs, inspect training artifacts, evaluate memorization, and trace how specific examples affected model behavior.

Discovery will matter even more. The parties can request internal documents and records that public product announcements do not reveal.

The first lawsuit already created disputes about timing and amendments. In August 2026, the court denied an attempt to add certain newer allegations to that older proceeding.

The judge indicated that a separate claim could be filed and treated as related. The plaintiffs then opened the second case in the same federal district.

That procedural history weakens any assumption that the new action alone proves newly discovered misconduct. Part of the second filing reflects how the first case was managed.

Suno’s description of v6 also requires scrutiny. A partnership announcement verifies that partners exist, but it does not disclose the full composition of a training corpus.

Likewise, the phrase “trained from scratch” describes one aspect of development. It does not answer whether old outputs, preference signals, or teacher models informed the process.

Universal and Sony’s claims remain allegations until tested. Their theory must still survive legal challenges and factual examination.

Suno’s denials also remain company statements. The startup has not publicly released enough technical documentation to let outsiders independently reconstruct v6’s lineage.

Readers should resist treating either side’s slogan as a conclusion. The evidence will be found in the pipeline connecting recordings, models, generated songs, and user feedback.

Why Developers and AI Buyers Should Care

This dispute can influence how every generative AI company documents a “clean” model rebuild after licensing problems or data-policy changes.

AI companies routinely replace models. They may change suppliers, remove disputed datasets, introduce licensed material, or retrain after customers raise privacy concerns.

The Suno copyright lawsuit asks how much separation such a replacement needs. That question applies to systems generating text, images, video, code, and voices.

A company may delete disputed files before its next training run. Yet it might preserve synthetic examples, evaluation sets, rankings, embeddings, or outputs produced by an earlier model.

Each preserved artifact can carry useful knowledge forward. It can also preserve legal uncertainty if its relationship to the original material remains unresolved.

This creates a documentation challenge. Teams need records covering more than the final dataset manifest.

They should track which models produced synthetic examples. They should also record which systems generated labels, rankings, summaries, or preference signals used during later training.

Model cards alone will not provide enough detail. Those public summaries usually describe capabilities and limitations, while omitting sensitive dataset and development information.

Internal governance must therefore connect source permissions with technical lineage. A license should identify which content, uses, territories, model versions, and downstream products it covers.

The same principle applies to vendor due diligence. An enterprise purchasing generative AI cannot rely only on a vendor saying that its newest model uses licensed data.

Buyers should ask whether earlier models supplied synthetic data or evaluation material. They should also ask how the vendor handles claims involving outputs from retired systems.

Indemnification terms deserve close attention. A provider’s willingness to defend customers can reveal how confidently it views its provenance controls.

However, contractual protection does not eliminate operational risk. A disputed model can still face restrictions, product changes, or reputational damage during litigation.

Developers building on music models face an additional concern. Generated material can move into advertisements, games, podcasts, social videos, and commercial recordings.

A user may assume that a downloadable file is cleared for every purpose. The platform’s terms might impose narrower rights or place responsibility on the user.

Content teams should retain generation records, prompts, source inputs, model versions, and license terms. Those records can help answer provenance questions later.

Organizations also need a clear distinction between model authorization and output clearance. A properly licensed training corpus does not guarantee that every output avoids third-party rights.

The reverse is also true. A disputed training method does not make every generated song infringing.

These distinctions matter because legal exposure often depends on a specific use. A private experiment presents different risks from a commercial release that imitates a recognizable artist.

Procurement teams should avoid demanding impossible certainty. The law remains unsettled, and vendors cannot promise that no claim will ever arise.

They can demand process evidence. Useful evidence includes catalog permissions, retention rules, lineage logs, output safeguards, and procedures for rights-holder complaints.

Suno’s transition also shows why deleting older model access can become part of risk management. Retirement limits future generation, but it does not resolve past development questions.

For knowledge workers, the lesson is broader than music. Generated content should remain connected to its sources, model version, permissions, and intended use.

That information becomes harder to reconstruct after files move between tools. Maintaining a searchable AI knowledge base can preserve the context behind generated assets and approval decisions.

The issue is not paperwork for its own sake. It is the ability to explain how a commercial output was created when a customer, partner, or rights holder asks.

What Comes Next for Suno v6

Three developments will show whether Suno’s licensed-model strategy creates a defensible boundary or only a new stage of the same dispute.

The first signal is Suno’s formal response to the complaint. Public statements have called the claims fundamentally flawed, but court filings require detailed legal positions.

Suno can challenge whether the plaintiffs have adequately alleged copying by v6. It can also dispute the stream-ripping claim, the transfer theories, or the requested remedies.

A motion to dismiss would test the legal sufficiency of those allegations. It would not resolve factual disputes about Suno’s actual training process.

If the case proceeds into discovery, the second signal will be the scope of model-lineage evidence. That includes training records, generated datasets, preference systems, and communications about the rebuild.

Broad discovery would increase pressure on Suno to substantiate its clean-break narrative. Narrow discovery could limit the labels’ ability to trace alleged influence across model generations.

Protective orders will probably keep much of that material confidential. Even so, expert reports and judicial decisions can reveal which forms of evidence the court considers important.

The third signal is how Suno’s partners and users respond. Warner, BMG, and Believe have commercial reasons to support the licensed system they helped develop.

Their continued participation would strengthen the case that negotiated AI music has a viable business model. A retreat or significant restriction would weaken that argument.

Artist participation will also matter. Suno and its partners have described future opt-in experiences that let artists authorize uses and share revenue.

The quality of those consent mechanisms remains crucial. Artists need understandable choices, clear payment rules, and control over voices or identities associated with them.

Users provide another market test. Some creators criticized the forced transition to v6 and said the new outputs sounded less distinctive than earlier versions.

Those reactions are anecdotal, not a reliable measure of overall performance. They still highlight the product tradeoff created by a licensing transition.

A narrower authorized catalog may reduce legal risk while changing the model’s range. Better controls can also improve professional utility, even if some users prefer older behavior.

Suno must therefore satisfy courts, partners, artists, and creators at the same time. Success with one group does not guarantee acceptance from the others.

The broader industry will watch the case for a reusable legal standard. A ruling on synthetic data or knowledge distillation could affect many model developers.

A settlement would provide less public guidance. It could still produce new licensing terms, technical restrictions, or revenue arrangements that competitors follow.

The original 2024 litigation also remains important. Its treatment of fair use and training copies can shape the foundation beneath the newer dispute.

Meanwhile, other lawsuits expose Suno to claims from publishers, performers, and collecting organizations. These parties control rights that label agreements may not resolve.

That means the second Suno copyright lawsuit is not simply a replay. It targets the proposed solution to the earlier conflict.

Suno says licensed collaboration offers a path for AI and the music business to grow together. Universal and Sony argue that the path still runs through disputed intellectual property.

The next one to three months should reveal Suno’s formal defense, the court’s initial case schedule, and whether its partners alter their commitments.

Readers should watch those concrete events rather than declarations about whether AI music has become ethical or legitimate. Neither label fits every model, agreement, artist, or output.

The durable question is more specific: Can Suno document a development chain that separates v6 from the conduct alleged against its predecessors?

If it can, licensed model rebuilding gains a stronger template. If it cannot, AI companies will need deeper technical separation before calling a new system clean.

Give every agent the context to do better work

Connect your agents to the knowledge, decisions, and history already organized in remio.

remio currently supports Windows 10+ (x64) and Macs with Apple silicon.

Your AI Partner at Work
Get more done with remio

Plan. Create. Deliver.
All in one place.

bottom of page