EIGHT FOCUSED TESTS · LOCAL PROCESSING

Controller Testing Tools

Choose the focused test that matches what you need to inspect. Input views are read-only and use only data and capabilities exposed by the browser. Vibration Test sends a finite actuator effect only after you explicitly start it; it does not change controller settings, drivers, or firmware.

Browse the catalog

Related tools by measurement

Input tools

Inspect browser-exposed axes, buttons, and trigger values without changing controller settings.

01input

Raw Input Viewer

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

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.

Geometry tools

Collect center, range, and circularity evidence for sticks and local calibration references.

02geometry

Stick Drift Test

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

08geometry

Controller Calibration

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

Timing tools

Measure intervals and response estimates as observed by this browser, with the scheduling limits kept visible.

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.

Output tools

Try finite vibration effects only when the browser exposes a compatible actuator.

05output

Vibration Test

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

Repeatable workflow

How to use these tools

01
Connect and activate
Attach a USB controller or pair one over Bluetooth, keep the tab active, and press a physical button.
02
Choose one question
Open the focused test that matches the input, geometry, timing, or output evidence you need.
03
Record the conditions
Repeat the test with the same browser and connection mode, then export a local report only if you want to share it.

Read the boundary

Measurement limitations

Browser-observed evidence

Results describe values visible through the Gamepad API. They are not a hardware certification and do not prove physical USB polling rate or true end-to-end latency.

Capability-based coverage

Mapping, timestamps, touch values, and vibration support can differ by controller, operating system, browser, and connection mode.

If a tool stays idle

Troubleshooting

Keep this tab active and press a physical controller button.
Confirm the controller is connected in operating-system USB or Bluetooth settings.
Close games or remapping software that may hold exclusive access.
Try a current browser, another cable or port, or a different connection mode.