DistroKid AI Detection: What Happens After the Scan
DistroKid now names the service behind its AI detection, publishes what the resulting tag does to a release, and answers the question in four words: it does not affect distribution.
- The short version: DistroKid accepts AI music, and what its detection produces is a tag rather than a rejection. In DistroKid's own words, "The tag is informational. It doesn't affect distribution through DistroKid."
- DistroKid is the only major distributor that names its detector. A help article created on 2 November 2026 says the tag appears when "an independent service called ACRCloud" flags a track as potentially AI-generated.
- A tag, a rejected upload and a copyright removal are three different events with three different published routes — a correction form, a reply to the rejection email, and an evidence-backed dispute. Sending the right evidence to the wrong one is the commonest wasted week.
- The word "appeal" appears zero times across all 421 DistroKid help articles, and so do "classifier" and "prediction model". No threshold, vendor accuracy figure or scoring rule is published anywhere in the help centre.
- Where a likely-AI flag does have a published consequence is publishing, not distribution: TuneCore states that songs flagged as likely AI-generated "may not be processed" for PRO registration because wholly AI compositions are not copyrightable.
If your track came back with a tag, a rejection email or a removal notice, the first useful thing to know is that those are three different events — and distrokid ai detection is only responsible for one of them. DistroKid changed the ground here on 2 November 2026, when it published an article naming the service behind its AI tag and stating, in four words, what that tag does to your release: it does not affect distribution.
That is a smaller and more precise claim than almost anything written about DistroKid and AI music, including the earlier version of this page. What follows is built from DistroKid's own help centre, read through its public API on 12 November 2026, with every other distributor's corpus read the same way for comparison. Where a figure comes from our own submission testing rather than a published source, it is labelled as ours.
What DistroKid publishes about AI music, in its own words

DistroKid's position is one article long and it has not moved since December 2025. Can I Upload Music Made With AI Tools to DistroKid? opens: "Yes—DistroKid accepts music created with AI tools, but there are some rules."
The rules are four, and the thing to notice is that not one of them is about the audio itself:
- You must own the rights — 100% of them, "including the legal right to distribute music created with any AI tools, samples, lyrics, etc."
- No impersonation — your music "cannot mimic or copy someone else's voice, likeness, or identity without permission."
- No mass-generated spam — music made "solely to game streaming algorithms or flood platforms with generic content."
- No infringement of anyone else's rights.
The article closes by pushing the consequence downstream: "streaming services may reject or remove releases that don't meet their guidelines." So a fully generated track made from your own prompt, released under your own name, with nobody else's voice in it, breaks none of DistroKid's published rules. There is no audio-quality bar, no "too synthetic" clause and no rule that a release is refused for scoring as AI-generated.
The AI tag, and the sentence that settles most of this
The newer article is Why does my track have an AI tag?, created 2 November 2026 and last edited 6 November 2026. It is short, it is written as five questions, and it answers the ones artists actually ask.
| The question | DistroKid's own words |
|---|---|
| What is the tag? | "It appears when an independent service called ACRCloud flags a track as potentially AI-generated." |
| Why does it exist? | "Some streaming platforms now require distributors to identify AI-generated music." |
| Does it affect my release? | "The tag is informational. It doesn't affect distribution through DistroKid." "Your track still goes out to all streaming platforms." |
| I did use AI — problem? | "Nope, and there's nothing you need to do. We pass the info along to the relevant streaming platforms." |
| Who decides what it means? | "Each streaming platform decides how it displays and handles AI-generated music." |
| I didn't use AI | "Third-party detection tools aren't perfect." Report an incorrect flag on the linked form |
| How long does that take? | "Typically within 24-48 hours", answered by email |
Two things follow that are worth holding onto. First, the tag is metadata, and metadata is handed to platforms rather than enforced by DistroKid — which is why no audio tool can remove it once it is attached, and why nothing you do to a file changes how Spotify or Apple Music chooses to display it. Second, DistroKid concedes the failure mode in writing: detection tools "aren't perfect", and the published remedy for a wrong call is a form, not an argument.
ACRCloud, the one detector a major distributor names

ACRCloud is an audio recognition company, and its AI detection product is documented publicly — which makes DistroKid's tag the rare industry decision whose mechanism you can read. The developer FAQ publishes the decision rule and the limits.
| What ACRCloud publishes | Figure |
|---|---|
| Decision threshold | "The current threshold is 50%." At or above, the output is ai_generated; below it, human |
| What the model returns | A binary prediction, an ai_probability score, and source_probabilities per generator |
| Maximum file length | 15 minutes (900 seconds) |
| Precision / recall (AI) | 99.98% / 99.88%, on "internal evaluation" data |
| Accuracy on Suno | 99.70%; Udio 99.82%, Lyria 99.97%, Boomy 96.37% |
| ACRCloud's own caveat | Results "are provided for reference only" and vary with "audio quality, transformations, compression, mixing, editing" |
Its public detector page adds a detail that matters for part-AI work: a track is scored segment by segment, with vocals and accompaniment analysed separately. A human vocal over a generated instrumental is not one verdict but several, which is the technical counterpart to DistroKid's own "Part of the audio" disclosure option. Our AI music detector tools page covers the wider detector landscape, including the free checks that run on this same engine; part-AI vocals and detection covers the hybrid case in detail.
Three things can happen to an upload, and they are not the same thing
This is where most of the bad advice on this topic comes from. A tag, a rejection and a post-release removal feel identical from the artist's side — something went wrong, an email arrived — but DistroKid publishes a different route for each, and the evidence that wins one is ignored by another.
| What happened | What it actually is | The published route | Where DistroKid publishes it |
|---|---|---|---|
| Your track carries an AI tag | Metadata passed to platforms; no effect on distribution | The correction form, if ACRCloud flagged it wrongly. Reply by email, "typically within 24-48 hours" | Why does my track have an AI tag? (2 Nov 2026) |
| Your upload was rejected | A release that failed review against a service's formatting or content guidelines | "Details on the rejection will be included in the email you received." Usually delete and re-upload; "If you think your release was rejected in error, just reply to that email" | Handling a Rejected DistroKid Release (edited 16 Jun 2026) |
| Your track was removed after a claim | A copyright claim against a live release | Open a chat and dispute it with documentation; counter-notice form for a DMCA takedown | Was your music removed because of a copyright claim? (edited 16 Oct 2026) |
Note what is not in that table: there is no row where an AI score causes a rejection. A rejection is a review outcome against the guidelines of the service a release is bound for, and two of the three published rejection categories — verification requests and artwork problems — do not even require a re-upload to fix.
The evidence that works, and which route takes it

The advice you will read everywhere, including in the previous version of this page, is to appeal an AI flag with stem files, project exports and an authorship statement. That evidence list is real and it is published by DistroKid — but it belongs to the copyright route, not the AI tag.
The copyright-claim article asks for a Splice sample certificate, a public beat listing plus your licence, or a signed agreement with the rightsholder, and then adds the line that matters for generated music: "Don't think your track shares elements with the song listed above? Send us your project files, stems, or a quick note on how it was made and we'll take another look."
That is a documentation standard you can prepare for. Suno's export tools produce stems and keep generation history, so the constraint is almost never DistroKid's willingness to look — it is whether you saved anything at the time. Regenerate a track without that history and the file is all you have.
For an AI tag, by contrast, the published route asks for none of that. It is a form, a statement that the flag is wrong, and a wait of a day or two. Sending a folder of stems to the tag route is not wrong so much as beside the point, and sending a written denial to the copyright route — the one that explicitly asks for documents — is how a dispute stalls.
What DistroKid does not publish, counted across 421 help articles
Absences are easy to assert and harder to measure, so this one is counted rather than claimed. DistroKid's help centre was pulled in full through its public API on 12 November 2026 — 421 articles — and searched as plain text.
- "appeal": 0 occurrences. There is no appeal process for anything, under that name.
- "classifier": 0. "prediction model": 0. DistroKid never describes the test it runs.
- No threshold, no confidence score, no accuracy figure. Nothing in the corpus states where the line sits or how often it is wrong — only that detection tools "aren't perfect".
- No retroactive-screening article, no repeat-offender policy, no AI-related royalty clawback rule. None of these is documented anywhere in the help centre.
What that means in practice is that every mechanism claim about DistroKid's detection on the open web — including the staged pipeline the earlier version of this page described — is reconstruction rather than citation. The two facts DistroKid does publish are the vendor's name and the tag's effect, and both are recent.
Two courts are now asking for the same missing facts
The unpublished details are not just missing from artists; they are being demanded in litigation, and the dates are worth stating as a sequence rather than a cause.
Universal Music Group sued DistroKid in Delaware federal court on 15 September 2026, alleging copyright infringement and deceptive trade practices, with DistroKid's response due 4 December. Separately, in the Massachusetts case against Suno, UMG and Sony served DistroKid — a non-party — with a subpoena in September, and on 14 October 2026 asked a Manhattan court to enforce it. Music Business Worldwide reported that the labels want monthly counts of recordings tested and flagged as likely AI-generated, the streams and royalties attached to them, and "the name and vendor of the prediction model" that DistroKid described in a 9 October response. On 28 October the parties told the court they were "working on a resolution".
Three cautions, because this is where coverage usually overreaches. DistroKid is a third party in the Suno case, not a defendant. Scoring as likely AI-generated is not a finding of infringement against anyone. And nothing published establishes that the "prediction model" described to the court and the ACRCloud service named in the help centre are the same thing — the help article appeared on 2 November, after the filings, and neither document refers to the other. As of 12 November 2026 no ruling had been reported.
What our own submission testing found, and how to read it now
Our own figures are separate from everything above and are labelled as ours. Across submission testing in 2025 and the first half of 2026 we placed DistroKid's effective rejection line near 0.78 confidence, inferred from where rejections began appearing in our own uploads rather than read off any score DistroKid returns — it returns none. False positives on heavily processed human-made material ran roughly 5-8% in that testing. In twelve appeal cycles run through DistroKid support in the second half of 2025, submissions that included Suno project exports, individual stems, generation-history screenshots and a one-paragraph authorship statement succeeded 9 of 12 times, while a separate small batch of bare written denials succeeded 0 of 6.
Read those beside the published figures rather than instead of them. ACRCloud's published decision threshold is 50% on its own ai_probability scale, which is a different scale from anything DistroKid exposes, and our 0.78 describes where outcomes changed in our submissions, not a number anyone showed us. The appeal results describe the evidence-plus-statement package working — which is exactly the standard DistroKid's copyright-claim article publishes today. The one thing that has clearly changed since that testing is the vocabulary: DistroKid now documents a tag with no distribution effect, and documents no AI rejection category at all.
The other distributors, and the one place a flag has a published consequence

The same API read was run against four more help centres on 12 November 2026 — TuneCore (237 articles), CD Baby (191), LANDR (464) and UnitedMasters (302). Across all 1,194 of them, "ACRCloud", "IRCAM", "classifier" and "prediction model" return zero hits, which is the measurement behind the claim that DistroKid is the only major distributor naming its detector.
| Distributor | Accepts AI music? | What it says it does | What you get, and the route back | Read at source |
|---|---|---|---|---|
| DistroKid | Yes, under four rights rules | Names ACRCloud; publishes no method | An informational tag; correction form, 24-48h | 12 Nov 2026 |
| UnitedMasters | Yes, under its guidelines | "the file is automatically scanned by a tool to detect AI", then "reviewed by a human on our team" | Tags for audio and artwork, email on the first one; appeal to support, but a confirmed tag "is final" | 12 Nov 2026 |
| LANDR | Yes, with monthly caps | "We use detection technology to identify AI-generated songs"; vendor not named | 20 or 60 AI tracks a month by tier, no AI covers; "We may request proof of rights" | 12 Nov 2026 |
| TuneCore | Only from licensed-dataset models | "TuneCore only distributes music created using GenAI models trained on fully licensed datasets" | Unlicensed-model output "is not eligible for distribution" | 12 Nov 2026 |
| CD Baby | No | "You will not be able to distribute A.I.-generated content" | — | 12 Nov 2026 |
LANDR's disclosure form, edited on 9 November 2026, is also the most detailed in the industry: two axes, Composition and Sounds, each set to None, AI-assisted or AI-generated, plus a field for the tools used, with Suno given as the example.
And the published consequence nobody writes up sits on the publishing side rather than distribution. TuneCore states that compositions generated entirely by AI "are currently not afforded copyright protection and therefore cannot be registered with PROs/CMOs", and that where songs are "flagged as likely AI-generated, they may not be processed due to the legal and commercial risks associated with registering non-copyrightable songs." That is the one place in all five corpora where a likely-AI flag has a stated operational effect — and it costs you collection society royalties, not your release. Our distributor detection overview and the DistroKid vs TuneCore vs CD Baby comparison go further into the trade-offs.
Before you upload, and after it is live
Nothing above is an argument for hiding anything, and the disclosure questions are separate from detection entirely: DistroKid's AI Credits exist so you can declare generated lyrics, music or audio, and are explicitly not needed for "Pitch correction, auto-tune", "AI-assisted mixing or mastering" or "AI-assisted workflows". Declaring accurately is both the rule and the thing that makes a wrong tag easy to contest. eraseai.co's guide to DistroKid AI credits walks through the fields themselves.
What is worth doing before you submit is ordinary release preparation. Generated audio often carries audible artifacts — smeared transients, vocoder-ish high end, a hiss floor that mastering amplifies — and those are worth fixing because they make the record worse, not because they change a label. Undetectr works on that artifact and signal layer before submission; what it cannot do is alter how a platform labels your release, because that label travels in metadata rather than in the audio. Anyone promising otherwise is selling you something no tool can deliver. If you are unsure what the Suno layer involves, what is the Suno watermark covers it, and why AI music gets flagged covers the signals.
The harder problem starts after the release goes live, and it is not distribution. Getting distributed is close to solved for AI-assisted artists; being heard is not, and the forums are full of people with twenty releases and no listeners. That is the argument for routes that do not depend on algorithmic discovery: selling direct to the people who already like your work, and pitching for paid sync placements in TV, film, games and ads, which is where the money conversation in this niche actually is. played.fm's sync route is built for that, and keeping 100% of a direct sale follows from it rather than leading. Bandcamp, the obvious comparison, bans AI music outright, so it is not an option for this catalogue at all.
DistroKid's detection is no longer a black box with a rumoured threshold. It is a named third-party service, producing a tag that DistroKid says does not affect distribution, with a published correction route that takes a day or two — and three separate doors, only one of which is the one you probably need.
Questions readers ask.
Yes, through a third party. DistroKid's help article on AI tags says the tag appears when an independent service called ACRCloud flags a track as potentially AI-generated. DistroKid does not describe the test, publish a score or name a threshold anywhere in its help centre.
No, on DistroKid's own published answer. It states that the tag is informational, that it does not affect distribution through DistroKid, and that your track still goes out to all streaming platforms. What each streaming service then does with that tag is that platform's decision, not DistroKid's.
DistroKid answers this one directly: "Nope, and there's nothing you need to do." The published rules are about rights rather than audio — you must own 100% of the rights, not impersonate anyone, not mass-generate spam, and not infringe. Streaming services then apply their own guidelines.
DistroKid publishes a correction form for a track it says ACRCloud flagged incorrectly, and says it reviews submissions and replies by email, typically within 24 to 48 hours. If the tag should not be there, DistroKid says it will tell the streaming platforms right away.
There is no published appeal process, and the word does not appear in the help centre at all. What is published is narrower: if your upload was rejected, the reason is in the email, you will usually need to delete and re-upload to fix it, and DistroKid says to reply to that email if you think the rejection was an error.
They are the published evidence for a copyright claim, not for an AI tag. DistroKid's article on music removed after a claim asks for a Splice sample certificate, a beat listing plus licence, a signed agreement, or "your project files, stems, or a quick note on how it was made". Keep those from generation time.
They differ in kind rather than strictness. UnitedMasters scans then has a human review and allows an appeal whose outcome is final. LANDR accepts AI music but caps it at 20 or 60 tracks a month by tier. TuneCore takes only output from models trained on fully licensed datasets, and CD Baby does not distribute AI-generated content at all.
The verdict, in one sentence: Undetectr.
Undetectr works on the generation artifacts and the signal layer a detector scores, before you submit anything. It cannot change how a platform labels a release: that label travels in metadata your distributor sends onward, and no audio processing touches it.