Microphone Not Working on a Mac: How to Test & Fix It

A microphone not working on a Mac produces a strange symptom: the hardware tests fine, yet apps hear nothing. That gap is the clue. macOS almost never breaks a microphone outright. Instead a privacy toggle, a stalled Core Audio process, or a Continuity handoff to a nearby iPhone quietly steals the input. The microphone itself stays in perfect order. Apple routes every recording through a privacy layer, introduced in macOS Mojave, before any app can listen. A block there is silent and shows no error. This guide separates a real fault from a blocked one. Open our microphone test first and watch the input meter as you speak. If it moves, the capsule works and the fix lives in software. The sections below walk through permissions, device selection, the Continuity trap, and a Core Audio restart for the cases that resist everything else.

Mac Microphone Not Working: Quick Fix Checklist

✓	Check for a signal with our microphone test or System Settings › Sound › Input.
✓	Allow the app in System Settings › Privacy & Security › Microphone.
✓	Select the correct input; stop AirPods or Continuity from stealing it.
✓	Reset app permissions with tccutil reset Microphone.
✓	Restart Core Audio with sudo killall coreaudiod.

Test your Mac's microphone in under a minute

Confirm that the microphone captures sound before you change any setting. The fix for "no signal" differs completely from the fix for "signal, but nobody can hear me." A live input meter gives the fastest honest answer. It reacts to your voice in real time. A record-then-play-back loop hides latency and device-selection mistakes, so avoid it here. Open our online microphone test and allow access when the browser asks. Now speak normally. If the level indicator moves as you talk, the microphone hardware and drivers are fine. The problem then sits higher up, in permissions or in one specific app. If the meter stays flat, the signal is blocked or the wrong input is selected. The sections below show you exactly where to look.

Test Your Microphone →

macOS exposes the microphone in several native places. Knowing which one to trust saves time. The most reliable built-in gauge is the input meter under System Settings › Sound › Input. Select your microphone in the device list. The row of dots beneath it should light up as you speak. Suppose the dots move here but an app still hears nothing. You have then proven the fault is app-specific rather than system-wide. In that case, skip straight to the app and permission sections below. The table maps every place your Mac reveals the microphone. It also states what a reading in each one confirms.

Where to look	Path	What it confirms
Sound input meter	System Settings › Sound › Input	Whether macOS receives a signal, and from which device
Privacy consent list	System Settings › Privacy & Security › Microphone	Which apps are allowed to use the microphone
Menu-bar recording dot	Top-right of the screen (amber dot)	That an app is capturing audio right now
Voice Memos / QuickTime	Applications folder	A neutral second app to isolate a faulty program

Why a working microphone still goes silent on macOS

The privacy layer is the number-one culprit

macOS Mojave introduced a consent system called Transparency, Consent and Control, or TCC. Every app must now be granted permission before it can access the microphone. This single mechanism causes more "broken" Mac microphones than every hardware fault combined. The trap is that the block is invisible. An app that was never granted access simply receives silence. There is no error message and no prompt. A macOS update, a reinstall, or a change to an app's code signature can also revoke a permission that once worked. Video-conferencing tools are especially exposed. They update constantly, and each major update can reset the app's standing in the consent database. One clear tell-tale exists. An amber dot appears at the top-right of the menu bar whenever the microphone is live. Suppose you are talking, expect to be heard, and the dot never appears. The app almost certainly never received permission. You resolve this in System Settings › Privacy & Security › Microphone. Every app that has requested the microphone is listed there with a toggle. Often the fix is simply switching one of them back on.

The "wrong device" trap and Continuity handoffs

Modern Macs switch audio inputs aggressively on your behalf. That helpfulness is a frequent source of confusion. Connect AirPods, a USB interface, an HDMI display, or a Bluetooth headset, and macOS may promote it to the default input at once. You then speak into the built-in microphone while the system listens to a headset in another room. Continuity makes this subtler. With an iPhone nearby and signed into the same Apple ID, macOS can route audio through the phone. The Mac's input meter then goes flat for no visible reason. Suspect device selection first whenever the microphone works only "sometimes." Pin the input you want in System Settings › Sound › Input. Then unplug and replug your accessories and watch whether the selection holds. If it keeps jumping back, a connected device is winning the default-input contest. Disconnect or disable that device.

The physical layer still matters

Hardware causes are less common on a Mac. They remain worth an early check, because they are quick to rule out and cannot be fixed in software. Many headsets carry an inline mute switch. Some mute the boom microphone automatically when the arm is raised. A surprising number of dead-microphone reports end there. External interfaces and USB microphones can draw significant power. Chained through an unpowered hub or a marginal USB-C dongle, they misbehave. Connect them directly to the Mac, or to a powered hub, and they often recover instantly. Modern MacBooks carry a single 3.5 mm combo jack. That port expects a four-conductor TRRS headset plug. A three-conductor microphone plug will play audio but capture nothing. The built-in microphone sits beside the speakers, so a genuinely faulty internal mic is rare. If the built-in input is dead but a USB device works, the fault is almost always software.

Fixing it, from the most common cause down

Work through these fixes in order. Do not jump to the dramatic ones. The sequence is deliberate. It resolves the most cases first, with the least disruption. Permissions and device selection together account for most Mac microphone failures. Only then does the sequence escalate to restarting system audio. After each change, return to the microphone test or the Sound input meter. Re-check for a signal before moving on. That way you always know which step made the difference.

Grant, then reset, microphone permissions

Open System Settings › Privacy & Security › Microphone. Confirm that the app you are troubleshooting is present and switched on. For a browser-based call, the entry you need is the browser itself. The site inherits the browser's system-level access. A second, in-browser prompt must also be allowed; our Safari and Chrome guides cover that step. Suppose the app is present and toggled on but still hears nothing. The stored consent record is then likely corrupt. The clean fix is to reset it. In Terminal, run tccutil reset Microphone. This clears every app's saved microphone decision. The next time each program asks, macOS shows a fresh prompt, and you click Allow. The command is safe and reversible. It revokes nothing permanently. It only forces the consent dialog to appear again. Because it resets all apps at once, expect to re-approve a few on next launch.

Force the correct input and raise the level

Return to System Settings › Sound › Input with permissions confirmed. Select the microphone you intend to use. Do not trust whatever macOS chose. Speak, and watch the input-level dots. If they barely move, drag the Input volume slider up. Check whether your microphone has a hardware gain dial that is turned down. Disable any input device you are not using. An idle Bluetooth headset or a virtual audio device will steal the default slot and leave you talking into nothing. Many applications also keep their own input selector. It overrides the system default entirely. So if the Sound meter reacts but the app does not, open that app's audio settings. Point it explicitly at the right device. Our guides for Zoom, Microsoft Teams and Discord cover each audio panel in detail.

Restart Core Audio when the meter stays frozen

Suppose permissions are granted, the correct device is selected, and the input meter still will not budge. The audio engine has probably wedged. This is a known behaviour after the Mac wakes from sleep or hot-swaps an interface. macOS runs all audio through a background process called coreaudiod. Restarting it forces the entire input and output stack to reinitialise without a reboot. The command is sudo killall coreaudiod in Terminal. The daemon relaunches automatically within a second or two. All system audio cuts briefly as it does. Treat this as the reset button for a frozen audio stack, not a routine step.

Note: Terminal commands such as tccutil reset Microphone and sudo killall coreaudiod are safe and reversible. They still act system-wide and briefly interrupt audio or clear saved permissions for every app. Close active recordings and calls first. Run them only after the simpler settings-based steps have failed. You perform these actions at your own discretion.

Keeping your Mac's microphone reliable

A few habits keep the microphone working once it is back. Review the microphone list under Privacy & Security from time to time. Switch off access for apps that have no reason to listen. This tightens both reliability and privacy. It also stops a forgotten background app from grabbing the input during a call. Keep macOS current. Apple ships regular Core Audio and Bluetooth fixes. Give any major upgrade a microphone check afterwards. Upgrades are the single most common moment for app permissions to reset. Suppose you rely on an external interface or USB microphone. Connect it to a powered hub or directly to the Mac. Pin it as the default input. macOS then stops re-electing your AirPods whenever they wander into range. When the same microphone must work across a browser, a desktop app, and a phone, test it in each place. A microphone that is flawless in Voice Memos can still be blocked one layer up, in your browser or your conferencing tool.

Frequently Asked Questions

Why is there an orange dot at the top of my Mac's screen?

The amber dot means an app is using the microphone right now. It is a privacy indicator built into macOS. Click the Control Center icon beside it to see which app is listening. If the dot never appears while you try to be heard, the app has not been granted microphone access.

Why does my Mac keep switching to my AirPods microphone?

macOS promotes newly connected Bluetooth and USB devices to the default input. AirPods rejoin the moment they leave the case near your Mac. Set your intended microphone in System Settings › Sound › Input. Disconnect or forget devices that you do not want competing for the default slot.

How do I test my Mac's microphone without recording anything?

Use a live meter rather than a recording. Our online microphone test shows your input level in real time in the browser. System Settings › Sound › Input shows the same thing natively. Both confirm that the microphone captures sound without saving a file.

My USB microphone does not appear in Sound settings. What now?

Connect it directly to the Mac or to a powered hub. Interfaces that draw real power often vanish when under-supplied. Try a different cable and port. If it still does not appear, restart Core Audio with sudo killall coreaudiod so macOS re-scans connected audio devices.

Does resetting microphone permissions delete any of my data?

No. The command tccutil reset Microphone clears only each app's saved allow-or-deny decision for the microphone. Nothing else is removed. The next time an app needs the microphone, macOS simply asks you to allow it again.