Gamepad Tester
See every button, stick and trigger on your controller report live — and catch stick drift red-handed.
Controllers fail quietly. A button that only registers at the bottom of its travel, a trigger that tops out at 0.87, a stick that creeps a few percent to the left while your thumb is nowhere near it — games feel “off” long before the cause is obvious. This tester makes the controller narrate itself: through the browser’s Gamepad API it polls ten times a second and shows every button’s pressed state and analogue value, and every axis twice — raw, and after the deadzone — so you can watch behaviour instead of guessing at it.
Connect a controller, press any button on it to wake it up, and watch every button, stick and trigger report live — including the slow stick drift that ruins aim.
Drift check: leave the controller untouched on a flat surface. If an axis sits outside the deadzone while nothing is pressed, that stick is drifting. Everything is read locally through the browser's Gamepad API — nothing about your controller leaves this page.
Quick answers
How do I test a gamepad in the browser?
Connect the controller, press any button to wake it, and poll the Gamepad API: every button shows its pressed state and value, every axis its live position. This page polls ten times a second.
The press-to-wake step is a browser privacy rule, not a fault — a controller that has never had a button pressed stays invisible to web pages on purpose.
How can I tell if my controller has stick drift?
Leave it untouched and watch the axes: a centred stick should read near zero and 0 after the deadzone. An axis that persistently sits outside the deadzone — beyond 0.15 at the default — with nothing touching it is drifting.
Values are rescaled past the deadzone, so a raw 0.5 reads as about 0.412 corrected. Mild drift can be masked by a larger in-game deadzone; severe drift is a worn stick module.
How to use
- Connect your controller by USB or Bluetooth, then press any button on it — browsers hide gamepads until one is pressed.
- Press Start polling and work through every button; each one lights up with its live value as you press it.
- Wiggle both sticks and both triggers through their full travel and watch the axis values follow.
- Finally, hands off: leave the controller flat and untouched. Any axis sitting outside the deadzone on its own is drifting.
About this tool
The drift check is the part worth doing slowly. A healthy stick at rest reports an axis value near zero (small noise like 0.003 is normal); the deadzone setting, 0.15 by default, is the margin games themselves apply to ignore that noise. This page rescales honestly — a raw 0.5 with a 0.15 deadzone reports as (0.5 − 0.15) ÷ (1 − 0.15) ≈ 0.412, not a raw repeat — and it names any axis that sits outside the deadzone while polling. If that happens with the controller untouched on a table, the stick is drifting, and no in-game setting is the root cause (though a larger in-game deadzone can mask mild cases). Everything is read locally; the browser API exposes the controller to this page only, and nothing is recorded or sent anywhere.
Frequently asked questions
Why does the tester say no gamepad is detected?
Usually because the browser has not been introduced to it yet: for privacy, the Gamepad API hides controllers until you press a button on them, so connect the controller and press any button, then start polling. After that, check the obvious — Bluetooth actually paired, USB cable that carries data and not just power, and a browser tab that is focused, since polling pauses in background tabs.
How do I check for stick drift with this tool?
Start polling, put the controller down flat, and touch nothing. Each axis should read near zero and, after the deadzone, exactly 0. If an axis persistently reads outside the deadzone — say a raw 0.21 against a 0.15 deadzone — while nothing is pressed, that stick is drifting. Test all four stick axes (both sticks, both directions) and re-check after a few full circles of the stick, since drift often shows worst right after movement.
What does the deadzone value do?
It is a margin around zero that counts as “centred”. Raw values inside it report as 0; values outside it are rescaled so the remaining travel still spans 0 to 1 — a raw 0.5 at a 0.15 deadzone becomes about 0.412. Games apply their own deadzones for the same reason: no analogue stick rests at a perfect 0.000.
The buttons light up but the numbers look wrong. Is the controller broken?
Not necessarily. Button numbering follows the “standard mapping” where the browser supports it, but some controllers report a vendor layout, so B7 might be a trigger on one pad and a bumper on another. Judge the pad by whether every control responds smoothly and returns to rest — the labels are a map, and a few controllers simply draw the map differently.
First time embedding? Read the step-by-step guide →
More free tools
Typing Speed Test
How fast can you type? Measure your WPM and accuracy in one minute or less.
Click Speed Test
Take the 5-second CPS test: click as fast as you can and get your clicks per second.
Keyboard Tester
Press any key and watch it light up — check every key on your keyboard works.
Microphone Test
Check your microphone works — see your voice level live and record a short playback.
Webcam Test
Preview your camera before the call — and snap a test photo to check the picture quality.
Dead Pixel Test
Fill your screen with five solid colours, one at a time, to spot dead and stuck pixels.