Connect your DualSense Edge
USB: the braided USB-C cable from the case carries data, and its housing locks into the controller so it can’t be pulled out mid-game. Any USB-C data cable works.
Bluetooth: switch it off, then hold Create and the PS button until the light bar blinks, and pick the controller in your Bluetooth settings.
Before testing, switch to the default profile. Custom profiles can set stick and trigger deadzones and sensitivity curves, and they are stored and applied in the controller (PlayStation), so a browser sees the processed values. A profile with a 10% deadzone would hide 8% drift entirely.
What a browser sees on the Edge
Chrome reads the Edge exactly like a standard DualSense (Chromium): the 17 standard buttons plus the touchpad click, both sticks and the analog L2 and R2. The two back buttons and the Fn buttons have no index of their own: a back button appears only as whatever standard button its profile maps it to, which is handy for checking that a back button works at all. The trigger stops and the adaptive triggers are outside the Gamepad API, but a trigger stop shows up here as L2 or R2 topping out early. In Chrome or Edge on a computer, Connect for more tests reads the controller directly: the motion sensors, touchpad and battery, and it can play adaptive trigger effects.
Testing and swapping stick modules
The Edge’s selling point is that a worn stick doesn’t mean a repair: each stick is a module you can replace yourself (PlayStation), and either module fits either side. Sony lists them at $19.99 each in the US.
- Run the drift test on the default profile with the controller on a table. Note which stick fails.
- Run the circularity test. A module that can’t reach full travel in one direction is worn even if it rests at centre.
- If one stick fails, swap the two modules and test again. If the fault moves to the other side, it’s the module; if it stays, the controller itself needs service.
The Edge’s shorter battery life is its other well-known weakness: a teardown found a 1,050 mAh cell, about two thirds of the standard DualSense’s (Gizmodo). For the standard controller, use the PS5 controller tester.
How the browser numbers the DualSense Edge’s buttons
Browsers describe a recognised controller with the W3C standard gamepad layout, which numbers buttons by position, not by the symbol printed on them. This is the map the tester uses for the DualSense Edge; the list under the diagram shows the same numbers live.
| Button | Position | On the DualSense Edge |
|---|---|---|
| 0 | Bottom face button | ✕ |
| 1 | Right face button | ○ |
| 2 | Left face button | □ |
| 3 | Top face button | △ |
| 4 | Left bumper | L1 |
| 5 | Right bumper | R1 |
| 6 | Left trigger | L2 |
| 7 | Right trigger | R2 |
| 8 | Back / select | Create |
| 9 | Start / menu | Options |
| 10 | Left stick press | L3 |
| 11 | Right stick press | R3 |
| 12 | D-pad up | ↑ |
| 13 | D-pad down | ↓ |
| 14 | D-pad left | ← |
| 15 | D-pad right | → |
| 16 | Home / guide | PS |
| 17 | Touchpad / capture | Pad (the click only: swipes aren’t reported) |