Button Stuck / Sticky Test
Idle-state check
Put the controller down. Don't touch anything. We watch every button for 3 seconds.
Release-time check
Press each input, then lift off. We time the release in milliseconds (polled at ~16ms).
Press and release any button to begin. Anything over 100ms is flagged as slow-release.
Repeat-press check
Press the selected button 10 times. We confirm each press registers cleanly and separately.
Diagnostic summary
Why controller buttons get sticky
A sticky button is almost never a wiring fault. It is the physical part of the controller — the rubber dome, the conductive pad underneath, or the surrounding plastic — failing in a small but recoverable way. Knowing which cause matches which button shortens the fix from an afternoon of guessing to a five-minute clean.
Dust under the skirt
Fine dust collects around the button's plastic skirt and gets pressed down into the housing every time you tap. After enough cycles it binds the button so it sits slightly depressed even at rest, which the idle-state check picks up immediately. Triggers and bumpers are the worst-affected here because their travel pulls more air across the gap.
Spilled drinks and dried sugar
Sweet drinks are the most common cause of stuck face buttons. A small splash dries into a thin film of sugar around the dome, and the button now releases slowly because it is mildly glued back down. The release-time check is built for exactly this — you will see a button hold for far longer than a clean tap should.
Rubber domes losing their snap
Each button sits over a small rubber dome that snaps back when you lift off. After tens of thousands of presses the rubber compresses and stops returning fully, which shows up as slow release on the most-used buttons — typically A/Cross on Xbox and PlayStation shooters, or R2/RT on racing pads. The repeat-press check catches the same issue from a different angle: a tired dome occasionally misses a press entirely.
Dirty conductive pads
Underneath the dome is a small carbon pad that touches the circuit board to register a press. Skin oils and dust transfer through over time, leaving the contact partially insulating. The button feels normal to press but the registration is intermittent — which is the exact pattern repeat-press tests catch when only seven or eight of ten taps come through.
Bent membrane traces
A dropped pad can flex the membrane under the buttons enough to leave a trace permanently pressed or permanently disconnected. Bumpers take this damage most often because the shoulders absorb the impact when a controller hits a hard floor. This is the one cause on the list that usually means a replacement part, not a clean.
What each check actually proves
The three stages of the tester look similar but each isolates a different type of sticking. Knowing which check flagged a button tells you which cause is likely, and which fix to try first.
Idle-state check
With the controller untouched for three seconds, every button should read as released. Anything flagged here is being read as actively pressed without you touching it. This is the most serious form of sticking and almost always points to dust, debris, or liquid residue physically holding the button down. In some cases an impact-damaged membrane can keep a trace closed, which looks identical from the API's point of view.
Release-time check
A clean tap should hold for roughly 60 to 150 milliseconds, depending on how quickly you lift your finger. If a button shows a hold time well above 800ms after a normal tap, the button is releasing slowly — which is the textbook signature of sticky residue or a tired dome. One caveat worth knowing: the browser's Gamepad API polls at roughly one frame per 16ms, so sub-frame differences are invisible. The check is reliable for the kind of multi-hundred-millisecond stickiness players actually notice in game; it is not a precision instrument for measuring tap speed.
Repeat-press check
Ten clean taps on the same button should produce ten registered presses. If the counter stops short or stalls, the button is registering intermittently — sometimes the press goes through, sometimes the contact does not close. This is almost always a dirty conductive pad rather than a sticking dome, and it responds well to the alcohol clean described below. Worth noting: the counter only ticks when the button transitions cleanly from released to pressed, so a button stuck halfway down will fail this test even if you tap it hard.
Fixing a sticky button
Start with the least invasive fix and escalate only if the cheaper step does not clear the fault. Most sticky buttons are recovered without opening the controller shell at all.
Isopropyl alcohol around the button skirt
Put a small amount of 90% or higher isopropyl alcohol on a cotton swab and work it around the edge of the affected button. Press the button repeatedly while the alcohol is still wet — the action draws the solvent down into the housing and lifts sugar residue and skin oil off the contact. Let it air-dry for ten minutes before re-running the test. This single step clears the majority of sticky-button cases.
Compressed air for dust
If the idle-state check is still flagging a button as pressed after the alcohol clean, blow a short burst of compressed air around the button skirt at a shallow angle. Hold the can upright to keep liquid propellant from escaping into the controller. This usually frees a button that the alcohol soak did not reach because the obstruction was solid debris rather than residue.
Open the shell for a full clean
For stubborn cases — usually a button that fails both idle-state and repeat-press — the real fix is a shell-open clean. Remove the screws, lift the front housing, and pull the silicone button pad away from the membrane. The conductive carbon pads on the back of the silicone clean easily with a dab of alcohol on a microfibre cloth; the membrane itself wipes clean with a dry cloth. This is moderately involved, voids warranty on most pads, and is best attempted only after the easier steps have failed.
Send it for warranty or replacement
If a button fails after cleaning, or if the test results suggest impact damage to a bumper or membrane trace, the realistic option is a warranty claim or a replacement part. Both Sony and Microsoft will replace a faulty pad within the standard 12-month warranty, and most regions extend that under consumer protection law when the fault appears later. Keep the receipt and the test results — a screenshot of a clear failure on this page is the kind of evidence a support agent will take seriously.
Sticky button questions, answered
Common questions about stuck and sticky controller buttons, what the test results actually mean, and when a fault crosses the line from a clean-fix to a warranty claim.
Why does my button feel stuck but the tester says it's fine?
The tester reads what the controller's hardware reports to the browser, not what the button physically feels like under your finger. A button can feel mushy, gritty, or slow to spring back while still registering electrically as a clean press-and-release because the dome is making contact at the right moments. If the tool gives you a pass but a button still feels wrong, the fault is mechanical — usually a worn dome or dust in the skirt — and the alcohol clean in Step 1 of the fixes section will often restore the feel even though the electrical reading was already passing.
Will rubbing alcohol damage my controller?
Isopropyl alcohol at 90% or higher is the standard for cleaning electronics for good reason. It evaporates fast, leaves no residue, and is safe on the plastics and rubber used in modern controllers. The two cautions worth knowing are these: keep the alcohol off the analog stick rubber tops, which can dry out and crack over time if soaked repeatedly, and use small amounts on a swab rather than pouring it on the pad directly. The same alcohol used to clean wounds at 70% is too dilute for electronics work — the extra water takes longer to evaporate and can sit in the housing.
How often should I run this test?
There is no maintenance schedule for this — it is a diagnostic tool, not a service interval. Run it when a button starts feeling wrong in game, when you are deciding whether a used controller is worth buying, before a warranty claim so you have evidence, or any time a pad has been put away for a few months and you want a quick health check before a long session. Running it weekly when nothing feels wrong adds nothing.
Why does my trigger show pressed when I'm not touching it?
Analog triggers report a value between 0 and 1, not just pressed or released. A trigger
at rest should read close to 0, but worn triggers — especially the adaptive ones on the
PS5 DualSense after heavy use — often settle at 0.05 or so when fully released. The
Gamepad API's pressed flag flips on at any non-zero analog value on some
implementations, which is why a slightly worn trigger can flag in the idle-state check
without genuinely being stuck. If the value sits low and stable rather than at full
press, the trigger is not stuck — it just has a small calibration drift. The dead-zone
calibration tool covers this case directly.
A button passes idle but fails in game — what next?
This is the exact case the repeat-press check exists for. A button that registers cleanly when you tap it deliberately but misses inputs during fast play is almost always failing intermittently, not constantly. Run the repeat-press stage on the problem button and watch the counter — if it stalls before reaching ten, the button is losing contact on some presses. The cause is usually a dirty conductive pad rather than mechanical sticking, and a Step 1 alcohol clean clears most cases. If the counter reaches ten cleanly on the tool but you still miss inputs in fast game scenarios, the issue may sit on the game side or the controller's polling rate rather than the button itself.
Does this test work on Switch Pro and third-party controllers?
Yes for most modern pads, with one caveat. The browser's Gamepad API works with any controller that maps to the Standard Gamepad layout, which covers Xbox, DualShock 4, DualSense, the Switch Pro Controller over USB or Bluetooth, and most reputable third-party pads such as 8BitDo, GameSir, and PowerA. The caveat is mapping: some third-party pads expose buttons in a different order than the Standard Gamepad layout, so an input labelled here as "A / Cross" may correspond to a different physical button on your pad. The names in the tester follow the standard mapping; if the button you press lights up a different label, that is a mapping difference, not a fault.
What if a button only sticks when the controller is warm?
Temperature-dependent faults are the hardest to confirm. The usual cause is residue inside the housing that softens with heat from a long session, which is why a button feels fine after a five-minute test and starts sticking an hour into play. The practical workaround is to run the test immediately after a long gaming session rather than from cold — that is the state the fault actually appears in. If a button fails the test only when warm, the fix is the same: alcohol clean on the dome and conductive pad, which usually clears the residue that softens at temperature. A pad that only sticks when warm and resists cleaning is one of the few cases where replacement parts are the better answer.
Will Sony or Microsoft accept this test as warranty evidence?
A test result from this page is useful supporting evidence, not a guaranteed claim. Both Sony and Microsoft accept warranty cases on their own diagnostic process — typically a video of the fault, the controller serial number, and proof of purchase — and a clear screenshot of an idle-state failure or a repeat-press stall strengthens that case because it shows the fault is reproducible on hardware that has no game-specific variables. Pair the screenshot with a short phone-camera video of the button behaving oddly under your finger, and most support agents have enough to escalate. The controller serial number is on a sticker inside the battery compartment for Xbox pads and on the bottom edge for DualSense.