Question 1

How many taps do I need for an accurate BPM?

Accepted Answer

At least 4 taps are required to show a value, but 8–12 taps produce the most stable reading. The counter uses a rolling window of 8 intervals and trims outliers that deviate more than 40% from the median.

Question 2

Why does the result keep jumping between two values?

Accepted Answer

You may be tapping inconsistently or alternating between quarter and eighth notes. Look at the 0.5× and 2× cards — if one of them matches the song, you tapped the wrong subdivision. Slow down and aim for the main pulse (the beat you would nod your head to).

Question 3

Does the counter work on mobile?

Accepted Answer

Yes. Tap the big pad area on the screen. We listen to touchstart events (not click) to minimize input latency, and disable the 300 ms tap delay via the viewport meta tag and touch-action CSS.

Question 4

Why do some pros tap on every second beat?

Accepted Answer

For tracks above 140 BPM, tapping every beat is exhausting and imprecise. DJs tap on the downbeat of each bar (every fourth beat in 4/4), then multiply by 4 — our counter displays the 2× multiple card so you can pick the right value.

Question 5

Can I detect BPM from a song automatically?

Accepted Answer

Automatic BPM detection from audio requires FFT + autocorrelation of the onset energy envelope. That feature is planned but is not in the current MVP — you must tap along for now. Services like getsongbpm.com maintain large song→BPM databases for looking up known tracks.

Question 6

What is a good BPM for running / walking?

Accepted Answer

Walking: 100–120 BPM. Jogging: 140–160. Tempo running: 160–180. 180 BPM is a widely-cited "optimal cadence" for efficient running form. Match your music to your target stride.

Question 7

How do I calculate delay time from BPM?

Accepted Answer

Quarter-note delay (ms) = 60000 / BPM. Eighth = half of that. Dotted eighth = quarter × 0.75 (the famous U2 / The Edge delay). Our counter shows these three values automatically whenever BPM is stable.

Question 8

Is Allegro always 120 BPM?

Accepted Answer

No — Allegro is a feel, not a fixed number. Common range is 120–156 BPM. Different editors and scholars place the boundaries slightly differently. The counter reports the classical marking that best fits your measured BPM.

Question 9

Why does the metronome not play on iPhone until I press Start?

Accepted Answer

iOS Safari blocks Web Audio until a user gesture. That is why pressing the Start button is required to initialize and resume the AudioContext. Once running, you can adjust BPM and beats per bar without interruption.

Question 10

Is my tap data sent anywhere?

Accepted Answer

No. All calculations run in the browser. Timestamps are never uploaded. We use Google Analytics only to count aggregate page views and whether a stable BPM was reached, with no personal identifiers.

Question 11

What counts as "stable" tempo?

Accepted Answer

Stable = at least 4 taps, with a coefficient of variation (standard deviation / mean) under 8% across the trimmed samples. Anything above that is still shown but marked "Measuring…".

Question 12

Can I tap with two hands or on a drum pad?

Accepted Answer

Yes — any input device works. For tactile feel, use a MIDI pad controller bound to spacebar. Some USB foot switches also emit spacebar and work great with this tool.

Question 13

Why is the BPM rounded to one decimal?

Accepted Answer

For tap tempo, the measurement precision is typically ±0.5 BPM due to finger timing jitter. Displaying more decimals implies false precision. If you need to match a DAW exactly, nudge the value to the nearest integer after the tempo stabilizes.

Question 14

Is this tool free forever?

Accepted Answer

Yes. BPM Tap Counter is free and runs entirely in your browser — no accounts, no audio uploaded. Ads cover the maintenance costs.

FAQ