PS5 controller (DualSense) test
Connect your DualSense over USB-C or Bluetooth, then press any button on it. Every face button, shoulder button, trigger, stick and the D-pad respond live below, using the same standard-mapping index order your browser normalises PlayStation controllers to. Not affiliated with or endorsed by Sony Interactive Entertainment.
How DualSense buttons map onto this tool
Browsers that recognise a DualSense controller (current Chrome, Edge and Firefox all do) normalise it to the same W3C standard gamepad mapping every other recognised pad uses. That means the labels this tool shows — A, B, X, Y and so on — correspond to PlayStation's own button shapes in a fixed, predictable order:
| DualSense button | Standard label shown here |
|---|---|
| Cross (✕) | A |
| Circle (○) | B |
| Square (□) | X |
| Triangle (△) | Y |
| L1 / R1 | LB / RB |
| L2 / R2 (analog triggers) | LT / RT |
| Create / Options | Back / Start |
| L3 / R3 (stick clicks) | L3 / R3 |
| PS button | Home |
| Touchpad click | Usually reported as an extra standard button, index 17 — outside the core 0–16 set this tool labels by name, so it appears in the raw “all buttons” grid without a friendly label. |
What to check on a DualSense specifically
- L2/R2 through their full pull. These are the two triggers this tool draws an analog fill bar for — pull slowly and confirm the bar moves smoothly from empty to full, with no dead spot or jump.
- Both sticks for drift, using the live dot and the resting-position marker — DualSense stick drift is a widely reported failure mode on this generation of controller, and this is the same raw-value test used to spot it on any pad.
- Create and Options — smaller buttons that get pressed rarely and are easy to skip in a quick check.
- The touchpad click (not the touch surface itself, which this tool can't read) — check it in the raw button grid, since it usually sits outside the named button list.
- Rumble, on the exact connection you plan to use day to day — the tool's rumble button plays a short dual-rumble pulse if your browser and connection support it.
- Compare USB-C and Bluetooth if you use both, since reporting and rumble can differ between them.
Frequently asked questions
Will a DualSense controller show up as "standard" mapping?
On current versions of Chrome, Edge and Firefox, yes — DualSense (and the older DualShock 4) are recognised and normalised to the W3C standard gamepad mapping, so this tool's A/B/X/Y-style labels line up correctly: button 0 lands on Cross, button 1 on Circle, button 2 on Square, button 3 on Triangle, following the standard mapping's index order regardless of the shapes printed on the pad. If your browser instead reports a non-standard mapping, this tool falls back to a plain numbered list rather than guessing.
Does the touchpad or the built-in microphone show up here?
The touchpad click registers as a standard button in most browsers' mapping, but touch position and swipe gestures on the touchpad are not part of the Gamepad API at all — this tool can't read touchpad coordinates. The built-in microphone and the light bar aren't part of the Gamepad API either; neither is testable from a webpage.
Can this test the DualSense's adaptive triggers?
No. Adaptive trigger resistance profiles are a PlayStation-specific feature controlled through Sony's own SDK, not something the standard web Gamepad API can set or read. This tool reads the trigger's pull position as a plain 0-to-1 analog value, the same as any other controller's analog trigger — useful for checking the trigger itself moves smoothly and reaches full range, but it can't drive or report adaptive resistance.
Does it matter if I connect over USB-C or Bluetooth?
It can. Button and stick reporting is generally consistent either way once the browser recognises the pad, but rumble support and reporting latency are exactly the places wired and wireless connections tend to diverge on many controllers, DualSense included. If something looks or feels off over Bluetooth, plug in a USB-C cable and re-test before concluding the controller itself is at fault.
My DualSense works fine on the console — why test it in a browser at all?
A console's own UI abstracts a lot away from you — it won't show a trigger's raw analog value or a stick's exact resting offset, only whether the console's own deadzone-filtered input still works. This page shows the unfiltered numbers, which is exactly what you want before a return window closes, or before spending money assuming a fault is software when it's actually the stick's raw reading sitting off-centre.