utility

Device Check

Check cameras, microphones, speakers, displays, input devices, gamepads, and motion sensors from one browser tool.

Local processing

About your filesFiles and content selected in this tool are processed in your browser and are not uploaded to a Browser Kitty backend.

Operation demo See the basic workflow in a short video.

About this tool

Device Check is a browser-based diagnostic tool for cameras, microphones, speakers, displays, keyboards, pointer and touch input, gamepads, and motion sensors on PCs and phones. A guided quick check walks through camera, microphone, and speaker tests before a meeting, while individual panels provide deeper checks for each device.

It visualizes browser-accessible information such as camera resolution and FPS, microphone levels and waveforms, key input, simultaneous touch counts, and gamepad axes. Diagnostics do not require a backend, and only lightweight preferences such as language are stored locally.

Good for

Check camera, microphone, and speakers together just before a web meeting
Test keyboard, touch, pointer, or gamepad input on a new PC or phone
Visually inspect a display for dead pixels, gradients, banding, or motion behavior
Check whether the device and browser expose APIs such as WebGPU, WebCodecs, or motion sensors

What it can do

Key capabilities available in this tool.

Run a guided pre-meeting check for camera, microphone, and speakers
Inspect camera resolution and FPS plus microphone level and waveform
Use full-screen display tests for solid colors, gradients, fine lines, and motion
Inspect keyboard, mouse, pen, and multi-touch input in real time
Check gamepad buttons, analog axes, and vibration on supported devices
Review browser support for APIs such as WebGL, WebGPU, and WebCodecs

How to use

Open the tool and start the pre-meeting quick check when you want a guided flow, or jump directly to an individual test.
For camera and microphone tests, review the browser permission prompt and allow access to the device you want to check.
Operate the hardware and confirm that video, audio levels, keys, touch coordinates, or gamepad axes respond as expected.
For display tests, choose a pattern and use full-screen mode to inspect colors, gradients, fine lines, and motion visually.
Review the device summary and API support table when you need to know which browser capabilities are available in the current environment.

Supported

Tests cover cameras, microphones, speakers, displays, keyboards, mouse/pen/touch input, gamepads, and device orientation or acceleration where exposed by the browser.
Display patterns include solid colors, gradients, 16-step grayscale, checkerboards, 1-pixel lines, RGB gradients, burn-in checks, and motion tests.
The tool targets modern Chromium-based browsers, Firefox, and Safari. Available checks vary with the operating system, hardware, and browser API support.
Some APIs such as camera, microphone, full-screen, and motion access require a secure HTTPS context and explicit user permission.

Limitations and notes

Browser APIs cannot conclusively diagnose operating-system driver problems or physical hardware failure.
If camera, microphone, or sensor permission is denied, a working device may appear unavailable.
The browser cannot automatically determine whether you physically heard the speaker test, so listening is a manual check.
Display tests are visual checks, not professional calibration performed with a colorimeter.
Gamepad vibration and motion API support vary by browser, operating system, controller, and connection method.
When opened directly from file://, features that require a secure context may be unavailable.

Frequently asked questions

Are camera or microphone data sent to a server?

No. Camera video, microphone input, key events, sensor values, and other diagnostics are processed locally and are not sent to Browser Kitty.

What should I check before a web meeting?

Use the pre-meeting quick check to test the camera, microphone, and speakers in sequence. Individual tests provide additional details such as resolution, input level, and left/right output.

Can it automatically detect dead pixels or display faults?

It can show full-screen solid colors, gradients, fine lines, and motion patterns to make visual inspection easier, but it does not automatically diagnose display faults.

Can I use it without an internet connection?

The app itself has no runtime external libraries or API calls. However, some camera or motion features require a secure context and may not work when the HTML is opened via file://.

Offline version and source code

The diagnostic UI, test sounds, and display patterns run from a single HTML file with no runtime network communication. Some device APIs still require a secure HTTPS context, so the set of available tests may be smaller when opened offline from file://.

View source on GitHub