What the report includes
A report can include the controller name, browser support, user agent, gamepad index, mapping, button count, axis count, vibration exposure, drift sample, suggested deadzone, trigger peaks, microphone status, and a diagnostic disclaimer.
The report is most useful when paired with a focused test. Run drift, deadzone, mapping, polling rate, or vibration checks first, then copy or download the report with the result still visible.
- Copy Summary for quick messages.
- Download JSON for structured troubleshooting notes.
- Download CSV for spreadsheet-friendly records.
- Print Report for repair counters or buyer checklists.
- Save to Local History for the most recent 10 reports on this device.
Privacy boundary for reports
Reports are generated locally. The site does not upload controller input, raw axis arrays, microphone audio, or report contents. If you clear browser data, local history can disappear.
Browser and hardware limits
Gamepad API support, haptic feedback, MediaRecorder, and WebHID are exposed differently across Chrome, Edge, Firefox, Safari, Linux, mobile browsers, USB, Bluetooth, and third-party drivers. For Controller Test Report, treat that limit as part of controller test report guidance rather than as a separate verdict.
A missing feature in the browser does not prove that the controller is damaged. Use the live readings as diagnostic hints and compare results across connection methods when possible. On this Controller Test Report page, compare that note with the live module that matches the article steps, the browser readings they depend on, and the practical decision the reader needs to make.
Controller test report evidence
A controller test report is strongest when it describes the conditions behind the reading. Include the controller name, connection method, browser, operating system, and the specific symptom. A controller test report that says "right trigger peaks at 0.72 over Bluetooth" is more useful than a report that only says the controller feels bad.
Use the controller test report after a focused test, not before. Run the relevant button, drift, trigger, vibration, or mapping check first, then generate the controller test report once the symptom is visible and repeatable.
- Keep one controller test report per connection method.
- Do not treat a controller test report as a warranty decision.
- Share only the controller test report details you are comfortable sharing.