When Suno introduced V6 on September 9, 2026, it described a new generation of music models developed with industry partners, naming Warner Music Group, BMG and Believe. That is a meaningful change, and it is a change to the generator's position rather than to yours. It speaks to what the model was trained on. It does not speak to whether the recording you just made is protected, or to who may register it.
This is an AI-assisted article from the Galvanized Souls Editorial Desk. We read the linked primary pages on September 15, 2026. Copyright rules vary by territory, and nothing here is legal advice for your particular recording.
Suno separates owning a song from holding copyright in it
The distinction is drawn on Suno's own help pages rather than only by outside commentators. Suno's copyright page sets out the ownership split by tier: songs made on the free plan are owned by Suno and permitted for non-commercial purposes, while songs made while subscribed to Pro or Premier are owned by you.
Then it adds the sentence that matters most here: “In both cases, however, the material may not be eligible for copyright protection.”
Ownership and copyright are being described as two different things, and paying for a subscription resolves only the first. The same page explains why: “In the US, copyright laws protect material created by a human. Music made 100% with AI would not qualify for copyright protection because a human did not write the lyrics or the music. Writing the prompt does not constitute the creation of the song.”
The September 2026 terms put the same point in contractual language. Alongside the assignment of Suno's interest in Output to Pro and Premier subscribers, the terms state: “Due to the nature of machine learning, Suno makes no representation or warranty to you that any copyright will vest in any Output.”
Read those together and the position is consistent. You may own the song and still hold nothing registrable in it.
Why licensed training does not move that line
The underlying authority here concerns authorship, not the provenance of the training set. The US Copyright Office is publishing its report on copyright and artificial intelligence in parts, and Part 2, published January 29, 2025, addresses the copyrightability of outputs created using generative AI.
The question that analysis asks is what a human contributed to the work in front of it. A licensing agreement between a model developer and a group of rights holders does not answer that question, because it is not about your recording at all. It reduces the developer's exposure for how the model was built. Your authorship claim still rests on what you did.
This matters because the inference runs the other way in a great deal of current commentary: the models are licensed now, so the output must be cleared. Those are separate propositions, and the second does not follow from the first. Treat any claim that V6 makes your output copyrightable as an assertion that has not been established, and keep it out of your own release notes and sales copy.
What does move the line
The route Suno itself describes is the one worth working. Its copyright page continues: “If you wrote the lyrics for your song(s), you own those lyrics. Most copyright offices will allow you to register those lyrics on their own, and you may be able to use those lyrics to register your whole song as well. Some regions/registrars may recognize you as the writer of the song and Suno as an instrument to help you create the song.”
That is a description of human authorship doing the work, with the generator treated as a tool. So the practical question for each recording is what you can actually evidence: lyrics you drafted, a melody you wrote or sang, a structure you determined, edits and arrangement decisions you made, a performance you recorded.
Record those contributions while you still remember them. Keep lyric drafts with their dates, keep any voice memo or demo you worked from, and keep a short note of what you changed between versions. Our release checklist builds this into the rights record for each track, and the licensing routes guide covers what you can and cannot offer a buyer when the position is partly settled.
Where a contribution is thin, describe it honestly rather than inflating it. An overstated authorship claim in a registration or a sales listing is a worse problem than an unregistered recording.
Two consequences people miss
Suno's contractual restrictions do not depend on copyright existing. The September terms state that the commercial use restrictions “apply as contractual obligations regardless of whether copyright or any other proprietary right subsists in any Output.” So “there is no copyright in this anyway” is not a route around the terms you agreed to. You can be bound by contract in material that no registry would accept.
The second consequence points at distribution. Suno's own copyright page notes that “Some distributors exclude songs that are not eligible for copyright protection, so it may be helpful to research several options.” A distributor may ask a question your copyright position cannot answer favourably, and it may also apply a test that has nothing to do with copyright at all. Our guide to Suno V6 and TuneCore works through one such test, which turns on the model rather than on the recording.
Where this leaves a release decision
Keep three answers separate for each track, and write them down in this order. What do you own, per your subscription tier at the time the song was generated. What is likely to be protectable, based on what you contributed. What each destination requires, which is its own question again.
A confident answer in the first column tells you less than it appears to. It is the second and third that decide whether a registration is worth filing and whether a given route will accept the release at all. The rights and policies hub sequences those decisions, and it is worth working them before a release date is announced rather than after.