Web meetings often expose problems only after the call has started: the camera does not appear, the microphone shows no input, or the speakers stay silent. Checking whether the browser can access each device first makes it easier to separate browser and permission issues from meeting-app settings.
This guide walks through camera, microphone, and speaker checks in order, with optional checks for details such as resolution and input level. Browser diagnostics cannot conclusively identify physical hardware faults or operating-system driver problems.
Start with browser permissions
Pages that use cameras and microphones require browser permission. If access is denied, a working device can still appear unavailable. When a test does not respond, review the site's camera and microphone permissions near the address bar before assuming the hardware is faulty.
On a PC with multiple cameras or microphones, also confirm that the intended device is selected. A built-in microphone and a USB headset can both be present, and choosing the wrong input may look like a hardware problem.
Check more than whether the camera simply appears
For the camera, first confirm that the preview appears and remains stable. Then check whether resolution and frame rate are reasonable so that an unexpectedly low-quality capture does not go unnoticed.
Place the computer or phone where it will be during the actual meeting and also check lighting, framing, and whether the background contains anything you do not want to show.
Check microphone response with normal speech
Speak at your normal conversation volume and watch whether the microphone level and waveform respond. A signal that stays near zero suggests checking the selected input or permission, while a level that immediately stays near maximum may indicate excessive input gain.
Noise floor and channel information can be useful, but the practical goal is stable capture of normal speech. Test in conditions that resemble the meeting instead of optimizing only for diagnostic numbers.
Verify speakers by actually listening
Play center, left, and right test sounds and confirm that they come from the output you intend to use. With Bluetooth headphones or an external display connected, the operating system may be routing audio somewhere unexpected.
A browser cannot determine whether you physically heard the sound. Do not stop when the playback control moves; listen for usable volume and correct left/right output yourself.
Step by step
- Open Device Check and start the pre-meeting quick check.
- Allow camera access and review the preview, orientation, resolution, and frame rate.
- Allow microphone access, speak at a normal volume, and confirm that the level and waveform respond.
- Play the center, left, and right speaker test sounds and confirm that you hear them from the intended output.
- If needed, move to individual tests for the keyboard, display, browser API support, or other hardware.
Device Check
Check cameras, microphones, speakers, displays, input devices, gamepads, and motion sensors from one browser tool.
Tips and limitations
- Run the check with the same headset, external camera, and other devices you plan to use in the meeting.
- Bluetooth reconnection can change input or output routing, so a final check shortly before the meeting is useful.
- If a test fails, check browser permissions, operating-system input/output routing, and another browser before concluding that the hardware is broken.
Frequently asked questions
Are camera or microphone data sent to a server?
No. Device Check processes camera video, microphone input, key events, sensor values, and other diagnostic data locally and does not send them to Browser Kitty servers.
If the camera test fails, is the camera broken?
Not necessarily. Denied browser permission, another application using the device, operating-system settings, or the wrong selected camera can also make it unavailable.
Does this check settings inside Zoom, Teams, or other meeting apps?
No. Device Check verifies device access from the browser. Camera, microphone, and speaker selections that are specific to a meeting application should also be checked inside that application.
Can I use it on a phone?
Yes. It supports phones, although availability of gamepad, motion, display, and other APIs varies by device and browser.