Someone Re-Uploaded Your AI Track: What Recourse You Actually Have

You found your own track on someone else's channel, with their name under it, and the phrase you typed into a search box was probably someone stole my song. What came back was written for bands: register the copyright, then use that registration to force a takedown or claim damages. For an AI-generated recording that chain has a hole in the middle of it, because the US Copyright Office's position is that prompts alone do not make you the author — so following the standard advice in the standard order will cost you the first week and get you nowhere.

The stakes are not abstract. The thread that prompted this page ran to 192 comments from a creator who reported a re-uploader three weeks earlier and now has three of their videos live with the same song. Reports going nowhere is the normal outcome, and the reason is usually that the wrong instrument was used first.

This page gives you the order that works: what to capture in the first hour, what you own and what you do not, and the reporting route for each platform. Every rule below was read at source on 22 September 2026 — the Copyright Office's Part 2 report, Suno's terms effective 3 September 2026, and current help-centre text at DistroKid, LANDR, YouTube, Spotify and TikTok.

Three different things get called "someone re-uploaded my track"

Before you report anything, work out which of these you are actually looking at. They have different answers, and three of the five have no route at all.

The third row is the one that surprises people, and Suno's own terms are the reason. The agreement effective 3 September 2026 states that "due to the nature of artificial intelligence and machine learning, your Output may not be unique and the Service may generate the same or similar output for a third party," and, separately, that "Output that is requested by and generated for other users is not your Content."

Read those together and a whole category of complaint dissolves. If another user prompted their way to something resembling your track, that is a documented property of the service, not theft, and no report will succeed. If what is online is your audio file — same master, same performance, same artifacts — that is a different situation, and the rest of this page is about it.

The first hour: preserve everything before you report

Evidence here has a habit of disappearing. Accounts get deleted, videos get set to private, and the moment a report lands the other party may start tidying up. Capture first, report second.

The last two are worth more than creators expect: a downloaded master carries Content Credentials, and a distributor's delivery record is a dated document you did not write yourself. Our ISRC code guide covers how that identifier pins a specific recording across platforms.

One habit worth building now: when you find the first re-upload, search for others before you report. Reporting them one at a time is how a pattern gets treated as isolated incidents.

Do you actually own the recording? The AI authorship problem

This is the section every competing guide skips, and it is the one that determines which routes are open to you.

The US Copyright Office published Part 2: Copyrightability on 29 January 2025. Its conclusion on prompts is unambiguous: "The Office concludes that, given current generally available technology, prompts alone do not provide sufficient human control to make users of an AI system the authors of the output. Prompts essentially function as instructions that convey unprotectible ideas."

What it does protect is equally clear, and more useful: "Human authors are entitled to copyright in their works of authorship that are perceptible in AI-generated outputs, as well as the creative selection, coordination, or arrangement of material in the outputs, or creative modifications of the outputs." Whether a given contribution clears that bar "must be analyzed on a case-by-case basis."

Suno's own help centre says the same thing without the hedging: "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," and "writing the prompt does not constitute the creation of the song."

Most Suno releases sit in the top row, which means the copyright-first playbook was never built for you. This is information about the US position, not legal advice; other jurisdictions differ. Our AI music copyright explainer goes deeper on registration mechanics.

What you own by contract even when copyright is thin

Here is the part nobody writes down, and it is the good news. Copyright is not the only thing that gives you standing.

On a paid tier, Suno's terms state that "Suno hereby assigns to you all of its right, title and interest in and to any Output owned by Suno and generated from Submissions made by you through the Service." In the same subsection it adds: "Due to the nature of machine learning, Suno makes no representation or warranty to you that any copyright will vest in any Output."

That pairing is the whole picture. You own the thing; whether the thing carries copyright is a separate question the company will not answer for you. On the free tier it differs again — Suno retains ownership and your use is non-commercial.

What contractual ownership buys you is a route through platform terms rather than copyright law. Every platform's rules prohibit more than infringement: impersonation, spam, passing off another user's work as your own. You do not need to prove authorship to report a breach of community guidelines, and a Suno-to-Suno repost is an in-platform matter first.

This distinction also protects you from a mistake the standard advice walks you into. A DMCA notice contains a statement made under penalty of perjury that you own the copyright or are authorised to act for whoever does. YouTube's warning is explicit: "Do not submit false information. Misuse of our processes, such as submitting fraudulent documentation, may result in the termination of your account or other legal consequences." Firing off copyright notices for a prompt-only track is not a free shot. Use the terms-of-service route where that is the truthful claim.

Reporting routes, platform by platform

Every competing guide stops at "send a DMCA". These are the actual routes, as published by each platform.

Suno's in-app report is fastest for a Suno-to-Suno repost and asks nothing of you legally, so start there. And YouTube's removal request is the one with teeth: it puts a copyright strike on the other channel, which is what actually changes a repeat re-uploader's behaviour.

DMCA takedown versus Content ID claim: not the same instrument

These get used interchangeably in creator forums and they are different in every respect that matters.

The counter-notice is the step people forget: if the other party files one, the content can go back up and you choose between dropping it and going to court. Our Content ID guide covers the mirror case — what happens when a claim lands on your upload.

The Content ID trap: the one tool that would stop this is the one AI tracks cannot enter

If you could register your recording into Content ID, every future re-upload would be caught automatically and you would never file another report. That is the fix — and for most AI releases it is unavailable, which no page on this topic says.

YouTube's own requirement is that "copyright owners must have the exclusive rights to the material that's evaluated." DistroKid's eligibility article for its Content ID option, updated 9 September 2026, is blunter: "If your release contains any audio that you didn't create yourself like beats, loops, samples, or video game sounds, then it is unfortunately ineligible for YouTube Content ID," and the first condition on its list is "You own 100% of the sounds."

Neither page mentions AI. That silence is the problem: whether a generated master counts as sounds you created is a question the rules do not answer, and the wrong answer is not a rejection — it is a false eligibility declaration. Ask your distributor in writing before you opt in.

One distributor has answered it already. LANDR's AI policy, updated on 22 September 2026, lists YouTube Content ID first among "platforms currently not accepting AI-generated music," alongside Meta, TikTok, Deezer, Lissen, Pandora and Tencent, and caps submissions at "a maximum of thirty (30) AI-generated songs per calendar month per subscriber."

A second reason for caution even if you qualify: Suno's non-uniqueness clause cuts both ways, and registering a reference the model could produce again for someone else invites automated claims against uploads that are nobody's fault. Distributors differ, and the test is the model and the rights rather than a simple yes or no — our page on what distributors ask about AI training covers how it is applied.

The Copyright Claims Board, and where the free routes stop

If the platform routes fail and the money is real, the escalation ladder looks like this.

The Copyright Claims Board is designed for people in your position — "a three-member tribunal with extensive expertise in copyright matters that provides a streamlined alternative to federal court to resolve copyright disputes involving claims up to $30,000," with statutory damages capped at $15,000 per work and no lawyer required.

But it loops back to the authorship problem. You must "either (1) have a registration from the Copyright Office for the work(s) at issue or (2) have submitted an application to register the work(s) either before or simultaneously with filing the claim." For a prompt-only recording there is nothing to register, so the CCB is closed. If you wrote the lyrics, they are registrable and that route reopens for that part of the work — the clearest practical argument for writing your own lyrics that exists.

When it keeps happening

The thread behind this page is not about one repost. It is about reporting someone, waiting three weeks, and finding three more uploads. That pattern has a lever, and it is not resending the same report.

Every platform here publishes a repeat-infringer policy. Suno's terms describe "terminating, in appropriate circumstances and at Suno's sole discretion, the accounts of users who are deemed to be repeat infringers." TikTok says it will "ban the account of a user who repeatedly commits copyright infringement." Spotify "has a policy to terminate, in appropriate circumstances, the accounts of repeat infringers."

These fire on documented patterns, not individual reports. So make the pattern legible: same claimant, same work, every report dated, each notice referencing the earlier case numbers, all uploads listed together rather than trickled in. A support agent seeing five linked incidents behaves differently from one seeing a fifth isolated complaint.

The structural fix sits elsewhere, and it is worth being honest about. Most creators here are not fighting off thieves — they are struggling to be heard at all, which makes someone else profiting from your track especially bitter. Chasing re-uploads does not build an audience; a canonical version somewhere you control does more. played.fm exists for pitching tracks for paid sync placements in TV, film, games and ads, where the money does not depend on winning a search result, and for selling direct to listeners on a page that is unambiguously yours. If discovery is your real problem, see nobody listens to AI music.

Making the next release harder to steal

You cannot prevent a re-upload. You can make it cheap to prove and quick to remove.

• Release through a distributor and keep the ISRC. It gives every recording a dated, independent identifier.
• Publish first on a channel you control, with a dated public post. Priority in time settles most disputes.
• Keep the original download untouched. Content Credentials travel with that file and are evidence in your favour. Suno's terms ask you not to obscure provenance metadata "for the purpose of concealing or misrepresenting the provenance, service tier, or status of that Output" — and here it works for you anyway.
• Write your own lyrics and register them. The one reliable way to put a registrable work inside a generated track, and it reopens the CCB route.
• Keep your generation history. A project timeline is hard to fake and easy to show.

Release-readiness is a separate problem from theft, but it is the other thing that stalls a catalogue — see our AI remix guide and the disclosure question at eraseai.co. Note that nothing in the screening process, or in any tool that helps with it, has any effect on someone re-uploading your track afterwards.

None of this is legal advice, and it describes the United States. If real money is attached, get an hour with a music lawyer.