Test the inputs exposed by your browser, with familiar button labels and clear stick readings.
Live controller test
Waiting for a controller
Connect with USB or Bluetooth, focus this page and press a controller button.
Choose a model reference (optional)
Your selection is recorded separately from the browser’s device identity.
Choose a model for setup notes. This does not change your inputs or identify hardware automatically.
Press any controller button to begin
Layout illustration only. The button grid shows the actual inputs received.
L2 / LT
R2 / RT
Buttons detectedWaiting for input
Resting-stick measurement
This describes the input exposed by your browser. Firmware and remapping software can already apply deadzones. These readings do not certify hardware condition.
Raw readings & input history
Indices are shown as reported by the browser. Unknown layouts are not assigned stick or trigger names.
Waiting for controller input.
GUIDED CHECKUP
Check every control.
Buttons
Triggers
Stick drift
Stick range
Results
Connect a controller to begin.
Saved snapshots & comparison 0
Saved only when you choose, in this browser. Compare readings taken under the same conditions.
Connect and test your DualSense and DualSense Edge
Connect the controller to your computer with a data-capable USB cable or pair it using your operating system’s Bluetooth controls. Press a button in this tab.
Choose the intended controller from the device menu.
Press each button and move both sticks.
Run a resting-stick measurement if the browser provides a standard mapping.
Save a snapshot with your connection and profile noted.
Mapping and feature limits
The label set uses Create, Options, L1/R1 and L2/R2. Depending on the browser and mapping, the touchpad click may appear as an additional button. Touch positions, gyroscope data, adaptive-trigger resistance and advanced game haptics are outside this browser test.
A browser-reported device name may describe a virtual device instead of the controller in your hands. Get connection and mapping help →
DualSense Edge and third-party PS5 controllers
DualSense Edge profiles and rear assignments can alter what you observe. Record the active profile and trigger-stop positions. A rear button mapped to Cross can highlight the same browser index as Cross; it does not need a separate chip.
A PC mode or remapper can present a virtual XInput device. The browser reports that input identity. Selecting PlayStation labels here only changes the displayed names; it does not change the controller or prove that the physical device is a Sony product.
Use the button test for exposed controls and the vibration test for basic browser rumble. Touch gestures, adaptive resistance, microphone and speaker functions need separate model-specific checks.