Decide which control is failing
Name the failing control. Is it a button, trigger, stick direction or a connection that disappears? Record the game and connection used there. A single browser pass cannot answer all those questions at once.
Keep one setup for the baseline. Check the system connection before changing bindings. A USB or Bluetooth route can affect what the page exposes, but changing route and application settings together makes the next observation hard to interpret.
Record a remapping profile before changing it. A tool can transform input before the page receives anything. A different browser reading after the change establishes a difference in the setup, not the electrical cause of a fault.
How to test a controller on PC
Open the gamepad test and press a controller button. Does a name appear? An empty page before activation is not a hardware verdict. If it stays empty, confirm system recognition and try one documented connection change.
Press buttons and triggers in a written order, releasing each before moving on. Compare displayed values with what you did. A vendor paddle or unlabelled extra control may reflect a mapping gap rather than a failed standard button.
Move both sticks and confirm the expected axes exist before recording values. A missing axis is not a centred value. For a rest comparison, put the pad down and run the stick drift test separately.
Check each trigger slowly. Some mappings expose an analogue value; others expose a button-like action. Record what the browser displays instead of assuming every model must sweep through the same range.
Repeat the original game action under the same binding. Browser and game routes differ. A clean page sample narrows the question but cannot certify that the game handles the input identically.
Follow one controller test checklist
Keep the controller, connection, browser and remapping profile unchanged for the first run. Press and release each control separately; wait for its displayed value to return before moving on.
Follow this order in the gamepad test.
- Face buttons and D-pad: press one direction or button at a time and note the browser label that changes.
- Shoulder buttons and stick clicks: press and release each exposed control once, then repeat the suspect control.
- Triggers: squeeze each slowly and record the visible values. A digital jump or missing entry may be a mapping limitation; it is not proof of worn hardware.
- Sticks: move each through its directions and release it. Check that the expected axes are exposed. Use the separate stick drift test for an untouched rest sample.
- Original symptom: repeat the same action in the affected game with the same route and profile. Change one condition only for the second comparison.
Keep a browser-versus-game record
| Control or symptom | Browser label and observed value | Game behaviour | Connection and profile | One changed condition |
|---|---|---|---|---|
| Baseline: ______ | ______ / Not exposed | ______ | ______ | None |
| Repeat: ______ | ______ / Not exposed | ______ | ______ | ______ |
Write “not exposed” instead of zero for an absent entry. This is a manual note, not a hardware pass certificate. If both runs differ, retain the details for support rather than choosing a component to replace.
For missing input, see controller not detected; for labels, see button mapping.
Hardware fault or game binding?
A control that changes here reached the browser during this run. A silent control needs a mapping and application comparison. The page cannot inspect its switch, so one missing value is a symptom rather than a confirmed physical fault.
Does it work here but fail in one game? Compare the game's selected controller, binding, dead zone and remapping profile. Do not assign the cause to the game merely because a browser received a button event.
An absent axis or vendor control leaves that portion incomplete. The browser's standard mapping is not a catalogue of all physical features. Record the model, route and missing entry for support.
What the Gamepad API cannot show
The browser samples mapped Gamepad API values during animation frames. That is page sampling, not the controller report rate. It cannot read raw stick values, firmware calibration or every accessory control.
Battery and vibration support vary by device and route. A disconnect event cannot explain why the pad disappeared. Compare cable, power and wireless conditions as separate checks.
Missing input must remain missing. A page should not turn an absent axis into a healthy zero or claim a complete pass for an unobserved control. Verify the original task in the application that matters.
Repair, remap or replace
Repeat the failing control after one connection or application change. A symptom that follows the pad deserves model-specific support review, but the browser cannot choose a replacement part or guarantee warranty coverage.
If only one game differs, compare bindings and dead-zone settings while keeping the controller setup fixed. A setting can suppress unwanted motion without repairing a physical component.
For dropouts, log when the device disappears and whether the route is wired or wireless. Try a documented alternative for the model. Do not promise that moving a receiver or changing a hub resolves every dropout.
Symptom table
| Symptom | Likely layer | Next action |
|---|---|---|
| A button never changes | Input was not observed; mapping or access needs comparison | Confirm the exposed label, repeat the same control and compare another supported route. |
| Trigger jumps from 0 to 1 | The browser may expose a digital mapping | Record the values and compare the same trigger in the game; do not diagnose wear from this alone. |
| Pad disappears during a run | The browser lost access to the device | Record when it disappeared, check system recognition and begin a fresh run after a single connection change. |
Common questions
Why does my controller not show up until I press a button?
Press a controller button in the foreground tab. Some gamepads are not exposed before user action. If still absent, check system recognition and the route. The page cannot identify a physical fault from that missing entry alone.
Can I test a PlayStation or Xbox controller in a browser?
A PlayStation or Xbox pad can be checked when the system and browser expose it through Gamepad API. Available buttons and axes vary by mapping and connection. This guide cannot promise every model or vendor feature will be represented.
My controller works in the browser but not in my game. Why?
The game may select another controller, mapping, dead zone or input route. Compare those settings with what the browser exposed. A working page sample does not prove game configuration is the only possible cause.
How do I test PS5 controller inputs on PC?
Connect the controller, press a button, then check face controls, triggers and both sticks in a fixed order. Mark an absent axis incomplete. Record the browser result and compare the affected game's mapping before a service decision.