DeviceTHE METHOD / TRANSPARENT BY DESIGN
What our tests actually measure.
Useful signals, not empty promises. DeviceDIY uses capabilities already available in your browser to help you check your devices — while being clear about what each result can and cannot tell you.
A browser signal is evidence. Not a hardware certificate.
A successful browser test shows that certain input or output was available to the browser at that moment. It cannot rule out every hardware fault, operating-system issue or application-specific problem.
What each test tells you.
For every category, we explain the useful result and the important limitation — then link directly to the tool.
Camera & microphone
A live preview means your browser has received video from a camera. A moving audio meter means the browser receives microphone input. A local recording lets you listen for noise or distortion.
This does not confirm performance in another application, autofocus quality, or the physical condition of the hardware.
Speakers & headphones
Play short audio tones to confirm that you can hear sound through your chosen output device. Listen for distortion, balance and unwanted noise.
Because sound is judged by you, DeviceDIY cannot measure acoustic volume or verify what you heard.
Keyboard, mouse & touchscreen
See browser-reported key presses, pointer movements, clicks, wheel actions and touch input. These checks help identify missed or unexpected events.
Operating systems and browsers may intercept some key combinations and gestures. A missed event is not conclusive proof of hardware failure.
Screen & dead pixels
Display full-screen solid colours so you can inspect the panel for potentially stuck or dead pixels, uneven colour or visible marks.
The test is visual and manual: dust, reflections, display scaling and overlays can look like faults.
Controllers & refresh rate
Where supported, the Gamepad API reports controller buttons and analogue axes. The frame-timing tool estimates browser animation cadence.
Neither test certifies controller latency, monitor hardware refresh rate or compatibility with every game.
Quick Device Check
Follow a guided flow to preview your camera, observe microphone activity and personally confirm that speaker audio is audible.
It does not certify meeting-app settings, internet stability or end-to-end video call performance.
Your camera. Your microphone. Your control.
Camera and microphone tests request your browser's permission when needed. The testing code in this release processes device streams and input events in your browser and does not upload media recordings to a DeviceDIY server. Hosting providers, browser settings and any analytics introduced during deployment may involve other data processing; review the published privacy notice for details.
Read the privacy policy ↗How to interpret a result
- Allow the relevant browser permission if requested.
- Run the test in an active browser tab, away from unnecessary background activity.
- If something fails, retry with another browser or operating-system diagnostic.
- Use additional hardware checks before making a repair or buying decision.
Built with web standards
These tests use documented browser capabilities. The references below explain relevant APIs and their constraints.