How to use the device test

The device test shows what your browser sees from your gear: controller, mouse, keyboard, headphones or speakers, and microphone. Use it to check a new or…

The device test shows what your browser sees from your gear: controller, mouse, keyboard, headphones or speakers, and microphone. Use it to check a new or second-hand device, find a button that has stopped working, look for stick drift, check left and right audio, or hear how your mic sounds. Everything runs in your browser. Nothing is sent or saved, and you don't need an account.

Picking a device

The tabs at the top of the page switch between Controller, Mouse, Keyboard, Audio, Mic and Other. Each tab has its own address, so you can bookmark or share one, for example /controller?device=mouse. Leaving a tab stops everything it was doing, including the microphone.

Controller: connecting it

Plug the controller in with a cable or pair it over Bluetooth, then press any button. Browsers hide controllers from a page until you press something, so the tab shows "No controller detected" until you do. If several controllers are connected, a menu lets you pick which one to test, or use the Other tab to see them all.

Once it's connected, the top card shows the controller's name, its layout, how many buttons it reports, and how many updates per second it is sending.

Shatir recognises PlayStation controllers from the DualShock 3 to the DualSense and DualSense Edge, Xbox controllers from the Xbox 360 to the Series X|S and the Elite pads, and the Switch Pro Controller. On Windows, many Xbox-style pads connect through XInput, which hides the exact model, so the page just says "Xbox controller (XInput)".

Controller: buttons, sticks and rumble

Press every button once. Each one lights up on the diagram while you hold it and stays marked as tested afterwards. The counter shows how many you have confirmed and changes to "All buttons working" when every button has responded. If a button never lights up, try it a few more times with a firm press. If it still doesn't register, the problem is the button or the connection, not the game you play.

Layout tells you whether the browser understands your controller. Standard means button positions on the diagram are correct. Non-standard means the browser doesn't know this controller, so the diagram may not match, but the raw list still shows which buttons respond.

Each stick has a circle with a dot that follows it, plus its exact X and Y values. Move each stick slowly in a full circle: the dot should reach the edge in every direction and come back to the centre when you let go. If a stick sits slightly off-centre for more than a second and a half without being moved, the label under it changes to "Possible stick drift". A tiny reading near zero is normal on almost every controller; games ignore it with a deadzone.

Test rumble makes the controller vibrate. Not every browser can control vibration from a web page. If yours can't, the page says so, and it doesn't mean your rumble motors are broken.

Mouse

Everything happens inside the dashed box. The right-click menu and the back and forward buttons' page navigation are switched off inside the box only, so you can test them safely.

The polling rate is an estimate. Browsers can cap, batch or round the timing of movement events, so the page may see fewer updates than your mouse sends. If the browser rounds times too much (some privacy settings do), the page says it can't measure rather than guess. Set the real rate in your mouse's own software.

Keyboard

Click the on-screen keyboard (or Tab to it) to start. While it's active, held keys light up and keys you've tested stay green, and keys don't scroll the page or trigger shortcuts. Press Esc or Tab to leave the test at any time. Phones show the main block; wider screens add the arrow and navigation keys and the number pad.

Keys are matched by their position, not the letter they type, so UK, German, French and other layouts test fine. Keys that aren't on the drawing (such as the extra key next to left Shift on European keyboards) appear in a list below it. The Last key card shows the code and character of the last key you pressed.

Rollover is how many keys your keyboard can report at once. Hold several keys together, the way you would in a game: W, A, S and D, then Space and Shift. The test shows how many are held now and the most it has seen at once. If a key you're holding doesn't light up, the keyboard dropped it. That's called ghosting. Many office keyboards only handle 2 to 6 keys at once, or fewer in some combinations; gaming keyboards usually advertise N-key rollover.

Some keys never reach a web page. The Fn key is handled inside the keyboard, the Windows key and media keys are often taken by the system, and shortcuts like Alt+Tab or Ctrl+W go to the system or browser first. That isn't a fault in your keyboard.

Headphones and speakers

Set your volume low, then press Left, Both or Right. Each plays three short beeps on that side only (Both plays them in the middle). The page tells you where you should hear them. Sound only starts when you press a button.

The volume slider sets how loud the test beeps are, and the meter shows the level the page is sending. If the meter moves but you hear nothing, check the system volume, that the browser tab isn't muted, and that the right output device is selected. The page always plays through your system's default output.

Microphone

A page can't hear your microphone without permission, so the browser asks when you press Start mic test, not before. The live meter shows your input level and says whether it's silent, quiet, good or too loud. Talk at your normal volume: speech should sit in the good range.

Record 5 seconds records a short clip you can play back straight away, so you hear yourself the way others do. The clip stays in your browser's memory and is gone when you leave the page. Nothing is uploaded or saved. Stop switches the microphone off; so does leaving the tab or the page.

Once access is allowed, the card also shows your microphone's name and whether noise suppression, echo cancellation and automatic gain are on, and a menu lets you switch between microphones if you have more than one.

Other devices

The Other tab lists every controller slot the browser reports, with each pad's name, layout, number of buttons and axes, and a small live view. Test this controller opens it on the Controller tab.

It also explains what a browser can and can't see on this device. Browsers can't list your mice or keyboards, read a mouse's DPI, or see a controller's battery. Drawing tablets and pens act as a pointer (the Mouse tab shows "pen"). WebHID and WebUSB can talk to some devices directly, but only after you pick the device in a browser prompt and only in Chromium browsers; the device test doesn't use them. Webcams aren't tested here.

What to do with the results

Run the test again after any fix so you can compare.

Questions

Why does it say no controller detected?

Press a button on the controller. Browsers only reveal a controller after a button press on the page. If it still doesn't appear, reconnect it or try a different USB port or browser.

Is the mouse polling rate exact?

No, it's an estimate of the movement updates your browser passes to the page. Browsers can cap or batch them, so the real rate can be higher. Your mouse's own software shows the setting.

Is my microphone recording saved anywhere?

No. The 5-second clip stays in your browser's memory for playback and is gone when you leave the page. Nothing is uploaded.

Does it work on a phone?

The audio and microphone tests work on phones. Controllers work if your phone's browser supports them and the controller is paired with the phone. Mouse and keyboard tests need a mouse or keyboard connected to the phone.

Can this fix stick drift or a double-clicking mouse?

No. It only shows you whether the problem is there. A larger deadzone hides mild stick drift, and a worn mouse switch needs a repair or replacement.

Open the trainer