Check the operating system connection, keep this tab foreground and press a physical controller button. Inputs and vibration have separate support. Try a browser that exposes dual-rumble or compare USB with Bluetooth. No plugin is needed; an absent actuator does not diagnose a broken motor.
Part of the Controller and gamepad test. Run the full gamepad test first for a complete device check.
No controller or actuator available Request failed, timed out or stop unconfirmed API complete but nothing felt
Controller vibration test
Run a controller vibration test with separate weak and strong requests. Browser support is shown first; hold the controller to compare each API reply with what you feel.
Also known as: controller vibration test, controller vibration tester, gamepad vibration test, controller rumble test, rumble test. Free, online, and no download required.
No permission neededNothing uploaded
Connect a controller and press a physical button. Choose one short vibration request; no output starts automatically.
01
What the controller vibration test checks
| Check | How it is measured | Fails when |
|---|---|---|
| Connection and support | A connected Gamepad with dual-rumble request and reset methods exposed to this tab | No device or no usable actuator means this browser route cannot run the vibration check |
| Separate channel requests | Latest weak and strong API replies recorded independently, at 25% API magnitude for 300 ms | Rejected, preempted, unsupported, stopped and timed-out requests do not count as API complete |
| Physical response | Your own observation while holding the controller, separate from browser replies | The page has no motor sensor and cannot confirm vibration strength, physical channel separation or motor health |
How to run the controller vibration test
- Connect the controller, keep this tab visible and press a physical button so the browser can expose it.
- Read the actuator support message. If vibration is unavailable, check the browser and connection before testing.
- Hold the controller, select Play weak channel and wait for its request status. Repeat with Play strong channel and compare the sensations yourself.
- Use Stop vibration at any time. Finish and read result reports API replies; Reset clears this round before another comparison.
If something failed
Rejected, interrupted and timed-out requests are incomplete. Stop, close other controller tools and retry one channel. If reset fails or times out, further output is locked: retry Reset or disconnect. Each effect is limited to 300 ms, but the page cannot guarantee faulty hardware obeys stop.
The browser reply does not measure motion. Check the controller's own vibration settings, compare the other channel and test a known supporting application. Record differences between replies and felt response. A completed request cannot certify motor health, force or physical channel separation.
02
How to read the result
How to run a controller vibration test
Start with the connection you actually use. USB and Bluetooth can expose different capabilities for the same controller. Once its name appears, read the support message before selecting an output. Recognition means the browser sees a gamepad, while vibration additionally needs a usable actuator. Pressing a controller button can make a previously hidden device visible to the page.
Keep the tab in the foreground and hold the controller comfortably. Play weak channel requests the high-frequency component of dual-rumble; Play strong channel requests the low-frequency component. Each effect lasts 300 milliseconds with the requested component at 0.25 on the API's zero-to-one scale and the other component at zero. That magnitude is a requested setting, not a measured vibration intensity.
Wait for the first request to settle before selecting the next. Output controls are disabled while a request or stop is pending, so fast repeated clicks cannot stack effects. There is no automatic repeating sequence. Stop vibration requests actuator reset, and Reset also clears the request records for a fresh round. Leaving or hiding the page requests stop rather than continuing a background pattern.
Reading weak, strong and combined request states
Not requested means that channel has no request in this round. Requesting means the browser promise is pending. API complete means that specific request returned complete; Preempted means it was interrupted before normal completion. Unsupported, Failed and Timed out are incomplete outcomes. Stopped marks a pending request that you cancelled. None of these labels claims that a physical motor was measured.
Selecting weak twice only replaces the weak record. It cannot complete the strong check. The latest reply for each channel is used, so a failed repeat does not retain an earlier successful reply for that channel. Disconnecting the controller clears the round to avoid combining observations from different devices or connections. Late replies from a cancelled round are ignored.
The combined pattern becomes available after separate weak and strong requests have complete replies. It requests both components at the same low magnitude and has its own status. It adds no separate-channel evidence. Finish and read result counts only the two independent replies, and still labels physical response as unconfirmed. If the sensations differ from the replies, record that difference instead of treating the result as a pass certificate.
Browser and connection compatibility
A controller vibration tester depends on the browser, operating system, device and connection together. A browser may display buttons and sticks without exposing rumble. The support message checks the methods needed to request dual-rumble and stop it. When an actuator lists supported effects, dual-rumble must be present. Actual request rejection can still reveal a limitation that the initial method check cannot detect.
Compare one variable at a time: the same pad over USB, then the same browser with a different documented connection, or another browser that exposes the vibration API. A successful input check is useful context but does not prove output support. Use the gamepad test, PS5 controller test or Xbox controller test for button and stick input checks.
Measurement limits
This page has no accelerometer reading, motor-current measurement or physical feedback sensor. It cannot measure vibration frequency, force, left-versus-right motor placement, battery health or wear. Weak and strong name API components; they are not a guaranteed physical layout for every pad. Your felt response is a subjective observation, not a numeric measurement generated by the tool.
The rumble test uses dual-rumble only. It does not exercise Xbox trigger motors, DualSense adaptive resistance or vendor-specific haptic waveforms. If one requested component feels absent, compare another supporting application and the controller's documented settings before deciding whether the device needs service. For a broader sequence, follow how to test a controller. Browser evidence alone cannot locate a hardware fault.
03
Controller vibration test questions
Which browsers can run this controller vibration test?
Use a browser and controller connection that expose a dual-rumble actuator with playEffect and reset. The panel checks this route at runtime, rather than assuming support from the controller brand. If inputs work but vibration is unavailable, compare another supporting browser or USB connection; installing a plugin is not required.
What do weak and strong mean in this vibration check?
They request the high-frequency and low-frequency dual-rumble components separately. The page uses 25% API magnitude for 300 ms, with the other component at zero. Those settings describe the request and do not measure physical strength or guarantee a particular motor position.
Why can API complete appear when I feel no rumble?
API complete is the browser's request reply, not feedback from a motor sensor. Device settings, the connection and the output implementation can affect what you feel. Compare both separate channels, check documented vibration settings and try a known supporting application before diagnosing hardware.
Does pressing the weak button twice complete both channels?
No. This round stores the latest weak reply and latest strong reply independently. Repeating weak updates only weak, and a combined pattern has its own record. Only complete replies from both separate requests produce the two-request result; physical motor response remains unconfirmed.
How do I stop or restart the controller rumble test?
Select Stop vibration to request reset, or Reset to request stop and clear the round. Hiding the tab, disconnecting or leaving the tool also requests cleanup. If reset fails or times out, new output is locked until a successful Reset or reconnection. Every requested effect has a 300 ms duration.
Can this gamepad vibration test verify trigger rumble or motor health?
It checks only browser dual-rumble requests. Trigger rumble, adaptive trigger resistance and vendor haptic waveforms are outside this task. Hold the controller to observe actual motion yourself. Two complete browser replies cannot certify two healthy physical motors, and the page does not create a strength or health score.