Tap along to the beat and Solmi works out the tempo. Click the pad or hit the spacebar in time with the music, and the BPM appears after a couple of taps — no file to upload, no signup, and it keeps getting steadier the longer you tap. Ideal when the music is playing somewhere you can't upload it: a rehearsal, a live set, a record, or a video.
Every time you tap, the tool records the moment. The gaps between those moments are beats, and a beat length converts straight to tempo: a 500 ms gap is 120 beats per minute, because 60,000 milliseconds divided by 500 is 120. Reading only the most recent gap would make the number jump around with every slightly-off tap, so Solmi fits a line through all your recent taps and reads the tempo from its slope. That uses the total time you've been tapping rather than any single gap, which is why the reading tightens up the longer you go. Taps that land well off the beat are set aside instead of dragging the average, and a pause of more than a couple of seconds starts a new measurement.
Tapping and analyzing the audio solve the same problem from opposite ends, and which one is better depends entirely on whether you have the file. If the track is sitting on your computer, upload it to the BPM finder and skip the tapping. If the music is coming out of a rehearsal room, a car radio, a record, or someone else's speakers, tapping is the only option — and for loose, live, or rubato playing, a human ear often beats a beat detector anyway.
| Tap tempo | Automatic detection | |
|---|---|---|
| Needs an audio file | No | Yes |
| Works on live or acoustic music | Yes | Often unreliable |
| Typical accuracy | ±1 BPM after ~8 taps | Within 0.1 BPM on a clean mix |
| Time to a result | A few seconds of tapping | A couple of seconds |
| Handles tempo changes | Yes, follows as you tap | Reports one overall tempo |
| Also finds the musical key | No | Yes |
The number itself is rarely the point — it's the input to something else. These are the jobs a tapped tempo usually feeds into, and the precision each one actually needs.
| Use | Why you need the BPM | Precision needed |
|---|---|---|
| Setting a DAW project tempo | So the grid lines up with the recording | Exact value, to 2 decimals |
| Setting a metronome or click | To rehearse or record in time | Nearest whole BPM |
| DJ beatmatching | To judge how far two tracks are apart | Nearest whole BPM |
| Learning a song from a record | To slow it down and build back up | Nearest whole BPM |
| Syncing visuals or edits to music | So cuts land on the beat | Exact value, to 2 decimals |
| Writing a chart or lead sheet | To note the tempo marking | Rounded to the nearest 5 |
Most inaccuracy in tap tempo is tapping technique, not the maths. Tap with the same finger and the same motion each time rather than alternating hands, which tends to produce a long-short pattern. Listen a bar or two before you start so you're following the beat rather than chasing it. Keep going for at least eight taps and watch the steadiness indicator settle. If you're listening on Bluetooth headphones, the audio you hear is delayed by a fixed amount — that shifts every tap equally, so it does not affect the tempo you get, only how in-sync you feel. And if the number lands at exactly double or half what you expected, you tapped a different subdivision rather than getting it wrong.
Play the music, then tap the pad (or press the spacebar) once on every beat. After two taps you'll see a BPM; it settles down over the next several taps. If you lose the beat, just stop for a moment and start tapping again — a pause begins a fresh measurement rather than mixing your old taps into the new one.
Two taps give a rough number, four to eight get you within about a BPM for most people, and sixteen or so is as good as tapping gets. Watch the steadiness read-out: once it stops moving, extra taps won't sharpen the result much. Tapping longer helps most when the music itself has a loose or human feel.
Tap every beat — the quarter-note pulse you'd count as 1, 2, 3, 4. Tapping only the downbeat of each bar gives you a number four times too slow in 4/4, so multiply by four if that's what you did. The tool measures the gap between your taps, so whatever you tap on defines the beat.
Because it depends what you tapped along to. A track that feels like 75 BPM has a hi-hat pattern at 150, and tapping that gives you 150 — both are 'correct', they're just different subdivisions. Halve or double the number to get the reading you meant. This is the same octave ambiguity that automatic detection runs into.
For a clean studio recording, no — analyzing the audio directly is more precise, and the BPM finder does that in a couple of seconds without you keeping time. Tapping wins when there's no file to analyze, or when the music is rubato, live, or acoustic enough that beat detection struggles. They're complementary, not competing.
Yes — tap the pad with your finger instead of clicking. Touch timing is slightly less precise than a mouse or key press on some devices, so it's worth tapping a few extra beats on mobile before trusting the number.
Yes, completely free with no signup, and it runs entirely in your browser. Once you have the tempo, you can use Solmi's AI music video generator to turn the song into a beat-synced music video — also free to start.