Find the BPM of any song by tapping along to the beat. Tap the button or press any key in rhythm with the music.
Last updated: October 31, 2026 · Written by the Pitch Detectors Editorial Team
A tap tempo calculator finds a song's BPM from your taps: tap the button or press any key in time with the music and it converts your tap intervals into beats per minute. This free tool averages your last 20 taps for a stable reading, and also shows beat duration, bar length, and half-time tempo — no signup, no audio upload.
Tap tempo is the musician's answer to "how fast is this song?" when no tempo readout exists. DJs use it to check vinyl and live recordings, producers use it to set DAW project tempos from reference tracks, and dancers use it to pick music at the right speed. Unlike automatic BPM detectors that analyze audio files, tap tempo uses human rhythm perception — which makes it more reliable on swing grooves, live drums, and half-time feels where algorithms get confused.
This calculator turns your taps into tempo with a rolling-average method. Each tap records a high-precision browser timestamp; the tool computes the millisecond interval between consecutive taps and keeps a rolling buffer of your last 20 taps. Averaging those intervals smooths out natural finger jitter while staying responsive when you deliberately change tempo.
Methodology: BPM = 60,000 ÷ mean tap interval (ms). Each
tap also feeds derived readouts: beat duration (60,000 ÷ BPM ms),
4/4 bar length (beat duration × 4), and half-time
tempo (BPM ÷ 2). If the gap between taps exceeds 2,000 ms, the buffer
clears automatically so a new track starts fresh. We verified the widget's math against
hand calculations on five sample inputs (500 ms intervals → 120 BPM; 484 ms → 124 BPM;
1,000 ms → 60 BPM; jittered 495–505 ms intervals → ≈120 BPM; a 2,100 ms gap →
auto-reset) — every result matched exactly.
One formula does all the work: divide 60,000 (milliseconds per minute) by your average tap interval.
BPM = 60,000 ÷ average interval in milliseconds
Worked example: you tap four beats with intervals of 495, 505, 498, and 502 ms:
Notice how the ±5 ms jitter in individual taps disappears in the average — that smoothing is exactly why the calculator uses a rolling buffer instead of single intervals.
Need the number nailed down to 0.1 BPM for production work? Take your tapped value to the BPM Calculator and verify it by counting 32 beats against a stopwatch.
The headline number is your tapped tempo; the supporting readouts tell you what to do with it:
| Readout | Meaning | Next step |
|---|---|---|
| BPM | Tempo from your rolling 20-tap average | Type it into your DAW, DJ software, or metronome |
| Taps | How many taps are in the current buffer | Keep going until you pass 8 for a trustworthy reading |
| Avg Interval | Mean milliseconds between your taps | A steady value means consistent tapping; a drifting one means the song's tempo moves |
| Beat Duration | One beat in milliseconds (60,000 ÷ BPM) | Use it to set delay and reverb times — see the BPM to Milliseconds tool |
| Bar Duration | One 4/4 bar in seconds | Multiply by bar count to time intros, drops, and transitions |
| Half Time | Your BPM divided by 2 | Use for trap, dubstep, and future bass written at double-time feels |
| Genre Match | Typical genre for that tempo range | Sanity check — a "Ballad" label on a techno track means you tapped the half-time pulse |
Averaging taps shrinks your error, but with diminishing returns. Random tapping jitter cancels roughly with the square root of the tap count: moving from 4 taps to 16 taps roughly halves the error, but going from 16 to 64 barely improves it further. This calculator's 20-tap buffer sits at the knee of that curve — enough taps to average out finger jitter to about ±1 BPM, few enough that the reading still responds quickly when you move to a new track or the tempo shifts.
The practical rule: 8 taps minimum, 16 ideal, beyond 20 you're just confirming. If the number keeps wandering after 16 steady taps, the music itself is drifting — measure the verse and chorus separately instead of chasing one number.
When people tap along with a beat, their taps typically land tens of milliseconds before the actual beat onset — a phenomenon timing researchers call negative mean asynchrony (Repp, 2005). Your brain predicts the beat rather than reacting to it, so the finger moves early.
For tap tempo this quirk is harmless: the early offset is consistent from tap to tap, so the intervals between taps stay accurate even though each tap is slightly early. What does hurt accuracy is inconsistent timing — rushing fills, dragging on syncopated hits. Tap the steady quarter-note pulse and let the average do the rest. Research on sensorimotor synchronization also shows tapping stays stable for intervals from about 200 ms up to 1,800 ms (roughly 33–300 BPM), with the most stable performance near 600 ms — so the tool covers every realistic musical tempo.
If you stop tapping for more than 2 seconds, this calculator clears its buffer and starts over. The threshold is deliberate: a 2,000 ms interval equals 30 BPM (60,000 ÷ 2,000), which is below any tempo you'd tap in practice. So the tool can safely assume a 2-second gap means "I'm done with this track" rather than "this song is extremely slow."
Use it to your advantage in live settings — finish measuring one track, wait two beats of silence, and start tapping the next without touching the Reset button. If you're measuring an unusually slow piece (below ~40 BPM), tap every beat without pausing or the buffer will clear mid-measurement.
Tap tempo wins on feel; auto-detect wins on files. Neither is universally better — they fail in opposite situations.
| Tap tempo (this tool) | DAW / app auto-detect | Manual count + BPM calculator | |
|---|---|---|---|
| Accuracy | ±1–4 BPM (human jitter) | Usually ±1 BPM on clean files | Exact to 0.1 BPM |
| Needs | Just the music playing | An audio file to analyze | Beat count + stopwatch |
| Best for | Live sets, vinyl, swing, half-time feels | Studio stems and full mixes | Production tempos, delay math |
| Weakness | Human error; drifts on tempo changes | Octave errors (reads 87 instead of 174); fails on swing and rubato | Slow; needs careful counting |
The classic failure of auto-detect is the octave jump: it locks onto the half-time or double-time pulse and reports 87 BPM for a 174 BPM drum & bass track. Human ears rarely make that mistake, which is why experienced DJs tap first and trust the tap when the software looks wrong.
Tapped tempo gets you close; this workflow gets you exact.
The whole process takes under two minutes and gives you a project tempo you can trust for warping, slicing, and tempo-synced effects.