Gamepad Tester

This controller tester reads input from a connected gamepad while the page is open. The browser starts sharing gamepad input with the page after the first button press, so press a button when the test is ready. The page then checks the controls as their readings update.

You can see a reading for every button, including its analog value when one is available. The test also draws both stick paths, shows trigger readings as bars and can try vibration where the device and browser support it. These readings help you see which controls respond and how their input changes.

The page may show a model name based on the gamepad identification string supplied by the browser. It uses the vendor and product identifiers in that string to select a model row and its button labels. If the browser does not provide a useful identification string, the shown model or labels may not identify your device.

Button readings show which buttons the test detects and each button's analog value. A button that does not change its reading when pressed may not be reaching the page. A changing reading shows that the page is receiving input, but the test does not tell you whether the button feels right or works in every game.

The stick drawings trace the paths of both sticks as they move. A circle marks the suggested dead zone, an area near the center where small movements may be treated differently. If a stick path moves while you are not touching the stick, that can point to unwanted input. The circle is a visual reference, not a pass or fail boundary supplied by the test.

Trigger bars show the input reported for each trigger. The update timestamps are used to estimate how often the browser reports changes. This is the browser's update rate, not the gamepad's USB polling rate, so do not use it as a reading of the device's USB connection speed.

The vibration check tries a rumble effect where supported, including trigger rumble on devices that support it. If you do not feel vibration, the test cannot tell from that alone whether the gamepad is broken. Support for the effect varies by device and browser.

If the page shows no input, first remember that it needs a button press before the browser shares gamepad input. If readings still do not appear, or a control does not change as you use it, the test has found a result worth checking. A model name or button label that looks unfamiliar can also reflect the identification information the browser supplied.

If a stick path moves while the stick is untouched, or a button or trigger reading behaves unexpectedly, use the page's linked the controller connection guide for next steps. The guide is there for connection and input problems; the test itself reports readings and does not repair the device.

Treat the display as a check of what the browser reports to this page. It cannot establish how the controller behaves in every other setting, and a missing vibration response does not by itself show that other controls have failed.

After the first button press, the page checks the gamepad on each animation frame, the repeated drawing update used while the page is active. It records button readings and stick positions as they arrive, draws the stick paths, and updates the trigger bars. The timestamps support an estimate of the browser's reporting rate.

Vibration is checked by asking the gamepad to play a rumble effect where supported. The test also reads the browser's gamepad identification string and uses its vendor and product identifiers to choose a model row and labels. The browser supplies this information, so the selected model is based on what it reports.