Connect your controller, focus this page and press a button. The tester displays the devices your browser exposes, including virtual controllers. Use the checks below to separate connection issues from game mappings.
Test your controller
Live browser input
Connect. Press. Check.
Connect a controller and press a button while this page is focused.
Buttons
Axes
Readings stay in this page. Export omits the controller identifier. This is a snapshot, not a hardware certification or latency measurement.
Run a useful controller test
- Connect by USB or pair in your operating system. Keep the browser tab focused and press a controller button to make the device available.
- Choose the controller in the list. If a mapper creates a virtual device, the list can contain more than one entry for the same physical pad.
- Press and release each button. Values should rise when actuated and return when released. Standard-layout labels are shown only when the browser reports a standard mapping.
- Rotate both sticks slowly, then release them. Observe the signed axis values. For standard layouts, the first four axes normally represent the two sticks.
- Squeeze both triggers through their travel. In the standard mapping, L2/LT and R2/RT are buttons 6 and 7 with analog values. Other mappings may differ.
- Use the vibration button only if enabled. It sends a short ordinary rumble request, not adaptive-trigger resistance. Download a snapshot if you want to compare a later test.
Understand what the readings mean
| Reading | What it tells you | What it cannot prove |
|---|---|---|
| Button / axis values | The browser’s current view of input | That an emulator or game is bound to the same device. |
| Mapping: standard | The browser recognizes a standard control arrangement | That all extra buttons, touchpad or motion functions are exposed. |
| Small resting stick offset | The current value reaching this page | A universal pass/fail result or the correct deadzone for every game. |
| Vibration accepted | The browser accepted the output request | That you physically felt it or that adaptive triggers work. |
The page deliberately does not invent battery level, connection type, polling rate or end-to-end latency. Browser sampling depends on page scheduling and is not a hardware timing measurement.
If your controller is missing
- Press a button with this tab in focus. Reconnect the device and try a known data cable or direct USB port.
- Check the operating system’s device settings. If the controller is not visible there, investigate its connection before changing the game.
- Inspect HidHide and remapping software. A hidden physical controller may be unavailable to the browser while its virtual counterpart is visible.
- Test one input path at a time. Make a note of the device label and mapping before comparing results.
- Try another supported browser if the API is unavailable or blocked. Embedded pages may need gamepad permission from their host.
If input works here but not in Nexus, it does not automatically mean Nexus settings are wrong: the browser may be reading a controller protocol that Nexus does not support. If input works in Nexus but not a game, inspect the virtual output, game bindings and duplicate-input settings. Start with a backed-up test profile instead of resetting everything.
Continue with the right diagnostic
Use Nexus troubleshooting for app and virtual-output problems, supported controllers for physical device compatibility, or Controller Tester for a dedicated testing workspace. For DualSense or Edge resistance, use Nexus Controller Setup or Trigger Lab: browser rumble is a different test.
Common questions
The tester code processes input in the page and makes no network request with those readings. The optional JSON snapshot is downloaded locally and excludes the controller identifier.
A remapper can expose a virtual device alongside the physical pad. Select the one you intend to test.
No. Its optional vibration test requests ordinary rumble. Use Nexus’s local trigger test for DualSense or Edge resistance.
Official sources
Use the project or manufacturer’s current documentation for downloads, requirements and model-specific details.