📳 Vibration Test — Device Haptics, Patterns & Gamepad Rumble
Device vibration and haptic capability check

Free Vibration Test for Device Haptics, Custom Patterns, and Gamepad Rumble

Use this vibration test to check browser Vibration API support, play short preset or custom patterns, stop vibration immediately, and detect gamepad rumble capability when available.

Free browser toolLocal processingNo signupMobile responsive
Interactive vibration test

Run the live browser test

Vibration API
Page visibility
Connected gamepads
Rumble actuator
Ready. Use the controls above to begin.
Built-in capabilities

12 practical features in this vibration test

01

Vibration API support detection

Built into this page as an interactive or diagnostic capability, not just a static explanation.

02

Short pulse preset

Built into this page as an interactive or diagnostic capability, not just a static explanation.

03

Double pulse preset

Built into this page as an interactive or diagnostic capability, not just a static explanation.

04

Heartbeat-style preset

Built into this page as an interactive or diagnostic capability, not just a static explanation.

05

Custom comma-separated pattern

Built into this page as an interactive or diagnostic capability, not just a static explanation.

06

Total-duration safety cap

Built into this page as an interactive or diagnostic capability, not just a static explanation.

07

Immediate stop control

Built into this page as an interactive or diagnostic capability, not just a static explanation.

08

Page visibility indicator

Built into this page as an interactive or diagnostic capability, not just a static explanation.

09

Gamepad connection detection

Built into this page as an interactive or diagnostic capability, not just a static explanation.

10

Gamepad vibrationActuator detection

Built into this page as an interactive or diagnostic capability, not just a static explanation.

11

Dual-rumble effect test when supported

Built into this page as an interactive or diagnostic capability, not just a static explanation.

12

Local test history and export

Built into this page as an interactive or diagnostic capability, not just a static explanation.

Interpretation reference

How to read the diagnostic signal

SignalUseful interpretationImportant limitation
Stable repeat resultMore useful for comparison than a single isolated sampleStill depends on the current browser, OS, and device state
Large change after one controlled adjustmentGood clue that the changed variable mattersCorrelation is not always proof of root cause
Missing or inconsistent browser eventUseful troubleshooting evidenceDoes not electrically inspect hardware components
Exported session summaryHelps compare before/after changesOnly as good as the test conditions you record

Worked example: run the same test twice, change one relevant setting, then repeat it. A consistent change across repeated runs is more informative than a single isolated number.

Microlearning

Six short lessons for better testing

01

Control one variable

Keep device settings, browser zoom, and test mode constant before comparing results.

02

Repeat the measurement

One run can be noisy. Repeat the same test and look for a stable pattern.

03

Separate browser from hardware

Browser events are useful diagnostics, but they do not expose every firmware or electrical detail.

04

Use the right metric

Choose timing, accuracy, count, support, or geometry metrics that match the problem you are investigating.

05

Record context

Save the device, connection type, relevant settings, and test condition with any result you compare later.

06

Interpret, do not overclaim

Treat the page as a practical diagnostic aid rather than a laboratory certification instrument.

Online checklist

Complete the diagnostic workflow

Knowledge challenge

Three-question diagnostic quiz

1. What improves comparison quality most?
2. What does a browser diagnostic measure best?
3. When is a saved result most useful?
Local diagnostic history

Recent saved milestones on this device

Related ready pages

Continue without a dead end

Return to TestsAndTools home

Frequently asked questions

Free Vibration Test for Device Haptics, Custom Patterns, and Gamepad Rumble: FAQ

Why does nothing vibrate?+

The Vibration API is not supported on every browser or device. Some browsers ignore it entirely, and vibration generally requires a physical device with a vibration motor.

Can a desktop browser vibrate my phone remotely?+

No. The API affects the device running the page when supported.

What do numbers in a custom pattern mean?+

They alternate vibration and pause durations in milliseconds, starting with vibration.

Can the page test gamepad rumble?+

When a connected gamepad exposes a vibrationActuator with a supported effect, the page can request a short rumble.

Is browser vibration the same as native haptics?+

Not necessarily. Native apps can have richer haptic APIs than the browser exposes.

Source and scope

Use the result responsibly

This tool reports what a browser can observe or calculate in the current environment. Firmware, drivers, operating-system processing, permissions, transport, display timing, audio hardware, device design, and browser implementation can add behavior that this page cannot isolate.

External technical reference: MDN: Vibration API ↗.

Free to use. No email, phone number, account, or payment required.