We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Test your gamepad buttons, joysticks, triggers, and vibration online. Quickly diagnose controller performance issues.
Connect a gamepad and press any button to start.
If connected but not showing, try pressing buttons.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This tester displays connected gamepad controls as button entries (B0, B1, and so on) and axis entries (Axis 0, Axis 1, and so on). Each button shows a pressed state and a numeric value; each axis shows its current numeric reading. In the W3C Gamepad specification, button values are in the range 0 to 1 and axes are in the range −1 to 1. A button with an analog sensor can report intermediate values.
The page uses the browser's reported indices instead of assigning familiar labels such as A, X, left trigger, or right stick. The W3C standard mapping defines a conventional layout, but browser and device mappings can vary, and unrecognized devices may be exposed in their raw form. Treat the values as input observations, not a hardware verdict.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Connect the gamepad to your computer using its supported wired or wireless method. If the page still shows a connection prompt, press a controller button and watch for a device panel.
Press and release one physical button, then look for the corresponding B-number tile to change its highlighted state and value. Repeat for each control you want to check.
Move one stick slowly and observe which axis numbers change and in which direction. Release it and observe where the readings settle. The page reports the values to four decimal places; this is display precision, not a stated sensor accuracy.
Use cases
See how the tool fits into real work and everyday tasks.
Before launching a game, a player can press a few buttons and move each stick to see whether the browser receives changing input. If nothing appears, check the connection and try pressing a button again.
When describing an intermittent input to a technician, note which numbered button or axis changed and what action produced it. This gives a reproducible observation without claiming a specific component has failed.
Q&A
Find concise answers to common questions and confusing cases.
The page displays browser-reported array indices and values. Mapping labels can differ across controllers, operating systems, and browsers, so press a physical control and note which index changes on your setup.
No. You can observe whether an axis stays away from its usual center while untouched, but the page has no drift threshold, calibration, or hardware diagnosis. Check the controller in its system settings or another game as well.
No. It displays button and axis inputs; it does not trigger vibration or measure haptic output.
Notes
Review scope, result limitations, and important precautions before use.
Available devices, button ordering, axis ordering, and mappings depend on what the browser and operating system expose. The page does not test vibration, dead zones, polling rate, calibration, wireless stability, or behavior inside a particular game. A value near zero or a value that fluctuates is an observation to investigate, not a universal pass/fail threshold or proof of damage. For a repair or warranty decision, compare with the device's own settings and the intended game or hardware service process.
Related
Discover related tools, collections, and available API capabilities.