GameControllerTest.com
PlayStation pro controller profile

DualSense Edge Controller Test

Test DualSense Edge stick, button, D-pad, and trigger input online. Check standard browser-visible controls before or after setup.

Live browser diagnostic

Complete controller check

Run every essential check from one private dashboard.

Not connected
Local-only test

Connect with USB, Bluetooth, or a supported wireless adapter. Then press any controller button so your browser can expose it. Your readings are processed on this device.

Detected device No controller detected Gamepad API ready · waiting for input
L1
R1
L
R
Update rate— Hzbrowser-observed
Buttonsreported
Axesreported
Mappingbrowser label
Live input

Sticks and triggers

Left stickX 0.000 · Y 0.000
Right stickX 0.000 · Y 0.000
Left trigger 0%
Observed range: not sampled
Right trigger 0%
Observed range: not sampled
Neutral sample

Stick drift and deadzone

Set the controller on a steady surface and do not touch either stick during the sample.

Ready for an 8-second sample.
Full movement

Range and circularity

Rotate each stick slowly around the outer edge, then sweep the center in several directions.

Move the sticks to begin range tracking.
Input coverage

Buttons and D-pad

Press and release every available control. Analog buttons show their reported value.

No button activity yet.
Raw browser data

Axes and mapping

Use these values to spot unusual layouts. A blank standard mapping does not automatically mean the controller is defective.

View raw browser data
Connect a controller to view raw data.
Optional capability

Vibration check

Browser haptics are not available for every controller, connection method, operating system, or browser.

Connect a controller to check browser support.
Private test record

Keep your result

Reports are stored in this browser. Sharing is optional and puts only the selected result in the link.

Diagnostic readings describe what this browser receives, not electrical measurements from the controller. Confirm important findings in the game or device where you plan to use the controller.

Controller overview

What this browser check can reveal

Use this profile to inspect the standard gamepad inputs exposed from a DualSense Edge controller. The live tester can check analog-stick centers and range, face buttons, D-pad, shoulder controls, stick clicks, and trigger values.

Back buttons, function buttons, profiles, replaceable stick-module settings, trigger stops, and advanced PlayStation 5 effects are not consistently available through the browser Gamepad API. Configure those features with supported PlayStation or PC software first.

If you are checking a replacement stick module, run the same hands-off drift and circularity tests before and after installation. Keep the controller mode, connection, and browser unchanged when comparing reports.

Connection notes

Start with a known, stable connection.

  • Hands-off drift check for each replaceable stick module
  • Range and circularity comparison for left and right sticks
  • L2 and R2 input check with trigger-stop reminder
  • Coverage check for standard browser-exposed buttons
Inspection workflow

A practical controller checklist.

  1. 01

    Confirm the controller appears and the reported name or identifier is plausible.

  2. 02

    Press and release every button, D-pad direction, stick click, bumper, and trigger.

  3. 03

    Run the hands-off drift sample, then sweep both sticks through their full range.

  4. 04

    Disconnect and repeat in the connection mode you actually plan to use.

  5. 05

    Verify any fault inside a supported game or console before making a purchase or repair decision.

Compatibility is a chain, not a promise

Disable or document trigger stops before comparing maximum values.

Frequently asked

DualSense Edge Controller Test questions

Can the page identify a bad stick module?

It can show repeatable center offset, noise, or reduced range in the input received by the browser. It cannot determine the internal cause or certify a module for warranty purposes.

Why do the back buttons not appear?

Rear controls are often handled inside the controller as profile remaps rather than separate browser-visible buttons. Their behavior depends on the active profile and supported configuration software.

Why does a trigger stop below full travel?

Check the physical trigger-stop setting first. A short stop intentionally limits mechanical travel and may change the reported maximum depending on the configured profile.