Trigger Deadzone Test | Measure L2 And R2 Dead Travel Now

Pull an analog trigger slowly and you expect the number to start climbing the moment the trigger moves. It does not. There is a stretch at the top of the pull where the trigger is physically moving and the reported value is still sitting at zero, and there is usually another stretch at the bottom where the value has already reached its maximum and the last part of your squeeze does nothing at all. Between those two dead bands sits the part of the trigger that actually works, and on a tired controller that band can be surprisingly narrow. This page measures where it starts, where it ends, and how much of your pull is doing real work.

Measure Your Trigger Deadzone

Results

Left Against Right

What A Software Deadzone Costs On Top

Report

The CSV holds every reading from your last sweep with its phase and timestamp, which is what you want if you plan to plot the curve yourself. The JSON holds the finished numbers for both triggers.

How To Run It Properly

1. Use a cable if you have one. Wireless adds its own gaps to the readings and you want to know which ones came from the trigger.
2. Press any button on the controller so the browser reveals it. A pad that has been sitting untouched since you plugged it in is invisible to any web page.
3. Run the rest check first, with both hands off the triggers. Five seconds. This tells you whether either trigger is reporting a value while it is fully released, which is the fault that quietly ruins everything else.
4. Switch to the slow sweep and pick a trigger. Wait for the countdown, then start pulling on the cue and reach the hard stop exactly as the bar finishes. Even pace matters more than exact timing.
5. Hold at the stop for a moment when the tool asks, then release at the same even pace on the second cue.
6. Read the usable travel figure first. If it is above eighty percent your trigger is healthy and the rest of the numbers are just detail.
7. Run the hold steady mode. It parks you at a quarter, a half and three quarters of the range and measures how still the reading sits at each. This is where a worn trigger gives itself away.
8. Finish with fast release. Ten hard pulls and quick releases, checking the trigger returns all the way to zero every single time.
9. Repeat everything on the other trigger. They almost never match, and the comparison table is where the interesting finding usually is.

If the bars do not move at all when you squeeze, the triggers are reporting somewhere other than the default place. Change the source option in the setup panel, and if you want to see exactly which index your pad is using, the controller mapping tool prints all of them.

A Trigger Has Two Deadzones, Not One

This is the part almost every guide gets wrong, and it is the reason this page exists rather than just pointing you at a stick deadzone tool.

When people say trigger deadzone they almost always mean the dead travel at the start. You begin squeezing, the trigger visibly moves, and the game does nothing for the first few millimetres. That is real, it is on every controller, and it is the one people complain about.

What almost nobody checks is the other end. Analog triggers very commonly reach their maximum reported value before they reach their physical stop. The number hits 1.00 and then you keep squeezing against a trigger that still has travel left in it, and every bit of that extra movement is thrown away. In a racing game that means the last part of your brake pull is doing nothing. In a shooter with an analog pull it means the top of your squeeze is wasted.

Both bands cost you the same thing, which is resolution. If your trigger reports nothing for the first fifteen percent of its travel and tops out at eighty percent, then everything you want to express with that trigger has to fit into the sixty five percent in the middle. Same finger, same physical movement, less room to be precise in.

The reason the top band is invisible is that nothing tells you about it. A game does not report that you have reached maximum. The trigger keeps moving, so your hand assumes the input keeps changing. You find out only when you measure, which is exactly what the slow sweep here does.

Why The Bands Exist At All

The bottom band is partly deliberate. A trigger that reported movement the instant it was breathed on would fire in your bag and register during a jolt, so manufacturers build in a margin at rest and often clamp small values to zero in firmware. A modest bottom band is a feature.

The top band is usually not deliberate. It comes from the sensor reaching the end of its useful range before the mechanism reaches the end of its travel, and it grows as the sensor wears. A brand new controller often has almost none. A well used one often has quite a lot.

What Each Mode Measures

Rest Check

Five seconds with both hands off. It reports what each trigger says while fully released and how much that reading wanders. A trigger sitting at 0.04 while untouched is the trigger equivalent of stick drift, and it is worse than it sounds, because many games treat any value above zero as a partial pull. That is the cause behind a car that creeps forward on its own and a weapon that will not stop being half drawn.

Slow Sweep

The main measurement. The tool counts you down, you pull from rest to the hard stop over a fixed window, hold briefly, then release over the same window. From that one movement it works out where the value first left zero, where it topped out, how much travel sat usefully in between, whether the value stalled anywhere along the way, and whether the release retraced the pull or took a different path.

Hold Steady

Three targets in turn at a quarter, a half and three quarters of the range. You park the trigger there and hold. The tool separates two different things: the slow drift over the four seconds, which is mostly your hand, and the fast wobble within it, which is mostly the hardware. A trigger that is quiet at rest and noisy in the middle is common, and holding an analog trigger halfway is exactly what driving games ask you to do all the time.

Fast Release

Ten hard pulls and quick releases. It checks that the value returns all the way to zero every time and times how long it takes. A trigger that comes back to 0.02 instead of 0.00, or that takes noticeably longer to return on the ninth cycle than the first, has a spring or a pivot problem rather than a sensor problem.

Reading Your Numbers

Dead At The Top Of The Pull

The share of your squeeze that reported nothing at all. Under ten percent is normal and desirable. Ten to twenty percent is noticeable but workable. Past twenty five percent you are losing a quarter of the trigger before the game hears anything, and it feels like a delay even though nothing is actually delayed.

Tops Out At

How far through your pull the value first reached its maximum. Ninety five percent or higher means the trigger uses almost all of its travel. Anything under eighty five percent means a meaningful chunk of the bottom of your squeeze is doing nothing. This is the number people have never seen before, and it is often the more surprising of the two.

Usable Travel

The gap between those two, which is the part of the trigger that actually does work. This is the single headline number on the page. Above eighty percent is healthy. Sixty five to eighty is workable. Below sixty means your finger is trying to express a full range of input through a narrow band, and precision suffers whether or not you can feel why.

Resting Value

What the trigger reports untouched. It should be a flat zero. Anything consistently above your zero tolerance is a real fault and it should be dealt with before you pay attention to any other number here, because a trigger resting above zero shifts every other measurement on the page.

Hysteresis

How far apart the pull and the release are. On a clean trigger the value crosses the halfway mark at the same point in the travel whether you are squeezing or letting go. When there is slop in the linkage or wear in the sensor, those two crossing points separate, and the size of that separation is what this number reports. It is the section below if you want the full explanation, because it is the measurement people find most unfamiliar.

Smallest Step

The finest change the trigger reported between two different values. Around 0.004 means the controller is sending eight bit values, which is roughly 256 steps across the full range and is by far the most common. Much finer than that means ten bit or better. Much coarser means the trigger is reporting in visible jumps, which feels like stepping rather than sliding when you move slowly.

Hysteresis, The One Nobody Measures

Worth a section of its own, because it is real, it is common, and there is almost nothing written about it in the context of controllers.

Squeeze a trigger halfway and note the number. Now squeeze it all the way, then let it back out until it is physically in the same place as before. On a perfect trigger you get the same number. On most real triggers you do not. The number on the way down sits slightly higher or slightly lower than the number on the way up at the same physical position.

That difference comes from mechanical slop. The trigger blade, the pivot, the return spring and the sensor arm are separate parts with tiny amounts of play between them. On the way up, one set of surfaces is in contact. On the way down, the parts settle differently and everything shifts by a fraction. Add a sensor that responds slightly differently depending on the direction it is being moved and you get a measurable gap.

Why it matters in practice is modulation. Anything where you ride a trigger and adjust constantly, which is threshold braking, trigger controlled throttle, and analog aiming pressure, depends on the relationship between where your finger is and what the game receives being stable. High hysteresis makes that relationship depend on which direction you last moved, which your hand cannot compensate for because it has no way to know.

Under about three percent of travel is normal and nothing to think about. Past eight percent it is a genuine fault, and it is one of the few trigger problems that has a mechanical cause you can sometimes see when the controller is open, usually as a visibly loose pivot or a spring that has lost its tension.

One honest caveat before you read too much into your number. This tool infers position from time, so a pull and a release taken at genuinely different speeds will produce a hysteresis figure that is partly you. Run it two or three times and only believe a result that repeats.

Why Trigger Deadzone Is Not Stick Deadzone

These get treated as the same setting with the same fix and they are not remotely alike.

A stick rests in the middle of a two dimensional space and can be pushed in any direction. Its deadzone is a region around the centre, and the reason it exists is that the stick reports small values while you are not touching it. It is a threshold that ignores noise. The joystick deadzone test is about finding the smallest circle that hides that noise without dulling the stick.

A trigger rests at one end of a one dimensional journey and only goes one way. Its dead bands are not there to ignore noise, they are the parts of the travel where the sensor is not telling you anything new, one at each end. You are not choosing a threshold, you are discovering a limit.

The practical difference is what you do about it. A stick deadzone that is too large is a setting you turn down. A trigger dead band that is too large is hardware, and no setting will give the travel back to you. What software can do is remap the range you have left so that it stretches across the full output, which is a genuinely useful fix and is covered in the fixing section below.

There is one more difference worth knowing. A stick has a spring pulling it toward the centre of its range, so the noisiest and least reliable part of its travel tends to be the middle. A trigger is held at one end by its spring and pressed hard against a stop at the other, so its least reliable region is the middle too, but for a different reason, which is that neither end is holding it steady. That is why the hold steady mode exists and why a general check of trigger travel like the trigger pressure test is worth running alongside this one.

The Failure Modes And What Each One Feels Like

What Counts As Normal

Two pieces of context. These figures describe what arrives at your browser, which has already been through the controller firmware and the operating system driver, so treat comparisons far more seriously than absolutes. And the last row is the one to trust most of all, because two triggers on the same controller went through the same firmware and the same driver, so a gap between them is genuinely about the hardware rather than about anything in the chain.

What Lost Travel Actually Costs You In Games

Most of the time an analog trigger is being used as a button, and none of this matters. Where it matters is anywhere the game reads how hard you are pulling rather than whether you are pulling.

Throttle and brake. The obvious one. A trigger that tops out at seventy five percent means you reach full throttle earlier in the pull than you expect, and the part of the squeeze you were using to feather is gone. Threshold braking, where you sit just below lock, is the hardest thing to do on a trigger with a narrow usable band.

Analog acceleration in anything that walks or flies. Flight and space games often map thrust to a trigger. Lost travel at the top means small adjustments are impossible, because the smallest movement you can make now covers more output than it used to.

Pressure sensitive actions. A handful of games read the trigger as a continuous value for bow tension, engine revs, or grip strength. These are the ones where a stall partway through the sweep is most obvious, because the action visibly hangs and then catches up.

Digital use with an analog threshold. Even when a game only cares whether the trigger is pressed, it usually picks a value between 0.10 and 0.30 as the point where pressed becomes true. A large dead band at the top of the pull pushes that crossing point later in your physical travel, which feels exactly like input lag and is routinely mistaken for it. If you want to know whether you have actual delay as well, the latency test measures that separately.

Adaptive triggers. On a DualSense the resistance mechanism sits in the same assembly as the sensor, and a trigger that has been driven hard with strong resistance effects can wear differently from one that has not. The adaptive trigger test covers what a browser can and cannot tell you about that side of it.

Why Triggers Go Wrong

The Sensor Wears At The Ends

Most triggers use a small potentiometer with a wiper dragging along a track as the trigger moves. The ends of that track see the most use, because every full pull ends there and every release returns there. Worn ends stop delivering their full swing, which is exactly what an early top out looks like on the sweep.

The Spring Tires

The return spring has one job, which is to bring the trigger back to exactly the same resting place every time. As it weakens the trigger returns more slowly, then stops returning quite all the way, and the resting value creeps above zero. This is the most common cause of a trigger that reads a small permanent value.

Debris In The Mechanism

Triggers sit on the shoulder of the controller with an opening straight into the shell, which makes them very good at collecting dust and crumbs. Contamination in the mechanism produces sticky returns and occasional stalls, and it is by far the most fixable cause on this list.

A Loose Pivot

The trigger rotates on a post, and that post and its bearing surface wear. Play at the pivot is the main source of hysteresis, and it also lets the trigger sit at a slightly different angle each time, which shows up as inconsistent readings between runs.

Heavy Adaptive Resistance

Specific to controllers with adaptive triggers. The mechanism applies real physical force against your finger many times a second, and that force is transmitted through the same parts that carry the sensor. It is not a defect, but it is more mechanical work than a plain trigger does, and it is worth measuring both triggers on those controllers rather than assuming they have aged together.

Software That Is Already Reshaping The Signal

Worth ruling out before you blame any hardware. Steam Input, vendor software and remapping tools all offer trigger range and threshold settings, and a profile configured months ago can be quietly clipping your output right now. Close everything and remeasure. The gamepad viewer is a quick way to watch the raw value move while you toggle a setting on and off.

Fixing It

Free Things Worth Trying First

• Work the trigger through its full range twenty or thirty times, then remeasure. This alone clears a surprising number of sticky returns and small resting offsets.
• Blow compressed air into the gap around the trigger while working it. Debris is a real and common cause and this costs nothing.
• Close any remapping software and measure again, in case a profile is clipping your range.
• Recalibrate if your platform offers it, which resets the endpoints the driver treats as fully released and fully pulled.
• Test wired rather than wireless, so you know the reading is about the trigger.

Range Scaling

If your trigger genuinely tops out at eighty percent, scaling stretches the range you have left across the full output, so the point where your travel ends reports as 1.00 again. Steam Input can do this and so can most remapping tools, usually described as trigger range or output range. It is a legitimate fix and it restores your thresholds rather than hiding the problem.

It has one cost worth knowing about. Scaling multiplies everything, including any noise the trigger has developed, so measure the wobble in the hold steady mode before you lean on it. A quiet trigger scales beautifully and a noisy one gets noisier.

Raising Or Lowering Your Game Deadzone

Raising it hides a resting value that is above zero, at the cost of pushing your actuation point even later in an already shortened travel. Lowering it recovers responsiveness but lets any resting value through. The cost table in the results section runs both against your own measurement so you can see the trade rather than guess at it.

Opening It Up

A weak spring and a debris blocked mechanism are both approachable repairs. The spring is a cheap part and needs no soldering, and cleaning needs nothing but isopropyl alcohol and patience. A worn potentiometer means replacing the trigger sensor module, which does need soldering. The teardown steps and the safety notes in the controller repair guide apply directly, since getting to the triggers means the same shell removal.

When To Leave It Alone

Usable travel above eighty percent with a clean zero at rest is a healthy trigger and there is nothing to gain from chasing the last few percent. A modest dead band at the top of the pull that is identical on both triggers is how that controller was built rather than a fault. And if you only ever use the triggers as buttons, none of this will ever reach you.

Which Controllers Actually Have Analog Triggers

Worth checking before you spend time hunting a fault that cannot exist.

Fully analog. Every Xbox controller since the original, every PlayStation controller from the DualShock 3 onward including the DualShock 4 and the DualSense, and most third party pads built for those platforms. These report a continuous value and everything on this page applies.

Digital only. Nintendo controllers. The Switch Pro Controller and both Joy Con units report their shoulder inputs as simple pressed or released, with nothing in between. The tool will detect this during a sweep and say so rather than reporting a meaningless deadzone. There is no fault and nothing to fix, and if you want to confirm those inputs are registering cleanly, the button test is the right page for a digital input.

Analog with a mechanical stop. Some enthusiast controllers, including several Xbox Elite style pads, have a physical switch that shortens the trigger travel for faster firing. With the stop engaged the trigger becomes effectively digital and the sweep will report a very narrow usable band, which is correct rather than a fault. Turn the stop off before measuring.

Analog reported as an axis. Older pads and many generic USB controllers put the triggers on axes rather than buttons, sometimes both on a single axis where one trigger reads negative and the other positive. That is what the source option in the setup panel is for, and the combined axis case is worth knowing about because on those pads pulling both triggers together cancels them out, which is a hardware limitation rather than anything this page can measure around.

Method And Honest Limits

Position Is Inferred From Time

The most important limit on the page, so it is worth stating plainly. Nothing tells a browser how far your trigger has physically moved. All it receives is a number. So when this tool says fifteen percent of your pull was dead, what it actually measured is that the value stayed at zero for the first fifteen percent of the time between the pull cue and the moment you reached the stop. That maps onto physical travel only as well as your pacing does. Pull unevenly and you will produce a dead band figure that is partly about your hand. Run each sweep two or three times and trust the number that repeats.

What 1.00 Actually Means

A reading of 1.00 means the reported value has saturated. It does not prove the trigger reached its mechanical stop, and a trigger reporting 0.90 at the stop is not necessarily ten percent short mechanically, because the firmware and the driver both normalise the value before you see it. This is another reason to weight the comparison between your two triggers more heavily than any single figure.

Sampling

Readings arrive in step with your display refresh, so a 60Hz screen gives about sixty a second. Across a three second sweep that is around 180 readings, which is plenty for finding dead bands and stalls. A faster display gives a smoother curve. If you want to know how often the pad reports underneath that, the polling rate test shows it.

Wireless

A dropped packet during a sweep looks exactly like a stall in the trigger. Measure wired for anything you plan to keep, and if your readings differ between sessions, check the link and the battery before concluding anything about the hardware.

Save The Numbers

Trigger wear is gradual and it is almost impossible to notice as it happens. A reading today is worth a great deal more when there is a reading from six months ago sitting next to it, which is what the export is for.

Browser And Platform Notes

• Chrome and Edge report trigger values most consistently. Firefox works but sometimes places the triggers on different indices for the same pad. Safari is the least predictable.
• Keep this tab focused. Background tabs get throttled and sampling stops, which will ruin a sweep partway through.
• If the bars sit halfway up while you are touching nothing, the triggers are on an axis that rests at minus one. Change the source option rather than assuming a fault.
• Some third party pads only expose analog triggers in one of their two modes, usually toggled with a button combination involving Home. If your triggers read as pressed or released only, try the other mode.
• If the browser cannot see the controller at all, that is a connection problem rather than a trigger problem, and the controller checker confirms it in a few seconds.
• Everything runs locally in the page. Nothing about your controller or your results leaves your device.

Questions People Actually Ask

What is a normal trigger deadzone?

Under ten percent of the pull reporting nothing is normal and healthy, and a small band there is deliberate rather than a defect. What matters more is the total usable travel once both ends are accounted for, and above eighty percent is where you want that.

My trigger reads a value when I am not touching it.

That is the trigger equivalent of stick drift and it is worth fixing before anything else, because many games read any value above zero as a partial pull. Work the trigger through its range thirty times and remeasure. If it persists, the return spring is the usual cause.

Can I reduce trigger deadzone with a setting?

You can lower a software deadzone, which moves the point where the game starts listening. You cannot recover travel the hardware is not reporting. For that, range scaling is the right tool, because it stretches the range you still have across the full output.

Why does my trigger reach maximum before I finish squeezing?

Because the sensor reached the end of its useful range before the mechanism reached its stop. It is very common and it grows with use. Scaling in software restores your thresholds, and a sensor replacement fixes it properly.

My Switch triggers show nothing analog.

They are not analog. Nintendo shoulder inputs report pressed or released with nothing in between, so there is no deadzone to measure. The tool detects this and says so rather than inventing a number.

What is hysteresis and should I worry about it?

It is the gap between what the trigger reports on the way up and on the way down at the same physical position, and it comes from play in the mechanism. Under three percent is normal. Past eight percent it will interfere with anything where you modulate the trigger constantly.

Should the left and right triggers match?

Roughly, yes. A gap under five percent is nothing. A large gap is the most trustworthy finding on this page, because both triggers went through the same firmware and the same driver, so the difference is genuinely mechanical.

Does a bigger deadzone protect a worn trigger?

It hides a resting value above zero, which is useful. It does not protect anything, and it costs you travel you may not be able to spare. Work out the smallest setting that actually does the job rather than reaching for a large one.

Why do my numbers change between runs?

Mostly pacing. The measurement infers position from time, so an uneven pull produces an uneven result. Run three sweeps at a deliberate steady speed and use the figure that repeats.

Do hall effect triggers avoid all of this?

They avoid the worn track, because there is no physical contact to wear. They do not avoid mechanical play at the pivot, a tiring spring, or debris in the mechanism, so hysteresis and return problems remain possible.

My trigger stalls partway through the pull.

Sweep twice more. A stall in the same place on every run is a flat spot on the sensor track and it is real. A stall in a different place each time is almost always you pausing without noticing.

Is this different from a trigger pressure test?

Yes. A trigger pressure test shows you the value as you squeeze and confirms the trigger is working across its range. This one measures where that range starts, where it ends, how much of it is doing anything, and whether the release retraces the pull.

Does it work on a phone or tablet?

Yes, with a controller connected over Bluetooth or through an adapter. The bars and the curve both scale down, though the sweep is easier to pace on a larger screen.

Can I use the report for a warranty claim?

That is what it is designed for. It names the controller, gives figures for both triggers side by side, and timestamps everything. Run it twice on separate days and attach both, since an intermittent fault documented once is easy to dismiss.

How often should I run a trigger deadzone test?

Once when a controller is new so you have a baseline, then every few months, or any time a car starts creeping or full throttle stops feeling like full throttle. Wear is gradual, so the value of the test comes from having something to compare against.