01Which controllers work?+
Xbox, PlayStation and generic controllers work when exposed by your system and browser. Use custom mapping if no standard layout is available.
02How do I check stick drift?+
Release the sticks and observe the center offset. Small variations can be normal; compare stability and behavior in games.
03Is anything installed or uploaded?+
No. Inputs are processed locally. Custom mappings are saved in browser storage; downloads are created only when requested.
04Why is my controller missing?+
Check USB or Bluetooth, press several buttons and keep this tab focused. Try closing other controller apps or restarting the browser.
05What do buttons, axes and ms mean?+
Buttons range from 0 to 1, axes from −1 to 1. The timestamp is the API's last update time, not latency or polling rate.
06Can I test multiple controllers?+
Yes. Select a connected controller from the list. Switching resets the button history.
07Does vibration work?+
Only when the controller, connection, system and browser expose a compatible actuator. The test reports whether the command completes.
08Why do axes look unusual?+
Indices, directions and centers can vary across browsers and systems. Raw input is unchanged; create a mapping when needed.
09What is circularity?+
It compares full stick travel with a circle of radius 1. This version shows current position and center offset, without calculating circularity error.
10What about motion sensors?+
Gyroscopes, pose and detailed touchpad data are not uniformly exposed. Only supported buttons, axes and vibration are used.
11How do I reuse my mapping?+
Download the JSON mapping and load it here with the same controller and browser. It is this site's format, not a universal game or emulator configuration.
12Will other hardware tests be added?+
Keyboard, mouse, display, audio and camera tools are planned. Common web APIs cannot read CPU temperature or SSD SMART data.