tap tempo BPM online
Each tap adds to the interval since the previous one, and BPM comes from the median of the recent intervals, not a simple average: a median ignores one isolated mistimed tap, an average would get dragged by it. The tool keeps only the last 12 intervals (a window of up to 13 taps) and resets the count on its own after a pause of 3 seconds or longer.
With perfectly regular intervals, the median and a simple average would give the same result, the difference only shows up once something breaks the pattern.
The result does not shift at all, because the error stays isolated in the two rejected intervals, it does not contaminate the final median.
Without that reset, a 4000ms interval would enter the median and drag the calculated BPM down to somewhere around 15.
BPM (Beats Per Minute) is the unit of measurement for musical tempo, how many beats occur per minute. 120 BPM means 2 beats per second. It is fundamental for syncing loops in music production, aligning video cuts to music, configuring delay and arpeggiators in synthesizers, and beatmatching in DJing.
A first value already shows up on the second tap, with just one interval measured. The tool keeps a window of the last 12 intervals (up to 13 taps) and recalculates the median with every new tap, so stability keeps improving steadily up to around the 12th or 13th beat.
No, as long as it sits far enough from the median: any interval more than 35% away gets discarded before the final calculation. In a test with 10 taps and a mistake that produced two 250ms intervals (instead of 500ms), both were rejected and the BPM came out at exactly 120, with no drift.
Because a pause of 3 seconds or longer is treated as the start of a new measurement, not as an interval to be filtered out. An 8 or 10-second interval entering the median would drag the calculated BPM down to an absurdly low value, so restarting is safer than trying to filter that case as an outlier.
The analysis runs entirely in your browser (in a Web Worker). No file is uploaded to any server.