How to use Manual BPM tap finder
- Listen to a beat and select Tap beat once on each beat.
- After the second tap, review the estimated BPM. Keep tapping at a steady pace to update the average.
- A tap less than 100 ms after the previous tap is ignored. A pause longer than 6 seconds starts a new measurement.
- Select Reset taps when changing the rhythm or starting another measurement.
How the number is calculated
The page records a local performance timestamp for each accepted button press. BPM equals 60,000 divided by the average interval in milliseconds. Two taps 500 ms apart therefore produce 120 BPM; this is a calculation example, not a measurement of your music.
At most 16 recent taps contribute to the displayed average. Once you have more taps, the oldest accepted tap drops out. The number is shown to one decimal place and remains a manual estimate whose accuracy depends on your timing.
Use one tap per beat
Tapping twice per beat doubles the calculated number. Tapping once every two beats halves it. Decide which pulse you are following before comparing results, and reset when changing your tapping pattern.
This implementation accepts adjacent tap intervals from 100 to 6,000 milliseconds, corresponding to a calculation range of 10–600 BPM. These are input limits, not a claim about the normal range of every musical style. It does not classify meter, identify a song, or correct inconsistent taps automatically.
No audio processing
There is no audio upload, microphone permission, speech recognition, or beat-detection model. You may listen to audio separately, but the page measures only your button presses. It cannot recover the tempo of a file that you have not tapped along with.
Tap timestamps remain in the current page state and are cleared by Reset taps or reloading. The calculation code sends no tap data to a server and stores no measurement history.
Which format do you need?
| Your next task | Input or choice | Output or result |
|---|---|---|
| Measure tempo manually | accepted button-press timestamps | average tap interval converted to BPM |
| Follow a different pulse | taps twice or half as often | a doubled or halved estimate |
| Analyze an audio file | audio recording | not supported; this is manual tapping |
Questions about this tool
How many taps are needed?
At least two accepted taps are needed. The estimate uses at most the latest 16 accepted taps.
Does it detect BPM from an audio file?
No. It measures your button presses. There is no audio upload, microphone access, or automatic beat detection.
Why did a tap get ignored?
A tap less than 100 milliseconds after the previous accepted tap is ignored. Tap more slowly or reset if you made a mistake.
What happens after a pause?
If more than 6 seconds pass between taps, the next tap starts a new measurement. A second tap is then needed to calculate BPM.
Is this an exact measurement of the music?
No. It is an estimate based on your tapping. Uneven timing or following a different pulse changes the result.
Are my taps saved?
They remain only in the current page state. Reset or reload clears them; the calculation does not send tap data to a server or keep history.