Test Camera and Microphone

Before a call, this check tests your camera, microphone, speakers and network connection in one guided pass so you know what works and what doesn't. It uses your browser's built-in WebRTC support end to end - nothing is uploaded, and nothing is recorded anywhere but your own browser tab.

Why use this check

How to run a pre-call check

1. Click Start Pre-Call Check and allow camera and microphone access.
2. Check the camera step: confirm you can see yourself, or say if you can't.
3. Check the microphone step: speak normally, then confirm the level meter picked up your voice.
4. Check the speakers step: listen for the tone on Left, Right and Both, then confirm what you heard.
5. Let the connection step run, then read your summary and copy the diagnostic report if you need it.

Common problems and fixes

• Camera or mic access was blocked: click the camera or microphone icon in your browser's address bar, set it to "Allow", then reload the page and run the check again.
• Camera works but shows a black screen: another app already has the camera open. Close Zoom, Teams, or any other browser tab using the camera, then retry that step.
• Microphone shows no level when you speak: the wrong input device may be selected, or your mic is muted at the hardware level. Pick a different device from the dropdown and check for a mute switch on your headset.
• You can hear the test tone but not your meeting app: this page and your meeting app can use different output devices. Check the output device selected here matches the one selected in your meeting app.
• Sound plays from the wrong device: your computer may still be routing audio to a previous device. Pick the correct one from the dropdown, or change the default output in your operating system's sound settings.
• The connection check shows host-only candidates: this usually means a firewall or restrictive NAT is blocking the kind of connection calls need. Calls may still work through a TURN relay, but direct connections are unlikely - see our guide on setting up a TURN server if you run your own infrastructure.
• Everything passes here but the meeting app still fails: each app holds its own camera, microphone and speaker permissions, separate from your browser's. On macOS, check System Settings > Privacy & Security for that specific app; on Windows, check the app's own device settings.
• It works on Wi-Fi but not on a corporate network: corporate firewalls commonly block the UDP ports WebRTC prefers. Ask your IT team to allow outbound UDP, or use a network that permits a TURN relay.

This is the hub of our device-test cluster - run the webcam test, mic test or speaker test on their own if you only need to check one thing, or browse all Meetrix features. Once your setup checks out, see what the meeting itself is actually costing with the meeting cost calculator, get real download, upload, latency and jitter numbers with the speed test, or line up your talking points in the online teleprompter before you go live. If your connection check came back restricted, Meetrix also does WebRTC consulting and load testing for teams running their own infrastructure - see our guide on setting up a TURN server.