Stick drift
See resting movement, peak deviation and whether the signal escapes your chosen deadzone.
Run drift test ↗Test PS5, Xbox, Switch and PC controller sticks, buttons, triggers, deadzone and observed polling rate in one focused workspace. Nothing is uploaded.
Gamepad API ready · no install
Ready when you are Connect a controller or open the demo to see live diagnostics.
Polling rate is inferred from Gamepad API timestamp changes. It is useful for comparison, not proof of end-to-end hardware latency. Non-standard mappings expose raw axis indices rather than guaranteed left/right stick assignments.
Measure ten seconds of untouched stick input, compare a before and after result, then export a local report.
Sampling and exports run locally. Shared links contain only aggregate values in the URL fragment; they omit the controller name and raw input history.
One tool, useful answers
Raw values are translated into visual checks you can repeat before and after calibration, cleaning or repair.
See resting movement, peak deviation and whether the signal escapes your chosen deadzone.
Run drift test ↗Estimate how frequently your browser receives fresh controller reports and compare setups consistently.
Measure rate ↗Press every input and confirm buttons, triggers and directional controls respond without sticking.
Check buttons ↗How to test a controller online
The live tester starts immediately after the browser detects input. A deliberate three-step pass is more reliable than moving every control at once.
Pair your controller with Bluetooth or connect it by USB, then press any button so the browser can expose it. Chrome and Edge currently provide the broadest Gamepad API support.
Leave the sticks untouched, then rotate each one through its full range. Press every face button and direction, squeeze both triggers, click the sticks and run the short rumble check.
Note the resting drift, set a realistic deadzone and repeat the same checks after changing the cable, port, firmware or connection. Consistent conditions make comparisons more useful.
Understand the readings
Each stick reports horizontal and vertical values from roughly -1 to 1. At rest, the point should settle near the center. Gamepad Bench combines both axes into a radial percentage so small center noise is easier to distinguish from movement that can escape a game's deadzone.
Learn about stick drift ↗A deadzone is the center area a game ignores. A larger value can hide wear but also removes fine control. Use the slider as a diagnostic reference, then apply the smallest stable value inside the game or the controller manufacturer's software.
Find a stable deadzone ↗Digital buttons should switch cleanly between released and pressed. Compatible triggers expose a gradual value, so you can spot incomplete travel or an input that never returns to zero. A non-standard browser mapping may label some controls differently.
Open the input map ↓The rate is estimated from changes in the Gamepad API timestamp. It is useful for comparing the same controller, browser and connection, but it is not a laboratory measurement of end-to-end input latency and may be limited by browser or operating-system behavior.
Measure and interpret rate ↗Send the strong low-frequency and weak high-frequency dual-rumble channels separately, then record what you actually felt. A completed browser command is kept distinct from a physical motor-health conclusion.
Test controller vibration ↗Trace the full outer edge and measure angular coverage, radial roundness error, maximum and minimum radius, and opposite-direction asymmetry instead of relying on a circle visualization alone.
Measure circularity ↗Private by default
Gamepad Bench reads the browser’s Gamepad API in real time. Controller identifiers and inputs are not uploaded or stored.
Platform guides
Compatibility and troubleshooting
Browser access sits on top of the controller, connection, operating system and driver. Checking each layer in order usually identifies where the signal stops.
Browsers may keep a gamepad hidden until the user interacts with it. Confirm that the operating system shows the controller, return to this page and press a face button. If it remains disconnected, reconnect it before reloading the page.
A charging-only cable can power a controller without carrying input. Try another cable and port, avoid an unpowered hub, and temporarily remove other gamepads. A wired comparison also helps separate radio interference from stick or button faults.
Standard mappings usually expose two sticks, common face buttons, shoulders, triggers and a D-pad consistently. Extra paddles, touchpads, motion sensors, battery data and adaptive triggers may be absent or require the manufacturer's software.
Use the result
If both sticks settle near center, buttons release cleanly and the same setup produces a consistent observed rate, the browser is not showing an obvious fault. Note the browser, connection and deadzone you used. That baseline makes a future comparison more meaningful if a game later feels different. Finish with a short in-game check because a clean browser result cannot reproduce game-specific response curves, remapping or aim settings.
Check fine movement ↗First update controller firmware and compare its resting position with no hands on the sticks. Recalibrate through official software when available, then test again. A modest in-game deadzone can hide small center noise, but increasing it does not repair worn components. Check warranty terms before opening or cleaning the controller. Persistent movement that escapes a reasonable deadzone across browsers and connections is stronger evidence that professional service or replacement may be justified.
Follow the drift test ↗Compare Bluetooth with USB, try a different data-capable cable or port, close software that remaps controllers and repeat the same motion. If the problem follows the controller across computers and connections, hardware becomes more likely. If it appears only in one game, review that game's input profile and deadzone first. Keep the battery charged and test at the same distance so power saving and radio conditions do not become hidden variables.
Compare report frequency ↗Gamepad tester FAQ
Yes. The tester runs in a supported browser with no account, download or payment. Connect a controller, press a button and the live panels will begin reading the inputs exposed by the browser.
No. Controller identifiers, axes, buttons and timestamps are processed in your browser and are not uploaded by Gamepad Bench. Raw input history is not stored. If you explicitly save a before baseline, only an aggregate report without controller identifiers is kept in this browser until you clear it.
Yes, if the controller is paired with your computer and the browser exposes it through the Gamepad API. USB is still useful as a comparison when Bluetooth results look inconsistent or the controller is not detected.
The tool is designed for Xbox Series and Xbox One controllers, PS5 DualSense and PS4 controllers, Switch Pro controllers, and many standard PC gamepads. Exact labels, rumble and extra controls depend on the browser, operating system and mapping reported by the device.
It is a strong first diagnostic step, not a repair certificate. Repeat the test with the same browser, try another connection or computer, update firmware and compare the behavior inside a game before deciding to repair or replace hardware.
This page estimates update frequency from browser-visible Gamepad API timestamps. Native tools may access lower-level USB or Bluetooth reports, while browser scheduling, power saving, firmware and connection type can change the observed result.