Why rumble support varies
Vibration is one of the least consistent browser controller features. A controller can work perfectly in a game while the browser does not expose its vibration actuator, especially over Bluetooth or in browsers with limited hardware APIs.
Where supported, the tool offers light, medium, strong, left motor, and right motor patterns. Not every actuator honors separate motors, so patterns may feel similar.
- Feature detection is based on the active browser and connected controller.
- Pulses are intentionally short to avoid long vibration sessions.
- Unavailable vibration does not mean the controller is broken.
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 Vibration Test, treat that limit as part of controller vibration test 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 Vibration Test page, compare that note with the live module that matches browser haptic support, short pulse behavior, actuator exposure, and safe rumble limits.
Controller vibration test safety
A controller vibration test should be short, deliberate, and limited to the patterns the browser can expose. Start with a light pulse, listen for scraping or rattling, and stop the controller vibration test if the shell becomes warm, noisy, or unstable. Browser haptics are not the same as a console's full vibration system.
When the controller vibration test does nothing, that result usually means the browser did not expose a compatible actuator. It does not prove that the motor is broken. Compare USB and Bluetooth, try Chrome or Edge, and check whether another app is already controlling the controller vibration test path.
- Keep each controller vibration test pulse brief.
- Do not repeat the controller vibration test continuously on a hot controller.
- Treat unavailable rumble as compatibility evidence first.
When vibration results disagree
If a controller vibration test works in one browser but not another, keep both results. That contrast is useful because it shows the controller may support rumble while the browser path is the limiting factor. A short note about browser, connection, and actuator response makes the controller vibration test easier to compare later.
- Retest after reconnecting by USB.
- Do not run pulses during charging heat.
- Record unavailable haptics separately from weak haptics.