1. Connect And Wake
Connect by USB, Bluetooth or adapter, then press any controller button so the browser can expose the gamepad.
Use this free gamepad tester to run a full controller health check in your browser. Test buttons, analog sticks, triggers, stick drift, deadzone, polling stability, vibration support and exportable report data.
Run the full controller check in one repeatable pass before jumping into the specialized test pages.
Connect by USB, Bluetooth or adapter, then press any controller button so the browser can expose the gamepad.
Press every button, pull both triggers, rotate both sticks and let the page collect drift, circularity and polling samples.
Use the health score, warnings and export tools for repair notes, used controller checks or support screenshots.
The homepage is the summary dashboard. It explains whether the controller is readable, stable and worth deeper testing.
A practical summary derived from visible input, stick drift, circularity, polling stability, trigger range and vibration capability.
Shows which face buttons, bumpers, stick clicks, menu buttons and D-pad directions are currently visible to the browser.
Measures left and right analog stick center offset while the sticks are at rest, then flags suspicious idle movement.
Turns the largest idle stick offset into a starting deadzone value you can try inside games.
Reads analog trigger travel from rest to full pull, which helps catch weak springs, partial travel or mapping issues.
Checks whether a stick reaches the outer gate evenly instead of only returning to center correctly.
Estimates browser-visible update rate, interval and jitter so you can compare USB, Bluetooth and 2.4G modes.
Detects whether the browser exposes compatible haptics and can run weak or strong rumble pulses.
ControllerTest separates direct browser readings from timed samples, browser estimates and capability checks so the result is useful without overstating precision.
| Measurement type | Applies to | Confidence and limits |
|---|---|---|
| Direct reading | Buttons, axes and triggers | Reads current Gamepad API values from navigator.getGamepads(). Strong for visible input state, but button labels and axis order can vary by controller, browser and mapping layer.MDN Gamepad API |
| Timed sample | Stick drift, deadzone and circularity | Uses repeated browser readings while the controller is idle or moving through a known action. Confidence improves with a clean sample and drops if the controller is bumped or the tab is throttled. |
| Browser estimate | Polling rate, interval, jitter and stability | Converts visible timestamp or input-change deltas into Hz-style metrics. Useful for comparing modes on the same PC, but not a raw USB analyzer reading. |
| Capability detection | Vibration and haptics | Checks whether the browser exposes a compatible haptic actuator. A game or native app may still support rumble when the browser cannot.Vibration test |
The Gamepad API is widely available, but some parts vary by device and browser. Treat this page as a local diagnostic workflow, not a manufacturer calibration certificate.
A controller tester is a diagnostic page that reads gamepad input and turns it into understandable condition checks.
A useful tester should show raw input, analog values, stick center noise, trigger travel, polling behavior and haptic capability.
Run the same check before buying a used controller, after replacing a stick module, or when a game feels wrong but the cause is unclear.
The test runs on your device. It does not need a login, and report exports are generated locally from the current browser session.
A clean test controls the connection, movement and sample timing before judging the controller.
Use a data-capable USB cable as the baseline when possible. Then compare Bluetooth or 2.4G with the same browser and PC.
Press each button once, pull each trigger slowly, and rotate sticks around the full gate instead of snapping between corners.
A drift sample only works when both sticks are untouched. Repeat the sample if you bumped the controller.
Run a second pass when you see low polling, high jitter or a failed vibration test. Browser scheduling and wireless state can change between passes.
Use these bands as a practical triage guide. The score is not a warranty grade; it helps decide what to test next.
| Health result | What it means | Next action |
|---|---|---|
| 90-100 | Excellent | Inputs look clean, drift is low, trigger range is healthy and no major browser-visible capability issue is obvious. Save or export the report if you need proof of condition. |
| 75-89 | Good | The controller is likely usable, but one area may deserve a second pass. Check the related specialized page for the flagged metric. |
| 60-74 | Usable With Settings | Expect some adjustment, usually deadzone, connection mode, calibration software or a firmware setting. |
| Below 60 | Needs Inspection | Repeat the test, then inspect the failing area. High drift, missing buttons, weak triggers or unstable connectivity can require repair or replacement. |
The health score is a browser diagnostic summary. It does not replace manufacturer calibration tools, native latency analyzers or hardware repair inspection.
Most controller issues should be separated into settings, connection path and hardware before you decide on repair.
If the controller drifts only slightly, raise the in-game stick deadzone just above the measured idle offset.
Low polling or unstable input is often easier to diagnose by comparing USB, Bluetooth and 2.4G one at a time.
Some controllers need Xbox Accessories, PlayStation firmware tools, Steam Input, Razer Synapse, GameSir Nexus or 8BitDo software for updates or modes.
Large, repeatable drift, missing button states or incomplete trigger travel usually points to cleaning, calibration, warranty service or part replacement.
If the page looks wrong, first verify that the browser can see the controller and that no other app is capturing it.
Press a physical button after connecting. Try Chrome or Edge, reconnect the cable, and close games or launchers that may capture the pad.
Disable battery saver, keep the tab focused, avoid crowded Bluetooth environments and repeat the test with USB as a baseline.
Generic HID pads, Switch controllers and remapping layers can expose different labels. Use the live input grid before assuming a button is broken.
A game may support rumble even when the browser cannot expose a compatible haptic actuator. Try another browser or USB mode.
These source-linked controller examples are real device references, not live user submissions. Use them to sanity-check browser results and understand why PC, console, wired and wireless modes can differ.
| Controller / setup | Published or measured reference | How to use it |
|---|---|---|
| Razer Wolverine V3 Pro 8K PC | Native 8000 Hz wired or wireless PC polling; TMR anti-drift thumbsticks | A high-end ceiling for PC controller speed. Browser-visible readings can still be lower than Razer Synapse or hardware-level measurement paths.Razer spec |
| Razer Raiju V3 Pro | 250 Hz wireless on PS5; 2000 Hz wired on PC; no haptic feedback | A clear example of platform-specific behavior. If vibration is unavailable in the browser, verify whether the controller is designed to expose haptics at all.Razer FAQ |
| GameSir G7 SE | 250 / 500 / 1000 Hz PC modes; Hall Effect sticks and triggers; Xbox capped at 125 / 250 Hz | A practical wired baseline. Use the vendor app for polling mode and deadzone settings, then compare what the browser can actually observe.Windows Central |
| GameSir G7 Pro 8K PC | 8000 Hz mode, TMR sticks, rumble motors retained | Shows the newer PC-only high-Hz trend. Use it as a reminder that higher polling can also require sensitivity and deadzone adjustments.GamesRadar review |
| Turtle Beach Stealth Pivot | About 125 Hz wireless and 165 Hz wired on PC; Hall Effect sticks | A real premium Xbox-focused controller with lower PC polling than esports pads. Good for explaining why price and polling rate are different checks.Windows Central review |
| ControllerTest interpretation range | Stick offset under 0.04 is low; trigger range should approach 0.00 to 1.00; vibration depends on browser-exposed haptics | Use real device specs as context, then use the homepage health score and related test pages to diagnose your own controller.Drift testInput testPolling test |
Published specs and review measurements describe device capability, not a guaranteed browser result. Firmware, USB port, driver, OS, browser and power settings can change what this page sees.
Short answers for browser access, vibration support, drift diagnosis and adaptive trigger limitations.
Browsers usually hide gamepads until the user physically interacts with the controller. Press any controller button after connecting the device.
It is a practical browser diagnostic summary based on visible input, drift, trigger range, circularity, polling stability and vibration capability. Use it as triage, then open the related specialized test for any weak area.
No. It measures drift and recommends a deadzone for games. Severe drift usually requires cleaning, stick module replacement or warranty service.
The tool estimates update rate from Gamepad timestamps and visible input changes. It is a browser-layer estimate, not a USB analyzer reading.
The standard browser Gamepad API can read trigger travel when exposed, but it does not provide normal control over DualSense adaptive trigger resistance.
No. The test runs locally in the browser. Reports, CSV, JSON and share cards are generated on your device.
Start with the homepage for a full controller health check. Use the drift, deadzone, polling, circularity or vibration page when you need a deeper explanation of one specific result.
Chrome and Edge usually expose the broadest Gamepad API behavior on Windows. Firefox also works for input testing, while vibration and mappings can vary by controller and operating system.
Chrome extension now live
Install the Chrome extension for a compact toolbar popup, local gamepad readings and a fast link back to the full online controller tester.
Chrome Web Store