Gamepad Tester / Controller Tester

A browser can expose controller values but cannot certify mechanical condition; compare neutral stick values and repeated movement patterns rather than one momentary sample.

Press a controller buttonThe browser exposes connected controllers after user interaction.

Controller diagnostic report

Summarize browser-visible controller state: neutral-axis excursion, pressed buttons, analog activity, mapping and vibration capability.

Controller evidence

Controller	Axes / drift	Buttons	Capabilities

Timed neutral-stick drift sample

Leave the controller untouched while the browser samples the first connected gamepad. The motion trail and suggested deadzone use browser-visible axis values only.

—Left-stick max excursion

—Right-stick max excursion

—Suggested starting deadzone

Connect a controller and leave both sticks untouched during the sample.

What this tool checks

Inspect Gamepad API buttons, triggers, axes and stick positions locally in real time.

How to use the result

A browser can expose controller values but cannot certify mechanical condition; compare neutral stick values and repeated movement patterns rather than one momentary sample.

Privacy & browser limits

Device streams and input events used by this page are handled in your browser unless the page explicitly says otherwise. Permission, label, timing and hardware-field availability depend on the browser and operating system.

Controller state now includes a neutral-axis drift sample

A user-triggered neutral sample reports the largest browser-visible axis excursion while the controller rests. This helps compare drift symptoms without claiming raw USB/HID calibration or hardware dead-zone certification.

Practical guide and verification

Sample neutral sticks instead of judging one frame

Analog sticks continuously report small values around center. A timed idle sample is more useful than one momentary reading because it exposes the maximum browser-visible excursion and whether the center moves consistently in one direction.

Treat the suggested deadzone as evidence, not calibration

The deadzone estimate is derived from the largest observed neutral excursion plus margin. Games use different response curves and controller firmware can apply its own processing, so copy the observed value into a game only as a starting point and retest movement.

Keep hands off the sticks during a drift sample

Any intentional movement becomes indistinguishable from drift to the browser. Place the controller on a stable surface, release triggers and sticks, then run the sample. Repeat it if the controller was touched or if the browser briefly lost focus.

Browser values do not certify hardware condition

The Gamepad API exposes processed axes and buttons selected by the browser, operating system and controller mapping. It cannot inspect potentiometers, Hall sensors, firmware calibration or mechanical wear directly. Use the result as local input evidence.

Retest after changing one variable

If neutral excursion looks high, repeat the same sample after reconnecting, changing the USB/Bluetooth path, recalibrating through supported system tools or trying another browser. A repeatable change is stronger diagnostic evidence than a single session.