DualSense Edge test
Connect the DualSense Edge and run the whole test: drift, the edge of each stick, every button, both triggers, and the rumble where your browser can run it. Its Fn buttons never reach a web page; its back buttons show only as the button a profile gives them.
Press any button on the controller
Browsers show a controller only after a button is pressed, so that pages cannot list your devices unasked. Wired or Bluetooth both work.
This browser cannot read controllers.
Try a current Chrome, Edge, Firefox or Safari on a computer, Safari on an iPhone or iPad, or Chrome on Android.
The controller was disconnected. Connect it again and press a button; your results are kept.
Result: No problem found so far
Press every button, then run the checks below: the result is written here as you go.
Sticks
The rings are dead zones: the inner one 10 %, which many games use, the outer one 24 %, Xbox's standard for the left stick (27 % for the right).
Drift check
Put the controller down and do not touch the sticks. The check reads them for three seconds.
Range check
Push each stick to its edge and turn it slowly round, two or three times.
Buttons
Press each one. A button turns blue while held and stays ticked once it has worked.
Triggers
Press each trigger all the way down. A trigger reports how far it is pressed, not just on or off.
Rumble
Each button runs a motor for one second. The tab must stay in front while it runs.
This browser cannot run this controller's motors: Firefox and the browsers on iPhone and iPad run none, and Chrome and Edge on Windows do not run a PS5 controller's. The rest of the test is not affected.
Report
For a return, a warranty claim or a sale: print it, save it as a PDF, or copy the text.
How it works
- Connect the controller with its USB-C cable, or pair it over Bluetooth: with the light bar off, hold Create, then hold the PS button too until the light bar blinks, then pick it in your computer's Bluetooth settings.
- Press any button so the browser shows it. Its buttons take the DualSense's names: Cross, Circle, Create, Options.
- Set both trigger-stop sliders on the back to the long stroke, so each trigger has its full travel.
- Run the drift check with the sticks untouched, turn each stick round its edge, press every button and both triggers, then try the rumble on a Mac or Linux: on Windows no browser runs a DualSense's motors.
- Copy or print the report. For the back buttons, switch to a custom profile that gives them a job, as below.
What the results mean
- What a browser reads from the Edge
- Chrome, Microsoft Edge and Firefox read it as a DualSense: the 17 standard buttons, both sticks, both triggers in steps, and on Windows and macOS the touchpad's click as an 18th button. Safari reads the standard buttons without the touchpad click.
- The back buttons and Fn buttons
- The Fn buttons never reach a web page: the controller keeps them for switching profiles, with a face button. A back button shows here only as the button a profile gives it, and the default profile, which cannot be changed, gives it none. On a PS5, give it a face button's job under Settings > Accessories > DualSense Edge Wireless Controller > Custom Profiles (on Windows, in Sony's PlayStation Accessories app); then, on this computer, switch to that profile with Fn and its face button and press the back button: the button it copies lights up.
- Stick modules and drift
- The Edge's sticks are modules you can swap. If one stick drifts, the report says which: swap that module only, and run the drift check again to confirm the new one is centred.
- Profiles change what you see
- A custom profile can swap buttons, change a stick's dead zone or a trigger's range. The browser reads the controller as it is set: use the default profile for a test that means the hardware.
Questions
Why does the rumble do nothing on Windows?
Chrome and Microsoft Edge on Windows do not run a DualSense's motors from a web page, and Firefox runs no controller's motors anywhere. On a Mac, in Chrome or in Safari 16.4 or later, or on Linux in Chrome, the test can usually run them.
My back buttons do nothing here. Are they broken?
Not if the default profile is on: there they have no job, so nothing shows. Switch to a custom profile that gives them one, as above, and the button they copy lights up.
A trigger stops short, or jumps straight to 100 %. Is it broken?
Check its trigger-stop slider and the profile first: a medium or short stroke, or a profile's trigger range, shortens or flattens the press by design. Set the sliders to the long stroke, switch to the default profile, and test again.
Can I test a new stick module here?
Yes. Fit it, connect the controller, then run the drift check and turn that stick round its edge: a new module rests under 3 % and reaches its edge in every direction.