Initializing, please wait a moment

How to check webcam and microphone before an interview


An interview that starts with 5 minutes of “Can you hear me now?” has already lost its opening. A 5-minute browser-based test the day before catches the three problems that kill interviews: a webcam pointing at the wrong physical device, a microphone input that’s muted or stuck on the wrong source, and lighting that makes you invisible against a bright window. This guide covers the exact sequence to run.


Run the tests the day before — not the hour of

Hardware failures, OS permission prompts, and browser compatibility issues all take time to resolve. Running the tests 24 hours ahead gives you room to install a driver, buy a cheap USB mic, or reroute the call to a different device. Same-day tests turn minor hiccups into “sorry I’m late” messages.


Step 1 — Camera test

Open camera test in the browser you’ll use for the interview (Chrome, Firefox, Edge, or Safari). Click “Allow camera access” when prompted.

  • Verify the preview shows. You should see yourself within 1–2 seconds of granting permission.
  • Check the camera selector. If you have a built-in laptop webcam AND an external USB webcam, the browser picks one (usually the most-recently-connected). Swap in the dropdown to the camera you want.
  • Check resolution. 1280×720 (HD) is the minimum for a professional video call. 1920×1080 (Full HD) is better. Below HD, your face looks soft. If only sub-HD options show, the camera is capped by hardware or a driver issue — swap cameras or restart the browser.
  • Verify frame rate. 30 fps is the target. Below 15 fps, movement looks jerky. Frame-rate drops usually indicate CPU contention (close other apps) or a USB hub limit (connect the webcam directly to a computer port).

Step 2 — Microphone test

Open microphone test. Grant microphone permission. Speak at normal conversational volume.

  • Watch the level meter. Peaks should reach the green/yellow zone (around -12 to -6 dBFS). Peaks stuck at the bottom mean the mic is muted, miswired, or at zero gain; peaks pegged at the top (red) mean the mic is clipping and needs lower gain or a greater distance from your mouth.
  • Check the mic selector. Built-in laptop mic, headset mic, USB desk mic, Bluetooth mic — the browser picks one. Swap until the level meter moves for the device you want.
  • Clap test. A single clap should show a brief spike and then silence. A sustained spike after the clap means echo cancellation is disabled or overwhelmed; keep a headset on for the interview.
  • “Say a sibilant” test. Say “sixty-six seashells” at normal volume. The high-frequency content of /s/ should come through clearly, not muddy. Muddy sibilants mean cheap mic capsule or aggressive codec compression.

Step 3 — Lighting and framing

With the camera test still open, glance at the preview:

  • Face the light source. Natural light from a window in front of you (not behind), or a desk lamp at face height, keeps you visible. Sitting with a bright window behind you silhouettes your face — move the camera or rotate the chair.
  • Framing: eyes in the upper third. Standard video framing puts your eyes 1/3 from the top of the frame, not dead-centre. Tilt the laptop screen or raise the webcam.
  • Background check. Walk behind the camera and look at what’s in-frame over your shoulder. Move clutter out of shot; if you can’t, enable your call software’s background blur.
  • Dress rehearsal. Wear what you’ll wear tomorrow. Thin stripes and busy patterns introduce moiré aliasing on camera; solid mid-tones (dark blue, olive, charcoal) work best.

Step 4 — Test on the call platform

Zoom, Google Meet, Microsoft Teams, and most video-call platforms have a built-in “test meeting” or “test call” feature. Run it to verify:

  • The platform uses the same camera/mic the browser test verified.
  • Audio levels still look good (some platforms apply their own gain).
  • Your internet connection handles the call quality (upload speed of 1 Mbps is the HD floor; 3+ Mbps gives headroom for HD + screen-share).

If the platform requires a desktop client (Zoom, Teams), install and run it the day before. First-run permission prompts, driver installs, and mandatory updates catch many people by surprise on the day of the interview.


Step 5 — Have a backup plan

  • Phone hotspot configured, tested, and battery-charged in case home internet fails.
  • Phone as a secondary call device — note the interview dial-in number; you can rejoin audio-only from the phone if the laptop fails.
  • Wired headset as a mic backup if the built-in mic underperforms. Bluetooth headsets occasionally disconnect mid-call; wired is safer.
  • A friend to text if you need the interview moved because of a hardware failure.

Keyboard test (bonus)

If the interview involves live coding, run a keyboard test too — verify every key you’ll need (Alt, Cmd, Shift, Ctrl, Esc, Enter, Tab) registers cleanly. A stuck modifier key shows up under pressure.


Privacy note

Every test tool on this site runs in-browser. The webcam stream and microphone audio stay on your device; nothing is uploaded or recorded. Close the tab and the access ends.


Related tools


← Back to Device Test Tools

Why trust these tools

  • Ten-plus years of web tooling. The freetoolonline editorial team has shipped browser-based utilities since 2015. The goal has never changed: get you to a working output fast, without an install.
  • Truly in-browser — no upload. Every file-processing tool on this site runs in your browser through modern Web APIs (File, FileReader, Canvas, Web Audio, WebGL, Web Workers). Your photo, PDF, audio, or text never leaves your device.
  • No tracking during tool use. Analytics ends at the page view. The actual input you paste, drop, or capture is never sent to any server and never written to any log.
  • Open-source core components. The processing engines underneath (libheif, libde265, pdf-lib, terser, clean-css, ffmpeg.wasm, and others) are public and audit-able. We link to each one in its tool page's footer.
  • Free, with or without ads. All tools are fully functional without sign-up. The Disable Ads button in the header is always available if you need a distraction-free run.