GEARCHECK LAB
Home / Tools / Controller Vibration
Controller Lab // Haptic Capability

CONTROLLER VIBRATION TEST

Detect whether your current browser, platform and controller expose haptic feedback through the Gamepad API. Where supported, test weak/strong dual-rumble channels, combined rumble and a short pulse without installing software.

Capability-aware diagnostic

Gamepad haptic actuator

AWAITING CONTROLLER
Connect a controller and press a button.Haptic support depends on the exact browser, operating system, connection and controller. A controller can vibrate in games yet still be unavailable to a browser.
NO CONTROLLER DETECTED
CAPABILITY UNKNOWNConnect a controller to inspect browser-exposed haptics.

How to test controller vibration

  1. Connect the controller and press a button so the browser exposes it.
  2. Check the capability panel. If no haptic actuator is exposed, the page will not try to force vibration.
  3. Try a short weak/strong/combined effect. Keep the controller in your hands so you can compare the channels.
  4. Use STOP VIBRATION if an effect remains active.
  5. Repeat in another supported browser or wired/wireless mode if a controller that normally vibrates is reported unsupported.

Why vibration support is limited

Browser haptics are not universally available. The Gamepad API can expose a vibration actuator on one browser/platform/controller combination and omit it on another.

An UNSUPPORTED result means the page cannot access haptics in this environment. It does not prove that the physical vibration motors are broken.

Weak versus strong rumble

The dual-rumble effect exposes separate weak and strong magnitude values where supported. Their physical feel depends on the controller's motors, firmware and browser implementation; the page does not assume a particular motor frequency.

Effect detection

Newer Gamepad haptic APIs can report an effects list such as dual-rumble or trigger-rumble. This page displays that list when the browser exposes it and otherwise uses capability checks/fallbacks.

Why the test can reject an effect

A haptic request can fail if the document is not active or the requested effect is unsupported. GearCheck Lab reports the browser's result instead of assuming a call succeeded just because the controller is connected.

Limitations

  • No force sensor confirms physical vibration intensity.
  • The page cannot verify vibration motors that the browser does not expose.
  • Wireless adapters, remote sessions and OS drivers can affect capability.
  • Trigger-rumble hardware is not guaranteed to be accessible even when the controller supports it in native games.

Controller vibration test FAQ

My controller vibrates in games but says unsupported here. Is it broken?

No. Browser haptic support is limited and platform-dependent. Test another browser or connection mode before drawing a hardware conclusion.

Can this test damage the controller?

The presets use short, bounded browser haptic requests. Stop the test if the device behaves unexpectedly.

Can you test adaptive triggers?

Not reliably across browsers. The page reports exposed effects but does not claim universal adaptive-trigger control.