Set your session.
Choose a timed test or a fixed number of taps. Ten seconds is a useful starting point. Use the default Z and X keys or customize them to match your setup. On a phone, select Touch / mouse and tap the two pads.
Measure your osu! stream speed and tapping consistency.
Alternate two keys or tap the on-screen pads.
Press Z and X alternately to start.
The first tap starts the clock.
Tap to plot your stream pace.
| SESSION | TEST | Average BPM | INTERVAL SPREAD | ALTERNATION | INPUT |
|---|---|---|---|---|---|
| Completed tests will appear here. | |||||
Compare sessions with the same duration, input method, and key setup. History stays in this browser.
Choose a timed test or a fixed number of taps. Ten seconds is a useful starting point. Use the default Z and X keys or customize them to match your setup. On a phone, select Touch / mouse and tap the two pads.
The first accepted tap starts the clock. Alternate your two inputs at a comfortable speed, then try a quicker session if you want. Release each key before pressing it again. Holding a key does not generate extra inputs.
Look at average pace alongside interval spread and alternation. A fast result with uneven intervals tells a different story from a steady result. Repeating the same test makes comparisons more useful than chasing an isolated peak.
For the common osu! ¼-beat stream convention, each musical beat contains four taps. If N taps span T seconds from first to last, they create N − 1 measurable intervals.
Example: 11 evenly spaced taps over one second create ten intervals of 100 ms. The average stream pace is 150 BPM.
A musical tap-tempo tool normally treats one tap as one beat. The same 100 ms gap would read 600 BPM there. That is a different note-spacing convention, not evidence that one tool measures your fingers four times faster.
A timed run also reports 15 × accepted taps ÷ test seconds. This includes time spent resting, including silence after your last tap. For example, 80 taps during a ten-second window gives 120 BPM of full-window throughput. It answers how much input you produced over the entire session.
These formulas answer different questions, so small differences between them are expected. A tap-count test has no separate fixed-duration window, and its full-window field is left blank.
This osu! stream speed test isolates the timing of your taps. A real beatmap also asks you to aim, read patterns, and land within hit windows. Use a repeatable browser result to choose a pace to try in the game.
Compare your osu BPM test results using the same mode, target, device, and pair of inputs. If you want a record outside this browser, use Copy result after a completed run. The copied text includes the test length, input method, and the main timing metrics.
Run another speed test ↑A short fixed-count run gives you a repeatable burst. Start with 50 taps and use the same target on your next attempt. When you want to see how long you maintain a pace, choose 30 seconds or 60 seconds and watch the second half of the graph. Build a separate baseline for each preset. Compare keyboard scores with keyboard scores and touch-pad scores with touch-pad scores.
Suppose two ten-second runs both average 180 BPM. In one, the taps are close to 83 ms apart. In the other, short gaps alternate with long gaps. The second run can average the same pace while producing a higher interval spread. If both runs show 100% alternation, that tells you the inputs switched every time. The spread and the graph tell you how consistently the switches were timed.
Read the curve from left to right. Each point uses up to four recent intervals, so several adjacent dips can reveal a slowdown. One sharp spike can come from two presses landing nearly together.
Suppose you record 80 taps in a 10-second run. Your full-window pace is 120 BPM. If the average is 180 BPM, the last tap landed around 6.6 seconds and the rest of the window was idle. If you spread the same 80 taps across nearly 10 seconds, both readings will be close to 120 BPM. In either run, look for dips to see where you lost pace before the last tap.
Divide stream BPM by 15 under the four-taps-per-beat convention. A 150 BPM stream is 10 taps per second, 180 BPM is 12 taps per second, and 240 BPM is 16 taps per second. With perfectly even alternation, each finger supplies half of that rate. To estimate the spacing you would hear at a target pace, divide 15,000 by the BPM to get the gap in milliseconds.
Check the input selector first. Keyboard mode listens for your two assigned physical keys, and Touch / mouse mode listens on the two pads. Release a key between taps so the next press can be counted. If a browser shortcut or input method takes over, try a different pair. Switching tabs or leaving the window interrupts the active session. You can inspect the partial measurements, then press Reset when you are ready to try again.
There is no universal score for every player. Use a pace you can repeat with controlled intervals as your baseline, then compare the same test over time. This tool does not assign player percentiles because it has no representative player dataset.
Free tapping removes aim and rhythm-reading demands. Uneven mashing or nearly simultaneous inputs can also inflate the number. Review interval spread and alternation alongside average BPM, and verify your control on actual beatmaps rather than treating this test as a gameplay prediction.
No. This test calculates the standard deviation of gaps between taps. In-game unstable rate is based on hit timing errors against scheduled notes. A free-speed test has no target note timeline, so labeling its interval spread as game UR would be misleading.
Yes. Choose Customize keys and record two distinct keys. Letters, digits, and many punctuation keys work; browser shortcuts and modifier keys are excluded. For a touchscreen or mouse, select Touch / mouse and use the two pads. Input method and key setup are recorded with the result.
Held-key repeat events are ignored. A tap needs a new press after release. If the window loses focus or the page becomes hidden, the run is interrupted and excluded from completed history. This avoids treating a background pause as an ordinary finished benchmark.
The test measures your taps and calculates results in your browser. It stores the last ten completed results and your key settings locally. Clear history removes the result list; private browsing or blocked storage may prevent it from persisting. The web host may still receive normal page-request information. The site uses Microsoft Clarity to measure how visitors use the pages. See the Privacy Policy for details.
Timing uses the browser's high-resolution clock, but hardware polling, operating-system scheduling, browser load, and event delivery still matter. The site does not measure keyboard latency or correct hardware differences. Close demanding background tasks and use the same setup when comparing attempts.
At least two accepted taps are needed to create one interval, and peak BPM requires five taps. A completed timed session with only one tap has no average interval pace. Reset and try again; do not interpret missing data as a measured zero BPM.