Independent input intelligence

Test the signal.
Own the setup.

Browser-based diagnostics for controllers, keyboards and mice—plus transparent setting converters built for players who want evidence, not guesswork.

Input stays on your device No account or install Limits documented
29Browser labs
31Game labs
22Sensitivity models
0Raw input uploads
Signal deck / live previewLocal
Move, press or connectThis panel reacts to your real mouse, keyboard and controller. Nothing leaves the page.
Pointer rate
Last key
Controller
Events0
Private by designRaw input stays in your browser
Repeatable resultsCompare the same test under the same conditions
Clear limitationsEvery result explains what it can and cannot prove
Built around real gamesFind the right workflow by title, platform and input
Start with the signal

Useful tests, not toy widgets

Every lab explains what it can observe, what the browser may hide and what to try next. Results stay connected to a practical decision.

01

Gamepad Tester

Check every reported button, trigger and axis in real time—without installing software or sending controller data to a server.

Run diagnostic
02

Stick Drift Test

Measure the observed center offset, maximum movement and stability of both analog sticks with a repeatable browser test.

Run diagnostic
03

Controller Deadzone Tuner

Measure the resting center, add a transparent safety margin and find the smallest practical game deadzone without hiding slow intentional input.

Open tune lab
04

Keyboard Tester

See every press, release, repeat and simultaneous key on a live keyboard map, and find the combinations your board silently drops.

Run diagnostic
05

Keyboard Ghosting Test

Test common gaming clusters and document which simultaneous key combinations your browser actually receives.

Run diagnostic
06

Mouse Tester

Check primary, secondary, middle and auxiliary buttons, wheel direction and press duration in one focused test surface.

Run diagnostic
07

Double-Click Test

Find suspiciously close browser click events with a transparent threshold and a session timeline.

Run diagnostic
08 Desktop

Mouse Polling Rate Test

Measure the rate and stability of pointer events delivered to your browser during a guided movement sample.

Run diagnostic
09

Sensitivity Converter

A 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.

Open AimCurve
10

Game Input Readiness Scan

Check browser capabilities, connected input paths and the right next diagnostic in one private, exportable readiness report.

Run diagnostic
11

Advanced Gamepad Analyzer

Analyze recenter stability, full-circle coverage, outer range, symmetry, triggers and two connected controllers in repeatable stages.

Run diagnostic
12 Phone

Touchscreen & Gyro Lab

Map multi-touch contacts, edge reach, contact duration and browser-exposed motion data on the phone or tablet you actually play with.

Run diagnostic
13 Desktop

Mouse DPI Analyzer

Estimate observed mouse DPI from a measured desk distance, repeat multiple runs and quantify variation instead of trusting one pass.

Run diagnostic
14

Keyboard Chatter Test

Isolate one physical key, compare down-event intervals and separate suspicious chatter from normal held-key repeat behavior.

Run diagnostic
15

BindIQ Keybind Optimizer

Model your keyboard, mouse and reach, then compare three explainable keybind plans without uploading the layout.

Open tune lab
16

Console Keyboard & Mouse Support Finder

Search a conservative, source-linked compatibility table and distinguish native play, text-only, limited and unverified support.

Run diagnostic
17

Gaming Input Problem Solver

Turn “my controls feel wrong” into a reproducible decision tree for controller, keyboard, mouse or touch problems.

Run diagnostic
18

Gaming Calculator Suite

Use four transparent calculators for Minecraft portal coordinates, frame-time budgets, deadzone scaling and touch-target planning.

Open AimCurve
19

Input Latency Test

Benchmark reaction time, browser event-to-frame delay, key repeat, controller update rate and device identity on the hardware you actually play with.

Run diagnostic
20 Phone

Touch Sampling Rate Test

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.

Run diagnostic
21 Desktop

Mouse Sensor Lab

Check a mouse sensor for acceleration, angle snapping, rest noise and tracking skips with raw counts, then compare two surfaces side by side.

Run diagnostic
22

System Latency Test (Photon Lab)

Measure 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.

Run diagnostic
23 Desktop

Controller HID Inspector

Read 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.

Run diagnostic
24

eDPI Calculator

Calculate 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.

Open AimCurve
25 Desktop

Mouse Settings Checker

See 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.

Run diagnostic
26 Phone

Phone Gaming Test

Find 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.

Run diagnostic
27

Reaction Time Test

Test your reaction time in five trials and see your true reflex with the mouse, browser and screen delay measured and subtracted.

Run diagnostic
28

CPS Test (Click Speed)

Measure 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.

Run diagnostic
29

Controller Check

A 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.

Run diagnostic
Measured, not guessed

What a chatbot cannot tell you

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 · delay · update rateNew

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 →
Center sample · both sticks

Does this controller drift?

A five-second untouched sample with average, maximum and stability per stick, plus a deadzone recommendation you can verify.

Run the drift test →
Observed counts · repeat runs

Is the DPI label honest?

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 →
Interval distribution · gaps

How stable is the polling stream?

Median, P95 and long-gap share across comparable runs instead of one flattering peak number.

Benchmark polling →
Physical codes · real clusters

Which key combinations vanish?

Hold the movement, sprint and ability clusters you actually use and record the physical codes that fail to arrive.

Test ghosting →
Panel Hz · tap latency · refreshNew

How fast is this phone's touch panel?

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 →
One clear workflow

Observe. Compare. Decide.

A lab reading is most useful when it is repeatable and interpreted inside its technical boundary.

1. Observe live input

See the exact events, buttons, axes or pointer samples delivered to the browser.

2. Run a defined sample

Use timing, distributions and repeatable conditions instead of reacting to one noisy number.

3. Confirm the cause

Compare browsers, ports and devices before changing settings, buying hardware or requesting repair.

AimCurve / Sensitivity workspace

Carry your physical aim distance—and keep the result.

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.

AimCurve / normalized turnReproducible
SourceCS2
Physical32.47 cm
TargetVAL
Deadzone Tuner / Guided sampling

Find the smallest deadzone that actually solves the problem.

Sample the resting stick, calculate its 95th-percentile center, add a visible margin and verify that deliberate micro-movement still escapes the proposed deadzone.

Built for real players

Readable in the middle of a problem.

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.

Controller labs

Live maps, axis plots and repeatable center samples.

Keyboard labs

Physical codes, active groups and realistic ghosting clusters.

Mouse labs

Buttons, wheel, unintended repeats and observed pointer rate.

Measurement-first tools

Know what the browser knows. Keep what matters.

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.