X-ray your device

Microphone, camera, keyboard, display and GPU checked in one click, right here in your browser. One card tells you what works and what does not.

Every test runs in your browser. Nothing leaves your machine. How to verify that.

Asks once for mic and camera. You can skip any step. About ten seconds.
XRAY Device report
Ready

Six checks, one card

Nothing has run yet. Results appear as soon as they exist.

  1. Microphone input level, device name
  2. Camera resolution, frame rate, device name
  3. Keyboard one key press to confirm
  4. Display resolution, refresh rate, gamut, touch
  5. GPU graphics chip as reported to WebGL
  6. Browser browser, OS, secure context
devicexray.com 100% client-side

Test one thing at a time

Each tool has its own page with the full instrument, deeper readouts, and step-by-step fixes for every browser and OS.

  1. MIC Mic test See your microphone level live, then record and play back a few seconds.
  2. CAM Webcam test Live camera preview with resolution and frame rate, mirror toggle and a local snapshot.
  3. KEYS Keyboard test Press keys to light them up, find dead keys, and count how many register at once.

How the Device X-Ray works

Your browser already has the instruments. The X-Ray just runs them in order and puts the readings on one card. Every check happens in this tab: no upload, no account, no download.

What it checks

  • Microphone. The page asks for the mic once, opens the stream and listens for a few seconds through the Web Audio API. If your voice crosses the noise floor, the row passes and shows the peak level in dBFS. If the mic opens but stays silent, that is a different problem from a blocked mic, so the card says which one you have.
  • Camera. The video stream is opened at the highest resolution the device offers, frames are counted for a second, and the average brightness is sampled so a closed privacy shutter shows up as "black frames" rather than a false pass.
  • Keyboard. One key press, any key. It confirms the keyboard reaches the browser and records the key and code. For a full dead-key hunt use the keyboard test.
  • Display. Physical resolution (CSS pixels times device pixel ratio), a refresh rate estimate from frame timing, colour gamut, HDR support and touch points.
  • GPU. The renderer string WebGL reports. Chrome and Edge give the real chip; Safari and Firefox hide it on purpose, and the card says so instead of guessing.
  • Browser. Browser, version and operating system, plus whether the page is on a secure connection.

What it deliberately does not do

It does not keep anything. Audio and video are analysed in memory and released the moment the check ends; the browser's own recording indicator goes off with it. The report image is drawn on a canvas in your browser and saved straight to your device. There is no server that could receive it. The privacy page explains how you can verify that yourself.

When to run it

Before a call that matters, after an OS update, on a new or borrowed laptop, or when someone says "we can't hear you" and you want to know in ten seconds whether it is you or them. If a row fails, the "Fix it" link takes you to the matching tool page, which walks through the fix for your exact browser and operating system.