Input Devices
Input devices are your primary interface with your computer. Test keyboards for NKRO and ghosting, mice for double-click issues and CPS, gamepads for stick drift, touch screens for multi-touch responsiveness, and touchpads for gesture and click detection.
Keyboard Test
keyboard test, keyboard tester, NKRO test
[READY]
Open Tool →Mouse Test
mouse test, CPS test, double click test
[READY]
Open Tool →Gamepad Test
gamepad test, controller test, gamepad tester
[READY]
Open Tool →Touch Screen Test
touch screen test, touchscreen test, multi-touch test
[READY]
Open Tool →Touchpad Test
touchpad test, trackpad test, touchpad tester
[READY]
Open Tool →Input Devices
Input devices are your primary interface with your computer. Test keyboards for NKRO and ghosting, mice for double-click issues and CPS, gamepads for stick drift, touch screens for multi-touch responsiveness, and touchpads for gesture and click detection.
Privacy First input devices Testing Tools on usbRecognized run entirely in your browser using secure Web APIs. No software download, no installation, no data upload — your privacy is 100% protected. Simply click on a tool above to start testing.
Some tools in this category are available now (marked with ✓). Others are coming soon — each coming soon page includes a detailed preview of what the tool will do and how you can test your hardware in the meantime.
What Each Input Test Actually Measures
A keyboard test is not a single check. It reports key rollover, which is how many keys the keyboard can report while held down at once; ghosting, where a specific combination of keys produces a phantom third keypress; and chatter, where one physical press registers twice. The last of these is the most common real-world fault and the one most often mistaken for a software problem.
A mouse test measures something different again: click speed in clicks per second, whether a single click is being reported as a double click, and the polling rate the operating system actually receives. Polling rate and pointer latency are frequently confused with each other, but they are separate quantities and a mouse can be fast at one while poor at the other.
Gamepad tests focus on analogue inputs rather than digital ones. The important measurements are stick drift, which is a resting position that no longer returns to centre, dead zone width, trigger travel, and whether the D-pad can register diagonals. A controller can pass every button test and still be unusable because of drift.
Touch screen and touchpad tests both deal with pointer input but check opposite things. On a touch screen the questions are how many simultaneous contacts are tracked, whether ghost touches appear when the panel is not being touched, and whether the digitiser has dead strips near the edges. On a touchpad the questions are gesture recognition, palm rejection while typing, and whether physical clicks register across the whole surface.
Common Failure Modes in Input Hardware
Mechanical switch chatter develops gradually. The metal contacts inside a switch oxidise and bounce, so a single actuation produces two or three electrical transitions. Typing feels normal at first because the extra character is often backspaced without conscious thought, and the fault is only obvious once you watch a key-by-key display and see the duplicate appear.
Mouse double-click failure comes from the same root cause in a different package. The switch wears, the bounce window widens, and the operating system interprets one press as two. This is why a mouse that registers double clicks is usually reported alongside an unexplained tendency to select and immediately deselect text.
Analogue stick drift is a wear problem specific to potentiometer-based sticks. The carbon track wears unevenly, so the resting voltage no longer sits at the midpoint and the game reports continuous input in one direction. Hall-effect sticks avoid the wear mechanism but can still drift after a strong magnetic field or a calibration fault.
Touch faults are usually mechanical or environmental rather than electrical. A digitiser that reports phantom contacts often has a trapped air gap or a failing bond between the glass and the sensor layer. Dead strips near an edge frequently follow a drop that damaged the flex cable where it bends around the chassis.
Choosing the Right Input Test
Start from the symptom rather than the device. If characters appear twice, run the keyboard test and watch the key display rather than the words. If text is being selected unexpectedly, run the mouse test and count whether single clicks are reported as doubles. If a character in a game moves on its own, run the gamepad test and read the resting axis values without touching the stick.
Input problems are often misattributed to the wrong device. A mouse that stutters can be caused by a wireless receiver competing for bandwidth with a keyboard on the same dongle, and a touchpad that ignores gestures can be caused by a driver that has silently replaced the vendor one. Testing the device you suspect is the fastest way to rule it in or out, and testing it takes under a minute.
If you are buying rather than diagnosing, the useful tests are different. Rollover and anti-ghosting matter most for keyboards used for simultaneous movement and action keys. Polling rate and click latency matter most for competitive mice. Stick resolution and drift resistance matter most for controllers. Running the same three tests on two candidates gives you a comparison that specification sheets do not provide.
Reading Input Test Results
Numbers from an input test are relative, not absolute. A polling rate measurement is limited by the browser event loop as well as by the device, so a value lower than the marketing figure is not proof of a fault. What matters is consistency: a mouse that reports a stable rate is healthy, while one that alternates between two very different values is being throttled somewhere in the chain.
Latency figures carry the same caveat. Every browser-based measurement includes the display pipeline and the event dispatch path, so the number is an upper bound on device latency rather than a precise instrument reading. Use it to compare two devices on the same machine, not to compare against a published specification.
Retesting is what turns a single measurement into a diagnosis. A key that chatters intermittently will pass a short test and fail a longer one, and a stick that drifts only when warm will pass when cold. Running the same test again a week later, and comparing the two results, is far more informative than a longer test run once.
Input Devices FAQ
Do I need to install anything to test my keyboard, mouse, or gamepad?
No. Every input test on this site runs inside the browser using standard DOM events and the Gamepad API. Nothing is downloaded, no driver is installed, and no system-level hook is placed on your input stack. The trade-off is that browser testing cannot measure anything below the event dispatch layer, so hardware-level scan rates are inferred rather than read directly.
Which keyboard test should I run for gaming?
Use the rollover and ghosting view rather than the typing view. Hold the movement keys and the action keys you use together, and watch whether every press is reported simultaneously. A keyboard that drops one of three held keys will cost you inputs in a game even though it types perfectly well in a text field.
Why does my mouse register one click as two?
This is almost always switch bounce from a worn micro switch, not a software setting. The contacts inside the switch no longer settle cleanly, so the operating system sees two electrical transitions. Run the double-click check: if the duplicate appears within a few milliseconds of the first press, the switch is failing and no driver update will fix it.
How do I test a controller for stick drift?
Open the gamepad test and read the axis values without touching the sticks. A healthy controller rests at or very near the centre value. If an axis reports a consistent offset, or wanders while untouched, the stick is drifting. Compare the resting value before and after a few minutes of use, since drift from a worn track often worsens as the controller warms up.
Can I test multi-touch on a laptop touch screen?
Yes, provided the browser exposes touch events, which every current browser on a touch-capable laptop does. Place several fingers on the screen at once and watch how many independent contact points are tracked. Most laptop panels support ten, but budget models sometimes track fewer, and the limit is a hardware property rather than something a setting can change.
My touchpad gestures stop working. Is that a hardware fault?
Usually not. Gesture recognition is implemented by the driver or the operating system rather than the touchpad itself, so a pad that moves the pointer correctly has working hardware. Check whether a recent driver update replaced the vendor driver with a generic one, and whether a precision touchpad setting has been disabled, before assuming the pad has failed.
Does testing input in a browser add latency to the results?
It adds latency to the measurement, not to your device. Every figure includes browser event dispatch and the display pipeline, so the absolute number is higher than the true device latency. The practical consequence is that you should compare two devices on the same machine and browser rather than compare a measured value against a published specification.
How often should I retest my input devices?
Once when you first suspect a problem, and then again after a repair or a swap. There is little value in testing a healthy keyboard monthly. The exception is a device with an intermittent fault, where testing at the moment the fault appears is the only way to capture evidence, because intermittent switch chatter frequently disappears under a short test run.