What BPM is this song? Drop it and see.
Autocorrelation over the onset envelope, right in your browser: a tempo, a confidence score, and a tap-to-verify button for when the machine and your foot disagree.
Nothing is uploaded — your audio never leaves your device.
This guesses one global tempo. The studio knows the grid.
Autocorrelation can octave-flip and can't follow tempo drift — that's the method, not a bug. The studio's engine heard the whole song: it locks the real grid and batch-tags your entire library with BPM and key. Sign up: 3 full packs free.
Frequently asked questions
How do I find the BPM of a song?
Drop the audio file into the tool. It builds an onset-energy envelope, autocorrelates it, and reports the strongest tempo between 60 and 200 BPM with a confidence score. Verify with a few taps if the confidence runs low.
Why does it sometimes show half or double the real BPM?
Octave ambiguity is baked into every autocorrelation detector: the pattern at 87 BPM also repeats at 174. The tool prefers the 70–180 range and shows both octaves when in doubt — your ears break the tie in two taps.
Does it work on songs without drums?
Poorly, honestly. The method needs rhythmic energy to correlate; ambient pads and rubato piano give it very little. That's exactly the material where the studio's full-song analysis earns its keep.
Is my file uploaded to analyze it?
No — decoding and analysis happen entirely in your browser. A four-minute MP3 takes about a second on a laptop.