How to Test Your Mic, Camera, and Speakers Before a Video Call

“Can you hear me? …Hello?” — the opening line of far too many meetings. The frustrating part is that every one of those minutes is preventable: microphone, camera, speakers, and connection can all be verified in about two minutes, in a browser tab, before anyone else joins. Here's the routine, plus the fixes for what each test can reveal.

Why calls fail even when the hardware is fine

The most common cause of “my mic doesn't work” isn't a broken mic — it's the wrong device being selected. Modern computers juggle several inputs and outputs at once (built-in mic, headset, webcam's mic, Bluetooth earbuds), and the OS or the meeting app picks one for you, not always sensibly. A pre-call test catches this class of problem, which is nearly all of them.

Step 1: microphone (30 seconds)

Open the microphone test, grant access, and speak normally. Two things to check: the device name shown — is it the mic you intend to use, or did the browser grab your webcam's tinny built-in? — and the level meter, which should bounce with your voice and peak around the middle of the range. A flat line means muted hardware, a disconnected headset, or another app holding the mic. A meter that slams to 100% will sound distorted; move the mic back or lower the input gain. Nothing you say is recorded or uploaded — the audio is analyzed entirely in the browser.

Step 2: camera (30 seconds)

The webcam test shows a live preview with the resolution and real frame rate. Beyond “does it work”, use the preview to check what your callers will actually see: light your face from the front (a window behind you turns you into a silhouette), raise the camera to eye level, and wipe the lens — laptop lids collect fingerprints exactly there. If the image is black, close other apps that might hold the camera (a videocall app left running in the background is the usual culprit) and check the physical privacy shutter.

Step 3: speakers or headphones (20 seconds)

Play the left, right, and stereo tones in the speaker test. You're confirming three things: sound comes out at all, it comes out of the right output (not the monitor's awful built-in speakers while your headphones sit silent), and left/right aren't swapped — which matters more than you'd think for spatial audio in meeting apps. If you hear nothing, check the output device in your OS sound settings and the physical volume keys on your headset.

Step 4: connection (30 seconds)

Choppy, robotic audio is rarely the mic — it's the network. The ping & latency test measures the three numbers that matter for real-time calls: latency (under ~100 ms feels natural), jitter (the wobble — high jitter is what makes voices stutter), and packet loss (anything above ~2% means dropped syllables and frozen video). If jitter or loss are high on Wi-Fi, the two fixes that actually work are moving closer to the router or plugging in a cable.

The two-minute pre-call checklist

• Mic: right device selected, meter moves, no clipping.
• Camera: preview on, face lit from the front, lens clean.
• Sound: tones play from the intended output, left/right correct.
• Network: ping steady, jitter low, packet loss ~0%.
• Close the tests before joining — the call needs the mic and camera you just released.

If it works here but not in the meeting app

Then the hardware is fine and the app is the problem — which is genuinely useful to know. Check the app's own input/output device pickers (they override the OS defaults), its permission to use the mic and camera in your OS privacy settings, and whether another app is holding the device. Testing in the browser first turns “something is broken” into “I know exactly which layer is broken” — and that's most of the battle.