PS5 DualSense Controller Test

PS5 DualSense Controller Test: Stick Drift and Button Check

The PS5 DualSense works natively in Chrome and Edge on Windows and Linux over USB without any additional software or drivers. Connect it via USB-C, open this page, and press any button to register it. The DualSense exposes 17 buttons, two analog sticks, and two analog triggers in the browser Gamepad API.¹

The DualSense's adaptive triggers appear as axes 4 and 5 on some browser and OS combinations rather than as standard button values, which is normal behavior. The resistance motor inside each trigger is not accessible through the Web Gamepad API, so you will see the trigger depth value but not the resistance level. Haptics and the built-in microphone are similarly inaccessible from the browser.²

To check for stick drift, place the controller flat on a desk after registering it and leave both sticks completely untouched for at least 10 seconds. The canvas dot for each stick should sit perfectly at center. Any persistent non-zero reading at rest indicates early potentiometer wear that will worsen over time. CapyToolkit keeps the result local in your browser while you decide what to do next.

Specifications³

Connecting the DualSense to a PC

On the DualSense, browser registration through the Web Gamepad API requires one physical button press after connecting. Chrome and Edge on Windows and Linux handle the USB-C connection without any additional software or drivers. Plug the USB-C cable into the controller, connect the other end to a USB-A or USB-C port on your computer, then press the PS button or any face button once the page is open. The tester shows the controller entry within one second.¹

Button registration and adaptive trigger mapping

Bluetooth pairing uses the DualSense-specific sequence: hold the PS button and the Create button simultaneously until the LED pulses white, then complete the pairing through your OS Bluetooth settings. On Bluetooth, the adaptive triggers sometimes appear as axes 4 and 5 rather than as standard button objects depending on the browser and OS combination. Both representations carry the same trigger depth information and neither indicates a fault.³

The tester shows the controller entry within one second of that first press, and the button grid then lights each control as you tap it so you can confirm the layout matches what you expect. A control that never lights up or a face button that maps to the wrong slot points to a hardware fault rather than a browser limitation, so check every button before moving on to the drift and trigger checks.

Testing both sticks for drift

Stick drift on the DualSense shows as a persistent non-zero axis reading while neither thumb touches either stick. The four main axes are left stick X (axis 0), left stick Y (axis 1), right stick X (axis 2), and right stick Y (axis 3). Place the DualSense flat on a desk after registering it, leave both sticks completely untouched for at least 10 seconds, and then read the values below each canvas. A reading above 0.05 on any axis at rest suggests early potentiometer wear.

L3 and R3 button wear

The stick click buttons, L3 and R3, tend to wear faster on controllers used in games where sprint or melee is mapped to pressing the stick down. Constant L3 pressing in run-always games stresses the stick housing around the potentiometer, which can accelerate drift on the left stick specifically. Press L3 and R3 in turn and confirm each lights up in the button grid. A stick click that fails to register reflects worn contact points at the mechanism rather than a software issue, and typically requires stick module replacement.⁴

What the browser cannot test on the DualSense

Because the DualSense's adaptive trigger resistance is controlled through a separate haptic feedback channel, the browser shows trigger depth values but not resistance levels. Pressing L2 or R2 changes the trigger axis value from 0.0 at rest to 1.0 at full press, and you can use that fill bar to confirm the potentiometer inside each trigger is intact. Press each trigger slowly and watch the bar climb. A trigger that jumps directly from 0.0 to 1.0 with no intermediate values has a faulty analog sensor rather than a normal digital switch design.

Trigger range, haptics, microphone, and touchpad

The built-in microphone, haptic actuators, speaker, and touchpad position tracking are not accessible through the Gamepad API. The touchpad press registers as a standard button. Press the touchpad surface down firmly and confirm it lights up in the button grid on this page, where you can also watch every DualSense button light up. The haptic feedback channel that drives the adaptive triggers is a separate output path from the Gamepad API input readout, so the tester cannot report whether the resistance motor is functioning correctly. The built-in microphone on the DualSense is similarly routed through a dedicated audio interface that the browser does not expose through any standard media capture API for gamepads.