← Blog

I made a song with Suno. How do I prove it's mine?

2026-09-20 · OpenStela

People ask this the day the song is done, and usually mean three things at once: I made it, I made it first, and I own it. They are different questions with different answers, and it helps to separate them before doing anything.

Three questions hiding in one

Did I make it? With an AI tool, the honest answer is “I made part of it”: the lyrics, the prompts, the twenty takes you threw away, the structure you kept, the vocal you re-recorded, the edit. That part is yours in every sense; the part the model generated is where the law is still being written (more on that here).

Did I make it first? This one is purely about dates, and it is the question a registry can actually answer. If the exact file existed under your name on 8 September, and someone else's copy appears on 20 October, the order is settled without anyone taking your word for it.

Do I own it? That depends on the tool's terms for your plan, on your jurisdiction, and on how much of the work is yours. No registry changes any of that. What a registry does is make sure that when the question comes up, you have evidence instead of a memory.

What a record fixes in place

An authorship record is a small card with four things on it: the fingerprint of the file (SHA-256 of every byte of your mp3 or wav), the name the track is published under, the date you say you made it, and — because the song is AI-assisted — a sentence or two in your own words on what you contributed. The card is fingerprinted in turn, and that fingerprint is bundled with everyone else's that night into one root written to a public blockchain. Months later, anyone with the file and the card can recompute the whole chain without asking us; the three-act diagram walks through it.

Two things it is not. It is not a copyright registration with any government office — if you want that, and your jurisdiction offers it, do it as well. And it does not stop the model from producing something similar for someone else; it only proves that this file, under your name, existed on that date, with the contribution you described.

Seven minutes, start to finish

1. Export the final track from Suno (or Udio, or wherever) as mp3 or wav. Register the version you actually published; earlier drafts can be added later as a version chain.
2. Open Works and upload the file. Audio up to 30 MB per file; an account has 300 MB of upload space, and registration is free.
3. Attribution: the artist name it is published under. Date: when you made it. Then the rights declaration — for music you confirm both the composition and the recording, because a song is two rights, not one.
4. AI-generated: yes. Name the tool, then write what you did. Be concrete: “wrote all lyrics; ~40 generations, chose and re-ordered sections; re-recorded the lead vocal; mastered in Logic.” This field is frozen into the record; a vague one is worth little later.
5. Leave public on if you want a page you can link from your Suno profile or your bio; turn it off if the track is unreleased. Either way the record is anchored that night.

Afterwards you have a public page for the work, a downloadable record, and a Proof Pack — a zip with the card, its proof path and a PDF summary — that works without the platform. Keep the original file with it; the chain can vouch for a fingerprint, not for a song you no longer have.

If the song belongs to a character

A virtual singer's track can be bound to that character's registry ID in one extra step. That binding is a second dated record, and from then on the song shows on the character's page and moves with the character if it is ever sold. How that works, and what evidence it carries, is its own post.

Register a song →  ·  How verification works →