This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
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.
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.
No comment highlights available yet. Please check back later!
About InputProbe on Product Hunt
“Hardware testers that show their error bars”
InputProbe was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #160 on the daily leaderboard. 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.
InputProbe was featured in Hardware (11.4k followers) and Developer Tools (519k followers) on Product Hunt. Together, these topics include over 86.3k products, making this a competitive space to launch in.
Who hunted InputProbe?
InputProbe was hunted by Andrew Williams. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how InputProbe stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Andrew Williams
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.