Learn how controllers actually work

The Gamepad API is a web standard supported by every major browser that exposes connected controllers as a simple JavaScript object. It reports a list of buttons, each with a pressed state and an analog value from 0 to 1, and a list of axes for the sticks, each reported as a value from negative 1 to positive 1.

Unlike keyboard or mouse events, gamepad state is not pushed to your page automatically. A site has to poll the browser on every animation frame and check the current values itself, which is why every tool on this site runs a continuous read loop rather than waiting for an event.

A digital input has exactly two states, pressed or not pressed. Face buttons, the D-pad, and the shoulder buttons on most controllers behave this way. A single boolean is enough to describe them fully.

An analog input reports a continuous range instead of two states. Sticks report their position along two axes, and most triggers report how far they have been pulled as a value between 0 and 1, not just whether they are touched. This is why a trigger can act as a delicate accelerator in a racing game rather than an all or nothing switch.

Polling rate is how often your controller sends a fresh state update to the device it is connected to, measured in Hz. A controller polling at 250Hz sends an update roughly every 4 milliseconds, whether or not anything changed.

Input latency is the actual delay between your thumb moving and that action being usable by the game, which includes polling interval, but also processing time, connection type, and how the game engine itself reads input on its own loop. A higher polling rate lowers the ceiling on latency but does not guarantee a lower number by itself.

The Gamepad API defines a standard mapping so that button index 0 is the bottom face button, index 1 is the right face button, and so on, regardless of whether the controller is an Xbox, PlayStation, or generic pad. When your browser recognizes a controller as standard, every tool on this site can label buttons consistently.

Some controllers, particularly less common third party pads, are not recognized under the standard mapping. In that case buttons still work, but the index order may not match what you expect, and extra buttons or axes can appear that do not correspond to anything physical.

A potentiometer stick reads position through a small resistive wiper that physically drags across a contact strip as the stick moves. That constant friction wears the contact surface down over months of use, which is the root mechanical cause of most stick drift complaints.

A Hall effect sensor reads a magnet's position without any physical contact at all, using the magnetic field itself, so there is nothing to wear down from friction. TMR, tunnel magnetoresistance, is a newer contactless technology in the same family, often reported as slightly more precise at small movements.

Drift shows up as movement the game registers while your thumb is not touching the stick. The two most common causes are dust or debris around the stick's base interfering with the sensor, and physical wear on a potentiometer style sensor after repeated use.

Dust related drift often responds well to careful cleaning. Wear related drift usually does not improve with cleaning and tends to get gradually worse, since the underlying contact surface is degrading rather than just being dirty.

An adaptive trigger contains a small motor connected to the trigger mechanism that can add or release resistance in real time, controlled by the game through a console specific API. This lets a game simulate the feel of a tensioned bowstring or a sticky mechanical switch.

That motor control channel is not part of the open web standards this site relies on. A browser can read where the trigger currently sits along its travel, but it cannot instruct the motor to apply resistance, and it cannot read the resistance profile a game may have set.

A gyroscope measures rotation rather than position, reporting how fast the device is turning around each of three axes. Some controllers, including the DualSense and Switch Pro, include one, and games use it to let you fine tune aim by physically tilting the controller.

Phones and tablets expose their gyroscope to the browser through the DeviceOrientationEvent standard, which this site's gyroscope test uses directly. Controller gyroscopes are not exposed through the Gamepad API standard, so a website cannot read that data from a connected game controller, only from the device it is running on.

Every tool on this site follows the same basic process. Connect the controller through the browser, exercise every button, stick, and trigger through its full range, and compare the readings against a defined threshold for that specific test, such as what counts as measurable drift versus calibration noise.

Where a claim can be measured directly, such as polling interval or trigger range, the tool measures it live rather than relying on a manufacturer spec sheet. Where something cannot be measured through the browser, such as true adaptive trigger resistance, the relevant page says so directly instead of guessing.

Individual reviews score five separate axes, build quality, sticks and triggers, buttons and inputs, connectivity, and value for money, each on its own scale before being combined into one overall score.

Value for money is weighted more heavily at the budget end of the market, where price is often the deciding factor, and weighted less heavily on premium controllers, where buyers are usually paying for a specific feature rather than looking for the cheapest option.

The Gamepad API and Web Bluetooth cover most of what a controller test actually needs, live button and stick state, trigger position, and in some cases battery level and basic vibration control, all without installing anything.

The trade off is that a browser is deliberately sandboxed away from lower level hardware access. Deep firmware information, proprietary motor control channels like adaptive trigger resistance, and manufacturer specific diagnostic modes sit outside what any website can reach, regardless of how it is built.

Every reading a tool on this site produces, button state, stick position, trigger value, is processed entirely in your browser's memory while the page is open. Nothing about your controller's input is sent to a server as part of normal use.

If a tool offers an export option, such as a text or JSON report, that file is generated and saved directly to your own device when you click the button. It is not uploaded anywhere by this site.