Your input path, timed
Reaction blocks, event-to-frame delay, OS key repeat, controller update rate and USB device identity in one session report.
Open the latency lab →Browser-based diagnostics for controllers, keyboards and mice—plus transparent setting converters built for players who want evidence, not guesswork.
Three pages that change with the games: what is free right now, what is releasing, and how every popular game is controlled.
Epic and Steam giveaways with the real claim deadlines, plus next week's Epic titles.
Open data · dailyRelease calendarEvery game coming out in the next six weeks, filtered by platform, with links to its controls.
Controls LibraryGame controls & keybindsDefault bindings on keyboard and every controller, a visual keyboard map and quick "how do I" answers.
Every lab explains what it can observe, what the browser may hide and what to try next. Results stay connected to a practical decision.
Check every reported button, trigger and axis in real time—without installing software or sending controller data to a server.
02Measure the observed center offset, maximum movement and stability of both analog sticks with a repeatable browser test.
03Measure the resting center, add a transparent safety margin and find the smallest practical game deadzone without hiding slow intentional input.
04See every press, release, repeat and simultaneous key on a live keyboard map, and find the combinations your board silently drops.
05Test common gaming clusters and document which simultaneous key combinations your browser actually receives.
06Check primary, secondary, middle and auxiliary buttons, wheel direction and press duration in one focused test surface.
07Find suspiciously close browser click events with a transparent threshold and a session timeline.
08 DesktopMeasure the rate and stability of pointer events delivered to your browser during a guided movement sample.
09A sensitivity converter and sensitivity calculator in one: convert hip-fire sensitivity between 22 games, keep the same physical cm/360 and see the formula behind the result.
10Check browser capabilities, connected input paths and the right next diagnostic in one private, exportable readiness report.
11Analyze recenter stability, full-circle coverage, outer range, symmetry, triggers and two connected controllers in repeatable stages.
12 PhoneMap multi-touch contacts, edge reach, contact duration and browser-exposed motion data on the phone or tablet you actually play with.
13 DesktopEstimate observed mouse DPI from a measured desk distance, repeat multiple runs and quantify variation instead of trusting one pass.
14Isolate one physical key, compare down-event intervals and separate suspicious chatter from normal held-key repeat behavior.
15Model your keyboard, mouse and reach, then compare three explainable keybind plans without uploading the layout.
16Search a conservative, source-linked compatibility table and distinguish native play, text-only, limited and unverified support.
17Turn “my controls feel wrong” into a reproducible decision tree for controller, keyboard, mouse or touch problems.
18Use four transparent calculators for Minecraft portal coordinates, frame-time budgets, deadzone scaling and touch-target planning.
19Benchmark reaction time, browser event-to-frame delay, key repeat, controller update rate and device identity on the hardware you actually play with.
20 PhoneMeasure the touch sampling rate, tap latency, refresh pacing, multi-touch capacity and motion-sensor rate of the phone or tablet you actually play on.
21 DesktopCheck a mouse sensor for acceleration, angle snapping, rest noise and tracking skips with raw counts, then compare two surfaces side by side.
22Measure 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.
23 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.
24Calculate eDPI for any supported game, see where it lands among pro settings, convert it to cm/360 and keep the same feel when you change DPI.
25 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.
26 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.
27Test your reaction time in five trials and see your true reflex with the mouse, browser and screen delay measured and subtracted.
28Measure 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.
29A 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.
General knowledge cannot see your hardware. These labs measure the device in front of you and keep the evidence on your side of the screen.
Reaction blocks, event-to-frame delay, OS key repeat, controller update rate and USB device identity in one session report.
Open the latency lab →A five-second untouched sample with average, maximum and stability per stick, plus a deadzone recommendation you can verify.
Run the drift test →Measure real sensor counts over a marked desk distance and compare the median of repeated runs with the number printed on the box.
Measure DPI →Median, P95 and long-gap share across comparable runs instead of one flattering peak number.
Benchmark polling →Hold the movement, sprint and ability clusters you actually use and record the physical codes that fail to arrive.
Test ghosting →Raw touch samples per second, tap-to-frame delay, refresh pacing, simultaneous contacts and sensor rate, measured on the phone in your hand.
Test touch sampling rate →Start with the exact title, platform and input method. Each hub sends the player to a working test and refuses unsupported conversions.
monster hunter wilds focus mode · mh wilds controls
Open game lab →02 / MLBBmobile legends controls · mlbb custom hud settings
Open game lab →03 / BSbrawl stars controls · brawl stars aim tips
Open game lab →04 / SF6street fighter 6 controls · sf6 modern vs classic
Open game lab →05 / T8tekken 8 controls · electric wind god fist how to
Open game lab →06 / 2K27nba 2k27 controls · nba 2k27 new controls
Open game lab →A lab reading is most useful when it is repeatable and interpreted inside its technical boundary.
See the exact events, buttons, axes or pointer samples delivered to the browser.
Use timing, distributions and repeatable conditions instead of reacting to one noisy number.
Compare browsers, ports and devices before changing settings, buying hardware or requesting repair.
Convert hip-fire sensitivity across 22 documented game models, compare every game at the same cm/360, solve for a target distance and save the result inside a device-local profile.
Sample the resting stick, calculate its 95th-percentile center, add a visible margin and verify that deliberate micro-movement still escapes the proposed deadzone.
Large targets, plain-language states and device-specific paths keep the site useful when a controller is drifting or a key combination will not register.
Live maps, axis plots and repeatable center samples.
Physical codes, active groups and realistic ghosting clusters.
Buttons, wheel, unintended repeats and observed pointer rate.
Keymap Labs does not pretend a browser can certify hardware. It gives you clearer evidence, game-aware routes, a repeatable tuning path and portable local reports.
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.