Mic Not Working on Mac? Fix Input Source, Privacy Settings, and CoreAudio
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic TestYour Mac has selected the wrong input device, a privacy block is silencing the app, or the CoreAudio daemon has crashed and needs a hard reset. These three causes cover roughly 90 percent of microphone failures on macOS. The hardware itself is almost never the problem โ the built-in MEMS microphone capsule on MacBooks is soldered to the logic board and fails far less often than the software stack that sits above it. Before you book a Genius Bar appointment, work through the software layer completely.
Confirm the Mic Is Actually Receiving Signal
Before touching any settings, go to Mic Test and run a live input check in your browser. It bypasses the app layer and talks directly to the browser's WebRTC stack, so if signal appears there, your hardware and CoreAudio are both functional and the fault is app-specific. If the level meter shows nothing, you have a system-level block or a crashed audio daemon.
While you are there, watch the input level bar carefully. A bar that peaks and immediately clips to maximum usually means the Mac has selected an input with a mismatched sample rate โ 48 kHz device feeding a 44.1 kHz aggregate โ which causes CoreAudio to feed garbage data upstream.
Set the Correct Input Source in System Settings
This is the most common cause of a macbook mic not working after connecting a USB interface, dongle DAC, or HDMI monitor with an embedded audio device. macOS silently re-routes input to the last connected device.
- Open System Settings (macOS 13 Ventura and later) or System Preferences (macOS 12 Monterey and earlier).
- Go to Sound > Input.
- Select MacBook Pro Microphone or MacBook Air Microphone depending on your machine. External USB devices will show their product string here โ a Focusrite Scarlett Solo appears as "Scarlett Solo USB".
- Set Input volume to 75 percent as a baseline. Do not set it to 100; that introduces noise floor artifacts on the built-in capsule.
- Speak and watch the input level indicator. If it moves, the device is live.
If you use an aggregate device in Audio MIDI Setup (Applications > Utilities > Audio MIDI Setup), verify the clock source is set to the primary device, not a secondary one. A clock mismatch produces the crackling, dropout, or silent-input symptoms that make microphone not working on mac reports so common in recording forums.
Fix Privacy and App Permissions
macOS has required explicit microphone permission for every app since Mojave 10.14. A permission that was granted, then revoked by a macOS update or a third-party privacy manager like Little Snitch or Privacy Cleaner Pro, will silently block input with no error message to the user.
- Open System Settings > Privacy & Security > Microphone.
- Find the app that is failing. Toggle it off, wait three seconds, toggle it back on.
- If the app is missing from the list entirely, it has never requested permission. Launch the app, attempt to use the mic inside it, then return to this screen โ the request should now appear.
- For browser-based tools, check the browser's own site permission. In Chrome: chrome://settings/content/microphone. In Safari: Safari > Settings > Websites > Microphone. Set the site to Allow, not Ask.
Terminal-based privacy resets occasionally help when the TCC database (Transparency, Consent, and Control โ stored at ~/Library/Application Support/com.apple.TCC/TCC.db) becomes corrupt. Running tccutil reset Microphone in Terminal wipes all microphone permissions and forces every app to re-request access on next launch. You will need to re-grant permissions to every app afterward.
Reset the CoreAudio Daemon
CoreAudio runs as a persistent daemon process. It can crash or enter a bad state after sleep cycles, sample rate changes, or hot-plugging audio devices. When it does, input devices may appear in System Settings but produce no signal. The fix is a forced daemon restart.
Open Terminal and run:
sudo killall coreaudiod
Enter your admin password. The daemon restarts automatically within two seconds. You will hear a brief audio dropout. Test your mic immediately after. If this fixes the issue temporarily but the problem returns after sleep, you have a power management conflict โ go to System Settings > Battery > Options and disable Enable Power Nap, which wakes the machine for background tasks and can leave CoreAudio in a half-initialized state.
On Apple Silicon Macs (M1, M2, M3 series), a full SMC reset is not available the same way it is on Intel. Instead, shut down completely, wait 30 seconds, and boot. This forces the audio subsystem to reinitialize from a clean state.
Input Source vs. Permission vs. Daemon: Quick Comparison
| Symptom | Most Likely Cause | Fix Location |
|---|---|---|
| Mic works in one app, silent in another | App privacy permission blocked | System Settings > Privacy & Security > Microphone |
| Mic silent everywhere after plugging in USB device | Wrong input source selected | System Settings > Sound > Input |
| Mic visible in settings but no level movement | CoreAudio daemon crashed | Terminal: sudo killall coreaudiod |
| Mic works then drops out randomly | Sample rate mismatch or Power Nap conflict | Audio MIDI Setup clock source / Battery settings |
| Mic silent only in browser | Browser site permission denied | Chrome or Safari site microphone settings |
If you want to verify your speaker output is also intact after these changes, run a quick check with the Speaker Test. And if you are troubleshooting a full meeting setup, the Meeting Check tool tests mic, speaker, and webcam in a single pass.
Frequently Asked Questions
Why did my Mac mic stop working after a macOS update?
macOS updates frequently reset TCC privacy permissions for microphone access, especially major version upgrades. Go to System Settings > Privacy & Security > Microphone and re-enable every app you use. Updates can also change the default input device back to the built-in mic even if you had an external one selected.
My mic shows input level in System Settings but the app hears nothing. What is wrong?
The app's permission is blocked. The System Settings input meter reads directly from the hardware driver, bypassing the permission layer. So you can see signal there even when an app is denied access. Fix it in System Settings > Privacy & Security > Microphone by toggling the specific app.
How do I know if my built-in MacBook microphone is physically damaged?
Run the Mic Test in your browser. If the browser has microphone permission granted and the level meter shows zero response to loud sound with no other input device selected, the capsule or its solder joint may be failed. At that point, Apple Diagnostics (hold D at boot on Intel, or hold the power button on Apple Silicon) will flag audio hardware faults if the failure is detectable at the firmware level.
Can a third-party app like Krisp or SteelSeries GG block my mic from other apps?
Yes. Virtual audio routing apps create a virtual input device and set it as the system default. Other apps then receive the virtual device's output rather than your physical mic. If Krisp, NVIDIA RTX Voice, or a gaming headset suite is installed, check Audio MIDI Setup and System Settings > Sound > Input to confirm you are selecting the real hardware device, not a virtual one.
Does running sudo killall coreaudiod delete any settings or files?
No. It only terminates and restarts the running daemon process. Your Audio MIDI Setup configurations, aggregate devices, and system sound preferences are stored separately and are not affected by the restart.
My mic works fine but sounds very quiet even at 100 percent input volume. What should I check?
First confirm you are not accidentally using a far-field microphone array pickup pattern โ some apps select a different mic element on MacBook Pros with multiple capsules. In Audio MIDI Setup, check if the built-in input shows 1 channel or 2; some configurations expose individual capsules. Also check that no app has inserted a software gain stage running at reduced level, which is common in DAWs like Logic Pro or GarageBand under the channel strip input gain knob.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic Test