Webcam Tester: Check Camera, Mic, Resolution, and FPS in Your Browser

A black preview in Zoom, a silent mic in Google Meet, or a 720p stream when you expected 1080p usually is not the meeting app’s fault — it is the device, the permission, or the stream the browser actually opened. The Webcam & Microphone Tester runs entirely in your browser with the MediaDevices getUserMedia API so you can confirm hardware before you join.

Open the page, allow camera and microphone access, and you get a live HD preview, the camera’s reported resolution and aspect ratio, a measured frame rate (not just the number in the spec sheet), a real-time audio level meter with peak hold, and a list of every camera, microphone, and speaker the browser can see. Nothing is recorded or uploaded.

Use it as a 20-second pre-call checklist, a USB webcam smoke test, or a quick way to see whether the browser is using the laptop’s built-in camera instead of the one on your monitor.

Why Use Webcam & Microphone Tester?

• Prove the hardware before the call. A live preview and a moving audio bar beat “it worked yesterday.”
• See delivered resolution, not marketing copy. The tool reads MediaTrackSettings so you know the width, height, and aspect ratio of the stream you actually got.
• Measure real FPS. Requested frame rate and measured FPS can differ. The tester uses requestVideoFrameCallback when available so you see frames that actually arrived.
• Diagnose the microphone without recording. Speak, watch the level bar, reset the peak, and confirm the mic is not muted at the OS or hardware level.
• List every media device. After permission, enumerateDevices() shows cameras, mics, and speakers with labels — useful when Meet picked the wrong input.
• Stay private. Video and audio never leave the browser. There is no server-side capture, account, or install.

Key Features

• Independent start buttons let you isolate a black camera from a dead mic instead of debugging both at once.
• Peak hold catches a single loud syllable so you are not staring at a bouncing bar.
• Unsupported browsers get a clear message instead of a silent failure when navigator.mediaDevices.getUserMedia is missing.

How to Use

1. Open the Webcam & Microphone Tester and click Test Camera + Mic, or Camera Only / Mic Only if you want a narrower check.
2. When the browser permission prompt appears, click Allow. If you previously blocked the site, use the address-bar camera/mic icon (or site settings) and retry.
3. Watch the live preview. Confirm the picture is the camera you expect — not a cover, not the IR Windows Hello camera, not a virtual background plugin.
4. Read the camera info card: width × height, aspect ratio, requested FPS vs measured FPS, facing mode (user / environment when reported), and a short device ID.
5. Speak into the microphone. The level bar should move; peak should rise. Click Reset Peak and speak again if you want a clean measurement. Stop the stream when you are done.

Understanding Camera and Mic Streams in the Browser

Browsers do not “open the webcam” as a generic file. They ask the user for permission, then create a MediaStream with video and/or audio tracks. Each track has settings that describe the negotiated format.

Resolution vs. what you asked for. Apps often request 1280×720 or 1920×1080. Drivers and the OS may downscale, pick a different camera, or fall back to a default. If the tester shows 640×480, the meeting app will look soft until you fix OS privacy settings, USB bandwidth, or the selected device.

Requested FPS vs. measured FPS. MediaTrackSettings.frameRate is what the track claims. The tester’s measured FPS counts actual video frames. USB 2.0 cameras, heavy CPU load, and power-saving modes often deliver 15–24 FPS even when 30 is requested. That is the number that matters for live streaming.

Facing mode. On phones, user is the selfie camera and environment is the rear camera. Laptops often omit facing mode or report user. If you expected a USB camera and still see user plus a tiny resolution, the browser may still be on the built-in webcam.

Audio levels are not dB SPL. The meter is a normalised analyser value (0–100%) from AudioContext, not a calibrated sound-pressure reading. Use it to confirm the mic is live and not clipping (the bar turns warning/destructive colors at high levels). For environmental noise in dB-like terms, pair this with a dedicated meter tool rather than treating the percentage as a lab measurement.

Permissions and labels. Until you grant access, device labels are often blank for privacy. After getUserMedia succeeds, enumerateDevices() fills in names so you can match “HD Pro Webcam” vs “MacBook Camera.”

HTTPS and support. getUserMedia requires a secure context (HTTPS or localhost). Locked-down enterprise browsers, missing camera drivers, and “block all cameras” OS toggles will still fail — the tester surfaces that as an error instead of a black box with no explanation.

Practical Use Cases

Pre-call check for Zoom, Teams, Meet, or Webex

Sixty seconds before a client meeting, start camera + mic. Confirm you are not wearing a lens cap, the lighting is usable, and the audio bar moves when you say “testing 1-2-3.” If measured FPS is stuck in the teens, close other apps that hog the camera (Slack huddles, browser tabs already capturing) before you join.

New USB webcam or headset

Plug in the device, grant permission, and check the device list. If the new camera never appears, the problem is USB, hub power, or OS permission — not the conferencing app. If it appears but the preview is black, try camera-only, another USB port, or disabling exclusive-mode apps (Windows Camera, OBS occupying the device).

Podcast and stream setup

Mic-only mode is enough to verify the interface or USB mic is the one the browser hears. Watch peak while you speak at normal volume; if the bar barely moves, raise input gain in the OS. If it pegs red on every word, lower gain before you record. Then switch camera-only to confirm the capture card or webcam can hold the FPS you need for the stream.

Remote IT and “my camera is black”

Have the user open the tester and read back: permission error vs. stream started, resolution, measured FPS, and which device label is active. That splits “denied permission,” “wrong device,” and “camera hardware/driver” faster than walking through Zoom’s settings screens.

Best Practices

• Grant permission once, then re-test after plugging hardware so labels populate and the new device can be selected at the OS level.
• Compare requested FPS with measured FPS under the same lighting and USB setup you will use live.
• Test camera and mic separately when something fails; mixed start can hide which track never arrived.
• Reset peak after adjusting gain so you are not judging a leftover shout.
• Close other apps that hold the camera (OBS, Teams, browser tabs) — many drivers allow only one exclusive client.
• Do not treat this as a recording studio. The page does not save video or audio; that is the point. Use it to validate, then open your real capture app.

Ready to check the hardware instead of guessing in the meeting lobby? Open the Webcam & Microphone Tester, allow access, and confirm preview, FPS, and mic level in one pass.

Related Tools You Might Like:

• USB Device Info Viewer — inspect connected USB devices when a webcam never shows up.
• Gamepad Tester — another in-browser hardware check for controllers and analog sticks.
• Decibel Meter — a closer look at microphone input levels when you need more than a 0–100% bar.

Happy testing — and may your next call start with a picture and a voice.