What does Gamepad Vibration Test check?
Test controller rumble and haptic actuator support where the browser exposes it. It is designed for controller users testing USB, Bluetooth, console-style, and browser-compatible gamepads.
Gamepad Vibration Test
Test controller rumble and haptic actuator support where the browser exposes it.
Gamepad Vibration Test helps controller users testing USB, Bluetooth, console-style, and browser-compatible gamepads. It focuses on button mapping, stick drift, trigger range, polling and vibration support and runs directly in the browser.
What this page checks
- button mapping
- stick drift
- trigger range
- polling and vibration support
- Gamepad Vibration Test result interpretation
How to use Gamepad Vibration Test
- Open Gamepad Vibration Test on the same browser and device you want to diagnose.
- Gamepad pages use the browser Gamepad API; connect the controller and press a button to expose it.
- Run the visible gamepad test controls and watch the live result area update before judging the hardware.
- Repeat the test once or twice, then compare related InputLab tools if the gamepad behavior looks inconsistent.
How to read the result
Gamepad Vibration Test is most useful when you read the result as a practical browser diagnostic. Browser support, Bluetooth latency, driver mapping, and controller firmware can affect readings. A repeated pattern across multiple runs is more meaningful than one isolated spike, missed event, or visual artifact.
Privacy and permissions
Gamepad pages use the browser Gamepad API; connect the controller and press a button to expose it. Tests are designed to run locally in the browser, with permissions controlled by the browser.
Related InputLab tools
Gamepad Vibration Test FAQ
Is Gamepad Vibration Test accurate?
Browser support, Bluetooth latency, driver mapping, and controller firmware can affect readings.
Do I need to install anything for Gamepad Vibration Test?
No. Gamepad pages use the browser Gamepad API; connect the controller and press a button to expose it.
Are results uploaded to a server?
The page uses local browser events or browser hardware APIs. InputLab does not need to upload the diagnostic result.
What should I try if the result looks wrong?
Check browser focus, device selection, operating-system settings, and then run related gamepad tools to separate a device problem from a browser or permission issue.