| Metric | Value |
|---|---|
| {{ row.label }} | {{ row.value }} |
Musical tempo—measured in beats per minute (BPM)—describes how frequently a repeating pulse occurs within one minute, anchoring timing for musicians, DJs, and producers. An accurate tempo lets performers synchronise parts, align backing tracks, and choose complementary effects.
This browser-based calculator records the interval between your consecutive taps, converts each gap to an instantaneous BPM, and derives a rolling average across a configurable window. A real-time pulse trace and trend chart update after every tap, giving immediate visual feedback.
Use it to match a drummer’s groove, clock a vinyl sample, or set delay times during mixing *without carrying a metronome*.
Tempo calculation relies on the inverse relationship between time and frequency. When you tap, the reactive engine timestamps each input, computes the time difference (Δt) to the previous tap, and converts that gap into BPM. Averaging successive intervals smooths human inconsistency while preserving live responsiveness.
Δt is the elapsed time between two taps in milliseconds.
| Tempo Marking | BPM Range |
|---|---|
| Largo | 40 – 60 |
| Adagio | 66 – 76 |
| Andante | 76 – 108 |
| Allegro | 120 – 168 |
| Presto | 168 – 200 |
Values outside traditional ranges are accepted; the charting layer simply plots the computed numbers for reference.
| Parameter | Meaning | Unit / Datatype | Typical Range |
|---|---|---|---|
| windowSize | Number of latest taps averaged | Integer | 2 – 20 |
| timeoutSec | Pause length that resets the counter | Seconds | 1 – 30 |
| playSound | Audible click on each tap | Boolean | true / false |
Example (4 taps at 550 ms, 560 ms, 540 ms):
Concept aligns with standard acoustics texts such as *Howard & Angus, Acoustics and Psychoacoustics* (2017) and papers on tempo perception by London (2004).
Calculations run entirely locally and do not process personal data, so no GDPR or HIPAA concerns apply.
Follow these steps to derive a stable BPM estimate.
Two taps generate the first estimate; five to eight taps usually yield a stable average.
Instant BPM reflects the last interval only, while the average smooths several intervals to minimise timing variance.
Yes, but screen latency can slightly lower the measured tempo; consider hardware keys for critical work.
No. All processing occurs locally in your browser; nothing is transmitted, logged, or saved.
The audible click is generated after the tap event and does not influence BPM calculations.