BPM Finder

No app needed Works instantly Nothing uploaded
Drag & drop or click to select

MP3, WAV, OGG, M4A · Max 30 MB / 12 min · file stays on your device

BPM Finder — analyze an audio file

This BPM finder reads the tempo and musical key of any song you give it. Drop in an MP3, WAV, OGG, or M4A file and it decodes the audio right in your browser, builds an energy envelope from the waveform, and finds the beat by autocorrelation — the same approach used by dedicated tempo-analysis software, running locally instead of on a server. Alongside the tempo it produces a chroma profile of the track and matches it against established key profiles, so you also get the song key and its Camelot wheel position.

Two things matter about how this works. First, your audio never leaves your device: the file is decoded by your own browser's Web Audio API and analyzed in a local Web Worker. Nothing is uploaded, nothing is stored, there is no account to create. Second, you are not limited to one number — real music often has tempo ambiguity, so when the detector finds a plausible reading at half or double the shown BPM, it offers those alternatives as one-click buttons, and you can always override the result by tapping the beat yourself in the panel above.

The analysis takes one to three seconds for a typical three-minute track. Larger files are downsampled first so the math stays fast, and a progress indicator shows each stage — decode, downsample, tempo, key — so you always know it is working.

Tap Tempo — find BPM by tapping

No audio file? Tap along with the beat instead. This is useful when you are hearing a track live, watching an online video, or working out the tempo of a melody in your head. Your taps turn the pulse you hear into a BPM estimate, so you can check music that is not available as a file. Open our tap tempo tool for the full browser-based tapper and detailed guidance.

What your BPM means — genre reference

Tempo is a strong hint about what kind of track you are holding. Electronic and dance genres cluster around hard conventions because DJs beatmatch; live genres spread wider. When a result appears above, the matching row in this table lights up.

BPM rangeTypical genres
60–69Ballads, downtempo, ambient, sleep music
70–89Hip-hop, boom bap, lo-fi hip-hop, reggae, dub
90–109Pop, R&B, soul, funk, old-school hip-hop
110–119Deep house, disco, afrobeats
120–127House, tech house, techno, electro
128–139Trance, progressive house, big room, dubstep (half-time)
140–159Trap (double-time feel), hardstyle, UK garage
160–180Drum & bass, jungle, hardcore
180–220Juke, footwork, extreme metal blast beats

If your result lands between genres, remember the half-speed / double-speed rule: a 140 BPM reading might really be a 70 BPM hip-hop track, and the one that matches the drums you actually hear is the right one. Electronic music is produced to these ranges on purpose — if a "house" track shows up at 96 BPM, it is probably halftime or the detector picked the wrong multiple.

How to read the results

BPM (beats per minute) is how many evenly spaced beats the track contains in one minute. A reading of 120 means 120 beats every 60 seconds, one beat every half second — count along with a clock and you can verify it by ear in ten seconds.

Half-speed / double-speed buttons exist because tempo has an octave ambiguity. A slow 70 BPM groove and its 140 BPM double-time reading are both internally consistent; snare placement usually decides which one people mean. The detector prefers the 70–180 range where most music lives, and shows the alternative so you can decide with your ears, not the algorithm.

Key and Camelot number: the key is the tonal center the track resolves to, major or minor. The Camelot number is a DJ-friendly code where each key gets a number from 1 to 12 plus A (minor) or B (major). Tracks with the same Camelot code mix cleanly, neighbors (8B→7B, 8B→9B) mix smoothly, and switching the letter on the same number (8A→8B) gives a brightening or darkening shift. That is the whole wheel system — no music theory required to use it.

Common questions

Does this work on mobile?
Yes. Both the file analysis and tap tempo run in your mobile browser. Analysis performance depends on your device — a three-minute song typically takes a few seconds on a recent phone. Tap tempo works even better on mobile since you can tap along anywhere.
Do I need to sign up?
No. There is no account, no login, no email. Open the page and use it.
Is my audio file uploaded to a server?
No. The file is decoded and analyzed entirely inside your browser using the Web Audio API and a local Web Worker. No audio data leaves your device, and nothing is stored after you close the page.
Which audio formats are supported?
Whatever your browser can decode: MP3, WAV, OGG, and M4A/AAC all work in Chrome and Edge; Safari adds support for more Apple formats. If a file fails to decode, convert it to MP3 or WAV and try again. The limit is 30 MB and 12 minutes per file.
Why might the BPM be off by a factor of two?
Rhythm has an octave ambiguity: the same track can be counted at 80 or 160 BPM depending on which pulses you follow. The detector prefers the 70–180 BPM range and offers the half/double alternative as a one-click button when it exists. Your ears make the final call.
What if the detection is inaccurate?
Check the confidence marker. Low confidence usually means the track has no clear beat (ambient, classical, field recordings). Two fixes: use tap tempo to measure the beat yourself, or try a section of the song with drums — most detections use the whole file, so a drum-heavy excerpt works well.
Can I analyze multiple files at once?
Not in this version — one file at a time. Click "Analyze another file" to start the next one.
Is this free?
Yes, completely. No limits, no account, no ads.

Related tools