Trigger range signals this page checks
This page isolates trigger travel. It checks whether each trigger reaches zero at rest, climbs smoothly while pulled, and reaches a useful maximum value near full travel.
Controllers
Controller Trigger Test: LT / RT Analog Range Checker
Controller trigger test for LT/RT or L2/R2 minimum value, maximum value, return-to-zero state, left/right range mismatch and analog mapping.
Min / max range
LT / RT
Zero return
0 - 1
Left-right balance
Local
When this test helps
Use it when acceleration, braking, aiming, camera zoom, or pressure-sensitive actions feel uneven, only work at full press, or behave differently in a browser game.
Details worth writing down
Record LT/L2 and RT/R2 current values, minimum value at rest, maximum value at full pull, browser, connection mode, controller mode, and whether a game treats the trigger as analog or digital.
Live controller input
Connect a controller, then press a button or move a stick.
Waiting for input
Activate your controller
Connect by USB or Bluetooth, keep this tab visible, then press any controller button. Some browsers do not reveal an already connected controller until the first interaction.
Result summary
A compact view of the current test state and the strongest signal detected so far.
Waiting for controller input
Current controller
-
Controllers
0
Active buttons
0
Maximum axis offset
0.000
Press any controller button so the browser can expose the device.
LT/RT trigger range test steps
1. Connect the controller and press any button to activate it. 2. Leave both triggers untouched and confirm their values start near 0. 3. Pull the left trigger slowly from rest to full travel, then release it. 4. Repeat with the right trigger at the same speed. 5. Compare minimum and maximum values for both sides. 6. Repeat in another browser or input mode if one side never reaches zero or never approaches full value.
How to read the result
A trigger that rests above zero may cause unwanted braking, aiming, or acceleration. A trigger that never approaches full value may feel weak in racing or pressure-sensitive games. If both triggers behave like only 0 or 1, the controller or browser may expose them as digital buttons. If the issue appears only in one game, check that game's trigger dead zone and input profile before assuming hardware failure.
Privacy and local processing
Trigger values are read locally from the Gamepad API. The page does not upload controller input, game settings, account details, or calibration files.
How to use Controller Trigger Test: LT / RT Analog Range Checker
Use it when acceleration, braking, aiming, camera zoom, or pressure-sensitive actions feel uneven, only work at full press, or behave differently in a browser game.
Controller trigger test for LT/RT range and zero return
The test tracks current trigger value, observed minimum, observed maximum, return-to-zero behavior, limited-range warnings, and left-versus-right trigger comparison.
Controller Trigger Test: LT / RT Analog Range Checker test steps
1. Connect the controller and press any button to activate it. 2. Leave both triggers untouched and confirm their values start near 0. 3. Pull the left trigger slowly from rest to full travel, then release it. 4. Repeat with the right trigger at the same speed. 5. Compare minimum and maximum values for both sides. 6. Repeat in another browser or input mode if one side never reaches zero or never approaches full value.
Controller Trigger Test: LT / RT Analog Range Checker symptom troubleshooting
Match what you see with the page records first, then decide whether the next check is settings, connection, drivers, or the device itself.
Throttle or trigger does not reach full pull
Press LT/RT slowly to the end and watch maximum value.
If one side never reaches full range, record the max value and inspect calibration or wear.
The trigger does not return to zero
Release fully and watch whether the minimum returns near 0.
This affects throttle and aiming; compare wired/wireless and the OS controller panel.
Left and right trigger ranges differ
Press both triggers at the same pace and compare min, max, and return.
Stable differences point next to firmware, calibration, or trigger mechanics.
Triggers behave like ordinary buttons
Watch whether the value is only 0/1 instead of continuous.
This is often input mode or browser mapping; try switching XInput/DInput mode.
Controller Trigger Test: LT / RT Analog Range Checker limits and privacy
What this page cannot prove
Most standard controllers expose LT/RT or L2/R2 as analog button values. Some controllers, adapters, browser combinations, or compatibility modes expose triggers as digital inputs or different numbered axes.
Local processing and privacy
Trigger values are read locally from the Gamepad API. The page does not upload controller input, game settings, account details, or calibration files.
Related tools
Still narrowing it down? Open the next page that matches the symptom you can actually see.
Troubleshooting Center
Start with the symptom
Start here
Gamepad Tester: Buttons, Sticks & Controller Drift
Gamepad test for connection status, buttons, D-pad, stick axes, trigger values, mapping type and browser Gamepad API detection.
Stick Drift Test: Controller Joystick Deadzone Checker
Stick drift test for left and right stick center offset, X/Y axis drift, maximum offset, return-to-center stability and deadzone behavior.
Gamepad Button Test: Controller Press and Release Checker
Gamepad button test for face buttons, D-pad, shoulder buttons, menu buttons, stick clicks, press counts, release events and possible stuck buttons.