Use this combined controller test when you want one place to inspect live stick axes, visualize an example deadzone, check digital and analog button values, and confirm that changing input reaches the browser. The page gives a broad first look; focused diagnostics below collect the longer samples needed to investigate one specific symptom.

When to use the full test

You are not sure whether the problem involves a stick, button, trigger, mapping or connection.
You want to compare several controller inputs without switching pages.
You are checking a used or repaired controller before moving to focused tests.
You need a quick browser-level check before opening manufacturer calibration software.

Before you begin

Connect one controller by USB or Bluetooth, then press a face button so the browser can expose it.
Close games, remapping tools or overlays that may capture controller input.
Place the controller on a stable surface when observing its released stick position.
Use the same browser, port and connection mode when comparing two runs.

How to run a complete controller check

Confirm detection. The lab should change from “Awaiting input” to “Controller linked” and show the browser-reported controller name. If it does not, press a button, refocus the page and reconnect before interpreting anything else.
Observe both sticks at rest. Release the sticks and watch the live positions. This instant overview can reveal obvious movement, but use the dedicated drift test for an untouched multi-sample measurement.
Move through the full range. Push each stick to the cardinal directions and rotate around the edge. Uneven outer travel belongs in the circularity and range test rather than a centre-only check.
Press every button deliberately. Open Buttons & Triggers, press controls one at a time and confirm the expected browser button index changes. Repeat any missing or inconsistent control.
Pull analog triggers slowly. On a standard mapping, LT/RT values should change progressively rather than only switching from off to on. Non-standard mappings stay labeled as raw indices.
Use the deadzone as a demonstration. The slider shows whether the current Axis 0/1 magnitude sits inside a threshold you choose. It does not recommend a setting for every game.
Check changing input. Signal Activity confirms that values are changing. It deliberately does not call animation frames a hardware polling rate.
Repeat suspicious results. Reconnect and compare USB with Bluetooth when possible. A pattern that follows the controller across repeated runs is stronger evidence than one brief fluctuation.

How to interpret common observations

What you observe	What it can mean	Best next test
A released stick repeatedly sits away from centre	Possible centre offset or drift visible through the current browser and connection path.	Collect an untouched drift sample.
One direction does not reach as far as the others	Possible outer-range, calibration or mechanical travel difference.	Map circularity and outer range.
A button value is missing or appears under an unexpected index	Mapping, remapping, connection or button behavior may differ from the expected layout.	Run the focused button test.
An analog trigger stops early or returns slowly	The browser-visible trigger range differs from the opposite side or from a previous run.	Compare trigger travel.
Inputs freeze or the controller disappears	The USB/Bluetooth path, battery, pairing, browser or operating-system connection may be involved.	Monitor connection and input changes.
Signal activity changes but one game still ignores input	The controller reaches the browser; game configuration, focus, mapping or platform support may be the next place to check.	Compare the game’s controller settings and manufacturer tools.

Standard and raw mappings

When the browser reports Gamepad.mapping as standard, the lab can use conventional left/right stick and LT/RT labels. If the mapping is empty or non-standard, GearCheck Lab shows raw axes and button indices instead of guessing a console-style layout.

A raw index that changes consistently is still useful. Note which physical control produces it, then compare that same index in a repeat run.

Browser and hardware limits

The Gamepad API reports what reaches the browser after controller firmware, drivers, operating-system mapping and the USB or Bluetooth layer. This page cannot inspect potentiometers, Hall sensors, batteries, radio interference or internal mechanical wear directly.

The broad lab does not turn one instantaneous position into a drift verdict, call a user-chosen deadzone “recommended,” or infer polling rate from animation frames.

Focused controller diagnostics

Stick Drift Test Deadzone Test Circularity & Range Test Button Test Trigger Test Vibration Test Polling Rate Test Calibration Test Connection Test Controller Testing Guide

Controller test FAQ

Why is my controller not detected?

Connect it before loading the page, press a face button and make sure another game or remapping tool is not exclusively capturing it. Then reconnect or compare a current browser. Browser and operating-system support varies by controller and connection.

Can this test diagnose stick drift?

It can show live stick position, including obvious movement at rest, but the dedicated Stick Drift Test is better because it collects an untouched sample and reports repeatable centre behavior. Neither page can identify the failed internal component.

Does the deadzone slider change my controller?

No. It is a local visualization of a threshold against the current Axis 0/1 magnitude. It does not write firmware, change game settings or recommend one universal value.

Why are the buttons shown as numbers?

The browser exposes buttons by index. A standard-mapped controller has conventional index meanings; a non-standard controller may not. The lab keeps raw numbers when it cannot label them reliably.

Can I compare USB and Bluetooth?

Yes. Run the same sequence in each mode and look for repeatable differences in detection, input stability and ranges. This is a practical comparison, not a laboratory latency certification.

Does a clean result prove the controller is fault-free?

No. It means no problem was visible in the browser-exposed signals you checked under those conditions. Internal wear, intermittent faults and features the browser cannot access may still require manufacturer or repair diagnostics.

Privacy and safe use

LOCAL INPUT: Controller axes, button values and mapping data are read by the page for this diagnostic and do not need to be uploaded for the test to function. GearCheck Lab does not change controller firmware or calibration settings.

Stop testing if the controller, cable or battery behaves abnormally. Check warranty terms and manufacturer guidance before cleaning, opening or repairing hardware.

Full controller signal overview