Touch Sampling Rate Test
Move one finger in fast circles on the canvas to measure how many touch samples per second your screen reports. You get a live reading plus the peak and average for the session.
Your browser reports this screen's touch support once the page has loaded.
Runs in your browser. Nothing is uploaded.
Sampling Rate mode
Start touching to test
Waiting for input...
Your browser reports this screen's touch support once the page has loaded.
Runs in your browser. Nothing is uploaded.
Run the next test
What This Test Measures
Your screen's touch controller scans the capacitive sensor grid many times per second and reports each finger position to the operating system. That report rate is the touch sampling rate. The higher it is, the less time passes between moving your finger and the system knowing where it went, which is why phone makers advertise 240Hz, 360Hz, or higher for gaming.
Browsers normally hand a web page only one movement event per animation frame, even when the hardware reported several. This test reads the browser's coalesced pointer events, which carry every sample the hardware reported between frames, and divides the number of samples by the time they span.
How to Get an Accurate Reading
- Use one finger: Only your first finger is counted, so extra fingers won't add samples.
- Keep moving: Draw continuous, fast circles. A stationary finger produces no movement samples, so pauses lower the live reading.
- Turn off battery saver: Power saving modes commonly lower both the display refresh rate and the touch scan rate.
- Run it a few times: Lift your finger between runs. The average covers every stroke in the session, and the peak shows the best half-second window.
- Check the Method line: Open View Results. "Coalesced pointer events" means you're seeing the hardware rate. "Dispatched events" means your browser is capping the reading at the display refresh rate.
Reading Your Result
| Average Reading | What It Usually Means |
|---|---|
| Exactly 60Hz or 120Hz | Often a browser cap. Check whether the Method line says "Dispatched events" before blaming the hardware. |
| Around 120Hz | Typical of mid-range phones, tablets, and most touchscreen laptops. |
| 180–240Hz | Typical of current flagship phones in normal use. |
| Above 240Hz | Gaming-class touch layer, or a phone that keeps its high-rate mode on outside games. |
| Big swings between runs | Usually thermal throttling or an adaptive power mode. Let the device cool down and test again. |
Further reading
For how sampling rate and refresh rate combine into the input lag you feel, read our Touch Sampling Rate vs Refresh Rate guide. To check how smoothly the touch path is tracked, try the Sensitivity Test.
Frequently Asked Questions: Touch Sampling Rate
What is touch sampling rate?
Touch sampling rate is how many times per second the touch controller scans the screen and reports finger positions to the operating system, measured in hertz (Hz). A 240Hz touch layer reports a new position roughly every 4.2 milliseconds, while a 120Hz layer reports every 8.3 milliseconds.
Is touch sampling rate the same as refresh rate?
No. Refresh rate is how many times per second the display draws a new image. Sampling rate is how often the touch sensor reports input. They are independent: a 120Hz display often pairs with a 240Hz touch layer, so each frame can use the freshest touch position available.
Why is my result lower than the number my phone advertises?
Several things lower browser readings. Many phones only switch to their highest advertised rate inside games or a dedicated gaming mode. Battery saver modes can lower the rate. And browsers that do not expose coalesced pointer events only deliver one event per frame, which caps the reading at the display refresh rate.
Why does my result match my refresh rate exactly?
If the result reads almost exactly 60Hz or 120Hz and the Method line in your results says 'Dispatched events', your browser is batching touch input to the display refresh rate. The touch hardware may be faster than the browser can show. Try Chrome or Edge, which expose every hardware sample through coalesced pointer events.
Can a low sampling rate indicate a hardware fault?
Rarely on its own. A sampling rate well below what the same model normally reports can point to a low-quality replacement screen, since aftermarket panels often use cheaper touch controllers. A rate that drops sharply after a few seconds is more often thermal throttling or a power saving mode than a fault.
Does this test send my touch data anywhere?
No. Every timestamp is counted and averaged locally in your browser. Nothing about your touches or results is uploaded, and closing the tab discards the session.