Device Test
Check a keyboard, microphone, webcam or screen in your browser. Every test runs on your own device — nothing is recorded or uploaded.
Click the keyboard or tab to it, then press keys. Esc leaves it again. Nothing you type is stored or sent.
- Held now
- Worked
- Chatter detected
- Not pressed yet
Last key
- key
- —
- code
- —
- location
- —
- repeat
- —
Rollover
0 held · max 0
Hold several keys at once
Chatter
None detected
A key that registers twice within 30 ms is flagged here.
Coverage
0 / 104 keys
0 presses · 0 auto-repeats
Table of contents
The four tests
Keyboard Tester →
Every key on a full-size drawing, with event.key and event.code, how many keys you can hold at once, and a flag for keys that register twice.
Mic Test →
A live level meter in dBFS with a peak marker, frequency bars, the sample rate and channel count, and a short recording you can play back.
Webcam Test →
A mirrored preview, the resolution and frame rate the camera actually delivers, its capabilities, and a snapshot saved straight to your device.
Dead Pixel Test →
Full-screen black, white, red, green, blue, grey and a gradient, stepped through by hand, to find dead, stuck and hot pixels.
How to test your devices online
- 1
Pick a test
Keyboard, microphone, webcam or dead pixel. The keyboard test is open already; each of the others loads only when you open its tab, and each has a dedicated page with more detail.
- 2
Allow access when asked
The microphone and webcam tests need your permission, and the browser only asks when you press Start — never on page load. The keyboard and dead pixel tests need no permission at all.
- 3
Read the result in plain words
Keys light up as they work, the mic meter says whether the level is too quiet, good or clipping, the webcam shows the size and frame rate it actually delivers, and the colour screens tell you what kind of fault to look for.
What stays on your device
A hardware test is a strange thing to send to a server. The keyboard under your hands, the microphone on your desk and the camera above your screen are all attached to the device you are reading this on, and the browser already has everything it needs to check them. So that is where the checking happens.
Nothing captured by these tests leaves the page. Key presses are counted, not logged as text. The microphone is read on every screen refresh to draw the meter, and each reading is thrown away as soon as it is drawn; the optional five- or ten-second recording is a blob in the tab’s memory that disappears when you close it. The webcam picture is shown in a video element and nowhere else, and a snapshot is made by your browser and saved to your own downloads folder.
The camera and microphone are switched off when you stop the test, when you move to another tab on this page, and when the browser tab is hidden. If the light on your camera stays on after that, something else has it open.
When a device is not found
Check the browser’s permission first. In Chrome and Edge, click the icon at the left of the address bar and set Camera or Microphone to Allow. In Firefox, the crossed-out camera or microphone icon in the address bar clears a block. In Safari on a Mac, use Safari → Settings → Websites. Then reload and press Start again.
Then the operating system. Windows has its own switch under Settings → Privacy & security → Camera (and Microphone), including one for desktop apps, which is the one that covers your browser. macOS asks once per app; if you refused, go to System Settings → Privacy & Security and turn your browser back on. Some laptops also have a physical camera shutter or a function key that cuts the camera or microphone in hardware, and no software setting overrides those.
Then other apps. On Windows a camera can usually be open in only one program at a time, so a video call, OBS or the Camera app running in the background makes the test report that the device could not be opened. Close it and try again. If the wrong microphone or camera opens, pick the right one from the device list, which fills in as soon as you have allowed access.
Frequently asked questions
No. The keyboard test reads key events while its area has focus and keeps only counts in the page. The microphone is measured frame by frame and the short test recording lives in your browser's memory until you leave. The camera picture is drawn on the page and a snapshot is saved straight to your downloads. None of it is sent to zeal.tools or anyone else, and you can check that in your browser's network panel.
Because a web page cannot touch either without it, which is exactly as it should be. The prompt only appears when you press Start, and you can revoke the permission at any time from the icon in the address bar. If you refuse, the test explains how to allow it again rather than failing silently.
The microphone, webcam and dead pixel tests do, in current Chrome, Safari and Firefox. iPhone Safari has no full-screen mode for pages, so the dead pixel test fills the window instead. The keyboard tester works with any keyboard connected to a phone or tablet, but an on-screen keyboard does not send physical key codes, so it is not a useful test of one.
The tests turn the device off when the tab is hidden, and when you leave the test. A microphone or camera left running in a background tab is a privacy problem and a battery drain, so the test asks you to press Start again rather than keep it open.
Current versions of Chrome, Edge, Firefox and Safari. A few readouts depend on the browser: measured frame rate needs requestVideoFrameCallback, the camera capability list is not offered by every browser, and some browsers do not report the microphone sample rate, in which case the audio engine's rate is shown.
Every check is of hardware attached to the device in front of you. A server, or an AI agent calling an API, has no keyboard, microphone, camera or screen to test, so there would be nothing to send and nothing true to return.
The Zeal Promise
Non-negotiable, on every tool we ship.
- No sign-up — ever
- No watermarks on any output
- No ads near the download button
- Works fully on mobile
- Privacy-first: processing stays in your browser
- Open source (MIT) — audit it, contribute, self-host
- Zero runtime dependencies in tool logic