Controller calibration online: what a browser can and cannot do

What a browser can check

• Stick centre: where each stick rests when untouched. The stick drift test records it.
• Stick range: whether each stick reaches the edge in every direction. The controller circularity test draws the outer limit as you rotate the stick.
• Deadzone: the smallest deadzone that would hide the resting offset, from the controller deadzone test.
• Triggers and buttons: whether analog triggers go from 0 to their full value, in the gamepad tester.

These checks are a good way to decide whether calibration is needed and to confirm the result afterwards.

Where calibration actually happens

Calibration means storing new reference points for centre and range. Only software with access to the controller or its driver can do that:

• Nintendo Switch: the system settings include stick calibration for Joy-Con and Pro Controller.
• Windows: the Set up USB game controllers panel (joy.cpl) offers calibration for controllers whose driver supports it. Many controllers, including Xbox ones, do not offer it there.
• Steam: Steam Input has calibration and deadzone settings for many controllers, applied when games run through Steam.
• Maker apps: some controllers have a companion app for calibration, deadzones and firmware.

If your controller has no calibration option anywhere, a deadzone setting in the game or in Steam is the practical substitute.

A simple calibration check routine

1. Measure the resting offset and the range before you change anything, and note the numbers.
2. Run the calibration offered by your system or app, following its instructions exactly. Do not touch the sticks when it asks for the centre.
3. Measure again. The offset should be smaller and the circle should reach the edge evenly.
4. If nothing changes, the issue is probably mechanical wear rather than calibration. See controller moving by itself.

Triggers and buttons

Analog triggers report a value from 0 when released to 1 when fully pressed. In the gamepad tester, press each trigger slowly: the value should rise smoothly and reach the top. A trigger that stops short or never returns fully to 0 may need calibration where the system offers it, or may be worn or obstructed. Some controllers have trigger stops or switches that shorten the travel on purpose; check those first.

Digital buttons are either pressed or not. If one only reacts with a hard press or flickers while held, calibration will not help; that is the button contact itself.

Vibration is not calibrated, but you can check that both motors respond in the controller vibration test.

Why a browser cannot measure input lag

Input lag is the time from your physical press to the game reacting. Measuring it needs an external reference, such as a high-speed camera filming the button and the screen together, or a dedicated tester wired to the controller.

A browser only sees when it receives a new controller state. Gamepad updates carry a timestamp, but it marks when the browser got the data, not when you pressed the button. Pages also read the controller about once per screen frame, so a browser-based number reflects the screen refresh, the browser and the system as much as the controller.

Polling rate and USB versus Bluetooth

Polling rate is how often the controller sends its state. A page can count how often the values change, which gives a rough idea of the update rate, but it is limited by the browser and the screen refresh, and identical values are not counted as updates.

A cable is usually at least as fast and more consistent than a wireless connection, and many controllers report at a higher rate over USB. If you compare, change one thing at a time, use the same browser and the same game, and repeat each measurement several times.

What browsers do not expose

Gyroscope and motion sensors, touchpads, adaptive triggers, rear paddles, battery level and firmware version are generally not available to web pages. Checking or updating them needs the console, the maker's app or the operating system.