How do you test your mic and hear what others hear on a call?

The call starts at 10:00. At 9:58 your AirPods reconnect on their own, macOS switches the input to them, and Zoom, set to follow the system, switches with it. You talk for four minutes before someone says, kindly, that you sound like you are calling from a tunnel. Nothing was broken. The meter in System Settings would have bounced happily the whole time. It was simply measuring a different microphone from the one you thought you were using.

That is the trap in "testing your mic". A moving bar proves that sound arrives. It tells you nothing about what the sound is like, and even less about what it is like after Zoom, the network and the other person's laptop speakers have had their turn. To hear what others hear you need a playback, and the closer that playback sits to the real call, the more it is worth.

The stakes are not only vanity. In a 2025 study published in PNAS, Walter-Terrill and colleagues at Yale played listeners the same recording either clear or distorted. People followed the words equally well, yet the speaker's hireability rating fell from 76 to 68.5 out of 100. The content was identical; only the audio changed.

This article is about finding out how you sound. If you already know the answer and want free fixes, the page for you is how to make your mic sound better without buying a new one. Come back here when you want to check whether those fixes worked.

Four places your voice changes before anyone hears it

Every test below captures some of these stages and misses others. Knowing which test sees which stage is most of the skill.

Most "my mic test sounded fine but people complain" stories live in rows 3 and 4. Most "people say I sound far away" stories live in row 1. Walk down the table from the top, because a problem in row 1 poisons every row below it, and no app setting in row 3 can put back detail the mic never captured.

How to test a microphone on a Mac in thirty seconds

To test a mic on a Mac, start with the boring check, because it is the one that catches the AirPods trap. Open the Apple menu, choose System Settings, click Sound, then click Input. Apple's guide lists what can appear in that list: the internal mic, a display's mic, an iPhone, or an external mic. Click the one you intend to use on the call and speak at your normal call volume.

What to look for on the input level meter:

• The bar moves with your voice and drops back when you stop. If it never moves, the wrong device is selected, the mic is muted with its own button, or the cable is in a port that is not giving it power.
• Your loudest words reach somewhere around two thirds of the meter, not the far end. A meter that slams to the right on every syllable means the input volume is too high, and loud words will crackle.
• Silence sits close to empty. If the bar hovers well above zero while you say nothing, the mic is hearing a fan, traffic, or its own hiss at a high gain setting.

The input volume slider sits right under the device list. Apple's advice is plain: lower it for loud sources, raise it for quiet speech. For a voice at arm's length from a USB mic, start in the middle and move it in small steps.

If an app shows no sound while this meter moves, you are looking at a permission problem, not a hardware one. System Settings > Privacy & Security > Microphone lists every app that asked for the mic, each with its own switch. Browsers count as apps here, so Chrome or Safari needs its switch on before any web call can hear you.

The full tour of these settings, including what the input volume actually changes and when to leave it alone, is in how to change microphone settings on a Mac.

Mic test with playback: record yourself first

A meter answers "does it work". A recording answers "how does it sound", which makes a recording the simplest mic playback test there is, and every Mac already has two recorders.

QuickTime Player. Choose File > New Audio Recording. Click the Options menu next to the record button and pick the microphone yourself, because QuickTime will not necessarily use the one your call app uses. Apple's guide notes that the volume control lets you hear the audio while you record: put headphones on before you raise it, or the speakers will feed back into the mic with a howl. Record, stop, play.

Voice Memos. Press record, talk, press Done. It is quicker, and it records from the system input, so do the System Settings check first.

Read the same text every time. A fixed script turns "it sounds okay, I think" into a comparison you can repeat after every change. This one takes about twenty seconds and covers the sounds that cause trouble on calls:

MIC TEST SCRIPT (about 20 seconds, read at call volume)

1. "Peter picked a pepper, put it back, and paid."  -> plosives: listen for thumps on P and B
2. "Sixty-six simple sessions, so she says."          -> sibilance: listen for harsh, spitting S
3. "Can you hear me okay? Good."                      -> your normal call voice
4. (lean back 40 cm, keep talking) "And now?"         -> how fast you fade when you move
5. (stay silent for 5 seconds)                         -> room and fan noise floor
6. (laugh once, or say one word loudly)                -> crackle on peaks

LISTEN TWICE: once on headphones, once on the laptop speakers.

Headphones show you detail. Laptop speakers show you the realistic worst case: a colleague who takes the call without headphones. While it plays, note: does the voice sound close or across the room, do the S sounds sting, do the P sounds thump, does the five seconds of silence actually sound silent, does the laugh crackle.

What this recording leaves out matters as much as what it contains. It captures stages 1 and 2 of the table: the mic, the room, the input volume. It does not include whatever your call app does. Mic Mode is chosen per app as well (Apple describes picking it inside an app that supports it, such as FaceTime), so a QuickTime file is not guaranteed to reflect Voice Isolation either. Treat the file as the raw material. If the raw material is bad, nothing further down the chain will rescue it.

Test inside the app you actually call from

The next step moves into stage 3. Every major call app has a built-in test, and they are not equal: some show a bar, some play your voice back, one places an actual call to a bot.

A few details from the vendors' own documentation change how you should read these results.

Zoom has a microphone modes setting under Settings > Audio. "Noise removal" is the default, with levels Auto, Low, Medium and High; "Original sound for musicians" turns the filters off; "Personalized audio isolation" is a third choice. There is also a toggle called "Automatically adjust microphone volume". If you test once on High and once on Low, you are testing two different voices, so write the setting down before you judge the result. High suppression is the first suspect when the start of each sentence sounds clipped or your voice seems to pump between words.

Teams keeps its own noise suppression and voice isolation settings on the same Devices page as the test call, and Microsoft says the test recording is deleted right after the call. Like Zoom's test meeting, and unlike a local recording, this test is an actual call: your message travels to the bot and back, so it sits closer to what a colleague receives.

Discord mutes and deafens you if you start the mic test while sitting in a voice channel, so run it before you join. If Discord is where people complain, why your mic sounds bad on Discord goes through its processing settings one by one.

Meet is the odd one out. The bar tells you the browser hears you; it does not let you listen. For Meet, use the browser test or, better, the two-device test below.

Online mic test with playback: what a browser test proves

Search "mic test playback" and you get pages that record a few seconds in the browser and play them back. They are handy on a borrowed computer, or when you have nothing installed yet. Two things to know before you trust one.

First, on a Mac the browser needs permission twice: once in the site's own prompt and once at the system level, the Privacy & Security switch from earlier. A test page that hears nothing has usually failed the second one.

Second, browsers can process the microphone themselves. As MDN documents, a web page can ask for noise suppression, echo cancellation and automatic gain control to be switched on or off on an audio track. One test page may request them and another may not, and you cannot see which. So a browser playback tells you roughly what a browser hears. That is close to Meet running in the same browser, but it is not Meet's chain, and Zoom's web app even offers its own choice between Zoom's noise removal and "Browser built-in noise suppression".

Use a browser test as a sanity check. Do not use it to decide whether a setting inside Zoom helped.

How to hear what others hear: the two-device test

Every test so far stops short of stage 4. The only way to hear compression, dropouts and a listener's speaker is to become the listener. This takes five minutes and a phone.

1. Put headphones on the Mac, or mute its speakers. Otherwise the phone's sound comes out of the Mac and loops back into your mic.
2. Start a meeting on the Mac in the app you will use for the real call, with the real mic selected.
3. Join the same meeting from your phone. Mute the phone's microphone. Plug earbuds into the phone, or hold it to your ear.
4. Say one sentence into the Mac's mic, then stop and listen. Your voice reaches the phone a beat late, and talking over your own delayed voice is surprisingly hard, so work in short pieces: sentence, pause, listen.
5. Read lines 1, 2 and 5 of the script. Pay attention to the silent part: whatever noise survives there is what your colleagues hear between your sentences.
6. Take the earbuds out and listen once on the phone's own speaker.

If you can recruit a person, even better. Ask a colleague to record twenty seconds of you on their end and send you the file. That file is the only recording in this whole article that contains every stage of the table, including their speakers, their room and their ears. Do it once with your usual setup and once after each change you make, and you have a before and after that nobody can argue with.

Hearing yourself live while you talk

Sometimes "hear myself" means something else: hearing your own voice in your headphones during the call, the way radio hosts do. That is monitoring, and it is more often a hardware feature than a software one.

Many USB mics have a headphone jack on the mic body. Logitech describes the Yeti's headphone output as a way to monitor your voice "latency-free", and Maono lists a 3.5 mm jack for real-time monitoring on the DM30. The sound in that jack is taken straight from the mic, before macOS and before Zoom. It is excellent for keeping your distance and volume steady through a long call. It is not what others hear, for the same reason a QuickTime file is not.

On a Mac with no such jack, QuickTime's recording volume gives you a basic version: you hear the input through the Mac while it records. Use headphones, and expect it to feel slightly different from a jack on the mic, since the sound makes a trip through the computer first.

What you heard, and what it usually means

Once you have a playback, the complaints tend to fall into a handful of groups. This is where testing turns into fixing.

Some of what you hear will not be gear at all: pace, breath, how close you lean in, how you end sentences. For that side, see how to make your voice sound better on calls and recordings.

Where TunedMic fits, and where it does not

Everything above is free and built in. Do it first. Plenty of problems end at "wrong input selected" or "sit closer".

TunedMic is for the case where the tests pass, the right mic is selected, and the playback still sounds like a laptop in an empty room. It is a Mac app that adds a virtual microphone called TunedMic to the list every app shows. You run a one-minute Sound Check, reading a short passage aloud, and it takes more than 30 measurements of your voice, your mic and your room. Then you pick TunedMic as the mic in Zoom, Teams, Meet, Telegram or Discord, and all of them get the processed voice.

Two parts of it connect directly to this article. With headphones on, you can flip between the raw mic and the tuned sound live, on your own voice, which is a hear-yourself test with the before and after built in. And because TunedMic appears as an ordinary microphone, every test above works on it unchanged: Zoom's Test microphone, the Teams test call and the two-device test all play back the tuned voice, so you can check the result the same way you checked the raw mic.

The limits, stated plainly. It needs a Mac with Apple silicon (M1 or newer) and macOS 14 or later; there is no Windows or Intel version. There are no refunds once you pay. It adds less than a tenth of a second of delay. It does not fix a muted mic, a permission switch or a bad connection, and it does not turn a budget mic into a specific expensive one. If your playback points to one of those problems, the free fixes above are the answer.

To judge it without paying anything, listen to the before and after recordings on the home page: the same voice through a Hollyland Lark M2 clip-on (once with a Dyson hair dryer running a meter away), a MacBook's built-in mic and a cheap wired headset, matched for loudness. If the "before" sounds like your own playback, try it free for 3 days and run the same tests through it; after that, the price is $39, paid once.

Before your next important call

Run this the day before, not the minute before, so a bad result leaves time to change something.

1. System Settings > Sound > Input: the right mic is selected, loud words reach about two thirds of the meter.
2. QuickTime and the six-line script, played on headphones and on laptop speakers. Write down the one thing you like least.
3. Change one thing (distance, input volume, the app's noise removal level) and record the script again.
4. Run the app's own test: Zoom's Test microphone or test meeting, the Teams test call, Discord's Let's Check.
5. Ten minutes before the call, open System Settings > Sound > Input once more and confirm nothing reconnected and took over the input.

Step 5 is the one that catches the AirPods at 9:58.