Free Gamepad Tester for Buttons, Sticks, Drift, Deadzone, and Vibration
Connect a controller and inspect every browser-visible button, trigger, analog axis, mapping state, timestamp, and haptic capability in real time. Nothing is uploaded.
Gamepad Tester for Buttons, Sticks, Drift, Deadzone, and Vibration
Axes
Connect or move a controller.
Buttons
| Field | Browser value | Interpretation |
|---|
Built for a complete diagnostic workflow
Live multi-gamepad detection
Gamepad Tester workflow feature designed for practical browser use.
Per-button pressed and pressure state
Gamepad Tester workflow feature designed for practical browser use.
Analog stick and trigger axis readout
Gamepad Tester workflow feature designed for practical browser use.
Center calibration offset
Gamepad Tester workflow feature designed for practical browser use.
Adjustable deadzone preview
Gamepad Tester workflow feature designed for practical browser use.
Three-second stick drift sampler
Gamepad Tester workflow feature designed for practical browser use.
Largest-drift axis identification
Gamepad Tester workflow feature designed for practical browser use.
Gamepad mapping and timestamp display
Gamepad Tester workflow feature designed for practical browser use.
Connection and disconnection event log
Gamepad Tester workflow feature designed for practical browser use.
Haptic actuator capability check
Gamepad Tester workflow feature designed for practical browser use.
Copyable diagnostic snapshot
Gamepad Tester workflow feature designed for practical browser use.
Local checklist and learning progress
Gamepad Tester workflow feature designed for practical browser use.
How to interpret this gamepad tester
A browser gamepad tester is useful when a controller connects but a game, emulator, or web app behaves unexpectedly. The browser exposes standardized button and axis data for compatible devices, which makes it possible to confirm whether an input is reaching the page before troubleshooting a specific game.
Start with the controller resting on a flat surface. Look for axes that remain noticeably away from zero without touching a stick. Small offsets are common, so the deadzone control lets you see how much input would remain after a chosen software deadzone is applied.
Press every button slowly, then move each stick through its full range. Triggers may appear as buttons with analog values, axes, or both depending on the browser and controller mapping. The tester reports what the browser actually exposes rather than assuming a specific hardware layout.
The drift sampler is a consistency check, not a laboratory calibration. Firmware, wireless transport, operating-system drivers, browser mapping, and game-specific processing can all affect the final experience.
What the browser can and cannot tell you
| Signal | What it represents | How to use it |
|---|---|---|
| Resting axis | Near zero after calibration | Persistent offset may indicate drift or a calibration issue |
| Button value | 0 to 1 on analog-capable controls | A value that never reaches its expected range may need retesting |
| Deadzone | User-selected software threshold | Higher values hide small drift but reduce fine control |
| Mapping | Standard or device-specific | Standard mapping makes button positions more predictable |
| Timestamp | Browser gamepad update time | Useful for confirming that reports continue to refresh |
Build a better troubleshooting habit
Start with a baseline
Run the primary diagnostic before changing settings so you have a comparison point.
Repeat the test
One sample can be misleading. Repeat the check and compare the pattern, not only the best number.
Change one variable
When troubleshooting, change one device, browser, permission, cable, or setting at a time.
Separate browser from hardware
A browser result reflects only the parts of the input or output path that the page can observe.
Document the environment
Keep browser, operating system, device connection, scaling, or permission context with the result.
Use the next diagnostic
Open a related ready page when the result suggests a neighboring part of the device or browser stack.
Three quick questions
Finish with a quality review
Recent saved milestones on this device
Continue without a dead end
Free Gamepad Tester for Buttons, Sticks, Drift, Deadzone, and Vibration: FAQ
Does this gamepad tester require installation?+
No. It uses the browser Gamepad API and runs entirely on the page.
Can it detect stick drift?+
It can measure browser-reported resting axis offsets and sample the largest observed drift. That is a practical screening test, not a factory calibration.
Why are my button numbers different?+
Controllers and browsers can expose different mappings. A standard mapping is more predictable, while other devices may use device-specific indexes.
Can it test vibration?+
The page reports whether a browser-exposed haptic actuator is available and offers a short vibration test when supported.
Can it test more than one controller?+
Yes. It lists every gamepad returned by the browser and updates them independently.
Use the result responsibly
This tool reports what a browser can observe or calculate in the current environment. Device firmware, drivers, operating-system processing, permissions, transport, display refresh, acoustic conditions, and browser implementation can add behavior that this page cannot isolate.
External technical reference: MDN: Using the Gamepad API ↗.