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.
Trigger range diagnostics
Controller Trigger Test
Check left and right controller trigger response, resting values, travel, and maximum input with clear live browser readings.
- ✓ Runs in your browser
- ✓ No sign-in
- ✓ Local results
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
Buttons—reported
Axes—reported
Mapping—browser label
Live input
Sticks and triggers
Left trigger 0%
Observed range: not sampled
Right trigger 0%
Observed range: not sampled
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.
Did you feel the pulse?
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.
Use the test as evidence, not a pass/fail sticker.
Analog triggers should move smoothly from released to fully pressed. The trigger test displays the value reported for each trigger so you can check its resting point, progressive travel, and observed maximum.
Press one trigger slowly several times, release it fully, and repeat with the other. Watch for jumps, a value that fails to return, or a maximum that is consistently lower on one side.
Some controllers expose triggers as buttons, shared axes, or digital inputs depending on their operating mode. Browser values can also be normalized by the driver, so compare behavior rather than relying on one universal threshold.
Signals to watch
- Separate left- and right-trigger meters
- Resting, live, and observed maximum values
- Slow-travel check for jumps or flat spots
- Side-by-side range comparison
Run a repeatable check.
- 01
Connect the controller and press any button so the browser can detect it.
- 02
Use the focused test panel slowly and deliberately. Watch the live values during presses, holds, movement, and release.
- 03
Repeat any suspicious result after reconnecting, then confirm it in the game or device where the controller will be used.
What a useful result looks like.
Look for repeatable behavior rather than a single momentary value. Stable, symmetric movement and clean press-and-release behavior are generally more useful signs than chasing a perfect zero.
If a result changes substantially between USB and wireless modes, browsers, or computers, the connection, driver, browser, or remapping software may be part of the problem.
Important browser-test limits
Disable physical trigger stops before judging full travel.
Questions about controller trigger test
Why does my trigger not reach 100 percent?
Possible causes include trigger stops, calibration, firmware mode, wear, or driver scaling. Confirm that adjustable stops are disabled, reconnect the device, and compare the value in supported manufacturer software.
Why is my trigger only on or off?
The controller or its current mode may expose the trigger as a digital button. Some retro controllers and alternate compatibility modes do not provide analog trigger travel.
Are adaptive trigger effects tested here?
No. The page reads input values available through the browser. It does not reproduce game-specific adaptive resistance or certify those mechanisms.