Skip to main content
Free tool

Google Meet microphone test

Google Meet runs in a browser tab, which means its microphone problems are browser problems. Test here first, then use Meet's own green room and Chrome's site permissions to finish the job.

  • No signup
  • Same audio path as Meet
  • Nothing uploaded

Check your microphone

Your browser will ask for permission. Speak a full sentence at your normal volume — tapping the microphone tells you nothing useful.

Audio is analysed on your device. Nothing is uploaded and nothing is stored.

Why a browser test is the right test for Meet

Google Meet is a web application. On a laptop it runs inside Chrome, Edge, Firefox or Safari and gets its audio through exactly the same browser API this page uses. That makes a browser microphone test unusually informative for Meet: if the tool above works and Meet does not, the difference is in Meet's own device selection or in a permission scoped to meet.google.com, and nowhere else.

That is not true of Zoom or Teams, whose desktop clients talk to the operating system directly and keep their own audio stack. For those, a browser test proves the hardware works and little more. For Meet it proves considerably more than that.

The one exception is the Meet mobile application, which is native and does have its own audio path. Everything below about Chrome permissions applies to the desktop browser only.

Testing your microphone in Meet itself

  1. 1

    Use the green room before joining

    Open the meeting link but do not press Join yet. The screen you land on — Google calls it the green room — shows your camera and a microphone level indicator beside the mute button. Speaking should make it move. This is the check to run when you are already a minute late, because it takes three seconds and needs no settings panel.

  2. 2

    Open the settings from the green room

    Click the gear icon on that same screen, then Audio. The Microphone dropdown shows which input Meet has chosen and a small level meter beside it. Changing the device here applies before you join, so you never enter the meeting on the wrong microphone.

  3. 3

    Run Meet's own check

    In the settings dialog there is an audio and video check that records a short clip and plays it back. It is the same idea as the playback in the tool above, run through Meet's own processing — so it shows you what the meeting will actually hear, noise cancellation included.

  4. 4

    Confirm the permission is granted to meet.google.com

    Browser permissions are per site. Granting the microphone to this page grants it to telvio.app and to nothing else. If Meet never prompts and never hears you, the permission for meet.google.com was denied at some point and the browser is silently honouring that.

  5. 5

    Check you are not muted by the host

    In large meetings a host can mute participants, and in Google Workspace tenants a host can prevent participants from unmuting themselves. Your microphone icon shows your own mute state, not theirs, so the two look the same from your side.

Chrome's permission model, which is where most Meet problems live

Per-site, not per-browser A microphone permission is stored against an origin. meet.google.com, this site and any other page each have their own answer, and a grant to one says nothing about the others.
A denial is remembered If you dismissed or denied the prompt once, Chrome will not ask again for that site. From the page's point of view this is indistinguishable from a broken microphone — no prompt appears and no error is raised.
Restoring it Click the icon at the left of the address bar while on meet.google.com, find Microphone, set it to Allow, then reload the tab. Or go to Settings → Privacy and security → Site settings → Microphone and remove the site from the blocked list.
The operating system layer sits above it On macOS, System Settings → Privacy & Security → Microphone controls whether Chrome itself may use a microphone at all. If Chrome is off there, every site is blocked regardless of its own permission, and Chrome's own settings will still show Allow.
Only one tab at a time, in practice Two tabs can hold the microphone simultaneously, but a device already opened exclusively by another application will not be available to any of them. Closing the tab that ran a microphone test before joining a meeting avoids the whole class of problem.

Meet's noise cancellation and what it removes

Google Meet applies noise cancellation on the way out, which is genuinely good at removing keyboards, fans and street noise. It is available on Google Workspace Business Standard and above, and on personal accounts it is either absent or applied automatically without a control.

Where it is available, the toggle sits in Settings → Audio → Noise cancellation. It is worth knowing that it works by separating what it believes is speech from what it believes is not, and that the judgement is imperfect on a quiet voice. If people report that you cut out on Meet but not elsewhere, turning noise cancellation off is the first thing to try — followed by raising your input level so there is more speech for it to be confident about.

The same processing is why singing, playing an instrument or holding a phone to the microphone rarely works on Meet: the algorithm classifies all of it as noise. There is no musician mode equivalent to Zoom's original sound.

One practical consequence for shared spaces: Meet's noise cancellation is applied per participant, so two people in the same room joining separately with unmuted microphones will each cancel the other's voice as noise while feeding back through the speakers. In a shared room, one device should carry the audio.

Meet on a phone and in Companion mode

The Google Meet mobile application is native, so the browser sections above do not apply. What matters instead is the operating system permission: Settings → Meet → Microphone on iOS, or Settings → Apps → Meet → Permissions on Android.

On iOS, Meet — like every other application — competes for a single audio session. If a phone call arrives during a meeting, iOS takes the session and does not always hand it back cleanly. Force-quitting Meet and rejoining is the reliable fix and takes less time than searching for a setting.

Companion mode is worth knowing about for meetings held in a room. Joining in Companion mode from your laptop gives you chat, hand-raising and screen sharing with your microphone and speaker deliberately off, so the room's own equipment carries the audio and nothing feeds back. If you are in a room with a Meet device and your laptop, this is the mode to use.

Dial-in numbers are the other half of Meet's audio story. Google Workspace meetings can include a phone number participants can call to join by voice, which is useful when somebody's connection cannot carry video. It is a normal telephone call from their side, priced by whatever they use to make it.

When the person you need is not on Meet

Google Meet needs both sides to have a browser, an internet connection and a link. That is most colleagues and very few relatives.

For calls to an ordinary phone number — a landline, a mobile in another country, a business that answers a switchboard — you need something that reaches the telephone network rather than another Meet participant. Telvio does that: calls to landline and mobile numbers in over 200 countries over your existing internet connection, billed by the second, with nothing to install at the other end.

Everything on this page about microphone level, distance and headsets applies unchanged to those calls. What does not apply is noise cancellation: a telephone call carries a narrow band of frequencies and does not run Meet's processing, so a quiet voice in a noisy room is harder to fix. Getting closer to the microphone is the whole technique.

Bottom line

For Google Meet, the fastest microphone check is the green room: open the meeting link, do not join, and watch the level indicator beside the mute button while you speak. The gear icon on the same screen lets you change the input device before you enter.

Because Meet runs in the browser, a browser microphone test is a genuine test of Meet's audio path. If this page hears you and Meet does not, the microphone permission for meet.google.com was denied at some point, or Meet has selected a different input — both are fixed from the address bar and the gear icon respectively.

Frequently asked questions

How do I test my microphone in Google Meet?

Open the meeting link and stop at the green room screen before pressing Join. The level indicator beside the microphone button moves when you speak. For a full check, click the gear icon, open Audio, and use Meet's built-in audio and video check, which records a short clip and plays it back.

Why does Google Meet not detect my microphone?

Most often because the microphone permission for meet.google.com was denied earlier and Chrome now honours that silently, without prompting. Click the icon at the left of the address bar while on the Meet tab, set Microphone to Allow, and reload. On macOS, also confirm Chrome itself is allowed in System Settings → Privacy and Security → Microphone.

Should I turn off noise cancellation in Google Meet?

Only if people report that you cut out. Meet's noise cancellation separates speech from background sound and can misjudge a quiet voice, removing parts of it. If that is happening, disable it in Settings → Audio and raise your input level instead. It is available on Business Standard and above.

Why can people in the same room as me hear an echo on Meet?

Because two devices in one room are each playing the other's audio through speakers and picking it back up. Meet's echo cancellation is designed for one microphone and one speaker, not two of each in the same space. One device should carry the audio; anyone else in the room should join in Companion mode with audio off.

Does a browser mic test tell me whether Meet will work?

More than for other applications, yes. Google Meet on a laptop is a web application using the same browser audio API as this test, so a working browser test rules out hardware, drivers and operating system permissions. What it cannot rule out is a permission scoped to meet.google.com or a different device selected inside Meet.

Can Google Meet call a phone number?

Google Workspace meetings can publish a dial-in number that participants call to join by voice, and some tiers can dial out to a participant. Meet cannot be used as a general telephone: to call an arbitrary landline or mobile you need a calling service that connects to the telephone network.

Other free tools

Now make the call

Telvio dials real phone numbers in 200+ countries over WiFi or data. Per-second billing, first minute free.

Download Telvio
1 free minuteNo account, no cardCall free