Neutral sample
Stick drift and deadzone
Set the controller on a steady surface and do not touch either stick during the sample.
Ready for an 8-second sample.
Button input diagnostics
Controller Button Test
Press every browser-reported controller button and verify live response, analog values, stuck inputs, and missed or repeated presses.
- ✓ Runs in your browser
- ✓ No sign-in
- ✓ Local results
Local-only test
Connect with USB, Bluetooth, or a supported wireless adapter. Then press any controller button so your browser can expose it. Your readings are processed on this device.
Detected device
No controller detected
Gamepad API ready · waiting for input
L1
R1
L
R
Update rate— Hzbrowser-observed
Buttons—reported
Axes—reported
Mapping—browser label
Live input
Sticks and triggers
Left trigger 0%
Observed range: not sampled
Right trigger 0%
Observed range: not sampled
Full movement
Range and circularity
Rotate each stick slowly around the outer edge, then sweep the center in several directions.
Move the sticks to begin range tracking.
Input coverage
Buttons and D-pad
Press and release every available control. Analog buttons show their reported value.
No button activity yet.
Raw browser data
Axes and mapping
Use these values to spot unusual layouts. A blank standard mapping does not automatically mean the controller is defective.
View raw browser data
Connect a controller to view raw data.
Optional capability
Vibration check
Browser haptics are not available for every controller, connection method, operating system, or browser.
Connect a controller to check browser support.
Did you feel the pulse?
Private test record
Keep your result
Reports are stored in this browser. Sharing is optional and puts only the selected result in the link.
Diagnostic readings describe what this browser receives, not electrical measurements from the controller. Confirm important findings in the game or device where you plan to use the controller.
Use the test as evidence, not a pass/fail sticker.
The button test shows which inputs your browser receives when you press the face buttons, shoulder buttons, stick clicks, menu buttons, and directional pad. A coverage checklist makes it easy to spot an input that never appears.
Press each button once, then repeat quick and slow presses on any control that feels unreliable. Analog-capable buttons such as triggers may report values between fully released and fully pressed, while most other buttons behave like on-or-off switches.
Button numbers and labels depend on the browser's gamepad mapping. If the highlighted label does not match the physical control, the controller may be using a nonstandard layout rather than having a broken button.
Signals to watch
- Live button state and reported pressure value
- Coverage checklist for all exposed buttons
- Visual indication for held or potentially stuck inputs
- Raw button index view for unusual controller layouts
Run a repeatable check.
- 01
Connect the controller and press any button so the browser can detect it.
- 02
Use the focused test panel slowly and deliberately. Watch the live values during presses, holds, movement, and release.
- 03
Repeat any suspicious result after reconnecting, then confirm it in the game or device where the controller will be used.
What a useful result looks like.
Look for repeatable behavior rather than a single momentary value. Stable, symmetric movement and clean press-and-release behavior are generally more useful signs than chasing a perfect zero.
If a result changes substantially between USB and wireless modes, browsers, or computers, the connection, driver, browser, or remapping software may be part of the problem.
Important browser-test limits
System, capture, touchpad, paddle, and profile buttons are not exposed on every platform.
Questions about controller button test
Why is my button shown with the wrong name?
Browsers apply the standard gamepad layout only when they recognize the device mapping. Generic, DirectInput, retro, and mode-switching controllers may expose different button indexes.
Can the test find double inputs?
It can help you observe rapid state changes and repeated activations. However, browser sampling and operating-system processing mean it cannot certify the switch's electrical behavior.
Why are some buttons missing?
A special button may be reserved by the console, firmware, operating system, or browser and never reach a webpage. Try another connection mode or the manufacturer's supported software.