Choose the right controller test tools
The controller test tools on this site are grouped by job, not by template. Start with the gamepad tester on the home page when you need a fast overview, then move to a focused tool when one symptom needs deeper evidence.
For repair notes, used-controller checks, and support conversations, combine a focused tool with the controller test report so the next person can see the browser, connection method, mapping, button count, axis count, and disclaimer.
- Core tests cover buttons, sticks, triggers, controller detection, and raw browser input.
- Precision tools cover drift, deadzone, circularity, polling rate, latency, and mapping.
- Hardware feedback tools cover vibration exposure and microphone checks when the browser exposes them.
- Reports and widgets help you document or embed a lightweight testing workflow.
When to use a focused tool
Use the stick drift test when the character moves at rest, the deadzone test when a small drift needs a practical setting, and the circularity test when a repaired stick feels uneven near the outer edge.
Use the polling rate and latency pages when Bluetooth feels unstable, a receiver feels inconsistent, or a wired connection appears smoother. These readings are browser-level estimates, so they should guide troubleshooting rather than serve as hardware-lab proof.
Controller test tools by symptom
Controller test tools work best when the page matches the symptom. Use the full gamepad view when the problem is unclear, a button page when one input sticks, a drift page when movement happens at rest, and polling or latency pages when the connection feels inconsistent. That keeps controller test tools useful instead of turning them into a wall of identical checks.
The controller test tools directory is also a planning page. Repair notes, buyer checks, and support conversations often need different evidence, so the best controller test tools path is the shortest path to the symptom you can repeat.
- Start broad, then choose focused controller test tools.
- Use report tools when the result needs to be shared.
- Use widgets when controller test tools belong inside another guide.