Common controllers
Xbox-compatible, PlayStation-compatible, Nintendo-style, and generic USB or Bluetooth controllers can work when the operating system and browser expose them through the Gamepad API.
RAW INPUT VIEWER · BROWSER-OBSERVED
Raw Gamepad Input Viewer
Inspect raw axes, buttons, triggers, and device fields exposed by the Gamepad API in one complete viewer. Input is read-only and processed locally in this browser.
COMPLETE RAW CONSOLE · LOCAL PROCESSING
No controller selected
No controllers detected.
Waiting for controller
Browsers expose a controller after it sends an input. Keep this page active, then press a physical controller button.
- Index
- Not available
- Mapping
- Not available
- Timestamp
- Not available
- Connected
- No
- Stale
- No
- Browser
- Current browser
- Connection
- Waiting
- Mapping
- Not exposed by browser
- Samples
- 0
Browser-observed values only. Availability depends on what this browser exposes.
Reduced motion: showing the latest point only.
| Current X | Not available |
|---|---|
| Current Y | Not available |
| Trail points | 0 / 600 max |
Reduced motion: showing the latest point only.
| Current X | Not available |
|---|---|
| Current Y | Not available |
| Trail points | 0 / 600 max |
LT / L2 trigger
Unsupported — no trigger value was exposed.
RT / R2 trigger
Unsupported — no trigger value was exposed.
Raw axes
| Raw index | Value |
|---|---|
| No axis values exposed. | |
Raw buttons
| Raw index | Value | Pressed | Touched |
|---|---|---|---|
| No button values exposed. | |||
Button event history
Newest 100 sampled pressed-state changes, kept in observed order.
No button changes observed yet.
Local report
The report is created in this browser and downloaded directly to your device. Nothing is uploaded.
Raw controller samples are excluded unless you opt in. At most 5,000 samples are included.
Raw and traceable
Inspect every browser-exposed input
This comprehensive view keeps the browser's raw axis and button indices intact, adds standard labels only when mapping is exposed, and shows the last frame as stale rather than pretending input is still live after a disconnect.
Three steps
How to use the raw gamepad console
01
Connect and activate
Attach a USB controller or pair one over Bluetooth, keep this tab active, and press a physical button so the browser can expose it.
02
Select the device
Use the controller selector whenever multiple devices are connected. The console preserves stale evidence if the selected device disconnects.
03
Read raw evidence
Compare exact raw indices, values, pressed and touched states, stick paths, triggers, and sampled button changes.
Capability-based
Controller and browser compatibility
Browser exposure varies
Mapping, timestamp, touch, and device coverage depends on the browser, operating system, controller, and connection mode. Use a current browser and interpret only the fields it exposes.
Nothing uploaded
Private local processing
Controller samples stay in this browser. The default local report excludes raw samples, the browser's raw device identifier, the full user-agent string, and IP or network data. Bounded raw samples are included only after a separate opt-in.
Observed, not certified
Measurement limitations
This console displays values observed through the browser. It does not certify hardware health and does not prove physical polling rate or true end-to-end latency. Browser scheduling can merge or delay changes, so event history can miss transitions between sampled frames.
If values stay idle
Troubleshooting controller input
- Keep this tab active and press a physical controller button.
- Confirm the device appears in operating-system USB or Bluetooth settings.
- Close games or remapping tools that may hold exclusive access.
- Try another cable, port, connection mode, or current browser.
Plain answers
Frequently asked questions
Why do I need to press a controller button first?
Many browsers expose a gamepad only after it sends input. Keep this page active and press a physical controller button after connecting.
What does a standard mapping mean?
The browser has mapped common axes and buttons to the Gamepad API standard layout. Non-standard devices still expose raw indices, but named controls may not be available.
Does the raw input viewer upload controller data?
No. Live samples stay in browser memory. A JSON report is built locally only when you choose to download it.
Can this diagnose a broken controller?
It can show browser-observed evidence, but it cannot certify hardware health, inspect firmware, or isolate every driver and operating-system effect.