What AI Music Detection Does to Your Upload

Every major distributor now screens uploads for AI, and on 2 November DistroKid became the first to say out loud which service does the screening. The result is not the rejection most producers expect.

Filed 2026-05-21 Read 10 min Method How we work
In short
  • The short version: in 2026 AI music detection produces a metadata tag, not a rejection. DistroKid states that the tag is informational and does not affect distribution.
  • DistroKid is the only major distributor that names its detector. A help article created on 2 November 2026 and edited on 6 November names ACRCloud, an independent service.
  • Across 1,192 help articles from TuneCore, CD Baby, LANDR and UnitedMasters, ACRCloud appears 0 times, IRCAM 0 times and the word classifier 0 times. Only one distributor has named anyone.
  • ACRCloud publishes 99.98% precision on its own internal test data at a 50% threshold. A peer-reviewed July 2026 paper puts baseline detectors at AUC 0.817 on Suno v5 once the audio is speed-modified.
  • LANDR is the only one that publishes a hard number, and it is a monthly submission cap of 20 or 60 AI tracks by plan tier, not an accuracy score.
Flat illustration on charcoal: a cyan audio waveform passes through a scanner arch and continues unbroken out the other side, with a small blank amber tag hanging from it just past the arch. Nothing blocks the waveform.
Detection output in 2026 is a tag attached to the release, not a barrier in front of it.

If you have shipped a Suno track in the last month, something scanned it before it reached Spotify, and until two weeks ago no distributor would tell you what. ai music detection is now running on every upload at every major distributor, and the guides describing it are built almost entirely on inference. That matters because the inference is wrong in the one place it counts: most of them describe a rejection, and what the system actually produces is a label.

This page was rebuilt on 7 November 2026 from the distributors' own help centres, read through their support APIs rather than their blocked web pages — 1,192 articles from TuneCore, CD Baby, LANDR and UnitedMasters, plus DistroKid's. Where a figure below has a source, the source is named and dated. Where nobody publishes one, this page says so instead of estimating.

What AI music detection actually produces in 2026

Start with the thing every competing guide gets wrong. At the distributor layer, a positive AI detection in 2026 does not stop your release. It attaches a piece of metadata that travels with the track, and the decision about what that metadata means is taken further down the chain, by each streaming service separately.

DistroKid is explicit: "The tag is informational. It doesn't affect distribution through DistroKid." UnitedMasters describes tagged releases being delivered to stores with the tag attached, not held back. LANDR accepts AI music and limits the volume of it. None of the five publishes a rule that rejects a release for scoring as AI-generated.

Table of what each distributor publishes about AI screening. DistroKid accepts AI music under four rights rules, names ACRCloud as its detector, produces an informational AI tag passed to platforms and states no limit, read 6 November 2026. UnitedMasters accepts it, names no detector, tags audio and cover art separately and runs spam review on high volumes, read 5 November 2026. LANDR accepts it with exclusions, refers only to detection technology, enforces caps and bars AI cover songs, with a published limit of 20 or 60 tracks a month by tier, read 7 November 2026. TuneCore accepts it, names nobody and publishes nothing; its AI programme is licensing rather than screening, read 6 November 2026. CD Baby does not state a policy in its help centre, read 7 November 2026. Only DistroKid names anyone. Across 1,192 help articles from the other four, ACRCloud appears 0 times.

Distributor Accepts AI music Names its detector What detection produces Published limit Read at source
DistroKid Yes, under four rights rules ACRCloud Informational AI tag passed to platforms None stated 6 Nov 2026
UnitedMasters Yes No AI tag for audio, plus a separate cover-art tag Spam review on high volumes 5 Nov 2026
LANDR Yes, with exclusions No, "detection technology" only Caps enforced; no AI cover songs 20 or 60 tracks a month by tier 7 Nov 2026
TuneCore Yes No Nothing published; its AI programme is licensing, not screening None stated 6 Nov 2026
CD Baby Policy not stated in its help centre No Nothing published None stated 7 Nov 2026

Table of what the AI tag does and does not do, from DistroKid's own help article created 2 November 2026 and edited 6 November. The tag appears when an independent service called ACRCloud flags a track as potentially AI-generated. It is informational and does not affect distribution through DistroKid. The track still goes out to all streaming platforms and the tag works like metadata. Each streaming platform decides how it displays and handles AI-generated music. DistroKid states that third-party detection tools are not perfect and provides a form for an incorrect ACRCloud flag. The distributor's own published position: the output is a tag, not a rejection.

Screenshot of the DistroKid Help Center article headed Why does my track have an AI tag, stating that an AI tag appears when an independent service called ACRCloud flags a track as potentially AI-generated, that the tag is informational and does not affect distribution through DistroKid, and that each streaming platform decides how it displays and handles AI-generated music. DistroKid's help article, the first time a major distributor named its detector.

The practical consequence is that the question worth asking has changed. It is no longer will this pass, it is what will the tag do once it arrives, and that answer belongs to Spotify, Apple and the rest rather than to your distributor. Our DistroKid vs TuneCore vs CD Baby comparison covers the choosing question; this page covers the mechanism.

DistroKid is the only major distributor that names its detector

On 2 November 2026 DistroKid published a help article called Why does my track have an AI tag, and edited it again on 6 November. It is the first time any major distributor has named the service doing the screening:

"Some streaming platforms now require distributors to identify AI-generated music. An AI tag gives you visibility into how those platforms may display your music. It appears when an independent service called ACRCloud flags a track as potentially AI-generated."

Three more things in that article are worth having in front of you. The tag "works like metadata, so it doesn't affect distribution". Using AI is explicitly fine — "Nope, and there's nothing you need to do" — because DistroKid simply passes the information on. And DistroKid states the limitation itself: "Third-party detection tools aren't perfect", with a correction form for a wrong flag and a stated turnaround of "typically within 24-48 hours".

How unusual that is becomes clear when you look at the others. Pulling the full help corpora — 237 TuneCore articles, 190 from CD Baby, 463 from LANDR, 302 from UnitedMasters — and searching all 1,192 of them returns ACRCloud 0 times, IRCAM 0 times, and the word "classifier" 0 times. One ranking competitor states that TuneCore licenses IRCAM Amplify's detection pipeline into its intake API. TuneCore's own help centre does not mention IRCAM at all. Our IRCAM Amplify explainer covers what that vendor actually sells and to whom.

What ACRCloud publishes about its own accuracy

Because DistroKid named a vendor, the vendor's published numbers are now relevant to a DistroKid upload in a way no competitor's guesswork was. ACRCloud documents its AI detection in its developer docs rather than on its marketing pages, which is why buyer's-guide writers consistently report that it publishes nothing.

It publishes a full confusion matrix: precision 99.98%, recall 99.88%, a false positive rate of 0.08% of human material and a false negative rate of 0.12% of AI. The decision rule is a 50% threshold — at or above, the output is ai_generated; below, human — and there is a 15-minute (900-second) file limit. It also breaks accuracy down by generator.

Table of ACRCloud's published accuracy by source, from its own internal test data at a 50% threshold. Lyria 99.97%, human 99.93%, udio 99.82%, mureka 99.76%, suno 99.70%, minimax 99.60%, elevenlabs 98.95%, treblo formerly sonauto 97.70%, riffusion 97.49%, seedmusic 97.12% and boomy 96.37%. The vendor's own figures on its own test data. A peer-reviewed July 2026 paper puts baseline detectors at AUC 0.817 on Suno v5 once the audio is speed-modified.

Source Published accuracy Source Published accuracy
lyria 99.97% minimax 99.60%
human 99.93% elevenlabs 98.95%
udio 99.82% treblo (prev. sonauto) 97.70%
mureka 99.76% riffusion 97.49%
suno 99.70% seedmusic 97.12%
boomy 96.37%

Read the vendor's own caveat before you read the numbers, because it is doing a lot of work: the figures are "based on ACRCloud's internal evaluation dataset for the current model version", they "reflect performance on internal test data and are provided for reference only", and "Actual performance may vary depending on audio quality, transformations, compression" and on mixing and editing.

The AI music detection number that matters is measured after processing

That caveat is the whole story, and independent research has now measured the size of it. A paper submitted on 29 July 2026, Improved Robustness in AI-Generated Music Detection (arXiv:2607.27454), tests detectors against simple audio manipulation rather than clean platform downloads.

On Suno v5 under speed modification, the baseline detector it compares against scores AUC 0.817 and F1 0.675. The same family of detector, trained clean and tested on altered audio, collapses to F1 0.008. The paper's own scale-invariant approach holds AUC 0.997 and F1 0.986, which is the useful part: the weakness is fixable, so expect the gap to close rather than treating it as permanent.

UnitedMasters publishes the pipeline the others keep private

UnitedMasters created an article called AI Tagging on Streaming Services on 29 October 2026, and it is the only published description of a distributor's internal flow. It has two stages, and the second one is a person: "First, the file is automatically scanned by a tool to detect AI. Then, your file is delivered to our review tool, where it's reviewed by a human on our team."

It also separates the audio from the artwork, which nobody else does in writing. Cover art is tagged manually by the artist at submission, then reviewed by the UnitedMasters team, and the release can carry an AI tag for artwork independently of the audio. Artists are emailed the first time a track is tagged, and can see tags against the release in their account.

Most usefully, UnitedMasters is the one distributor that states what the tag does downstream, naming platforms: TIDAL "has announced that fully AI-generated tracks will be excluded from royalty payments"; TIDAL and Qobuz are described as "potentially banning AI tracks from editorial and algorithmic playlists"; while "some services like Spotify and Apple Music are focused on simply distinguishing AI-generated music from human-generated music". That is the clearest published map of where a tag actually costs you something. For the Spotify end of it specifically, see our Spotify AI music detection breakdown.

LANDR puts a number on AI music, and it is a cap, not a score

LANDR's AI article was last edited on 7 November 2026, the day this page was rebuilt, and it is the only distributor publishing a hard number. The number is not an accuracy figure or a threshold. It is a volume limit, framed as anti-spam: LANDR "limits the number of AI-generated tracks that each subscriber may submit per month" and says it uses "detection technology to identify AI-generated songs", without naming it.

Table of LANDR's monthly AI track cap by plan. Distribution ALC, Basic and Mobile allow 20 AI tracks per calendar month, as do Studio Mobile and Studio Essentials. Distribution Pro, Distribution plus Mastering, Studio Standard and Studio Pro allow 60. The only hard number any distributor publishes, and it is a submission cap rather than an accuracy score.

LANDR plan AI tracks per calendar month
Distribution ALC, Basic, Mobile 20
Studio Mobile, Studio Essentials 20
Distribution Pro 60
Distribution + Mastering 60
Studio Standard, Studio Pro 60

Exceeding the cap "may result in processing delays, removal of excess submissions, or restrictions on future uploads". Two further LANDR rules are worth copying down because they are absolute rather than graded: it does not distribute AI-generated cover songs at all, and it lists platforms that do not accept AI-generated music through it — YouTube Content ID, Meta, TikTok, Deezer, Lissen, Pandora and Tencent. Losing YouTube Content ID is the one most people do not see coming, because it is enrolment rather than distribution.

Disclosure and detection are two different systems

A lot of confusion in this topic comes from collapsing two separate things. Detection is something done to your file by a scanner. Disclosure is a field you fill in, and the rules for it are much narrower than most producers assume.

DistroKid's AI Credits article, updated on 2 November 2026, draws the line precisely. You add AI credits if part of the track was generated by AI: "AI-generated audio (vocals, instrumental tracks, etc.)", "AI-generated lyrics (not written by a human)", or "AI-generated compositions (melody or arrangement not composed by a human)". You do not need them if you used AI as a tool — the article names "Pitch correction, auto-tune, etc.", "AI-assisted mixing or mastering" and "AI-assisted workflows".

So the obligation is to declare generated creative content, not to declare that software was involved. An AI mastering chain is not a disclosable event; an AI vocal is. DistroKid names the three platforms currently showing this to listeners as Spotify, Apple Music and YouTube, and our family site keeps a running list of which platforms accept AI music as those rules move. This is also why the honest answer to "can I stop the label" is no, from anyone: the tag is metadata your distributor transmits, and the generator side of it is moving too — Suno confirmed its own provenance marking on 6 August 2026.

What a court filing asked for, and what it does not establish

There is a second reason the word ACRCloud matters this month, and it needs stating carefully. On 14 October 2026, Universal and Sony moved in federal court in Manhattan to enforce a subpoena against DistroKid in their copyright case against Suno, which is itself pending in Massachusetts. Reporting by Music Business Worldwide on 2 November sets out what they asked for.

The labels want monthly figures for how many recordings DistroKid delivered, how many it tested, and how many its model scored as likely AI-generated, plus streams and royalties for those. They describe DistroKid's 9 October response as referring to a third-party "prediction model" used to test tracks for AI generation, and they specifically ask for the name and vendor of that prediction model, along with the basis for DistroKid's statements about false positives. In a joint filing approved on 28 October the parties told the court they were "working on a resolution".

Here is the part to be careful about. DistroKid's help centre named ACRCloud on 2 November, and the court filing seeking a vendor name was pending at the time. That is a sequence, not a cause. Nothing published establishes that the service named in the help centre and the prediction model described to the court are the same thing, and no threshold or accuracy figure for DistroKid's own deployment is public either way. Note also that scoring as likely AI-generated is not a finding of infringement, and DistroKid is a third party in that case, not a defendant.

What this means for a Suno track tonight

Three things follow from the sources above, and none of them is the advice this topic usually attracts.

First, stop optimising for a rejection that the published policies do not describe. Your distributor is not the gate. Spend the attention on the four rules DistroKid actually enforces — own 100% of the rights, no impersonation, no mass-generated spam, no infringement — because those are the ones that get releases pulled. Our DistroKid AI screening page goes through them, and why AI music gets flagged covers the false-positive side for producers in genres that share statistical features with generated audio.

Second, be clear about what processing can and cannot do. Cleaning up generation artifacts is a real and worthwhile job — it is the layer that detector tools score, and Undetectr is built for it. But it does not touch the label. The tag is metadata, transmitted by your distributor alongside the audio, and no audio processing reaches it. Anyone selling you otherwise is selling something that does not exist.

Third, and most importantly: screening is rarely the actual wall. The genuinely hard problem for AI releases is that nobody is listening, which no classifier causes and no cleanup fixes. Once a track is finished and out, the routes that do not depend on algorithmic discovery are selling direct to people who already know you and pitching for paid sync placements in film, TV, games and ads — which is what played.fm is for. That is a different problem from this page's, and it is the bigger one.

Frequently asked

Questions readers ask.

Not at the distributor, on the published evidence. DistroKid states that an AI tag is informational and does not affect distribution through DistroKid, and UnitedMasters delivers tagged releases to stores. What the tag changes is downstream: each streaming service decides how it displays and handles AI-generated music.

ACRCloud. DistroKid's help article Why does my track have an AI tag, created on 2 November 2026 and edited on 6 November, says a tag appears when an independent service called ACRCloud flags a track as potentially AI-generated. No other major distributor names a vendor anywhere in its help centre.

ACRCloud publishes 99.98% precision and 99.88% recall for AI, at a 50% decision threshold, and says plainly that these results reflect performance on internal test data and are provided for reference only. Independent work finds far lower numbers once audio has been altered.

DistroKid publishes a correction form and says third-party detection tools are not perfect. It reviews submissions and replies by email, typically within 24 to 48 hours, and tells streaming platforms if the tag should not be there. UnitedMasters also accepts appeals on AI tags.

No, they are separate systems. Detection is a scan your distributor runs. Disclosure is a field you fill in: DistroKid's AI Credits cover AI-generated audio, lyrics and compositions, and are explicitly not needed for pitch correction, auto-tune, AI-assisted mixing or mastering, or AI-assisted workflows.

LANDR does, and it publishes the table. It caps AI-generated submissions at 20 tracks per calendar month on its entry tiers and 60 on Pro and Standard tiers, and says exceeding the cap may cause processing delays, removal of excess submissions, or restrictions on future uploads.

There is no published basis for expecting one. No distributor publishes its threshold, its retry behaviour or whether scores are cached, so anyone telling you a second upload scores differently is guessing. The documented route for a wrong tag is the correction form, not a re-upload.

The verdict, in one sentence: Undetectr.

Undetectr targets the generation artifacts and the signal layer that screening tools score. It does not change how any platform labels a release — that label rides in metadata your distributor sends, and no audio processing touches it.