Why is vibration unavailable when controller input works?
Input and haptic output are separate capabilities. The browser, operating system, driver, connection method, and controller must all expose a compatible dual-rumble actuator.
CONTROLLER VIBRATION TEST · LOCAL OUTPUT
Controller Vibration Tester
Check whether your browser-controller pair exposes dual rumble, then run a deliberate finite effect with independent motor levels and a maximum duration of five seconds.
OUTPUT TEST · FINITE DUAL RUMBLE
No controller selected
Every request is finite and capped at five seconds. Adjust the two motors separately, then start the effect deliberately.
No controllers detected.
Waiting for controller
Browsers expose a controller after it sends an input. Keep this page active, then press a physical controller button.
Actuator capability
Select a controller before checking vibration support.
Effect controls
Start low, keep the controller on a stable surface, and stop if the response is uncomfortable.
Current effect
- Pattern
- None
- Status
- unsupported
- Connected
- No
- Stale
- No
Local report
The report is created in this browser and downloaded directly to your device. Nothing is uploaded.
This tool exports summary data only.
Capability before sensation
Observe browser-exposed vibration support
Browser and device support must align before controller vibration can run. This tester checks the selected Gamepad API device for a compatible dual-rumble actuator, shows whether early reset is available, and keeps every requested effect finite. Input can work even when haptic output is not exposed.
Three cautious steps
How to test controller vibration safely
01
Connect and choose
Connect a controller, press a physical control so the browser exposes it, and choose the intended device when more than one is listed.
02
Start with low intensity
Place the controller on a stable surface, choose a short duration, and begin with conservative strong and weak motor settings.
03
Run one finite effect
Choose Steady, Pulse, or Ramp, start deliberately, and use Stop whenever the browser exposes actuator reset support.
Capability, not diagnosis
Vibration test limitations
Vibration response is subjective and this page provides a browser capability observation only. Strength depends on firmware, transport, operating system, driver, browser, controller design, grip, and surface. The result does not certify hardware condition, compare calibrated force, or provide a hardware health verdict.
When output stays quiet
Troubleshooting controller vibration
- Keep this page active and press a physical controller control after connecting.
- Choose the intended controller when several Gamepad API devices are listed.
- Try a current desktop browser, a wired connection, or a fresh Bluetooth pairing.
- Close games and remapping software that may control or reserve the haptic actuator.
Plain answers
Frequently asked questions
What happens when Stop is unavailable?
The tester sends only one finite effect and does not schedule later pattern segments. The controller finishes that request at the selected duration, never beyond the five-second cap.
Do strong and weak mean left and right?
They are the strong and weak magnitude channels defined by the browser dual-rumble effect. Their physical feel and motor arrangement vary by controller.
Does a strong response prove hardware health?
No. Perceived strength is subjective and affected by the device, surface, grip, firmware, transport, and browser. This page observes capability, not hardware health.