Vibration Test Vibration Simulator Online & Free Test vibration on iOS and Android instantly. No app, no download, no registration required.

Yes. This free online vibration test works on iPhone and iPad using Safari. The Web Vibration API (navigator.vibrate) is supported in Safari on iOS. Open this page in Safari on your iPhone and press Start Vibration to trigger haptic feedback through your phone's Taptic Engine or vibration motor. If you do not feel vibration, check that your iPhone is not in silent mode (the physical ring/silent switch on the left side of the phone), that vibration is enabled in Settings then Sounds and Haptics, and that the Vibrate on Silent or Vibrate on Ring settings are turned on.

Yes. The Web Vibration API has excellent support on Android and works in Chrome, Firefox, Edge and Samsung Internet browser. Open this page in Chrome on your Android phone and press Start Vibration. If you do not feel vibration, check that your phone is not in silent or Do Not Disturb mode, that vibration is enabled in Settings then Sound and Vibration, and that the vibration intensity is not set to the minimum level in your sound settings. The tool uses standard navigator.vibrate API calls that all modern Android browsers support.

There are several reasons the vibration test might not produce vibration. On iPhone, check the Ring/Silent switch on the left side of the phone (orange stripe visible means silent mode, which may prevent vibration). Check Settings then Sounds and Haptics and ensure Vibrate on Silent and Vibrate on Ring are enabled. On Android, check Settings then Sound and Vibration and ensure vibration intensity is not set to zero. On both platforms, check that Do Not Disturb mode is not active. If all settings are correct and you still feel nothing, the vibration motor may be damaged or disconnected.

The Web Vibration API is a W3C browser standard that allows websites and web apps to trigger vibration on the device's haptic motor directly from JavaScript using navigator.vibrate(). The API accepts either a single number (vibration duration in milliseconds) or an array of numbers alternating between vibration duration and pause duration. For example navigator.vibrate([200, 100, 200]) produces two 200ms vibrations with a 100ms pause between them. The API requires no special permissions on Android. On iOS it is supported in Safari with some limitations on pattern complexity.

On Android, the DeviceMotionEvent API used for accelerometer readings does not require explicit user permission and works automatically in Chrome and Firefox. On iOS 13 and later, Apple requires explicit user permission for DeviceMotionEvent access. Safari on iOS may show a permission prompt the first time the accelerometer is accessed. If you deny permission, the accelerometer panel will show zero values. On iOS 12 and earlier, no permission was required. On desktop computers, the accelerometer panel will show near-zero values as desktop computers do not have motion sensors.

Each pattern is built as an array of alternating vibration and pause durations. Single Pulse is navigator.vibrate(duration). Double Tap is navigator.vibrate([freq, 80, freq]). Triple Tap is navigator.vibrate([freq, 80, freq, 80, freq]). Heartbeat is navigator.vibrate([freq*0.6, 80, freq*0.6, 350]). SOS is navigator.vibrate([100,80,100,80,100,150,300,80,300,80,300,150,100,80,100,80,100]). Ramp Up builds an escalating array of increasing durations. Buzz is navigator.vibrate(duration * 3). These arrays can be copied directly for use in your own web development projects.

Yes, 100% free with no hidden costs, no subscription, no premium features and absolutely no registration required. Every feature works immediately when you open the page: all eight pattern presets, the frequency and duration sliders, all three intensity levels, the live waveform visualization, the accelerometer monitor, the test history log and the device frame animation. Nothing is uploaded to any server, no account is created and no data is stored anywhere outside your browser session.

Frequency in this tool refers to the pulse width (duration of each vibration burst) in milliseconds, not the physical oscillation frequency of the motor. A short pulse (50ms) feels like a sharp tap while a long pulse (1000ms) feels like a sustained buzz. Intensity is simulated by adjusting the pulse structure: Low intensity uses shorter pulses spaced further apart; Medium uses the exact slider values; High uses longer, overlapping pulses. The physical vibration motor in a phone typically operates at a fixed hardware frequency, so the perceived intensity from the Vibration API is controlled entirely through pulse timing.

Most desktop and laptop computers do not have vibration motors so the physical vibration will not be felt. The tool still works on desktop browsers and will show the device animation, waveform visualization and test history, but navigator.vibrate() returns false on devices without hardware vibration support. The accelerometer panel will show near-zero values on desktop computers as they do not have mobile-style motion sensors. For best results, open this page on a smartphone or tablet with a working vibration motor.

Yes. The vibration patterns used in this tool are standard Web Vibration API arrays that work in any JavaScript context that supports navigator.vibrate(). The API is supported in all modern Android browsers and Safari on iOS. For native app development, Android provides the Vibrator and VibrationEffect API and iOS provides UIFeedbackGenerator and CHHapticEngine for more precise haptic control. The millisecond values from this tool can be used as a starting reference when implementing the equivalent patterns in native Android Vibrator.vibrate() or iOS CoreHaptics frameworks.