Tap the beat. Read the BPM.

Tap tempo, done properly: from finger to trustworthy number

You're in a rehearsal room and the drummer asks what tempo the bridge sits at. No laptop cable, no file — just the song in the air and a spacebar. Tapping is the oldest tempo tool there is, and done right it's accurate enough to set a click, a delay, or a set plan.

The catch is that fingers are noisy instruments. This page is built around that fact: it doesn't just average your taps, it audits them.

§How to tap a tempo accurately

1. Tap on the beatHit the pad, click, or press any letter key in time with the music. Aim for the kick or the snare, not the melody.
2. Keep going to eightThe reading refines with every tap. Watch the steadiness label — 'locked' means the number has settled.
3. Check the octaveIf the song feels slow but reads fast, look at the half-time readout. Both are true; pick the one you'd count.
4. Save or send itCopy the BPM, save it to the tap log with the song's name, or hand it straight to the delay calculator.

01What eight taps know that two don't

Every pair of taps is one measurement of the beat period. This page keeps your last twelve, finds the median interval, then throws away any interval wilder than 0.6–1.6 times that median before averaging what survives. That trimmed mean is why one flubbed tap doesn't wreck the reading — the outlier simply never enters the average.

The steadiness label is the same data read differently: it measures how tightly your kept intervals cluster around their mean. Tight cluster, trustworthy number. Wide cluster, keep tapping.

02How accurate can a finger be?

Do the arithmetic on your own jitter. At 120 BPM the beat period is 500 ms; if your individual taps land within about ±25 ms of the beat — a realistic spread for a musician tapping attentively — a single interval can read anywhere from roughly 114 to 126 BPM. Averaging eight intervals pulls that error down to a couple of BPM, and the trim discards the taps where you flinched.

That's the honest ceiling of any tap tool: a tempo, not a grid. It cannot tell you where beat one is, and it inherits whatever push and pull the performance itself has.

03When tapping beats the detector

A file detector needs the file. Tapping works on the club PA, the radio edit, the video that won't download, the live band mid-soundcheck. It also settles arguments a detector can't: when a track reads 150 but the room is dancing at 75, your foot is measuring the truth that matters — the felt pulse. Tap what you'd count, and use the half/double readouts to translate.

04From tap to session

A tempo you don't write down is a tempo you'll tap again tomorrow. The Tap log mode names and stores each reading on this device and copies the lot as CSV — a rehearsal's worth of songs in one paste. From there the number feeds everything tempo-shaped: eighth-note delay is 60,000 ÷ BPM ÷ 2 milliseconds, a four-bar loop is 16 beats, and a DJ transition wants the next song within about ±6% or ridden at half-time.

05The library that taps itself

Tapping is for the room; the studio is for the catalog. BPMandKey in the studio hears every song you upload once and remembers its BPM, key, and Camelot code forever, fingerprinted so a re-upload costs nothing. The tap log on this page is a pocket notebook — the studio is the shelf it belongs on.