How to Test Your Webcam and Mic Before a Call

Nothing wastes the first five minutes of a meeting quite like "I don't think we can hear you." A quick check beforehand catches the handful of faults that cause almost every call disaster, and it takes about two minutes. Here's a practical pre-call routine, in the order that surfaces problems fastest, using tools that run right in your browser so there's nothing to install.

Start with the camera, because it's the fastest tell

Open the webcam test and press start. If you can see yourself, three things are already confirmed at once: the camera is connected, your browser has permission, and no other app is hogging the device. That last point matters more than people expect — a camera can only be used by one application at a time, so if you left a previous Zoom or Teams call running in the background, your next app will find the camera "busy" and show a black rectangle. Seeing your own live preview rules that out immediately.

While the preview is up, glance at the resolution readout. Many laptop cameras negotiate a lower resolution in dim rooms to keep the image bright, so if you look soft or grainy, the fix is usually light rather than hardware. Face a window or put a lamp behind your screen, not behind you, and the camera will often step back up to a sharper mode on its own. Check the framing too: the classic "up the nostrils" laptop angle disappears if you raise the machine a few inches onto a stack of books so the lens sits near eye level.

Then confirm the microphone is actually capturing you

A camera problem is obvious the instant it happens; a microphone problem is invisible until someone tells you they can't hear you. That's why the mic deserves a deliberate check. Open the microphone test, allow access, and talk at your normal speaking volume. The level meter should move clearly and the waveform should react to your voice. If the meter stays flat, the single most common cause is that the wrong input device is selected — laptops love to default to a built-in mic even when you've got a headset plugged in. Switch devices in the dropdown until the one you actually intend to use is the one that responds.

Watch how far the meter travels, not just whether it moves. If normal speech barely nudges it, you'll come across as faint and distant, and the other side will keep asking you to repeat yourself; move the mic closer or raise the input gain in your operating system. If it slams to the top and stays there, you're likely clipping into distortion, which sounds harsh and crackly — back the gain off or pull the mic slightly away from your mouth. A good target is a meter that lives in the middle and peaks toward the top only on your loudest words.

Don't forget the speakers — you need to hear them, too

People test their mic and camera and forget that a call is a two-way conversation. If you can't hear the other participants, the meeting stalls just as badly. Run the speaker test and play a tone through the left, then the right channel. This catches a surprisingly common problem: one earbud that has gone silent, or a headset plugged in just far enough to connect but not seat properly, so audio comes through only one side. It also verifies that the right output device is active — plugging in headphones after joining a call sometimes leaves the audio routed to the laptop speakers, or vice versa.

One extra habit pays off here: use headphones or earbuds rather than open speakers. When the other side's audio comes out of speakers, your microphone picks it back up and sends it around again, which is what causes the echo and howling feedback everyone dreads on group calls. Headphones break that loop entirely, so if you have a pair, testing and then wearing them is the single easiest way to make yourself sound clean to everyone else — no amount of software echo cancellation is as reliable as simply not letting the speaker sound reach the mic.

The five faults this routine catches

Run through those three tools and you've pre-empted almost every real-world call failure:

Permission not granted — the app never gets the camera or mic because the browser or operating system is still blocking it. The tests force the permission prompt early, while you have time to fix it.
Device busy — a previous call or a background app is holding the camera or mic. A black preview or dead meter reveals it before your meeting does.
Wrong device selected — audio is coming from or going to a device you didn't intend. The dropdowns let you pick the right one and confirm it responds.
Level problems — you're too quiet, or clipping into distortion. The meter shows you exactly where you sit.
One-sided or muted output — a dead channel or misrouted output that leaves you unable to hear others.

A repeatable 90-second checklist

Once you've done it a couple of times, the whole routine compresses into a habit you can run right before you click "join": open the webcam test and confirm you can see yourself and you're well lit; open the mic test and speak to confirm the meter moves on the device you'll actually use; run the speaker test's left and right tones to confirm you'll hear everyone. If all three pass, you can join with confidence instead of crossing your fingers.