Skip to content
ControllerTesterControllerTester
Test Controller ↗

PROFILE-AWARE TESTING

DualSense Edge Controller Test

Record the active profile and physical settings before comparing input.

Live Controller Test

Waiting for a controller

Connect with USB or Bluetooth, focus this page and press a controller button.

Controller model & setup Optional · automatic input detection
Search the model list or leave it automatic.

Choose your model for setup notes and suggested naming. The connected device above is reported separately by your browser.

Model setup guide →
Controller layout reference
Press any controller button to begin

Choose a model to see its controller illustration. Live inputs appear in the buttons, triggers and stick plots.

L2 / LT—
R2 / RT—
Buttons detectedWaiting for input

THIS SESSION

Your Check At A Glance

Buttons observedWaitingConnect and press a button
Trigger travel observedNot measuredMinimum → maximum · left / right
Resting-stick offsetNot measured95th percentile · left / right

Connect your controller, then press a face button.

Troubleshoot a problem →
Vibration options

Connect a controller to check browser rumble support.

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.
    Save, export or compare this session

    KEEP YOUR BASELINE

    Save Or Export This Session

    Stored on this device

    Snapshots stay in this browser. Export a report before clearing site data or moving to another device.

    Saved snapshots & comparison 0

    Choose two records to compare. Imported files are checked locally and never uploaded.

    By EmuCores · Setup guide · Updated 30 October 2026

    Test The Controls Fitted To Your Edge

    Choose DualSense Edge in the model selector and record the active controller profile. The browser identity can differ when a remapper supplies a virtual device.

    Rear Buttons

    Press a face button, release it, then press the rear control assigned to it. Matching browser indices can be expected. A rear control assigned to another type of action may not appear as an extra gamepad button.

    Trigger Stops And Profiles

    Record each stop position. Slowly press and release both triggers, then compare their minimum and maximum exposed values. A short physical travel and a full reported range are different measurements.

    Keep The Comparison Consistent

    1. Name a baseline and record connection, firmware and profile.
    2. Run a resting-stick measurement and sweep the range.
    3. Change one profile setting, then save a second snapshot.
    4. Compare the observations and confirm the practical effect in the game.

    Browser tests do not establish adaptive-trigger resistance, touch gestures or speaker output. Use Sony’s supported tools for those checks.

    Sources And Further Help

    Which Setting Changed The Result?

    Use descriptive names such as “USB default profile” and “USB custom stick curve.” Keep the connection and physical stop positions the same, then repeat the exact action. A different response curve can change intermediate values without changing the maximum. A game deadzone can suppress movement in the game while the browser trace still moves.

    The Rear Button Works In One Profile Only

    Check the assignment in each profile and test the ordinary button that supplies its action. Record whether the action is disabled, reassigned or delivered through a remapper. If the normal control works but its rear assignment does not, that is a narrower observation than saying the whole controller is missing.

    What Should I Send With A Support Enquiry?

    Keep the exact model, firmware, connection, active profile and steps that reproduce the issue. Export the before-and-after reports if useful, reviewing the notes before sharing. Explain what happens in the affected game as well as in the browser.