PlayStation controller diagnostics

PS5 Controller Test

Connect a DualSense or compatible PlayStation pad and this PS5 controller test will visualize buttons, touchpad, PS, mute, sticks, triggers, mapping, and browser support.

DualSense Button Visualizer

PS5 controls are mapped to browser button indexes for local visual testing.

No Controller Detected

Connect via USB or Bluetooth, then press any controller button to activate detection.

L2R2L1R1TouchpadL3R3△○×□Create buttonOptions buttonPS buttonPSMute buttonPress any DualSense button to activate detection

Cross

B0

Action button

Circle

B1

Action button

Square

B2

Action button

Triangle

B3

Action button

L1

B4

Left bumper

R1

B5

Right bumper

L2

B6

Left trigger

R2

B7

Right trigger

Create

B8

Create controls

Options

B9

Options controls

L3

B10

Left stick press

R3

B11

Right stick press

D-pad up

B12

Directional button

D-pad down

B13

Directional button

D-pad left

B14

Directional button

D-pad right

B15

Directional button

PS

B16

PS button

Touchpad

B17

Touchpad button

Mute

B18

Mute button

Analog Sticks

Crosshair scopes show center drift, range, and live trail.

Left stick

X +0.000 Y +0.000

Right stick

X +0.000 Y +0.000

Triggers

Analog pressure appears as local intensity values.

L2 trigger+0.000
R2 trigger+0.000

Raw Data

Latest values expose browser mapping and analog button state.

Last input

Waiting

Press a button to populate the live event log.

Vibration Test

Haptic commands run only after a user click.

Click a pattern after selecting a connected controller.

PlayStation-Style Controls In The Browser

A PS5 controller test needs to show more than a generic button list because PlayStation-style labels, touchpad controls, PS and mute buttons, adaptive triggers, and browser haptic support can all behave differently from the physical controller experience on a console. This PS5 controller test uses a PlayStation-oriented visual layout with live face buttons, shoulder controls, stick clicks, d-pad directions, raw axes, and a compact status area for browser capabilities.

The Gamepad API may report a DualSense as a standard gamepad, a wireless controller, or a vendor-specific device name. That difference is normal. The controller tester displays the sanitized device ID and the browser mapping so you can compare USB and Bluetooth modes. If a game labels controls incorrectly, the visual PS5 controller test helps separate a game profile issue from browser input mapping.

Adaptive trigger effects and advanced haptics are not broadly exposed through the standard Gamepad API. When the vibration panel reports unsupported, it may mean the browser cannot access that feature rather than the controller is broken. The optional WebHID-based calibration and gyro pages are better places to explore advanced permission-dependent behavior.

Stick Drift, Trigger Travel, And Button Confirmation

DualSense sticks can feel precise while still reporting idle noise. The PS5 controller test draws live scopes for both sticks, so a tiny returning wobble is distinct from steady drift. If the dot rests away from center, open the stick drift test and note whether the same offset appears after reconnecting by USB. If edge travel forms a box or clipped corner, the circularity test provides a more specific controller tester view.

The L2 and R2 triggers should report pressure changes where the browser supports analog trigger values. Use the PS5 controller test to pull each trigger slowly and compare the meter curve. A trigger that starts late, releases slowly, or never reaches full travel can affect shooters, racing games, and accessibility remapping. The raw data panel shows whether the value is truly analog or only a pressed state.

Face buttons, d-pad directions, and stick clicks should highlight immediately and clear when released. If a PlayStation-style label feels swapped, trust the raw index shown by the controller tester rather than the printed cap. Browser games and emulators often care about the API index, so the button mapping test is the right follow-up when the PS5 controller test reveals inconsistent labeling.

USB, Bluetooth, WebHID, And Safe Expectations

For the cleanest PS5 controller test, compare USB and Bluetooth. USB often exposes a more stable identity, while Bluetooth can be convenient but may hide haptics or advanced reports. Press a controller button after the page loads, keep the tab focused, and avoid running another application that captures the controller exclusively while this browser controller tester is active.

WebHID permission is intentionally not requested on page load. A browser prompt should follow a clear click because HID access is broader than ordinary Gamepad API readings. Pages that use WebHID explain why the permission is useful, and the PS5 controller test remains functional without it. This keeps the basic controller test private, predictable, and comfortable for everyday users.

This page cannot update DualSense firmware, repair a drifting stick module, or reproduce console-only haptic features. It can show repeatable browser evidence: which controls respond, how sticks settle, whether triggers are analog, whether vibration is exposed, and whether the device is recognized consistently enough for web games and cloud gaming.

Diagnostic Glossary

DualSense

Sony's PS5 controller family, often reported by browsers as a wireless controller.

Adaptive trigger

A console feature that is not generally available through the standard browser Gamepad API.

WebHID

An optional browser permission for compatible low-level HID reports.

Questions Users Ask

Short answers for common diagnostic decisions on this page.

Why does the PS5 controller test show a generic device name?

Browsers and operating systems normalize device IDs differently. A generic wireless name can still provide usable button and axis data.

Can this test adaptive triggers?

The standard browser Gamepad API does not expose full adaptive trigger control. The page reports ordinary trigger values and haptic fallback status.

Should I use USB or Bluetooth?

Use both if you are troubleshooting. USB is often the most stable baseline, while Bluetooth reveals wireless-specific issues.

Useful Next Checks

Run a stick drift test

Check idle offset and deadzone before changing in-game sensitivity.

Review calibration

Estimate center offset, range behavior, and practical deadzone choices.

Check gyro support

Review motion capability, optional WebHID permission, and fallback tilt behavior.

Inspect button mapping

Confirm indexes, labels, analog values, and unusual layouts.