Open source DualSense tester tools on GitHub
Searching GitHub for a DualSense tester turns up drivers, libraries and calibration tools. Here is how to tell them apart.
Real projects and their different roles
The projects below exist, but they are not interchangeable. Follow the repository's own link to its hosted tool and check supported models before connecting.
| Project | Role | Important distinction |
|---|---|---|
| DualShock Calibration GUI | Web calibration tool | Can change device calibration; Edge has special limitations |
| daidr/dualsense-tester | Web tester and Edge profile editor | Buttons, touch, motion, output tests and Edge customization |
| Sense Calibrator | Web testing and calibration | Standard DualSense over USB; not Edge or DualShock 4 |
| Linux hid-playstation | Operating-system driver | Reference for device report layouts |
| SDL | Application library | Developer component, not a ready-to-use web tester |
The three web projects declare MIT licenses. Linux and SDL have their own licenses; inspect the relevant files and notices before reusing code. A repository being open source does not establish safety or complete hardware validation.
Testing does not always mean read only
The name DualSense Tester does not imply that every operation is read only: daidr's project also supports Edge profile customization. Calibration tools may alter working state before a separate permanent-save action. Read the function-specific description, not just the product name.
For ControllerTester, the implementation does not flash firmware or store hardware calibration. The battery tool can send temporary light and rumble commands. The gyro tool currently decodes supported USB input layouts; do not assume that every feature another project lists is implemented here.
How browser access works
The Gamepad API exposes ordinary controller input. WebHID gives compatible pages access to device reports after permission is granted. Initial device selection needs a user gesture; a site may later obtain previously authorized devices without showing the same picker again.
Input reports carry readings; output reports can control effects; feature reports may read information or change device settings. The report category alone does not tell you whether an operation is safe or persistent. The actual command matters.
Connection troubleshooting
- Use a desktop browser with native WebHID support, such as Chrome or Edge. Standard Firefox and Safari do not provide that native interface; third-party extensions are a separate setup.
- If the device is missing or access is denied, close software holding it and reconnect with a data cable.
- On Linux, check the project's hidraw permission instructions. Grant only the required device access.
- Missing Bluetooth motion or charge data may be a simple-report mode or decoder issue. USB is a useful comparison, not a guaranteed fix.
Sources
Repository descriptions, license declarations and this site's implementation checked 26 October 2026. This is not an endorsement based on physical tests.