Output
Cursor path, CSS pixels and distance
UserBenchmark / All Tools / Mouse Jitter Test
Mouse
Mouse Jitter Test
Draw a slow straight line and inspect cursor deviation.
Free to useNo downloadNo sign-up
Mouse Jitter Test · At a glance
Quick answer: Draw a slow straight line and inspect cursor deviation. Visible deviation includes hand movement, surface behavior and cursor processing.
Mouse Jitter Test
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
How to use this tool
- Draw a slow straight line, then repeat in another direction.
- A ruler beside the pad can help you keep the physical path consistent.
Input
Movement inside the test surface
Browser requirement
Pointer coordinates after OS transforms
Processing
Runs on your device; no tool-result upload
How it works and what the result means
Coordinates are CSS pixels after operating-system pointer settings. Speed is browser-visible cursor speed. They do not directly expose raw sensor counts, DPI, physical acceleration or lift-off distance.
Reading the result
Visible deviation includes hand movement, surface behavior and cursor processing. A wavy trace is not automatically sensor jitter.
What to check next
Clean the sensor area and repeat on a different surface. Keep zoom and pointer settings unchanged.
For drift, leave the mouse still. For jitter, draw a slow straight line. For lift-off testing, add measured spacers yourself and observe when movement stops being reported.
Frequently asked questions
Can the trace separate hand tremor from sensor noise?
No. Both reach the browser as pointer movement. Controlled physical guidance and comparison with another device provide more useful evidence.
How do I start the Mouse Jitter Test?
Start the tracker and move the cursor inside the test surface. Use the trace and distance statistics to compare different movements.
Does this tool require a download or an account?
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Why can two attempts give different results?
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.