AI Music Copyright: Who Owns an AI Song, and the Two Rights That Decide What You Can Sell
Almost every article about AI music copyright answers the wrong question. It asks whether you own the track, concludes that you probably do not, and stops there — as if ownership were the thing standing between you and getting paid. It is not. The right to sell an AI-generated song and the right to own it are two different rights, granted by two different sources, and in 2026 one of them is settled law while the other is still being fought over in three countries. This page separates them, and shows what each one actually costs you.
- The short version: a wholly AI-generated track carries no copyright in the United States, and that does not stop you selling it. The right to release comes from your generator's licence; the right to own comes from copyright law. Conflating the two is the single most common error in AI music coverage.
- The US human-authorship question is closed at the top of the system. The Supreme Court denied certiorari in Thaler v. Perlmutter on 2 March 2026 (No. 25-449), leaving the D.C. Circuit's human-authorship requirement standing.
- What you lose without copyright is exclusivity, not revenue. You cannot stop someone re-uploading your track, which makes enforcement-dependent income weak and delivery-dependent income — direct sales, sync placements — unaffected.
- No action has ever named a user. Across the Munich judgment, the SOCAN claim, the indie-artist class action and the wave of publisher suits filed in October 2026, every named defendant is a company.
- Prompts alone do not create authorship. The Copyright Office's January 2025 report is explicit that prompt selection, however detailed, does not by itself yield a copyrightable work. Human lyrics, arrangement and substantial editing can.
Almost every article about AI music copyright answers the wrong question.
It asks whether you own the track, concludes that you probably do not, and stops — leaving the reader with the impression that ownership is the obstacle between them and getting paid. It is not the obstacle. It is not even in the same category as the obstacle.
There are two separate rights in play. The right to sell an AI-generated song comes from a contract: the terms of service of whichever generator produced it. The right to own it comes from copyright law. They are granted by different sources, they fail in different ways, and you can hold either one without the other. In 2026 the ownership question has been settled at the top of the US system, while the litigation everyone worries about turns out to be aimed somewhere other than the people reading this.
This page separates the two rights, states what each is worth in practice, and gets to the part that actually decides whether you see money.
The right to sell comes from a contract, not from copyright
When Suno or Udio grants a paid subscriber commercial use, that grant is contractual. It says: we will not come after you for releasing this. It does not say, and cannot say, that copyright law recognises you as the author of the output. No private company can grant that, because authorship is not theirs to give.
This matters because the two rights fail differently. A licence fails when the terms change — and they have changed. Udio disabled downloads after settling with Universal in October 2025, pivoting to a walled garden where tracks live on the platform rather than on your drive. Suno's November 2025 settlement with Warner commits it to launching new licensed models during 2026, deprecating the current ones, and restricting downloads to paid accounts.
Read that list again as a seller rather than as a hobbyist. Everything on it changes what you are permitted to do with files you already made, decided by a company under litigation pressure, with no notice period you negotiated. That is the real fragility in an AI music business, and it has nothing to do with copyright. It is also the argument for keeping the catalogue somewhere the terms are not rewritten around you, such as a storefront whose terms you actually control. What your distributor's own contract takes from you in the meantime is a separate question, and the terms are not uniform.
Copyright fails differently. It does not get revoked by a settlement. It simply never attached in the first place.
Who owns an AI-generated song in the United States
This question is now closed, and it closed recently.
On 2 March 2026 the Supreme Court denied certiorari in Thaler v. Perlmutter (No. 25-449), leaving standing the D.C. Circuit's holding that the Copyright Act requires a human author. Thaler had applied to register an image generated entirely by an AI system, listing the system as author, with no claim of human contribution. The Court declined without opinion.
That ends a seven-year run of test litigation. The human-authorship requirement is not a Copyright Office policy preference a future case might unsettle. It is the law, and the last appeal has been exhausted.
One honest caveat, because the commentary split on it. A denial of certiorari is not an endorsement of the reasoning below; it leaves the D.C. Circuit's ruling as the last word rather than blessing it. And the case decided the easy end of the spectrum — Thaler neither prompted the system nor edited the result. How much human involvement is enough remains genuinely open, which is the next section.
The Copyright Office's own position, set out in the second part of its Copyright and Artificial Intelligence report published on 29 January 2025, fills in the detail that matters for musicians. Wholly AI-generated output is not protected. Human contributions to AI-assisted output can be, assessed case by case. And critically: the mere selection of prompts, however detailed and however much effort went into them, does not by itself yield a copyrightable work.
That last point is worth sitting with, because prompt craft is exactly where most AI musicians invest their skill. The Office's view is that no amount of it converts into authorship on its own.
How much human input is enough
The practical question is not "is my track copyrightable" but "which parts of it are, and can I show which". The registration mechanics answer it, and no competing page on this keyword walks through them.
Applicants have a duty to disclose AI-generated material in the application and to disclaim anything more than de minimis. In practice that means naming the AI content in the Material Excluded field and describing your own contribution in New Material Added. Where there is sufficient human authorship, the Office registers the human-contributed elements and disclaims the rest.
| What you are filing | What goes in "Material Excluded" | What goes in "New Material Added" | What you end up holding |
|---|---|---|---|
| Prompt-only track | The whole recording and composition | Nothing | No registration; the application should not be filed |
| Your lyrics, AI music | The generated audio and melody | The lyrics as written | A registration covering the lyrics only |
| AI bed, your arrangement and edits | The raw generated material | Your arrangement, edits and re-performances | A registration covering the human layer, disclaimed elsewhere |
| Already registered, AI not disclosed | — | — | A registration at risk of cancellation until a supplementary filing corrects it |
That last row is sharper than most people expect. If you have already registered a work without disclosing AI content, the Office expects you to correct the record with a supplementary registration. Failing to do so puts the registration at risk of cancellation, which leaves you worse off than never having registered — you lose the benefits while creating a record of a misstatement.
The honest summary: original lyrics you wrote are yours. Arrangement and structural decisions you made and can document are arguable. Substantial editing, re-performance and production work over a generated bed is the strongest case. A prompt, however good, is not. The performing-rights societies drew the same line independently: under the aligned ASCAP, BMI and SOCAN policy of 28 October 2025, partially AI-generated compositions are registrable and wholly AI-generated compositions are not eligible at any of the three.
What the lawsuits are actually about
The AI music litigation is large, loud, and aimed somewhere other than you.
Universal, Sony and Warner sued Suno and Udio in June 2024 through the RIAA, alleging infringement in the training data and seeking statutory damages up to the wilful maximum of $150,000 per work. Since then the block fractured: Universal settled with Udio in October 2025, and Warner settled with Suno in November 2025, taking a licensing deal that also handed Suno the live-music discovery platform Songkick. The UMG and DistroKid disclosure fight is a downstream echo of the same pressure.
Then autumn happened. The docket has roughly doubled since this page first published, and the new filings come from publishers and societies rather than the three majors.
| Action | Filed | Where | What it targets | Names a user? |
|---|---|---|---|---|
| UMG Recordings v. Suno | 24 Jun 2024 | D. Mass. | Training data | No |
| Tony Justice v. Suno (indie class action) | Jun 2025 | D. Mass. | Training, derivative works, DMCA circumvention | No |
| GEMA v. Suno | Jan 2025, decided 31 Jul 2026 | Munich I, 42 O 763/25 | Training and outputs | No |
| SOCAN v. Suno | 2 Sep 2026 | Federal Court of Canada | Outputs and public availability | No |
| Gerencia 360 Music v. Suno | 18 Oct 2026 | N.D. Cal., 3:26-cv-09248 | Training data | No |
| Round Hill Music v. Suno | amended 19 Oct 2026 | N.D. Cal., 3:26-cv-8507 | Training data | No |
| Reservoir Media v. Suno | 21 Oct 2026 | N.D. Cal., 3:26-cv-12305 | 1,050 compositions | No |
Three of those deserve a sentence each. Reservoir's complaint identifies 1,050 works and states that "the total statutory damages sought in this case is $157,500,000.00" — a ceiling rather than an expectation, but an indication of how publisher-side claims are now being sized. SOCAN's action is the one structurally different claim: it lists "a sample of 150 publicly available Suno outputs" and alleges infringement by "using it to generate and make available outputs that replicate songs in SOCAN's repertoire" — the output side, not the training side. And in the indie class action, Judge F. Dennis Saylor IV refused to dismiss the derivative-work and circumvention counts in August 2026, sending them to discovery.
Notice what is still absent from all of it, nine filings in. Not one names an end user who generated or released a track.
What the Munich ruling changed
On 31 July 2026, five days before this page was published, the Regional Court of Munich I decided the first European case on AI music training, and it went against Suno.
GEMA, the German collecting society, brought the claim in January 2025 on behalf of the composers of six works. The 42nd Civil Chamber, presiding judge Elke Schwager, found in case 42 O 763/25 that Suno had no right to use the repertoire, and ordered it to cease reproducing the works, stop using them for training, disclose the revenue connected to the infringement and pay damages to be assessed later.
Memorisation defeated the mining exception. Suno argued that EU text-and-data-mining rules, implemented in Germany as §44b, covered the training. The court rejected that on the finding that the works were not merely analysed but retained in the models in reproducible form. That is the reasoning most likely to travel to other European cases.
US fair use was considered and rejected on the outputs. The court applied a US fair use analysis to training that happened in the United States and found the defence inapplicable, because simple, open-ended prompts produced outputs substantially similar to the originals. It expressly distinguished Bartz v. Anthropic and Kadrey v. Meta, where the outputs had not been shown to resemble the training works.
Repeated prompting did not shift responsibility, and liability sat with the provider: Suno, having trained the models and remaining responsible for their architecture, bears the liability for infringing reproductions in the outputs, rather than the users generating them.
Two caveats, stated plainly. The judgment is first-instance and not yet enforceable; Suno has said it will explore all options including an appeal, and nothing on the public record confirms one has been filed. And it is a German ruling about German rights, arriving before the Court of Justice of the European Union decides Like Company (C-250/25) — the first EU case on generative AI and copyright, heard by the Grand Chamber on 10 March 2026. If you read in August that the CJEU would rule by September, that has slipped: the Advocate General's opinion was pushed back and now sits on the Court's own judicial calendar for 3 November 2026, with the judgment itself following later. Anyone telling you European AI copyright is settled is ahead of the facts.
What all this means if you want to sell the track
Strip the legal detail back and the seller's position is unusually clear.
You can release. Your licence permits it, no case has targeted a user, and the largest European judgment to date explicitly put liability elsewhere. What you cannot do is enforce exclusivity over a wholly AI-generated track, because there is no copyright in it to enforce.
That single fact should reorganise how you think about revenue, because income streams differ enormously in how much they depend on exclusivity.
Enforcement-dependent income assumes you can exclude others. YouTube Content ID is the clearest example: the entire mechanism is a claim of ownership asserted against someone else's upload. Catalogue exclusivity deals assume the same thing. So does chasing whoever re-uploaded your track. On an unprotected track, all of that is built on a right you do not hold. The YouTube monetisation fallout specifically — why a wholly AI track cannot file a Content ID claim, and what that costs in RPM terms — is covered in Vidyo's pillar on the subject.
Delivery-dependent income does not care. When someone buys a track directly from you, they are paying for the file and the relationship, neither of which requires you to be able to sue a copycat. When a music supervisor licenses a cue for a scene, they are paying for a cleared, correctly formatted piece of music that fits a brief and a deadline. What they need from you is a warranty that you have the right to grant the licence, which your generator's terms supply, and a file that works.
So for AI catalogue specifically, direct and sync revenue are structurally stronger — not because they pay more per unit, but because they do not rest on the one right the law has now definitively withheld. If you want that route, you can sell direct and pitch at open sync briefs rather than depending on one generator's download policy surviving the next settlement.
Two honest limits. Sync buyers still ask you to warrant that you can grant the licence, and some libraries will not take AI-assisted material at all; our sync licensing companies breakdown covers which ones publish a policy and which stay silent. And direct sales require an audience you have to build yourself, which is the harder problem and the one most AI musicians actually have. Neither of those is a legal problem. Both are real.
The gate that copyright does not open
Here is the part that legal coverage of AI music almost never reaches, and it is the part that stops the most releases.
None of what you have just read is what blocks a typical AI track from reaching a store. A classifier does, and it runs before any legal question is asked. Two files with identical copyright status — both wholly AI-generated, both unprotected, both licensed for commercial release — routinely get opposite answers from the same distributor, because the distributor is scoring audio, not assessing law. DistroKid's editorial discretion sits on top of that as a second, non-legal filter.
Which produces the one rule to take away from a legal page: artifact processing changes what a classifier measures, and changes nothing about what you own. A wholly AI-generated composition is unprotected in the United States before processing and unprotected after it. It is ineligible at ASCAP, BMI and SOCAN before and after. Anyone marketing artifact removal as a route to ownership, registration or PRO eligibility is describing something that does not exist. It is a distribution-clearance step. That is a genuinely useful thing to be, and it is not this thing.
The same separation applies on the earnings side: passing the gate gets your file listed, which is not the same as making the listing pay. Our breakdown of what AI music creation actually earns has the arithmetic, and output-side plagiarism is the risk that survives all of it.
What to do this week
Four things are worth doing now rather than later.
Write down what you actually contributed, while you still remember it. Lyrics, structural decisions, edits and re-performances. If any of it is registrable, this record makes the case; if none of it is, you have learned something useful for the price of ten minutes.
Get your files off the platforms. Udio's download lockdown and Suno's move to paid-account-only downloads are the same pattern arriving twice. Keep local copies of everything you might sell.
Listen critically to what you generate. Output-side infringement is real and independent of how the file was made — the Munich court found plain prompts producing substantially similar outputs, and SOCAN's whole claim is built on outputs. If a melody feels familiar, treat that instinct as data.
Stop building on exclusivity you do not have. If a plan depends on claiming, blocking or excluding, it needs a copyright you may not hold. If it depends on delivering a good file to someone who wants it, it does not. The practical version is to put the catalogue somewhere it can be bought and licensed directly, keep the customer relationship, and treat placements as the revenue rather than plays.
We are not your lawyers and this is not legal advice. It is a documented account of where the law stood on 27 October 2026, sourced to the rulings, filings and reports themselves, and written for people who have to make a release decision this month.
Questions readers ask.
In the United States, nobody owns the copyright to a wholly AI-generated track. Copyright requires human authorship, and the Supreme Court's refusal to hear Thaler v. Perlmutter on 2 March 2026 settled that at the top of the system. What you hold instead is a contractual licence from the generator, which is what permits you to release and monetise the track.
You can register the human-authored parts of it, not the AI-generated parts. The Copyright Office requires applicants to disclose AI-generated material and disclaim anything more than de minimis. A track built from your own lyrics and significant human production work is registrable on those elements; a track produced from a prompt alone is not.
If the track is wholly AI-generated and carries no human authorship, you have no copyright claim against someone who re-uploads or re-sells it. Platform terms of service, trade mark on your artist name and contractual claims may still help, but the core copyright remedy is unavailable. That is the most concrete consequence of the ownership question.
No. Not the label suits against Suno and Udio, not the GEMA judgment in Munich, not SOCAN's Canadian claim, not the indie-artist class action, and not the publisher suits filed through October 2026. Every named defendant is a company. The Munich court was explicit that responsibility sat with the provider that trained the models.
On 31 July 2026 the Regional Court of Munich I (case 42 O 763/25) found that Suno had infringed by training on GEMA's repertoire, and ordered it to stop reproducing those works, disclose connected revenue and pay damages to be assessed. The court rejected the text-and-data-mining exception because the works were retained in reproducible form. The judgment is not yet enforceable.
Yes, and this is the distinction most coverage misses. Selling requires the right to distribute, which comes from your generator's licence terms. Owning requires authorship, which comes from copyright law. Most AI releases run on the first without the second. What you cannot do is stop a competitor selling the same file.
No. Processing a file changes what a classifier measures, not what the law recognises. A wholly AI-generated composition is unprotected in the United States before processing and unprotected after it, and ineligible at ASCAP, BMI and SOCAN either way. Artifact work is a distribution-clearance step, not a legal one.
The verdict, in one sentence: Undetectr.
Copyright status is not what stops most AI releases — a classifier is, and it runs before any legal question is asked. Undetectr clears artifact layers and masters to distribution spec in a browser pass, listed at €39 one-time for its Lifetime tier. It changes what a detector measures. It does not change what you own, and nothing does.