PS5 controller test. DualSense, on a computer.
Connect a DualSense by USB-C or Bluetooth and the browser reads it through the Gamepad API: buttons, both triggers and both sticks. Chromium recognises it by Sony's vendor number 054c and product 0ce6 (0df2 for the DualSense Edge). This page measures how often its reports arrive, through the Gamepad API and, in Chrome and Edge, through WebHID, and tells you which report the pad is sending, because over Bluetooth that changes the rate.
One check · Five seconds a reading
Asks for: A controller, and a button press. It runs in its own window and nothing leaves this page.
In short
PS5 controller test: the answer first
Yes, a DualSense can be tested on a PC in the browser. Chrome and Edge recognise it by Sony's numbers and read its buttons, triggers and sticks through the Gamepad API; this page also counts its own reports over WebHID and says whether it is sending its USB report, its Bluetooth simple report or its Bluetooth full report.
Reading your result
- Simple reports over Bluetooth
- A DualSense paired over Bluetooth starts on a short report until a host switches it to the full one. The page does not switch it, so a low rate over Bluetooth can be the simple report.
- USB at the browser's cap
- Over USB the Gamepad API reading often sits at Chrome's 4 ms polling. The WebHID reading is the pad's own.
- Edge or standard
- Product 0ce6 is the standard DualSense and 0df2 the DualSense Edge.
What it measures
Measured here, not assumed.
- Identified, by number
- The vendor and product numbers the browser reports: 054c and 0ce6 for the DualSense, 0df2 for the Edge, as Chromium's gamepad_id_list.cc lists them.
- Gamepad API interval
- Every change of Gamepad.timestamp while you roll a stick for five seconds. In Chrome and Edge this is capped at the browser's 4 ms polling, so a DualSense over USB usually reads at the cap.
- WebHID report interval
- The controller's own input reports, counted in Chrome and Edge after you pick it in the browser's list. SDL's driver (SDL_hidapi_ps5.c) uses a sensor rate of 250 Hz over USB for the DualSense and 1000 Hz for the DualSense Edge; the page measures yours rather than assuming it.
- USB, Bluetooth simple or Bluetooth full
- Over USB the pad sends report 0x01 at 64 bytes. Over Bluetooth it starts on a short simple report 0x01 and sends the full report 0x31 only once a host switches it, per SDL's driver. The page names the one it saw and never switches the pad itself.
- Drift at rest
- Each stick read once it has been still for a second; outside our 8 percent dead zone is drift, the gamepad tester's reading.
If it fails
The usual failures, and what fixes each.
- Not seen over Bluetooth
- Hold the Create and PS buttons until the light bar flashes, then pair it from the system's Bluetooth settings. Press a button on the page after it connects.
- Seen, but some buttons are wrong
- A browser that does not recognise the pad maps it by guesswork. Chrome and Edge recognise the DualSense by its numbers; try one of them, or a cable.
- The rate is low over Bluetooth
- The pad may be on its simple report. A game or Steam usually switches it to the full report; until then the simple report's rate is what arrives.
Where a browser stops
What it cannot tell you.
- The touchpad, the motion sensors, the light bar and the adaptive triggers. The Gamepad API's standard layout does not carry them, and this page reads WebHID reports without decoding them.
- Battery level. It sits inside the full report; this page does not decode it, rather than print a figure it has not validated on real pads.
- Input lag, which needs a camera or a photodiode.
- Whether a game supports the DualSense's own features on PC. That is up to the game.
Privacy
Nothing leaves this page.
The camera and microphone are read on this page and stopped as soon as they have been measured. The clip you can play back lives in the browser's memory and is discarded when you leave. The location check discards the position. The internet test sends random bytes to this site and nothing else. The result is stored nowhere unless you ask for it by email, and then only the fact that an email was sent is kept.
Questions
PS5 controller test, answered
- How do I test a PS5 controller on a PC?
- Connect it by USB-C or pair it over Bluetooth, open the test above and press a button. The page shows how it was identified and measures its report interval; the gamepad tester shows every button and both sticks.
- Can a browser read the DualSense touchpad and gyro?
- Not through the Gamepad API's standard layout. WebHID in Chrome and Edge receives the full reports that contain them; this page counts those reports but does not decode them.
- What is the DualSense's polling rate on PC?
- Measure yours with the WebHID reading. SDL's driver works with 250 Hz over USB for the standard DualSense and 1000 Hz for the Edge. Through the Gamepad API in Chrome and Edge, the browser's 4 ms polling caps what you see at 250 Hz.
- Do I need a remapper such as DS4Windows to test a DualSense on a PC?
- Not for this test: Chrome and Edge read the DualSense directly. A remapper can add a second, virtual controller, so close it if two appear.
Read next