Why does your voice sound bad on Teams or Google Meet, and how do you fix it?
No audio in Google Meet, choppy words in Teams, a voice like a phone line: where each problem comes from on a Mac, which permissions and noise suppression settings fix it, and what to do when settings are not enough.
Monday stand-up, eleven people in Teams, and your turn comes. You talk for forty seconds, and the project lead says: "Sorry, you were breaking up, can you repeat that?" Your Wi-Fi is fine and your video never froze. Half an hour later, in a Google Meet with a client, the little bars next to your tile stay flat while you speak, and the client types "can't hear you" into the chat.
These are two different problems, and they get fixed in different places. When audio is missing, it is almost always a permission or a device choice: the browser, macOS or the meeting app is holding the door shut, or the app is listening to a microphone you are not talking into. When audio is there but sounds bad, the cause is usually the microphone, the distance to it, the room, or the call app's own noise processing being too aggressive or too weak. This guide covers both halves for Microsoft Teams and Google Meet on a Mac, in the order you should check them.
If Zoom is the app you spend your day in, the same logic with Zoom's own menus is in the Zoom audio settings guide, and that page will serve you better than this one. If your real enemy is a dog, a fan or a street outside the window rather than a setting, start with how to stop your mic picking up background noise.
Symptom first: which problem do you have?
Read the row that matches what people tell you on the call, then jump to that section.
| What people say or see | Most likely cause | Where to fix it |
|---|---|---|
| Nothing at all, your level bars do not move | Permission blocked or wrong mic selected | Browser site permission, macOS Privacy & Security, the app's device list |
| "You're very quiet" | macOS input volume low, or mic far away | System Settings > Sound > Input, mic position |
| "You keep cutting out" while your network is fine | Noise suppression treating the ends of words as noise | Teams noise suppression mode, Meet noise cancellation |
| "You sound like you're in a tunnel" or "on a phone line" | Bluetooth headset in call mode, or laptop mic in an echoey room | Use a wired or USB mic, soften the room |
| They hear themselves echo | Your speakers leak into your mic | Headphones; Meet flags this with a red dot |
| Your keyboard and the TV come through | Suppression off, or not available on your account | Turn it on, or process the mic before the app |
Google Meet audio not working: check the three gates
Google's own troubleshooting page puts it plainly: to use your microphone in Meet you must give access to three separate things, Google Meet itself, your browser, and your device. On a Mac, Meet runs in the browser, so a block at any one of these layers silences you, and each layer has its own switch.
Gate 1: the Meet site
Address bar on meet.google.com > View site information > Microphone: on
Gate 2: the browser (Chrome)
chrome://settings/content/microphone
Default behavior: "Sites can ask to use your microphone"
(the same page lets you pick the default mic and remove blocked sites)
Gate 3: macOS
Apple menu > System Settings > Privacy & Security > Microphone
Turn on the browser you use for Meet (Chrome, Safari, Firefox, Edge)
Then, inside the meeting:
More options > Settings > Audio > Microphone: pick the real mic by name
The classic trap sits in gate 1. Someone clicks "Block" on the browser's microphone prompt once, months ago, and since then every Meet link opens silent with no prompt at all, because the browser remembers the answer. Gate 3 bites right after you switch browsers: macOS asks for permission per app, so Safari having access tells you nothing about Chrome. After changing a macOS privacy switch, quit the browser fully and open it again; the change does not always reach an app that is already running.
When Meet hears the wrong microphone
If the permission is fine but the bars still do not move, Meet is probably listening to a different input. On a Mac this happens all the time: AirPods connect on their own when you open the case, a monitor or webcam brings its own microphone, a docked MacBook with the lid shut still offers its built-in mic. In the meeting, open More options > Settings > Audio and choose the mic by its name instead of trusting the default.
Two more checks from Google's list. First, Meet can be unmuted while macOS itself is set to a very low input: Google points Mac users to System Settings > Sound > Input, where the input volume slider lives. Second, Meet has a built-in helper: More options > Troubleshooting & help shows suggestions tailored to what Meet detects on your call. The same list ends with updating Chrome and restarting it (type chrome://restart in the address bar), then turning the mic back on before you rejoin.
If the mic is dead in every app, not only in Meet, the problem is lower down, and the guide to a Mac microphone that is not working goes through it step by step.
Teams microphone not working on a Mac
Teams is a desktop app, so it has its own macOS permission, separate from your browser. Microsoft's help page still describes the old System Preferences layout; on current macOS the path is Apple menu > System Settings > Privacy & Security > Microphone, and Microsoft Teams must be switched on there. Microsoft's advice is to close your apps and restart after changing it, so the new permission takes effect.
Then check the device Teams uses. Go to Settings and more > Settings > Devices and, under Audio settings, choose the speaker and the microphone by name. In a meeting the faster route is the dropdown arrow next to Mic in the meeting controls.
Before your next important call, use the button almost nobody presses: Make a test call, in the same Devices section. You record a short message for the Test Call Bot, it plays the message back, and Teams shows a summary of the call with a shortcut to your device settings. It is the cheapest way to hear yourself the way colleagues hear you. For more ways to do that across apps, see how to hear what others hear on a call.
Microsoft Teams audio settings that change how you sound
Once Teams hears you, four settings decide how you come across. Microsoft's support pages name them like this:
| Setting | Where | What it does | For a talking voice |
|---|---|---|---|
| Microphone | Settings > Devices > Audio settings | Picks the input | The real mic by name, never "default" |
| Automatically adjust mic sensitivity | Same section | Teams keeps your level even for everyone | On, unless your level audibly pumps up and down |
| Noise suppression | Same section, or More actions > Audio settings in a meeting | A toggle, then Background noise only or Voice isolation | See below |
| High fidelity music mode | Mic dropdown, or More > Audio settings in a meeting | Sends music at a 32 kHz sampling rate and 128 kbps when bandwidth allows | Only for music lessons or performances |
High fidelity music mode deserves one sentence of warning. Its name tempts people who want "better audio", but Microsoft describes it as a mode for sharing music, such as online lessons or performances. A speaking voice on a call does not need it: the regular processing is built for speech.
Teams noise suppression: which option to pick
In the current Teams desktop app on a Mac, Noise suppression is a toggle in Settings > Devices, also reachable in a meeting under More actions > Audio settings. With it on, you choose one of two modes:
- Background noise only suppresses the noises around you: a fan, a keyboard, traffic.
- Voice isolation also suppresses other voices that reach your mic, so the meeting hears only you.
Older guides talk about Auto, Low and High levels. Microsoft's support page now lists those under the Teams app for iPhone and iPad, but their descriptions still map the trade well: Low handles steady noise such as a computer fan or an air conditioner, High suppresses all background sound that isn't speech, and Microsoft suggests turning suppression off entirely for a high-fidelity mic in a low-noise room, such as a quiet studio.
Voice isolation works from a voice profile that Teams keeps on your device, and Microsoft says you need one if you are not using a headset. After you opt in, Teams starts building the profile at your next eligible meeting; if you would rather not wait, open Settings > Recognition and read a short passage into your mic. Voice isolation reached Teams on macOS in October 2024, about a year after Windows. Admins can switch it off with a policy, so if the option is missing on a work account, that is a question for IT, not a fault on your Mac.
Which mode to choose is a trade, not a ranking. The harder a suppressor works, the more aggressively it decides what counts as noise, and the quiet ends of words are the first thing it can mistake for noise. That is where "you keep cutting out" on a perfect connection often comes from. A practical rule:
- Quiet room, decent wired or USB mic: run a test call with suppression off, then with Background noise only, and keep whichever sounds cleaner.
- Fan, keyboard, a café: Background noise only.
- Other people talking near you (open office, family at home): Voice isolation, once the profile exists.
- Clipped words with any of the above: step back one notch (Voice isolation to Background noise only, or Background noise only to off) and run the test call again.
If words drop out even with suppression turned down, the cause may be the device or the connection rather than the filter, and why your mic keeps cutting out separates those cases.
Google Meet noise cancellation: who gets it and what it misses
Meet's noise cancellation is a cloud feature, and it is not on every account. Google's help page lists the Workspace editions that have it on a computer: Business Standard and Business Plus, Enterprise Essentials, Standard and Plus, Education Standard and Plus, Teaching and Learning Upgrade, Frontline, Workspace Individual subscribers, and Google One subscribers with 2 TB of storage or more. A plain free Gmail account is not on that list. It is on by default for business and enterprise editions, Workspace Individual and Google One, and off by default on education accounts.
To switch it on, open More options > Settings > Audio and turn on Noise cancellation, either before joining or during the meeting. Google is also clear about the limits:
- Voices from a TV or people talking nearby are not cancelled. Meet's filter is built to remove noise, not other speech.
- Audio you share with your screen is not affected by noise cancellation.
- It is not available when you dial out to add a phone participant mid-meeting.
So if you search for "google meet noise cancellation" and the toggle is not in your settings, nothing is broken. Your account simply does not include it, and the fix has to happen before the sound reaches Meet: a closer microphone, a quieter spot, or software on the Mac that cleans the mic for every app.
The echo warning
Meet watches for one more problem. If your audio has an echo, a red dot appears on the More options button. Echo means the other people's voices leave your speakers and enter your microphone, so they hear themselves a moment later. Headphones end it. Lowering the speaker volume and muting when you are not talking help too. The longer explanation, including why it is usually your setup that echoes and not theirs, is in why people hear an echo from your mic.
When every setting is right and you still sound bad
At this point Teams and Meet hear the correct mic, permissions are open and suppression is at a sensible level. If people still complain about your Teams audio quality, or say you sound thin, boomy or far away in Meet, settings are no longer the bottleneck. The usual suspects:
Distance. A MacBook's built-in mic sits behind the keyboard, often 50 cm (about 20 inches) or more from your mouth. Every extra inch lets more room into the signal, and no call app can take the room back out completely.
Bluetooth in call mode. Bluetooth limits how much detail a mic can send, and that is the "phone line" quality people complain about with AirPods and many wireless headsets on calls. A wired headset or a USB mic gives the call app far more to work with. Why AirPods sound bad on a Mac covers this in detail, and which headset has a good enough mic for work calls helps if you are shopping.
The network. Google's Meet quality page calls bandwidth a major cause of poor video quality and suggests a wired Ethernet connection, 5 GHz Wi-Fi instead of 2.4 GHz, closing tabs and apps you do not need, and pausing a VPN for the call. A starved connection can chop your voice too, so rule it out before blaming the mic.
Is it worth the effort for a work call? A 2025 study from Yale by Walter-Terrill and colleagues, published in PNAS, played listeners the same recording either clear or distorted. People followed the words equally well, yet hireability ratings fell from 76 to 68.5 out of 100 for the distorted version. Being understood and being judged well turned out to be two separate things.
One fix for Teams, Meet and everything else on a Mac
Doing all of this per app has a catch: Teams has its suppression, Meet has its own (or none on your account), Zoom has a third, and a Telegram or Slack call has whatever it has. Your voice sounds different in each, and fixing one does nothing for the rest. Gamers know the same story from voice chat, where Discord runs yet another filter; why a mic sounds bad on Discord is the version of this page for them.
The alternative is to process the microphone once, before any app sees it. That is what a virtual microphone does: an extra input device on the Mac that carries an already cleaned signal, so Teams, Meet in Chrome, Zoom and the rest pick it from their microphone list. If the idea is new, what a virtual microphone is explains the mechanism.
TunedMic works this way. It adds a microphone called TunedMic, takes the sound from your real mic (built-in, USB, headset or AirPods), and processes it on the Mac in real time. Setup is a one-minute Sound Check: you read a short passage aloud and the app takes more than 30 measurements of your voice, your mic and your room, then builds its profiles from that, not from a stock preset. In Teams you pick TunedMic under Settings > Devices; in Meet under More options > Settings > Audio. Switching profile changes the sound in every app at once. It adds less than a tenth of a second of delay, which on a call disappears into the connection's own delay, and the voice is never uploaded.
Two practical notes if you go this way. With the voice already cleaned before Teams or Meet, keep the call app's own filter light: Background noise only in Teams, and in Meet compare noise cancellation on and off in a test meeting. Two filters guessing at the same quiet syllables is how words start to clip. And on a work Mac, check first that you are allowed to install software: TunedMic installs an audio driver, and macOS asks for your password once to install it.
The limits, plainly. TunedMic needs a Mac with Apple silicon (M1 or newer) and macOS 14 or later. There is no Windows version, so if your Teams calls happen on a Windows laptop, this does not help you. It does not make a bad mic sound like a studio one, and it does not remove every noise. And if the problem is a blocked permission, it cannot open the gate for you: the steps earlier on this page come first.
Ten minutes before your next call
Do this once, in this order, and keep the list for the day something changes:
- Open System Settings > Privacy & Security > Microphone and make sure both Microsoft Teams and your browser are switched on.
- In Chrome, open
chrome://settings/content/microphoneand remove meet.google.com from the blocked list if it is there. - In Teams, go to Settings > Devices, choose your mic by name, and run Make a test call. Listen to the playback with headphones.
- Set Teams noise suppression to match your room, using the rule above.
- Join a test Meet on your own, open More options > Settings > Audio, pick the same mic, and turn on Noise cancellation if your account has it.
- If the playback still sounds like a tunnel or a phone line, switch from Bluetooth to a wired or USB mic, or move the mic closer.
If after step 6 your voice is clear in the test call but noisy or thin in real meetings, the next thing to look at is the 38-second video on the TunedMic home page: a one-minute Sound Check before the call, a Speech Report after it. The free 7-day trial starts at first launch, opens every feature and needs no card or account; there are no refunds after purchase, so use those seven days on your real Teams and Meet calls. Prices are on the pricing page.