Browser haptic diagnostic

Controller Vibration Test

Check the high-frequency, low-frequency, and combined feedback your current browser connection exposes. Each stage separates the browser command from what you actually feel in your hands.

Current controller No controller detected
Waiting for controller

Connect by USB or Bluetooth, press any controller button, then detect it.

Three-stage check

Run each pattern, then confirm it

A completed command only proves that the browser accepted the effect. After each stage, tell DriftHub whether you felt it.

Selected pattern High-frequency (weak)

Detect a compatible controller to begin.

What the result means

A browser command is not a motor sensor

The browser can report whether the command completed, was preempted, or was rejected. It cannot detect whether a physical actuator moved. That is why this diagnostic keeps the technical result separate from your Felt or Not felt confirmation.

Haptics not exposed describes the current browser, platform, connection, and controller combination. It is not a hardware verdict. Gamepad haptics remain limited availability; read the MDN GamepadHapticActuator reference for the API boundary.

Interrupted tests are not recorded. Retry them before comparing results.

Troubleshooting

Controller vibration test FAQ

Why doesn’t my controller vibrate during the test?

The browser may not expose dual-rumble for this controller and connection. Press a controller button, retry with USB, and compare a current Chromium browser before deciding the controller itself has a problem.

Can this controller vibration test damage my controller?

DriftHub sends short, adjustable Gamepad API commands like those used for game feedback. Start at a moderate intensity, keep the duration short, and use Stop vibration whenever you want to end a test.

What do high-frequency and low-frequency mean?

Dual-rumble exposes a lighter high-frequency channel and a heavier low-frequency channel. DriftHub checks each magnitude separately, then combines them so you can compare what you feel.

Does this work with every Xbox, PlayStation, or Switch controller?

No browser page can promise every controller, operating system, browser, cable, and wireless combination. The live capability check on this page reports what your current setup exposes.

Why does the test ask whether I felt the vibration?

The browser can report whether the command completed, but it cannot sense whether a physical actuator moved. Your Felt or Not felt answer supplies that missing physical observation.

What should I do when no vibration is felt?

Retry the checks, use a wired connection, change the USB port or cable, compare Chrome or Edge, inspect system controller settings, and update controller firmware before considering hardware service.