Most online mouse testers measure your monitor: they count one movement per frame, so a 1000 Hz mouse reads 60 on a 60 Hz display. InputProbe reads the device events themselves. Every tool publishes its measured error band (from repeated runs on real hardware) and refuses to print a number when the capture can't support one. DPI, polling rate, button bounce, key rollover, eDPI. Free, no accounts, runs entirely in your browser.
Forum Threads
What has an online input tester told you that turned out to be wrong?
I'm launching Saturday, and this product exists because of wrong numbers. Most browser-based mouse testers count one movement per displayed frame, which means they're measuring your monitor (a 1000 Hz mouse reads as 60 Hz on a 60 Hz display), printed with total confidence.
When I started measuring properly, I ended up publishing error bands instead: every number on InputProbe comes with the accuracy band it was measured to, and when a capture can't support a number, the tool refuses to print one and says why.
Before launch I'm collecting failure stories. Have you ever used an online DPI checker, polling rate tester, double-click tester, or keyboard tester and gotten a result that didn't survive a second look (a DPI that didn't match reality, a polling rate that changed between runs, a "faulty switch" verdict on a healthy mouse)? Which tool, and what did it tell you?
I'll take the failure modes people report here, reproduce them, and write up what actually causes each one.
Hi PH — I’m Andrew. I built InputProbe after testing my own devices on popular online testers and getting answers that were confidently wrong.
For mouse measurements, the root problem is that a browser renders the page at your display’s refresh rate and can deliver mouse input in batches around those frames. Testers that count one movement per frame can end up measuring the monitor instead of the mouse (a 1000 Hz mouse can look like 60 Hz on a 60 Hz display). InputProbe reads the individual device reports inside those batches, with their own timestamps.
The second thing I cared about is honest error bars. For example, the DPI test measures against objects with standardized dimensions (every bank card is 85.60 mm long under ISO/IEC 7810) runs three passes, and reports the median plus the spread. The accuracy bands are measured, not assumed: 100 runs across four mice came out within ~5% on bank cards, A4 paper, and US Letter. And when a capture can’t support a number, the tool refuses to give one and tells you why, rather than averaging the mess into something confident-looking.
What it deliberately doesn’t do: no accounts, no uploads, no ads. Every measurement runs in your browser and nothing leaves it. The methodology page also lists what hasn’t been validated against hardware yet (polling rates above 125 Hz, for example) because a tool that shows its own error bars should show those too.
Seven tools: DPI, polling rate, click speed, double-click, button test, keyboard rollover, and eDPI, plus the full methodology: https://inputprobe.com/methodology/
The measurement engine is open source so the method can be checked rather than believed.
One ask: if you’ve used another online tester, tell me which one and what it told you. I’ll try to explain what it was actually measuring. That’s the conversation I most want to have today.