Gamepad Tester and Controller Drift Test

It displays connected controllers, live buttons, analog triggers and axes, measures stick drift and center noise, checks stick range and circular coverage, and offers an optional vibration test when the browser and controller support it.

Connect the controller, press one of its buttons, choose it from the controller list and keep monitoring enabled. Some browsers do not expose a newly connected controller until the first button press or stick movement.

Stick drift is unwanted analog input while the stick is resting near its center. It can make a character, camera or cursor move without intentional input.

The neutral test samples the mapped left and right stick axes while you leave both sticks untouched. It records average center offset, maximum drift magnitude and short-term noise.

Use the smallest deadzone that reliably covers the controller’s neutral movement without making normal aiming feel unresponsive. The report suggests a value slightly above the largest movement observed during the neutral test.

No. Minor electrical noise and centering variation are common. Whether it causes a problem depends on the game’s deadzone, the controller, the operating system and the browser-reported values.

No. It diagnoses browser-visible input and estimates a practical deadzone. It cannot physically clean, calibrate, replace or repair a worn analog-stick mechanism.

Yes. After a neutral test, enable measured-center compensation to subtract the recorded average offset from the live display and exported metrics. This does not change system or game settings.

The range test records the maximum movement reached in different directions while you rotate each stick around its full travel. It reports directional coverage and approximate outer-range consistency.

Circularity describes how closely full stick movement follows a consistent circle. Real controllers can report square, clipped or uneven ranges, so the result is a diagnostic observation rather than a universal pass standard.

Yes. The standard controller diagram and raw button list show pressed state and analog value. The activity log records button presses, releases and hold duration during the current session.

Yes. Controllers that expose analog trigger values show gradual values between released and fully pressed. Some devices or mappings may expose triggers differently.

Yes when the selected controller and browser expose compatible vibration controls. The vibration button remains unavailable when support is not reported.

Vibration support differs by browser, operating system, connection method and controller. A controller can work for buttons and sticks while vibration remains unavailable.

Many commonly used USB and Bluetooth controllers can be detected, but button naming, axis order, vibration and special features vary by device, operating system and browser.

Yes when the operating system and browser expose the device as a game controller. Use the raw axes and custom axis mapping when the standard diagram does not match the physical layout.

Yes. Every browser-detected controller appears in the controller selector. Choose one device at a time for the detailed drift, range and button tests.

Confirm that the controller is connected and recognized by the operating system, press a button, try Scan Controllers, use a secure page, and test another cable, USB port, Bluetooth pairing or browser.

Browsers may delay exposing game-controller information until the user interacts with the device. This privacy behavior can make a connected controller appear only after a button press or axis movement.

Not every controller reports the same order or standard mapping. Use the four axis selectors and Y-axis inversion options to match the left and right physical sticks.

An analog axis is normally reported near zero at rest and approaches negative or positive one toward opposite extremes. Actual values and direction can vary by device and mapping.

A standard mapping indicates that the browser has arranged common buttons and axes into a familiar layout. An empty or different value means raw positions may need manual interpretation.

It records when the browser observes button changes, but it does not claim true hardware input latency because display refresh, operating-system scheduling, USB polling and browser timing all affect that measurement.

No page-specific server endpoint receives the live controller state. Reading, visualization, analysis and report creation happen in the current browser session.

It saves only non-sensitive preferences such as deadzone, test duration and axis mapping. Controller identifiers, button activity and sampled input are not saved by the tool.

No. It does not request camera, microphone, location or sensor access. Controller detection is handled through the browser’s controller interface.

It can work on mobile browsers and devices that expose a connected controller, but mobile operating systems, browsers, cables and Bluetooth profiles can limit detection or vibration.

Current Chrome, Edge, Firefox and Safari releases support the main controller-reading interface on many devices. Connection behavior, mappings and vibration support still vary.

Yes. Download a structured JSON report, a CSV log of retained samples, or copy a concise diagnostic summary to the clipboard.

The report includes the selected controller description, mapping, button and axis counts, test settings, neutral drift metrics, range metrics, observed buttons and optional retained samples.

A reconnect can assign a different controller index or mapping, reset browser state, alter the wireless connection or change the operating system’s reported calibration. Run a fresh neutral and range test after reconnecting.

Choose Reset Tests to clear drift, range, activity and retained samples while keeping the page ready to detect connected controllers again.