Your keyboard, mouse, mic or webcam is not responding
Four causes produce one identical failure on screen. This is the order that tells them apart with the fewest steps.
Before a call or a match, the useful question is not "is my microphone broken" but "which of the four layers is blocking it". A browser test cannot answer that on its own — ours catches every failure into a single message and does not guess the cause, because guessing wrong sends you to buy hardware you did not need. What follows is the order that eliminates the cheapest explanations first.
1. The permission, not the cable
A denied camera or microphone prompt looks exactly like dead hardware: no image, no level, no error you can act on. Browsers remember the refusal per site, so the prompt never comes back on its own and every later attempt fails silently.
Check the padlock in the address bar before anything else. If access is blocked there, no test on any site will work, and nothing about your device is wrong.
2. Another program is holding the device
Cameras and microphones are commonly claimed exclusively. A meeting window left open in the background keeps the camera for itself, and the next page that asks gets nothing — again with no explanation.
Close the other application entirely rather than just its window. Our own page releases the device when you leave it, so tabs of ours are not the thing holding your camera; other software may keep it until the process ends.
3. If the wrong character appears, the keyboard is fine
This is the single split that saves the most time. A key that produces the wrong letter is a layout mismatch, not a hardware fault — the switch under your finger reported itself correctly and the operating system translated it with a different map.
The keyboard test shows the label and the physical position side by side precisely so you can tell those apart. Same position, wrong label means change the layout. No reaction at all in either column is the case that points at the hardware.
4. Two numbers that look absolute and are not
The microphone bar is a scaled loudness figure, not a decibel reading: it saturates well before the signal is actually clipping, so a bar pinned at one hundred does not prove distortion, and a bar at forty does not prove your microphone is quiet.
The mouse readout has the same caveat in the other direction. Coordinates are reported in the page's own pixels relative to the test area, which is not the same unit your mouse counts in — a page cannot read your sensor's resolution, and any site claiming to measure it is inferring, not reading.
5. The order, condensed
Padlock first, other applications second, layout third, hardware last. Three of the four cost nothing and take seconds, and they account for most of the failures people bring to a peripheral test.
If all four tests still show nothing after that pass, the problem is below the browser — a driver, a port, or the device itself — and no page in any browser will tell you more than that.
Tools in this guide
- Peripherals TestTest keyboard, mouse, microphone, and webcam in the browser.
- Keyboard TesterTest every key online — live key and code display in your browser.
- Mouse TesterTest left, right, middle click and scroll wheel online.
- Microphone TestCheck your mic level in the browser — audio never leaves your device.
- Webcam TestPreview your camera in the browser — local only, no upload.