GAMEPAD CHECK

GAMEPAD TESTER · BROWSER-OBSERVED

Gamepad Tester. See the raw signal.

Use this browser-based controller tester with a USB or Bluetooth controller to inspect exposed inputs—no install required. Every sample is processed locally in this browser.

Waiting for controller input.

Live input summary

No controller selected

Waiting for controller
Signal stream · Waiting for controller
LXLYRXRY

No captured samples

t − 3.0 snow

Four browser-observed stick-axis channels over a fixed three-second window. Button labels mark rising-edge activity.

LX
Unavailable
LY
Unavailable
RX
Unavailable
RY
Unavailable
LT
Unavailable
RT
Unavailable
Browser-observed rate
Collecting

Pressed buttons · 0

No pressed buttons

Open the complete raw console in Raw Input Viewer →

Read-only

Samples stay here

No install

Reports are shared only when you export them.

Browser
Current browser
Connection
Waiting
Mapping
Not exposed by browser
Samples
0

Browser-observed values only. Availability depends on what this browser exposes.

Focused tests

One raw signal. Eight ways to inspect it.

01input

Raw Input Viewer

Inspect every browser-exposed axis, button, trigger, and device field in one raw console.

02geometry

Stick Drift Test

Observe stick center, idle movement, range coverage, and circularity evidence.

03input

Button Tester

Check pressed states, analog values, simultaneous inputs, and bounded event counts.

04input

Trigger Test

Compare LT and RT travel, release baselines, observed ranges, and value changes.

05output

Vibration Test

Run short, finite dual-rumble effects when the browser exposes a compatible actuator.

06timing

Polling Rate Test

Measure browser-observed controller report intervals without claiming physical USB rate.

07timing

Input Latency Test

Estimate browser observation age and prompt-to-browser response time with clear limits.

08geometry

Controller Calibration

Build a local center, range, and trigger reference without changing device settings.

Three steps

How it works

  1. 01

    Connect

    Attach a USB controller or pair a Bluetooth controller to begin a controller test, then press any physical button.

  2. 02

    Observe

    Watch browser-exposed sticks, buttons, triggers, and timestamps update without changing device settings.

  3. 03

    Choose a focused test

    Open the tool that matches the evidence you need and read its measurement limits before interpreting results.

Capability-based

Controller and browser compatibility

Common controllers

Run a gamepad test with Xbox-compatible, PlayStation-compatible, Nintendo-style, and generic USB or Bluetooth gamepads when the operating system and browser expose them through the Gamepad API.

Browser coverage

Current Chrome and Edge releases generally provide the broadest desktop coverage. Firefox and Safari support varies by platform, permissions, connection mode, and controller capability.

Measurement boundary

Private by default. Precise about limits.

Local samples

Live controller samples stay in browser memory. Nothing is uploaded by the tester, and optional reports are created locally only when you request them.

Observed, not certified

These tools describe values visible to the browser. They do not certify hardware health, prove physical USB polling rate, measure true end-to-end latency, or repair a controller.

If input is missing

Connection troubleshooting

  • Keep this tab active, then press a physical controller button.
  • Confirm the controller appears in operating-system Bluetooth or USB settings.
  • Close games or remapping utilities that may hold exclusive device access.
  • Try another cable, port, connection mode, or current browser release.

Plain answers

Frequently asked questions

Does Gamepad Check change controller settings?

No. The tester reads values exposed by the browser and does not write firmware, drivers, operating-system calibration, or controller settings.

Are controller samples uploaded?

No. Samples stay in this browser. A report leaves the browser only when you deliberately export and share it.

Can this prove hardware polling rate or true input latency?

No. Browser scheduling and the Gamepad API affect timing. An external physical reference is required for true end-to-end latency and physical report-rate certification.

Why does my controller not appear immediately?

Many browsers expose a gamepad only after it sends input. Keep this tab active, press a physical button, and verify the controller is paired with the operating system.