Check each browser-visible gamepad button, its raw index, release state and common simultaneous combinations. The live matrix records session coverage and recent press events without turning one browser reading into a hardware verdict.
LOCAL TESTButton values are read and processed only in this browser session.
Live diagnostic
Button input matrix
AWAITING CONTROLLER
Connect a controller and press a button.If your controller is supported by the browser, each input will light up below. Button names use the browser's standard mapping conventions when available; your physical labels may differ.
How to run a repeatable gamepad button test
Connect one controller, press a button to wake browser gamepad access, and keep this tab in the foreground.
Before touching a control, confirm ACTIVE NOW is zero. If not, note the active index before continuing.
Press every face, shoulder, menu, stick-click and D-pad control once; use TESTED INPUTS as a session checklist.
Repeat any suspicious button ten times at a steady pace, checking that each press appears once and returns to 0% after release.
For analogue triggers, watch the live percentage but use the dedicated trigger test for endpoint and resting-value comparisons.
Hold common two- and three-button combinations for a second and repeat each combination three times.
If a result matters, reset, reconnect, and repeat with only one variable changed: cable, port, Bluetooth, browser or device.
What this button test measures
The page reads the browser's Gamepad.buttons array. Each tile shows the reported index and current value; TESTED INPUTS records indices that crossed the page's active threshold during this tab session, while ACTIVE NOW counts simultaneous browser-visible inputs.
Standard-mapped devices receive conventional cross-family labels. Non-standard devices deliberately stay in index mode because a guessed physical label would be less honest than the raw browser position.
A visible press confirms that the browser reported an input. It does not certify switch force, electrical continuity, contact wear, latency or in-game mapping.
Worked gamepad button result examples
Observed pattern
Careful interpretation
Useful next check
A / Cross / B reports 100%, returns to 0%, and appears once in history
The browser saw a clean press-and-release cycle for that index in this run. It is useful session evidence, not a durability or latency certificate.
Repeat several times, then verify the same action inside the affected game or app.
Button 4 misses two of ten repeat presses
The missed browser-visible events are repeatable enough to investigate, but connection, focus, drivers, remapping and the physical button are still possible causes.
Reconnect, compare USB and Bluetooth where available, and repeat in another supported browser.
Button 7 rests at 12% after release
An analogue button value remains above zero in the browser. One reading is not enough to identify a worn trigger or calibration fault.
Open the trigger test, compare both sides and repeat after reconnecting.
A + B + RB reports three active inputs, but A + B + LB repeatedly reports only two
That exact combination is not reaching the browser consistently. Timing, mapping, transport, firmware or a physical input can all contribute.
Hold each button separately, repeat the combination three times, then compare the full controller test and the game.
Troubleshoot missing, stuck or mislabelled buttons
No controller appears: reconnect it, press a button after opening the page, keep the tab focused, and try the controller connection test.
The physical label differs: trust the raw index first. Xbox, PlayStation and Nintendo-style layouts use different symbols and order conventions.
A button never activates: check operating-system remapping, controller profiles and the same input in another browser before assuming a failed switch.
A value stays active: release every control, reset the session, reconnect and compare the same index again.
Only one combination fails: repeat at a slower pace and verify each member separately before treating it as a rollover limit.
The game behaves differently: inspect its own binding, deadzone, accessibility and controller-profile settings.
Limits of browser-based button diagnosis
Browsers receive an operating-system Gamepad API view, not raw switch or USB electrical data.
System, touchpad, capture, paddle and vendor-specific controls may be absent or mapped differently.
Most digital buttons expose only 0 or 1; the page cannot measure actuation force or contact resistance.
A standard label is a convenience across controller families, not proof of the physical legend.
Background throttling, focus, transport, firmware, drivers and remapping software can affect observed events.
This test cannot determine repair eligibility, warranty status or the exact internal cause of a fault.
Use repeatable browser evidence as a screening aid, not a repair or warranty decision. See the testing methodology and privacy policy.
Gamepad button test FAQ
Why does my PlayStation Cross button show as A?
When the browser reports a standard mapping, the page uses cross-family labels so the same browser index can be recognized across Xbox, PlayStation and Nintendo-style layouts. Use the reported index and live value when the physical symbol differs.
Why is a button missing or shown under the wrong index?
The controller may expose a non-standard mapping, a remapping layer may be active, or the operating system and browser may label the input differently. Compare the raw index in the full controller test before treating it as a hardware failure.
Can this test detect a stuck or intermittent button?
It can show a button that remains browser-active after release or misses repeated presses, but it cannot identify the physical cause. Repeat the same press sequence, reconnect the controller and compare another supported browser or device.
Why are LT and RT included in the button array?
Many standard-mapped controllers expose analogue triggers as GamepadButton values between 0 and 1. This page confirms activity; the dedicated trigger test is better for resting value, travel and repeatability.
Can I test simultaneous button presses here?
Yes. ACTIVE NOW shows how many browser-visible buttons are active together. Repeat the same combination several times because one missed attempt can come from timing, focus, mapping or the connection rather than controller rollover.
Can this page remap, calibrate or repair controller buttons?
No. It only reads the Gamepad API values exposed by the browser. It cannot change firmware, operating-system mappings, game bindings, switches, membranes, contacts or warranty status.
