What Gamepad Tester Pro checks
The gamepad tester combines a controller button test, joystick tester, stick drift test, trigger meter, deadzone checker, short vibration pulses, microphone recording, compatibility notes, and a local report generator.
It supports up to four connected gamepads where the browser exposes them. Standard mappings are labeled with familiar names such as A, B, X, Y, L1, R1, L2, R2, Share, Options, Start, Select, L3, R3, and D-pad directions. Unknown layouts fall back to raw button and axis indexes.
- Live button state, analog value, touched state, and last pressed input.
- Left and right stick X/Y values, center offset, movement trail, peak reach, and circular range hints.
- Idle drift sample with average offset, peak offset, stability, direction bias, and suggested deadzone.
- Trigger pressure range, smoothness hints, peak value, and mapping notes.
- Local microphone recording and playback for controllers or headsets that appear as an audio input.
Raw input diagnostics inside the gamepad tester
The gamepad tester on the home page also includes the raw browser view that previously sat on the standalone raw-input page. Use it when you need to see exactly what the browser receives before a game applies its own layout, sensitivity curve, Steam Input profile, or deadzone setting.
Raw input is useful when a game shows the wrong layout, when a controller reports a non-standard mapping, when two gamepads are connected at the same time, or when a repair bench needs a browser-level sanity check. The same gamepad tester session can show the controller index, ID, mapping label, timestamp, button count, axis count, raw axis array, and button value array without leaving the home page.
- Use the gamepad tester raw panel to compare standard labels with raw button and axis indexes.
- Check whether a symptom follows the controller, the USB or Bluetooth connection, the browser, or a driver layer.
- Keep raw values visible when inspecting used controllers, adapters, unusual PC pads, or browser mapping differences.
Reports and mapping evidence from one gamepad tester session
After checking buttons, sticks, triggers, drift, vibration, microphone input, raw mapping, and browser support, the gamepad tester can generate a local text or JSON report. That report is meant for troubleshooting notes before changing game settings, buying a used controller, or asking a repair shop to verify a symptom.
The report stays in the browser unless you copy or download it yourself. It records practical evidence from the gamepad tester session, but it remains guidance rather than an official manufacturer diagnostic or repair certificate.
Why browser-based controller testing is useful
A browser gamepad tester is fast because it does not require installing a driver utility or opening a game. The gamepad tester is useful before a game session, after changing Bluetooth adapters, when checking a used controller, or after cleaning and repair.
The gamepad tester live readings make it easier to separate connection problems from mechanical symptoms. For example, if the controller is not detected at all, start with cable, Bluetooth, browser, driver, or Steam Input checks. If it is detected but one input behaves strangely, use the relevant gamepad tester module to narrow the symptom.
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.
Microphone recording starts only after you press the recording button and grant browser permission. Playback and deletion happen locally in the browser.
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.
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.