AI Song Checker

How to check a song

The workflow takes under a minute. Drag an MP3, WAV, M4A, FLAC or OGG file onto the panel above, or pick it from your device. Your browser decodes the audio locally, samples several sections spread across the track, and measures each one.

You then get a report rather than a label: an estimated AI probability with a plausible range around it, a confidence level, a plain-language explanation of every measurement that contributed, and an explicit statement of what the result cannot establish.

• Upload a file of at least ten seconds — longer is materially better
• Prefer the highest-quality version you have; a 320 kbps MP3 or a WAV beats a 96 kbps rip
• Avoid clips that are mostly silence, speech, applause or crowd noise
• Check more than one section of a long track if the first result is inconclusive

Reading the result properly

The single most common mistake is reading a percentage as a verdict. A 78% estimate does not mean the track is 78% AI, nor that there is a 78% chance it is AI in any calibrated statistical sense. It means the measured signals lean that way by roughly that much, given an analysis engine that has not yet been validated against a labelled dataset.

That is why every result carries a range instead of a bare number, and why the checker caps its own output between 15% and 85%. A tool that returned 99% would be claiming a precision no acoustic detector currently has.

Confidence is a separate axis and matters just as much. A high probability with low confidence — usually because the sampled sections disagreed, or the file was heavily compressed — is much weaker evidence than a moderate probability with high confidence.

What the checker cannot tell you

It cannot name the generator. It cannot separate AI vocals from AI instrumentals. It cannot prove authorship, and it is not forensic evidence. It cannot see through heavy remixing, re-recording or aggressive mastering, and it cannot recognise a specific song or artist because it holds no database at all.

It is also asymmetric: much better at raising suspicion than at clearing a track. A 'likely human-created' result is the absence of a signal, not a certificate of authenticity.

Privacy

Nothing is uploaded. Decoding and analysis both run inside your browser tab using the Web Audio API, so no copy of your music reaches our servers. Deletion is automatic in the strongest sense — the decoded audio lives in memory only for the duration of the analysis and is discarded when you remove the file or close the tab.

There is no account, so there is no history of what you checked and no profile attached to it.