Raw Input Viewer
Inspect every browser-exposed axis, button, trigger, and device field in one raw console.
GAMEPAD TESTER · BROWSER-OBSERVED
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 captured samples
Four browser-observed stick-axis channels over a fixed three-second window. Button labels mark rising-edge activity.
Pressed buttons · 0
No pressed buttons
Read-only
Samples stay here
No install
Reports are shared only when you export them.
Browser-observed values only. Availability depends on what this browser exposes.
Focused tests
Inspect every browser-exposed axis, button, trigger, and device field in one raw console.
Observe stick center, idle movement, range coverage, and circularity evidence.
Check pressed states, analog values, simultaneous inputs, and bounded event counts.
Compare LT and RT travel, release baselines, observed ranges, and value changes.
Run short, finite dual-rumble effects when the browser exposes a compatible actuator.
Measure browser-observed controller report intervals without claiming physical USB rate.
Estimate browser observation age and prompt-to-browser response time with clear limits.
Build a local center, range, and trigger reference without changing device settings.
Three steps
01
Attach a USB controller or pair a Bluetooth controller to begin a controller test, then press any physical button.
02
Watch browser-exposed sticks, buttons, triggers, and timestamps update without changing device settings.
03
Open the tool that matches the evidence you need and read its measurement limits before interpreting results.
Capability-based
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.
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
Live controller samples stay in browser memory. Nothing is uploaded by the tester, and optional reports are created locally only when you request them.
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
Plain answers
No. The tester reads values exposed by the browser and does not write firmware, drivers, operating-system calibration, or controller settings.
No. Samples stay in this browser. A report leaves the browser only when you deliberately export and share it.
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.
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.