Test the signal before replacing the gear. Focused browser labs turn controller, keyboard, mouse, touch and motion events into readable evidence—without an account, driver installation or raw input upload.
Nothing detected yet. Move the mouse, touch the screen, or press a button on a controller — this updates as it sees each one.
A browser cannot detect a keyboard — only keys arriving — so keyboard tests are always offered rather than claimed. A connected controller stays invisible until it sends an input, which is the single most common reason a working pad looks undetected. Nothing on this page leaves your device.
The check above orders these by what your browser can see. This is the whole set, grouped by the device in your hand, with what each one measures and what it cannot.
Watch every button, stick and trigger light up on a drawn PS5, Xbox or Switch pad, then test vibration, report rate and stick circularity — nothing to install, nothing uploaded.
02Measure the observed center offset, maximum movement and stability of both analog sticks with a repeatable browser test.
03A guided two-minute check for any controller: stick drift at rest, full-circle range, every button and trigger, then a suggested deadzone and a clear verdict before launch day.
04Analyze recenter stability, full-circle coverage, outer range, symmetry, triggers and two connected controllers in repeatable stages.
05 DesktopRead the raw HID reports of a DualSense or DualShock 4: stick centres to the byte, drift percentage, gyro bias, report rate, battery and touchpad, read-only over WebHID.
06 DesktopSend real adaptive trigger effects to a DualSense on PC — resistance, weapon clicks, vibration — watch each trigger’s travel against the force it meets, and reset a trigger a game left stiff.
07 DesktopTurn the wheel and press the pedals: a guided check names every axis, then measures centre, real rotation, resolution, pedal range and spikes, and says what to change.
08 DesktopReads every flight device on your desk at once — stick, throttle, rudder pedals, yoke — and checks each axis for reach, centre, jitter, resolution and spikes, with the hat switch and every button.
09 DesktopEvery input from an arcade stick or leverless controller in numpad notation with the frames it was held, the motions you performed, and a two-step check of its SOCD mode against the tournament rule.
See every press, release, repeat and simultaneous key on a live keyboard map — ANSI, ISO or JIS, labelled with your own layout where the browser allows — and find the combinations your board drops.
02Test common gaming clusters and document which simultaneous key combinations your browser actually receives.
03Isolate one physical key, compare down-event intervals and separate suspicious chatter from normal held-key repeat behavior.
04 DesktopDrum across a few keys for ten seconds and see whether your keyboard reports at 125, 250 or 500 Hz, or faster — read from the rhythm of its events.
05 DesktopFind out whether your keyboard lets go of a key for you when you press its opposite — Snap Tap, Rapid Snap or SOCD handling — and time your own counter-strafes.
06 DesktopTap one key as fast as you can for five seconds: the page reads how long each press is held and how long the key stays released, and compares a run with rapid trigger off against one with it on.
07 DesktopMeasure actions per minute two ways: a drill of key and click prompts whose pace settles where you can keep up, and a free counter that separates real actions from spam.
Check primary, secondary, middle and auxiliary buttons, wheel direction and press duration in one focused test surface.
02Find suspiciously close browser click events with a transparent threshold and a session timeline.
03 DesktopMeasure your mouse's real report rate — every report timed as the operating system delivered it, not once per screen frame — with the interval spread and the gaps behind the number.
04 DesktopEstimate observed mouse DPI from a measured desk distance, repeat multiple runs and quantify variation instead of trusting one pass.
05 DesktopCheck a mouse sensor for acceleration, angle snapping, rest noise and tracking skips with raw counts, then compare two surfaces side by side.
06 DesktopSee the DPI, polling rate and battery your mouse is actually set to, read straight from the mouse with no software, then check it against a real measurement.
07Measure your clicks per second in 1 to 60 second modes or with the Space bar, see your best second and consistency, and catch clicks too fast to be human.
Measure the touch sampling rate, tap latency, refresh pacing, multi-touch capacity and motion-sensor rate of the phone or tablet you actually play on.
02 PhoneFind out if your phone is good for gaming in 90 seconds: touch response, display, slowdown when warm and network, scored and explained for BGMI, Free Fire, CODM and more.
03 PhoneMap multi-touch contacts, edge reach, contact duration and browser-exposed motion data on the phone or tablet you actually play with.
Measure the refresh rate your screen is actually running at, count dropped frames, and check the motion by eye.
02Benchmark reaction time, browser event-to-frame delay, key repeat, controller update rate and device identity on the hardware you actually play with.
03Measure click-to-photon system latency with a phone: the PC flashes on each click, the phone hears the click and sees the flash, and reports the median with an honest ± range.
04Test your reaction time in five trials and see your true reflex with the mouse, browser and screen delay measured and subtracted.
Five short checks with drawn drivers and a live scope: left and right, polarity, balance, how low and how high your headphones and ears reach, and a rattle sweep — each answer turned into a verdict.
02Shows your microphone’s level and spectrum live, then a ten-second check measures what your teammates hear — background noise, clipping, hum, Bluetooth hands-free quality — and the threshold to set; record and play it back.
03Plays each speaker of a 5.1 or 7.1 layout on your device’s own channels or through the browser’s 3D audio, tells you what is wrong from what you hear, and scores your footstep direction in both.
04Three ways to measure how late your sound arrives: tap to a beat, tap to a flash to cancel your own timing and find the audio/video gap, or loop a click through your microphone.
Check browser capabilities, connected input paths and the right next diagnostic in one private, exportable readiness report.
02Turn “my controls feel wrong” into a reproducible decision tree for controller, keyboard, mouse or touch problems.
03Search a conservative, source-linked compatibility table and distinguish native play, text-only, limited and unverified support.
A browser test can show whether a signal reaches the webpage, how it changes over time and whether a suspicious behavior repeats under controlled conditions. That is enough to narrow many practical problems: a stuck key, a controller axis that rests away from center, a mouse button that emits unusually close click events or an unstable pointer event stream.
It cannot see every layer between the physical switch and the operating system. Drivers, firmware, wireless links, calibration, power modes and browser scheduling remain part of the path. For that reason, Keymap Labs reports observations and timing distributions rather than declaring that hardware has passed a universal certification.
Every tool page includes its measurement boundary, interpretation and troubleshooting steps so the number is never separated from the decision it can support.
I answer from this site only — the 28 browser tests, the controls library for 46 games, the sensitivity converters and the two games. I can tell you which page to open, how a tool works and what its result means.
I will not guess. If something is not on the site, I will say so.
Answers come from this site's pages.