What Is a Controller Tester?
A controller tester helps you inspect game controller behavior through a repeatable sequence. This page asks you to activate controls deliberately and records which states the browser receives. Its purpose is to help locate a pattern worth investigating, not to issue a health grade. The connected device, browser, operating system, and mapping all shape the evidence. No download or account is required for this browser controller test.
Unlike the gamepad tester, which shows every current input live, this guided tool keeps a small session record of button coverage, resting stick readings, observed range, trigger range, and selected-button transitions. Moving to the next step is your choice. A skipped step is labeled as unobserved or unavailable in the summary rather than counted as a hardware failure.
How to Get Started with a Guided Controller Test
Connect your controller through a supported cable or wireless path, focus this tab, and press a button. Some browsers reveal gamepads only after interaction. When a device is detected, the first step shows its index, mapping, and control counts. If more than one device is connected, select the one you intend to handle. Changing devices starts a fresh observation record so readings from two controllers are not mixed.
For a fair comparison, keep the same browser, connection method, and operating-system settings across runs. Begin with all sticks released, then perform each requested action without touching unrelated controls. You may repeat a step or restart the whole guided check. The sequence is useful for comparing a symptom after cleaning, changing a setting, or reconnecting, but it cannot certify that a repair succeeded.
Check Buttons Methodically
The button step lists every button index exposed by the browser. Press and release each physical control once, watching the label move from not yet observed to observed. For a standard mapping, familiar positional names appear; for other mappings, numbered labels avoid guessing which physical input is which. The progress count says how many browser-exposed buttons produced a pressed state during this step. It does not say how many switches work.
Some controllers expose optional or system buttons that a browser cannot activate consistently. Use Skip unobserved controls to mark the remainder as skipped, then inspect the raw mapping if the count seems unexpected. Restart button check clears that step’s observations. If the wrong index changes, compare with the live gamepad view and your device documentation before assuming a hardware fault.
Observe Stick Center and Possible Drift
At the stick rest step, release both sticks, place the controller on a stable surface, and start the 2.5 second sample. The tool keeps at most 180 samples per stick. For each standard mapped stick it reports mean X and Y, root mean square distance from center, and maximum observed distance. Each instantaneous distance is sqrt(x² + y²); the RMS distance is the square root of the mean squared distances. These are descriptive statistics of browser values.
Stick drift commonly means an unintended input while the stick is released. A small nonzero coordinate alone is not automatic proof of drift. Device calibration, deadzone policy, sensor noise, mapping, and the browser path can all affect the center. More useful evidence is a repeatable unwanted movement in the affected game or app, alongside a persistent browser reading under controlled conditions. There is no universal broken-stick threshold here.
Inspect Stick Range Without a Quality Score
Rotate each stick through its comfortable travel during the range step. For the first four standard mapped axes, the controller tester retains the smallest and largest values seen in the current step. Reset range clears those extrema, letting you compare a second deliberate sweep. A minimum near negative one and maximum near positive one indicate what this browser observed, not exact physical travel or a promise that every angle is equally reachable.
The min and max values are separate one-dimensional observations. They do not define true circularity, mechanical alignment, or a calibrated percentage of controller quality. A browser may apply normalization or a deadzone, and a rushed sweep can miss an edge. If the mapping is non-standard or fewer than four axes are exposed, this step states that the standard stick interpretation is unavailable instead of assigning incorrect labels.
Check Trigger Range
For standard mapping, squeeze and release the left and right triggers independently while their step is visible. The page records each trigger’s minimum and maximum browser-exposed analog values. Reset trigger range starts a new observation. A partial squeeze may show a value between zero and one; a browser or device that sends only digital states may show just the endpoints. The numbers describe delivered values rather than measured spring force.
With a non-standard mapping, this controller trigger test declines to guess which raw button or axis represents a trigger. Open the live gamepad tester to examine numbered values while moving one control at a time, or consult vendor mapping documentation. A mapping difference is not itself a hardware failure.
Repeated Button Observation
Select a browser-exposed button and make ten separate presses, releasing it between each one. The tool counts rising transitions from released to pressed during this step. It also counts intervals under 50 ms between observed press transitions as rapid events for review. Restart 10 presses clears the count, and changing the selected button begins a fresh count. The selected control should be released before you start a new series.
These are browser-observed repeated state transitions. A rapid event might come from intentional fast pressing, remapping, a driver, a browser sampling effect, or a physical switch issue. The page cannot tell which cause applies and does not prove electrical switch bounce. If an anomaly recurs, note the browser, connection, button, and actions, then compare with an appropriate native or vendor diagnostic.
Read the Neutral Summary
The last step gathers the chosen device index and mapping, buttons observed or skipped, resting stick statistics, axis extrema, trigger extrema, and repeated transitions. It uses “not sampled,” “not observed,” or “unavailable” where the run lacks evidence. This is more informative than a made-up score because it shows what was actually tested and which paths were not. Start a new check when you change devices or test conditions.
Interpret each line in context. A browser-observed button press confirms delivery to this page; it does not prove that every game will bind it identically. A quiet center sample does not rule out intermittent behavior. A range captured in one sweep does not certify a stick’s mechanics. Repeating a controlled sequence can reveal consistency, but hardware diagnosis needs evidence from tools that can see the relevant layer.
Browser and Device Limits
This controller tester relies on the Gamepad API. Some browsers require a button press before exposure, and devices may disappear while a tab is hidden or after a disconnect. Standard mapping enables positional stick and trigger checks; non-standard mapping leaves raw indices without guessed semantics. The browser can receive values after driver calibration, operating-system filtering, and mapping. It cannot read firmware, electrical contacts, precise USB polling, or another application’s input state.
All raw input stays in this browser session. No controller identifiers or values are uploaded as test results. For formulas and collection rules, read the methodology. The disclaimer explains why offsets, missing readings, and repeated transitions cannot alone prove hardware failure. For continuous current input, return to the live gamepad tester.
Related Gaming Input Tools
The gamepad test is the faster choice for seeing which numbered state changes as you move a control. The mouse test and mouse double click test use pointer events, so they answer different questions. Pick the tool whose browser signal matches the symptom, and keep browser observations separate from manufacturer calibration or native-game telemetry.