Free tools for your next audio edit
Find a song’s BPM. Estimate. Listen. Check.
Choose a short, rhythmic MP3 or WAV section and estimate its tempo locally. Compare the result with the beat you hear; automatic detection can be wrong.
Estimate a song’s BPM
Free · localChoose a supported file. No audio upload or account required.
A rhythmic, steady section works best. The algorithm searches approximately 60–200 BPM and can return the wrong tempo, including half or double the beat you hear. Silence, ambient sounds, syncopation, changing tempos and mixed rhythms can prevent a useful estimate or produce a misleading result. This analyzes one channel and does not identify the song, key, time signature or beat-grid positions. Browser decoding support varies.
Listen, estimate, verify
How to find a song’s BPM
- 01 / CHOOSE
Choose an audio file
Select a mono or stereo MP3 or WAV up to 50 MiB and five minutes. The browser reads it locally. Codec support varies.
- 02 / ANALYZE
Pick a rhythmic section
Enter a start time in seconds and analyze up to 30 seconds. At least eight seconds must remain. Choose a passage with a clear, steady beat instead of a long quiet introduction.
- 03 / CHECK
Tap and compare
Listen to the recording and compare the estimate with the pulse you hear. Try a different section and check the half-time or double-time interpretation before using the result in an edit.
Understand the number
What does the BPM estimate mean?
BPM is beats per minute. The analyzer looks for patterns of note or percussion onsets in one decoded audio channel and estimates a periodic pulse between approximately 60 and 200 BPM. It is an estimate for the selected section, not a measurement of every beat across the complete song. The displayed decimal does not imply that the result is accurate to a tenth of a beat.
A groove heard at 80 BPM can also contain a strong 160 BPM subdivision. The two numbers can describe different ways of counting the same timing. Half and double values shown here are calculated alternatives, not separate detections. The analyzer can also give a completely unrelated result, particularly for syncopated, ambient or changing-tempo audio.
Compare with the tap-tempo calculator by tapping the beat you intend to count. The guide to finding a song’s BPM also explains manual counting and beat-grid checks. Then line up several bars against a grid or metronome in your editor and listen for drift. A single BPM cannot fully describe a performance whose tempo changes.
Choose a better test
Why might a BPM result be wrong?
Quiet introductions, long notes, irregular rhythms, prominent subdivisions and multiple overlapping pulses can confuse tempo detection. Use a longer, rhythmically clear section and compare another part of the same track. A rejection does not prove there is no beat, and an estimate does not prove there is one.
For stereo audio the tool analyzes the louder channel in the selected section, rather than averaging channels that could cancel each other. It does not identify the song, detect its musical key or time signature, provide beat positions or synchronize a project. Use audio speed changer only after deciding the original and target tempos; its calculator does not measure BPM.
Analysis uses music-tempo 1.0.3 by killercrush, an MIT-licensed BeatRoot-based implementation. License notice. The browser downloads the tool code but does not upload your selected audio.
A few useful answers
Free song BPM finder questions
How do I find the BPM of a song?
Choose a supported MP3 or WAV and enter the start time of a steady, rhythmic section. Analyze up to 30 seconds, then tap along and compare the estimate with a beat grid. At least eight seconds must remain.
Why is the BPM half or double what I expected?
A detector can follow a different pulse or subdivision. A groove felt at 80 BPM may contain a strong 160 BPM pattern. The displayed half and double values are arithmetic alternatives, not independent detections.
Is the BPM estimate always accurate?
No. Quiet or nonrhythmic audio, syncopation, changing tempos and competing pulses can produce a wrong estimate or no result. The analyzer attempts approximately 60–200 BPM; check the actual recording and several bars in your editor.
Is my audio uploaded?
No. The browser decodes and analyzes the selected file locally. The tool does not save it for later or identify the song.
What files are supported?
Supported mono or stereo MP3 and WAV files up to 50 MiB and five minutes. Browser codec support varies. Choose a section with at least eight seconds remaining; analysis uses at most 30 seconds of one channel.
After preparing your audio