Vibration
Connect a controller and press a button if the browser has not exposed it yet.
Gamepad Vibration Test: Controller Rumble, Haptic Feedback, Motor Strength, And Browser Support
Test controller rumble and haptic actuator support where the browser exposes it.
What this test checks
- Controller API detection
- Button, stick, trigger, or haptic behavior
- Live polling and input state
- Compare Motor Strength And Responsiveness
How to read the result
Vibration depends on the browser Gamepad API, so connect the controller and press a button first. Repeated drift, low polling, or missing button states usually deserve a second pass with the related controller diagnostics.
Confirm Browser Vibration Support
Not every controller or browser exposes rumble. The tool checks available haptic actuator support before users expect vibration feedback.
Run A Short Rumble Pattern
The test can trigger vibration patterns where supported. Users can feel whether the controller motors respond, feel weak, or fail entirely.
Compare Motor Strength And Responsiveness
Controller rumble can vary between low-frequency and high-frequency motors. A clear vibration test helps users notice uneven haptics or missing feedback.
Stop And Repeat Safely
Short, repeatable runs are better than long rumble sessions. Users can stop the test and repeat after reconnecting or changing controller drivers.
Related I/O Checkup Tools
What does Vibration measure?
Test controller rumble and haptic actuator support where the browser exposes it.
Do I need to install anything for Vibration?
No. Vibration runs directly in a modern browser. Some checks may ask for permission when they need camera, microphone, gamepad, pointer lock, touch, or audio output access.
Are results uploaded?
The test runs in your browser and uses local input events or browser hardware APIs for the visible diagnostics.
Why should I run related tests too?
Related tools help separate hardware issues from browser timing, display behavior, input device settings, or permission problems, which makes the final diagnosis more useful.
Detailed Testing Guide
Controller symptom
This controller page checks one part of the Gamepad API signal instead of assuming one button press proves the whole pad is healthy.
Start with a baseline run before changing device settings. Record any repeated symptom so the next comparison is useful.
API evidence
Watch button state, stick axes, trigger values, vibration response, polling updates, and whether the controller stays visible.
Watch Controller API detection, Button, stick, trigger, or haptic behavior, Live polling and input state, Compare Motor Strength And Responsiveness. These observations come from the browser; they do not reveal hidden firmware or factory calibration data.
Controller test method
Press a button to expose the pad, then test one control group at a time.
Keep the test conditions stable. Changing browser, cable, port, lighting, surface, volume, grip, or selected device all at once makes the result harder to trust.
Result reading
Browser support, Bluetooth latency, driver mapping, and firmware can all change what the page receives.
A repeated pattern matters more than a single spike. When something looks wrong, confirm it with another pass and compare a related tool before deciding the device itself is defective.
Limits and next checks
Use button, stick drift, trigger, vibration, and polling tests together for a complete controller pass.
For a closer comparison, try Gamepad Button Test, Stick Drift Test, Trigger Test, Polling Rate Test. Keep the same device and connection while you investigate the next symptom.