AI Music Detector Tools: Whose Verdict Follows Your Release

Three of the free AI music detectors in every 2026 roundup are the same engine behind different front doors, and it is the engine DistroKid names in its own help centre.

Filed 2026-05-21 Read 11 min Method How we work
In short
  • The short version: one engine decides most of what happens to an independent release. DistroKid names ACRCloud as the service behind its AI tag, and ACRCloud runs the same engine on a free public page at three checks a day.
  • Three of the free checkers in the roundups — ACRCloud's own page, AHA Music and The Ghost Production — are that same ACRCloud engine with different rate limits and upload caps.
  • ACRCloud publishes a 50% decision threshold and per-generator accuracy from 99.97% on Google Lyria down to 96.37% on Boomy. IRCAM Amplify publishes 99% with no test set named, and Vobile publishes no figure at all.
  • Every published accuracy figure describes raw generator output. A July 2026 paper measures a strong baseline detector falling to AUC 0.81 and F1 0.67 on Suno v5 once the audio is speed-modified, and states that EQ, dynamic range compression and codec compression remain untested.
  • Two tools that circulate in 2026 roundups, AISonic Detector and AICompose, could not be found as products. The earlier version of this page ranked both of them; they are gone.
An abstract audio waveform passing through a fine analysis grid that lights green where the grid reads it, with spectral bands above, illustrating how AI music detector tools score a track

Search ai music detector tools and you get a dozen lists of eight to ten products, each with an accuracy percentage beside it, and almost none of those percentages comes from a test anyone can inspect. That matters more in November 2026 than it did in May, because two weeks ago a major distributor said out loud which detector it runs — and it turned out to be an engine you can point at your own file, free, before you upload anything.

This page was rebuilt on 10 November 2026 from the vendors' own pages, their developer documentation, one distributor's help centre and two peer-reviewed papers. Every figure below names its source and its date. Where a vendor publishes a number without saying what it was measured on, the table says that instead of repeating the number as a fact.

What a detector verdict actually does to your release

Most tool roundups imply a gate: a detector scores your track, the score is too high, the release is refused. At the distributor layer in 2026, that is not what happens.

DistroKid's help article Why does my track have an AI tag? — created 2 November 2026, edited on 6 November — is explicit: "The tag is informational. It doesn't affect distribution through DistroKid." And then, in its own FAQ voice: "I did use AI. Is that a problem? Nope." The track still goes out to every platform; the tag travels with it as metadata, and each streaming service decides what to do with it.

So the practical question is not which detector is cleverest. It is whose verdict is attached to your release and travels downstream — and only one vendor is currently in that position by name. The full distributor-by-distributor picture is on our AI music detection page, and the two-layer mechanism underneath all of these tools is covered in how AI music detectors work.

The 2026 detector landscape in one table

Eight tools, three audiences. The split that matters is not free versus paid, it is whether the tool takes a file you hand it, a playlist you own, or a catalogue you operate.

Tool Who it is for Access and limits What it publishes Read at source
ACRCloud AI Music Detector Anyone, then platforms via API 3 free checks a day, no signup, 20 MB, 60s is enough Confusion matrix, per-generator accuracy, 50% threshold 10 Nov 2026
AHA Music Anyone 5 free detections a day, files to 99 MB Nothing of its own — "Powered by ACRCloud" 10 Nov 2026
The Ghost Production detector DJs, producers, labels Free, no registration Nothing of its own — "powered by ACRCloud" 10 Nov 2026
SubmitHub AI Song Checker Artists pitching to curators Free, search, link or file upload Method, version (v4.3), accuracy claim, false-positive causes 10 Nov 2026
Deezer AI Music Detector Listeners and curators Free, 27 languages, 20 streaming platforms 99.8% on 100% AI-generated music, 13.4m tracks tagged in 2025 10 Nov 2026
IRCAM Amplify AIMD DSPs, distributors, labels, PROs Request access, REST API/SDK, no public price 99% accuracy, under 1% false positives, 250,000 tracks an hour 10 Nov 2026
Vobile AI Song Detector (Pex) DSPs, distributors, labels, societies Sales-led demo, no public price No accuracy figure; benchmarks on request 10 Nov 2026
lofcz/ai-music-detector Developers MIT licence, self-hosted, ONNX model Full confusion matrix on a stated 17,866-sample test set 10 Nov 2026

Two things fall out of that table immediately. The free end of the market is less crowded than it looks, and the expensive end publishes less than the free end does.

Table of the 2026 AI music detector landscape. ACRCloud's AI Music Detector is for anyone and then platforms via API, allows 3 free checks a day with no signup at 20 MB, and publishes a confusion matrix, per-generator accuracy and a 50 percent threshold. AHA Music allows 5 free detections a day on files to 99 MB and publishes nothing of its own, stating it is powered by ACRCloud. The Ghost Production detector is free with no registration and also publishes nothing of its own, stating it is powered by ACRCloud. SubmitHub's AI Song Checker is free by search, link or file upload and publishes its method, version 4.3, an accuracy claim and false-positive causes. Deezer's AI Music Detector is free in 27 languages across 20 streaming platforms and publishes 99.8 percent on 100 percent AI-generated music and 13.4 million tracks tagged in 2025
Two of the five publish nothing of their own and say so, so a second opinion from either is the same engine answering twice.

Three of the free checkers are the same engine

AHA Music's detector carries the line "Powered by ACRCloud" at the top of the page. The Ghost Production's free detector describes itself as "completely free and powered by the reliable industry provider ACRCloud." And ACRCloud's own page says the free checks "run on the same detection engine as the API."

That is one model with three front doors, and the only real difference between them is the meter: three checks a day on ACRCloud's page, five on AHA Music, 20 MB against 99 MB on the upload cap. A roundup that ranks them as three separate tools with three separate accuracy scores is ranking the same classifier three times.

It also means the free check is not a rough approximation of the thing that screens you. If your distributor is DistroKid, the engine on that free page is the engine whose output gets attached to your release — the one difference being that the API version runs in batch, returns per-stem results and feeds upload gating, where the public page does one file at a time.

That is as close as an independent artist gets to seeing the decision before it is taken, and no competing roundup on this query says so.

What ACRCloud publishes, generator by generator

ACRCloud is also the only vendor here that documents its own decision rule. From its developer FAQ: the threshold is 50% — at or above ai_probability, the output is ai_generated; below it, human — files are capped at 15 minutes (900 seconds), and both the probability and the per-source scores are "generated directly by the model and are not manually adjusted."

The binary confusion matrix reads 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 per-source numbers are more interesting, because they are not flat:

Source category Published accuracy Source category Published accuracy
human 99.93% minimax 99.60%
lyria (Google) 99.97% elevenlabs 98.95%
udio 99.82% treblo (ex-Sonauto) 97.70%
mureka 99.76% riffusion 97.49%
suno 99.70% seedmusic 97.12%
— — boomy 96.37%

Lyria and Boomy were added in an engine upgrade published 1 September 2026, and they sit at opposite ends of the range. ACRCloud attaches its own caveat in the same document: these figures "reflect performance on internal test data and are provided for reference only," and real performance varies with "audio quality, transformations, compression, mixing, editing." That is a vendor telling you the number does not survive mastering, which is more than any competitor here does.

Table of ACRCloud's published per-source accuracy. Human 99.93 percent, lyria from Google 99.97, 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 percent
ACRCloud's own figures on its own internal evaluation data at a 50 percent threshold, not an independent benchmark.

The enterprise tier publishes claims, not benchmarks

IRCAM Amplify has rebuilt its site around AIMD, and the headline is unambiguous: "99% accuracy", "Less than 1% false positives", "The world's most accurate solution to detect AI-generated music", scanning "more than 250.000 tracks within 1 hour, depending on server capacity." What the page does not contain is a dataset, a threshold, a date or a route to try it: access is by request, for DSPs, distributors, labels, CMOs and publishers. Our IRCAM Amplify explainer goes through what is and is not knowable about it.

Vobile's AI Song Detector, the former Pex product, is the same shape with one more layer of distance. It names the generators it covers — Suno, Udio, Boomy, ElevenLabs — claims "higher overall accuracy compared to leading competitors" and a "zero day readiness" that "can often detect new models on the very first day," and then gates the evidence: "Contact us to run a custom test." No percentage appears on the page at all.

Both are plausible systems. Neither is checkable, and the asymmetry is worth naming: the two vendors selling to the companies that decide your release publish less about their accuracy than the free page and the MIT-licensed repository do. The research literature says it more bluntly. The ISMIR 2025 paper A Fourier Explanation of AI-music Artifacts observes that "AI-detection services have emerged, yet these systems remain largely opaque and privately controlled, mirroring the very issues they aim to address."

The one detector whose source you can read

lofcz/ai-music-detector is an MIT-licensed model, training and inference scripts, and a library for detecting Suno up to v5 and Udio up to v1.5. It works on the spectral artifacts that neural vocoder deconvolution layers leave behind, which is the mechanism the Fourier paper above proves is architectural rather than a property of training data.

It publishes what a vendor does not: accuracy 99.88% on a held-out test set of 17,866 samples (5,741 real, 12,125 AI-generated), precision 0.9985, recall 0.9998, F1 0.9991, a false positive rate of 0.31% and a false negative rate of 0.02%. The constraints are equally explicit — audio resampled to 16 kHz, "works best with 10+ seconds of audio" — and the README states the obvious limit on any detector of this kind: it "needs retraining on new generations of AI music generators."

The cost is operational, not financial: a .NET toolchain to run the released model, or Miniconda, a CUDA GPU and roughly 200 GB of disk to train your own. For most artists that is the wrong tool. For anyone arguing about whether these systems work, it is the only one of the eight where the argument can be settled by reading the code.

Every published number describes raw output

Here is the problem with the whole column of percentages above: they are all measured on files straight out of the generator.

Figure Published by Test material named? Condition measured
Precision 99.98% / recall 99.88% ACRCloud developer docs Internal evaluation data only Unaltered submissions
99% accuracy, under 1% false positives IRCAM Amplify site No Not stated
99.8% accuracy Deezer press release, 11 June 2026 No — scoped to "100% AI-generated music" Catalogue scanning
"More than 99% accurate" SubmitHub AI Song Checker page Own plus third-party industry tests, not published Downloads straight from an AI platform
Accuracy 99.88%, FPR 0.31% lofcz open-source README Yes — 17,866 held-out samples Unaltered, 16 kHz, 10s+
AUC 1.000 on Suno v3.5, v5, Udio v120 arXiv:2607.27454, 31 July 2026 Yes — 5,000 tracks per generator Clean audio
AUC ≈0.81, F1 ≈0.67 on Suno v5 arXiv:2607.27454, same baseline Yes After speed modification

That last pair is the finding. Improved Robustness in AI-Generated Music Detection tests a strong published baseline on 5,000 Suno v5 tracks against 5,000 human tracks from FMA-small, and states the result in its abstract: existing detectors "exploit these artifacts with near-perfect accuracy on raw generated tracks, but their performance collapses under simple audio manipulations, such as speed modification or pitch shifting." Clean, the baseline scores AUC 1.000. Speed-modified, it falls to roughly 0.81 AUC and 0.67 F1. Pitch shifting is harder still: the same baseline drops to 0.771 AUC on Suno v5, and the paper's own scale-invariant method, which holds 0.997 AUC under speed change, falls to an F1 of 0.279 on pitch-shifted Suno v5.

The paper's own limits section is the part to keep: "Other common manipulations (equalization, dynamic range compression, codec compression) remain untested." Those three are precisely what a mastering chain does. So the honest reading of every figure in this article is that it describes a file nobody has mixed yet — which is also why Undetectr is pointed at the artifact and signal layer rather than at the label: the layer these classifiers score is a property of the audio, and it is the only part of this chain a producer can actually change.

Table of every published detector figure against what it was measured on. ACRCloud's developer docs give precision 99.98 percent and recall 99.88 percent on internal evaluation data only, for unaltered submissions. IRCAM Amplify's site claims 99 percent accuracy with under 1 percent false positives, naming no test material and no condition. Deezer's 11 June 2026 press release gives 99.8 percent accuracy, scoped to 100 percent AI-generated music, for catalogue scanning. SubmitHub's page claims more than 99 percent accurate from its own and third-party tests that are not published, on downloads straight from an AI platform. The lofcz open-source README gives accuracy 99.88 percent and a false-positive rate of 0.31 percent on a named 17,866 held-out samples, unaltered at 16 kHz and 10 seconds or more. arXiv paper 2607.27454 of 31 July 2026 reports AUC 1.000 on Suno v3.5, v5 and Udio v120 across a named 5,000 tracks per generator on clean audio, and the same baseline falls to AUC about 0.81 and F1 about 0.67 on Suno v5 after speed modification
The last two rows are the same baseline on the same tracks. Only the condition changed.

Why a human-made track comes back as AI

False positives on this cluster are not mysterious, because one vendor documents them. SubmitHub's AI Song Checker runs two analyses — spectral, which it calls "our most reliable method", and temporal, which "struggles with shorter songs or low-quality audio" — and then publishes the four things that make a human song read as synthetic:

That last one is the trap worth stating twice: using an AI mastering service on a human performance can push a human track over an AI detector's threshold. SubmitHub's own posture is the right one to copy — "A result is a probability, not proof. Please don't use it to accuse anyone" — and it runs a feedback loop, marking results inaccurate feeds the next version, currently v4.3. Our SubmitHub explainer covers what its score gates and what it does not.

If the flag is already on a live release rather than a test upload, the route is the distributor's, not the detector's: DistroKid publishes a correction form, concedes that "third-party detection tools aren't perfect", and says it will tell platforms "right away" if the tag should not be there.

Two tools in the roundups that do not exist

Two names recur in 2026 detector lists: AISonic Detector and AICompose Detection Score, usually with accuracy figures around 80% and 71%. Checked in October and again on 10 November 2026, neither can be found as a product — no vendor page, no repository, no model card, no documentation, and no independent benchmark. Their domains are parked.

The uncomfortable half of that finding is that the pages carrying those two names on this query are largely ours, including the earlier version of this page. They are gone from it. The test is cheap enough to apply to any tool in any roundup, including this one:

Check What a real tool has What a phantom has
Vendor page A live domain with a product, pricing or access route A parked domain or nothing
Documentation A threshold, a file limit, an output format A paragraph in someone else's listicle
Evidence A named test set or a stated caveat A round percentage with no source
Provenance A company, a repository or a paper behind it A name that only appears in roundups

Run that on the eight tools in this article and only two pass all four columns: ACRCloud and the open-source model. That is the actual state of the AI music detector market in November 2026.

What to run before you release

The workflow that follows from the evidence is short, and three of its four steps are free.

Step Tool What it tells you What it does not
1. Screen the master ACRCloud free page, 3/day The probability and likely engine your distributor's tag will come from Whether a platform will label the release
2. Cross-check SubmitHub, free A second opinion from a different method, plus a false-positive read Anything about distributor behaviour
3. Check part-AI mixes ACRCloud, per segment and per stem Which section or stem is scoring, vocals separately from backing A segment-level number from any other vendor
4. Audit a playlist Deezer's free detector Which tracks in a streaming playlist are flagged, across 20 platforms Nothing, for a file you have not released

Two caveats to carry out of here. A detector score is not a platform label — the labels come from declarations your distributor sends, which is the gap covered on our Deezer detection page and in the part-AI vocals analysis. And clearing a screening check does nothing about the actual constraint on an independent release, which is that nobody is listening yet: that is what a storefront and a paid sync route are for, and it is a different problem from this page's.

Detection in 2026 is one engine, published once, measured on clean files. Everything else on this query is marketing or arithmetic nobody has shown you.

Frequently asked

Questions readers ask.

Nobody can answer that from published evidence, because no two vendors test on the same material and only one publishes its test set. ACRCloud publishes 99.98% precision and 99.88% recall on its own internal data, IRCAM Amplify advertises 99% with less than 1% false positives and names no dataset, and an open-source project publishes 99.88% on a stated 17,866-sample split. Those are three different measurements, not a ranking.

Yes, several, and three of them are the same engine. ACRCloud's own page gives three checks a day with no signup, AHA Music gives five and accepts files up to 99 MB, and SubmitHub's AI Song Checker is free with no stated daily cap. Deezer's free tool is different in kind: it scans streaming playlists rather than files you upload.

DistroKid is the only major distributor that names one. Its help article on AI tags, created 2 November 2026 and edited on 6 November, says the tag appears when an independent service called ACRCloud flags a track as potentially AI-generated. The other four majors describe detection without naming a vendor anywhere in their help centres.

The main ones try. ACRCloud returns source probabilities across eleven categories including Suno, Udio, Treblo, Mureka, Riffusion, Seed Music, MiniMax, ElevenLabs, Lyria and Boomy. Vobile says it identifies the source model when confidence is strong, and SubmitHub names nine engines it detects. Treat attribution as a weaker signal than the binary call.

SubmitHub publishes the causes: compressed audio such as a streaming link or low-bitrate MP3, clips under 60 seconds, heavy processing like extreme compression or pitch correction, and AI mastering tools such as iZotope Ozone or LANDR leaving artifacts behind. Upload a WAV or 320 kbps MP3 of at least a minute before concluding anything.

Not at the distributor, on the published evidence. DistroKid states that the AI tag is informational and does not affect distribution, and that your track still goes out to all streaming platforms. What each streaming service then does with that tag is its own decision, and DistroKid publishes a correction form for an incorrect flag, answered typically within 24 to 48 hours.

ACRCloud is the only one publishing a method for it: the track is scored segment by segment, with vocals and accompaniment analysed separately, so you can see which part of a file is synthetic. Deezer's headline figure is explicitly about detecting 100% AI-generated music, which is a different question from a human song with a generated hook.

The verdict, in one sentence: Undetectr.

Undetectr works on the generation artifacts and the signal layer these classifiers score, before you submit anything. It cannot change how a platform labels a release: that label travels in metadata your distributor sends, and no audio processing touches it.