Controller button signals this page checks
This page focuses on button transitions rather than stick movement. It shows whether each physical control reaches the browser as a distinct button value, press, hold, and release.
Controllers
Gamepad Button Test: Controller Press and Release Checker
Gamepad button test for face buttons, D-pad, shoulder buttons, menu buttons, stick clicks, press counts, release events and possible stuck buttons.
Press count
Down / Up
Release timing
Hold time
Stuck button watch
Local
When this test helps
Use it when a face button misses inputs, a bumper double-fires, a D-pad direction is not recognized, a stick click feels stuck, or a controller works in one game but not another.
Details worth writing down
Record the button label or index, current value, press count, longest hold, missing release, mapping type, browser, connection mode, and whether the same button works in another app.
Live controller input
Connect a controller, then press a button or move a stick.
Waiting for input
Activate your controller
Connect by USB or Bluetooth, keep this tab visible, then press any controller button. Some browsers do not reveal an already connected controller until the first interaction.
Result summary
A compact view of the current test state and the strongest signal detected so far.
Waiting for controller input
Current controller
-
Controllers
0
Active buttons
0
Maximum axis offset
0.000
Press any controller button so the browser can expose the device.
Controller button press and release test steps
1. Connect or pair the controller and focus this tab. 2. Press one button once to activate Gamepad API visibility. 3. Press every face button, shoulder button, D-pad direction, menu button, and stick-click once. 4. Hold each suspect button for two to three seconds and release it cleanly. 5. Watch whether the value returns to 0 after release and whether the press count increases only once. 6. Repeat the same suspect button over USB and Bluetooth if the mapping or release behavior looks different.
How to read the result
A healthy digital button should switch to pressed and return to released when you let go. Analog buttons may show values between 0 and 1, but they should still return near 0. A missing button can be a mapping issue, an unsupported controller mode, browser compatibility, or another program capturing input. A button that stays pressed for several seconds after release is stronger evidence of a stuck switch or software interception.
Privacy and local processing
Button states, values, press counts, and hold durations are displayed locally in the tab. The tester does not upload input logs, controller IDs as account identifiers, or gameplay actions.
How to use Gamepad Button Test: Controller Press and Release Checker
Use it when a face button misses inputs, a bumper double-fires, a D-pad direction is not recognized, a stick click feels stuck, or a controller works in one game but not another.
Controller button test for press, release, and stuck buttons
The page checks button value, pressed state, repeated press count, current hold time, last release duration, D-pad visibility, shoulder buttons, triggers as buttons, and standard versus raw mapping labels.
Gamepad Button Test: Controller Press and Release Checker test steps
1. Connect or pair the controller and focus this tab. 2. Press one button once to activate Gamepad API visibility. 3. Press every face button, shoulder button, D-pad direction, menu button, and stick-click once. 4. Hold each suspect button for two to three seconds and release it cleanly. 5. Watch whether the value returns to 0 after release and whether the press count increases only once. 6. Repeat the same suspect button over USB and Bluetooth if the mapping or release behavior looks different.
Gamepad Button Test: Controller Press and Release Checker symptom troubleshooting
Match what you see with the page records first, then decide whether the next check is settings, connection, drivers, or the device itself.
A controller button does not respond
Press face buttons, shoulders, D-pad, and stick clicks one by one; watch down/up pairs.
If several browsers miss the same button, inspect mapping mode or hardware.
A released button stays active
Hold, then release, and watch whether the state returns to idle.
Missing release events point first to launchers, macros, or remapping tools.
D-pad or menu keys are confusing
Test D-pad, Start, Select, Home, or Share keys separately.
Some systems reserve Home or Guide keys, so absence alone is not proof of hardware failure.
A game uses the wrong action
Record the displayed button number and standard mapping state.
Check game bindings, Steam Input, or controller input mode.
Gamepad Button Test: Controller Press and Release Checker limits and privacy
What this page cannot prove
Standard mapping gives familiar Xbox-style labels, but some PlayStation, Switch, arcade, racing, or generic controllers may expose numbered buttons. That does not automatically mean the controller is broken.
Local processing and privacy
Button states, values, press counts, and hold durations are displayed locally in the tab. The tester does not upload input logs, controller IDs as account identifiers, or gameplay actions.
Related tools
Still narrowing it down? Open the next page that matches the symptom you can actually see.
Troubleshooting Center
Start with the symptom
Start here
Gamepad Tester: Buttons, Sticks & Controller Drift
Gamepad test for connection status, buttons, D-pad, stick axes, trigger values, mapping type and browser Gamepad API detection.
Controller Trigger Test: LT / RT Analog Range Checker
Controller trigger test for LT/RT or L2/R2 minimum value, maximum value, return-to-zero state, left/right range mismatch and analog mapping.
Stick Drift Test: Controller Joystick Deadzone Checker
Stick drift test for left and right stick center offset, X/Y axis drift, maximum offset, return-to-center stability and deadzone behavior.