A simple workflow for everyday checks
Start with connection status and button response, then move both sticks slowly, squeeze each trigger, and run a short drift sample while the controller rests untouched. This sequence catches most common symptoms without changing device settings.
For used controllers, repeat the test over USB and Bluetooth when possible. Differences between the two modes can point to connection, driver, or adapter behavior rather than the physical controller alone.
- Check every face button, shoulder button, stick click, and D-pad direction.
- Watch for buttons that stay pressed after release.
- Compare left and right stick center behavior.
- Confirm that trigger values move smoothly instead of jumping straight from 0 to 1.
Local testing and privacy boundaries
Gamepad input is read by the browser and rendered on the page. The site does not upload button values, axis values, controller names, microphone audio, or generated reports to a server. For Controller Tester, treat that limit as part of controller tester guidance rather than as a separate verdict.
Microphone recording starts only after you press the recording button and grant browser permission. Playback and deletion happen locally in the browser. On this Controller Tester page, compare that note with the live module that matches connection status, standard mapping, button response, stick movement, trigger range, and device-level feature exposure.
Browser and hardware limits
Gamepad API support, haptic feedback, MediaRecorder, and WebHID are exposed differently across Chrome, Edge, Firefox, Safari, Linux, mobile browsers, USB, Bluetooth, and third-party drivers. For Controller Tester, treat that limit as part of controller tester guidance rather than as a separate verdict.
A missing feature in the browser does not prove that the controller is damaged. Use the live readings as diagnostic hints and compare results across connection methods when possible. On this Controller Tester page, compare that note with the live module that matches connection status, standard mapping, button response, stick movement, trigger range, and device-level feature exposure.
Controller tester troubleshooting notes
A controller tester is most useful when you run it before changing several settings at once. Start with a wired pass if possible, then repeat the controller tester check over Bluetooth only after the first result is clear. That order helps separate a weak cable, a noisy wireless adapter, and a worn control from each other.
When the controller tester shows every button but a game still misses input, the next place to inspect is the game's input layer. Steam Input, emulator profiles, accessibility remaps, and per-game presets can all change behavior after the browser has already shown a healthy controller tester result.
- Use the controller tester first when the whole pad feels unreliable.
- Use a focused drift, trigger, vibration, or mapping page when one symptom is isolated.
- Save a controller tester report only after the same symptom repeats.