Google Meet mic and camera test

Google Meet Mic and Camera Test

QUICK ANSWER

Test your mic and camera before a Google Meet call without creating or joining a meeting. Google Meet's own pre-call check — the green room — only appears after you open a meeting link. This page runs the same WebRTC getUserMedia stack Meet uses and confirms your devices in 30 seconds, no signup, nothing uploaded.

  • Runs in your browser
  • Nothing uploaded
  • No signup
  • Free forever
  • Same WebRTC stack as Meet
DEVICE TEST

Check your mic & webcam. In 30 seconds.

No downloads. No account. Grant access once and we’ll tell you what Clipy (or any tool) would see and hear.

Permission required

Camera and microphone access is required. Click below, then allow access in your browser.

Select devices

Access Required

Preview controls

Audio level

Speak into your mic to see the level bar react.

Camera preview

No camera selected

If everything’s working, you’ll see yourself above.

Video analytics

Real FPS
Resolution
Brightness
0%
Luminosity
0%
Saturation
0%
Sharpness
0%
Noise
0%
Color variety
Browser FPS cap

Metrics are estimated locally from the live preview frames. Lighting, browser negotiation, and camera drivers can change them in real time.

Trusted by creators at startups, agencies, and Fortune 500 teams.
Free forever — no signup, no watermark, no length cap.

How it works

  1. 1

    Allow camera and microphone for this page

    Click Allow on the browser permission prompt. Chrome stores permissions per-origin, so granting them here does not change anything for meet.google.com — and if meet.google.com had been blocked previously, this test will still work because it is a different origin.

  2. 2

    Confirm preview + level meter, switch devices as needed

    The live tile is exactly the frame Google Meet would receive; the level bar reads peak amplitude from your selected mic 60 times a second. Use the dropdowns to pick the same camera and microphone you intend to use in Meet — a Logitech webcam, AirPods, a USB condenser — and lock in the right hardware before the call.

  3. 3

    Open meet.google.com and confirm the same devices

    When you open the meeting link, Google Meet shows the green room with its own device dropdowns. Pick the same camera and microphone you tested here. Meet remembers them on the next call, so you only do this once per device.

Hopping between meeting platforms? Test once.

Because Google Meet, Zoom on the web, Microsoft Teams in the browser, and Slack Huddles all share the same OS-level audio and video stack, a working test here is also a working test for the other three. For a platform-agnostic check you can bookmark and run before any call, the camera and mic test works for every platform in one place. If you specifically want platform-flavored troubleshooting, Zoom mic and camera test covers Zoom-specific defaults (muted-on-join, noise suppression) and Microsoft Teams mic and camera test covers Teams' exclusive-mic capture behavior and the desktop-only test-call bot.

Want to skip the meeting entirely?

If the Meet was meant for a 5-minute walkthrough or async update, record it instead. Clipy is a free screen recorder with no watermark and a shareable link — no signup required to send the video. For a voice-only memo, the Voice recorder captures straight to MP3; for a camera-only talking-head clip, the Webcam recorder does that without a Loom signup wall.

Why Google Meet does not have a standalone test page

Google Meet exposes its pre-call check inside the meeting itself: when you open a meeting link, the green room screen has a camera preview, a microphone level bar, and a 'Test speakers' button. Useful — but it only exists after you create or open a meeting, which means committing to a calendar event or generating a throwaway link before you can test anything. This browser tester is the missing standalone page. It uses the same WebRTC getUserMedia API that Google Meet uses, against the same OS-level devices. A working test here predicts a working green room. The only thing it cannot tell you is whether your network can reach Meet — for that, run a real test meeting end-to-end.

Meet's quirks — Chrome WebRTC stack and per-origin permissions

Google Meet leans hard on Chrome's WebRTC implementation and on Chrome's per-origin permission model. If you ever clicked 'Block' on a microphone or camera prompt for meet.google.com, Meet stays silent or dark even when other sites work fine — click the lock icon in the address bar on a Meet tab to re-grant. Bluetooth headsets are a second pain point: most headsets switch from high-quality A2DP music mode to lower-quality HFP/HSP call mode the moment Meet activates the mic, which adds 100–300 ms of latency and changes the tonal character of your voice. For important calls, a wired headset or even the built-in laptop mic in a quiet room beats most consumer Bluetooth audio on Meet.

Same browser test works for Zoom, Teams, and Slack too

Google Meet, Zoom on the web, Microsoft Teams in the browser, and Slack Huddles all read from the operating-system camera and microphone through the same WebRTC stack. A working camera and microphone in this tester predicts a working device in all four — the only way that breaks is if a second app grabs an exclusive hold on the device between the test and the call. Practical workflow: run the tester once at the start of the day, leave the tab closed, then join meetings without re-testing. Re-run only when a new device is plugged in or after an OS update.

Common questions

Why can Google Meet not hear me even though my mic works in other apps?

Four common causes. (1) Chrome blocked microphone access for meet.google.com specifically — click the lock icon in the address bar on a Meet tab and re-grant. (2) macOS or Windows is routing audio to a different default input (a Bluetooth headset that disconnected, a USB mic that came unplugged). (3) Meet is muted at the bottom-toolbar mic icon. (4) Another app like Zoom or OBS is holding the mic exclusively. Quit those, reload Meet, re-check the device dropdown.

Why is my Google Meet camera black or frozen?

Three usual suspects. (1) Another app — Zoom, Teams, Loom, Photo Booth, OBS Virtual Camera — already has the camera open exclusively; Meet gets nothing. (2) Camera permission is blocked at the OS level (macOS: System Settings > Privacy & Security > Camera; Windows: Settings > Privacy > Camera) — Chrome itself must be allowed. (3) A virtual background or filter inside Meet is mid-load and stalled — disable effects via the three-dot menu, then reload.

Can I test mic and camera for Meet without joining a meeting?

Yes — that is exactly what this page is for. Google Meet does not expose a standalone pre-call test page; the green room only appears after you open a meeting link. The browser tester above uses the same getUserMedia API Meet uses, so a working test here predicts a working green room.

Why does Meet sound bad even though my mic test passes?

Two things separate from device health: network and acoustics. Run a quick speed test (Meet wants ~3.2 Mbps up for HD video) and switch to a wired connection if possible. For audio, Bluetooth headsets add 100–300 ms of latency and often downsample to call quality — a wired headset or built-in mic in a quiet room beats most consumer Bluetooth audio on Meet.

Will this work in Chrome, Safari, and Firefox for Google Meet?

The browser test works in Chrome, Edge, Safari 14.1+, and Firefox on macOS, Windows, and Linux. Google Meet itself works best in Chrome and Edge; Safari and Firefox support has improved a lot but still occasionally falls back to limited feature sets. If you can use Chrome or Edge for the Meet call, do.

Does my Workspace admin control mic and camera access?

Indirectly. Workspace admins can disable features inside Meet (recording, captions, breakout rooms) but they cannot block your device. If your camera works in the browser test but Meet shows it as disabled, check the toolbar at the bottom of the Meet window — the camera icon may be toggled off, or the admin policy may require host approval to turn it on.

Why does the level meter move but Meet says I am muted?

Meet has an in-call mute icon at the bottom-toolbar that is independent of the OS mic level. Easy to miss after re-joining or being placed in a waiting room — the strikethrough on the icon is small. Hover and click to unmute.

Is anything recorded or uploaded by this test?

No. The camera feed renders straight from the browser's MediaStream into the preview tile. The mic stream feeds a Web Audio AnalyserNode that reads peak amplitude locally — there is no MediaRecorder, no canvas capture, no upload. Open the browser network tab while the test is running and you will see zero requests on the media stream.

More free tools