How to use this workflow
Load at least ten seconds
Choose a supported local audio file with a clear rhythmic passage. The analysis requires at least ten seconds of audio.
Read the estimate and candidates
Wait for the analysis result. Check the main BPM, confidence information and alternative tempos where available. Silence or an unclear pulse can produce an unknown result.
Check with a metronome
Set the metronome to the suggested value and count with the recording. If every second click feels like the main beat, consider the half-time candidate before changing playback speed.
Why 70 and 140 BPM can both appear
A repeating pattern may support more than one interpretation of the beat. Counting every other pulse gives half the tempo; counting subdivisions gives double. A detector cannot always know which pulse a musician would use for a particular arrangement.
Use the musical phrase, drum accents and your practice goal to choose. A 140 BPM reading should not be described as twice as accurate as 70 BPM merely because its number is larger.
What this estimate covers
The tempo analyzer evaluates a limited analysis window, between ten and sixty seconds depending on the input, with tempo hypotheses from 40 to 240 BPM. It does not create a beat-by-beat tempo map for the entire recording.
Live performances, rubato, long introductions and tempo changes can make a single value misleading. Confidence is an algorithmic score, not a measured percentage of songs identified correctly. For a difficult passage, try Tap BPM or trim a representative section first.
Common questions
Will it identify every song correctly?
No. Dense mixes, weak attacks, silence and changing tempo can produce ambiguous or unknown results. Confirm important edits by listening.
Does detecting BPM change the file?
No. This page analyzes the recording. Use the speed changer to create an audio file with a different tempo.