PS4 controller test
Test browser-visible inputs from your PS4 DualShock 4 controller. Check button press and release states, trigger values and joystick axes without uploading readings.
Buttons and triggers
Press buttons one at a time. “Not observed” is not a failure.
Joystick axes
Move a stick to check its browser-reported axis values.
Test vibration
If the controller and browser expose rumble, this plays a one-second dual-motor pulse. It does not test adaptive-trigger resistance, trigger haptics or DualSense light-bar and haptic effects.
Support is detected when you click it; some controllers cannot rumble in the browser.
Connect a PS4 DualShock 4 controller
- 01
Connect the controller with a compatible data-capable micro-USB cable. Charging-only cables will not transmit controller inputs.
- 02
On a supported Bluetooth device, disconnect USB and turn off the controller. Hold SHARE and PS until the light bar flashes, then select the controller in Bluetooth settings.
- 03
Focus this page, press a controller button and start the test. Check the face buttons, D-pad, L1/R1, L2/R2, SHARE, Options and stick clicks where exposed.
DualShock 4 button, trigger and stick readings
When the browser reports a standard mapping, this page uses PlayStation face-button labels plus SHARE and Options. Otherwise it displays raw numbered inputs. Connection method and remapping software may affect which inputs appear.
Test limitations
This test does not check light-bar control, motion sensors, headphone audio, DualSense/DualShock haptics, adaptive-trigger resistance, trigger rumble or touchpad coordinates. The input tester exposes a shared dual-motor rumble check that works only on browsers and controllers that report rumble support. A browser may expose a touchpad click separately, but that is not a full touchpad test. Physical DualShock 4 validation is still pending.
Readings stay in this page’s memory. No account, controller-reading uploads or automatic calibration. If an input is missing, check the connection and browser mapping before assuming a hardware fault.
Controller connection help →