How to Test a Joypad Online in Your Browser (Buttons, Stick Drift, Vibration)

You can test a joypad in your browser without installing anything: connect the controller by USB or Bluetooth, press any button to wake the browser's Gamepad API connection, then read the on-screen visualizer for button presses, analog stick values, trigger pressure, and vibration. This works with Xbox 360, Xbox One, PS3, PS4, PS5, Switch Pro, and other major controllers on controllertest.io, which runs entirely in the browser and processes input locally. The main condition is that your browser supports the Gamepad API and that the controller is paired or plugged in before you start pressing buttons.

Before You Start

A controller with a working USB cable or a charged Bluetooth connection.
A desktop or laptop browser (the Gamepad API is a browser feature, not a downloadable app).
No driver installation is required, per the site's description of using the native Gamepad API.

Step 1: Connect and Wake the Controller

Plug the controller in via USB, or pair it over Bluetooth through your operating system's device settings.
Open the tester page.
Press any button on the controller. The page states that if the browser doesn't respond, pressing a button activates the connection. The visualizer shows "Waiting for Input" until a signal arrives, then displays the detected player slot (P1–P4).

Expected result: The controller appears as a connected player and the button/axis readouts stop showing "No Controller Detected."

Common snag: If nothing registers, the controller may be connected but idle — press a face button or a trigger rather than just moving a stick. Some controllers only report after a button event.

Step 2: Verify Buttons and Layout Mapping

Press each button one at a time and watch the visual interface. The tester highlights the pressed button and lists raw button indices (0–17 in the raw data panel).

Confirm every face button, shoulder button, stick click, D-pad direction, and menu button registers.
Check ABXY layout mapping: the visualizer shows which physical button maps to which label, which matters if you use a non-Xbox layout or a third-party pad.
Use the raw button list to spot a button that never lights up — that points to a hardware fault rather than a mapping issue.

Step 3: Check Analog Stick Centering, Deadzones, and Drift

This is the part most people come for. The tester shows left and right stick coordinates (for example +0.00, +0.00) plus an error value.

Let go of both sticks and watch the resting values.
A healthy stick returns to near 0.00 on both axes. If it settles at a non-zero offset, that's static offset or drift.
Move each stick slowly in a full circle and watch the trace for linearity and circularity. A lopsided or clipped circle suggests a worn or dirty potentiometer.
Nudge the stick in tiny increments to find where output first changes — this reveals the deadzone size.

How to read it:

Small resting offset that stays constant → likely static offset; the site notes this helps you decide between cleaning and hall effect sticks.
Values that wander or jump while untouched → drift, often dust or wear in the stick module.
A stick that won't reach full range → mechanical limit or calibration issue.

Step 4: Test Triggers

Triggers report analog pressure from 0 to 1 (shown as LT/L2 and RT/R2).

Squeeze each trigger slowly from rest to fully pressed.
Watch the value climb smoothly toward 1.00.
Release and confirm it returns to 0.00.

A trigger that jumps, sticks above 0 at rest, or never reaches 1.00 has a sensor or spring problem.

Step 5: Test Vibration (Dual Motor)

The tester offers independent left/right motor control with HEAVY, LIGHT, BURST, and PULSE patterns.

Trigger each motor separately.
Confirm you feel the heavy (low-frequency) and light (high-frequency) motors distinctly.
If one side is silent or weak, that motor or its connection is failing.

Note: vibration only works if your controller and connection support force feedback — some Bluetooth setups pass input but not rumble.

Step 6: Check Polling Rate and Latency (Optional)

The page includes a polling rate and latency readout so you can compare wired versus Bluetooth. Higher, steadier polling and lower latency favor competitive play; if Bluetooth shows noticeably worse numbers, that's your reason to switch to a cable.

Interpreting Results: What to Do Next

What you see	Likely cause	Reasonable next step
Stick rests at a small constant offset	Static offset / minor wear	Recalibrate if supported, or clean the stick module
Stick drifts or jitters at rest	Dust, wear, or failing potentiometer	Clean first; if it persists, consider hall effect sticks or replacement
One button never registers	Hardware or contact fault	Inspect/clean the button; replace if it stays dead
Trigger won't reach 0 or 1	Sensor or spring issue	Clean or service the trigger assembly
One vibration motor silent	Motor or wiring fault	Check connection; repair or replace

FAQ

Do I need to download software? No — the tester is browser-based and uses the native Gamepad API, so no driver download is required.

Is my input data sent anywhere? The site states all input processing happens locally in your browser.

Which controllers are supported? Xbox 360, Xbox One, PS3, PS4, PS5, Switch Pro, and other major controllers, per the site.

Why does nothing happen when I connect? Press a button to activate the connection — the browser often waits for an input event before reporting the device.