MacBook speakers not working is almost never a dead speaker — it’s usually a setting, a stuck audio process, or a Bluetooth device that never disconnected. I’ve had a MacBook Pro go completely silent mid-call because a pair of AirPods I wasn’t even wearing stayed “connected” in the background. If your Mac shows no sound at all, or sound that’s distorted, quiet, or coming from the wrong output, here’s what to check and in what order.
Quick Answer
- Check Sound settings in System Settings and confirm the internal speakers are selected as output
- Restart Core Audio using a Terminal command before assuming hardware failure
- Disconnect Bluetooth devices that might be silently claiming the audio output
- Check for physical debris in the speaker grilles, especially on older models
- Test with headphones to isolate whether it’s a speaker issue or a system-wide audio issue
Why It Fails
There’s more than one thing that can cause silent speakers, and they don’t all look the same from the outside. So here’s what actually causes this, based on what tends to show up in real cases.
Wrong output device selected. This sounds too simple to be the answer, but it’s the single most common cause. If a Bluetooth speaker, AirPods, or an external monitor with speakers was ever connected, macOS sometimes defaults back to it even after it’s out of range or turned off.
Core Audio process getting stuck. macOS runs audio through a background process called coreaudiod. It occasionally hangs, especially after waking from sleep or switching outputs repeatedly, and when it does, sound just stops working system-wide with no error message at all.
Muted or near-zero volume that got triggered by a keyboard shortcut. Easy to laugh at, but I’ve done this myself — accidentally holding the mute key or dragging volume down mid-multitask without noticing. Worth checking before anything more involved.
Physical debris or liquid damage in the speaker grille. Crumbs, dust, or a spilled drink can muffle or fully block sound output. This is the one people jump to last, when honestly it should be checked earlier if the Mac’s a few years old and gets used a lot outside a desk setup.
A failed macOS update leaving audio drivers in a broken state. Not common, but it happens — usually after a major version update rather than a routine security patch. Symptoms include speakers working fine right after login and then cutting out after a few minutes.
Common Scenarios
- No sound after connecting to an external monitor — HDMI or USB-C often carries audio output and hijacks it from the speakers
- No sound only in specific apps (Zoom, Spotify) — app-level audio permission or output setting issue, not system-wide
- Sound worked, then cut out mid-session — usually a stuck Core Audio process
- No sound after a macOS update — driver conflict, more common right after major updates
- Crackling or distorted sound, not silence — often debris in the speaker or an app-specific codec issue, different fix path than true silence
Step-by-Step Fixes
Step 1: Check the output device
Click the Sound icon in the menu bar (or go to System Settings > Sound) and confirm “MacBook Pro/Air Speakers” is selected, not a Bluetooth device or external display.
Step 2: Check the volume and mute state
Press F10/F11/F12 or check the slider directly in System Settings > Sound > Output. It’s worth doing even if you’re sure it’s not muted — I’ve been wrong about this more than once.
Step 3: Restart Core Audio
Open Terminal and run:
sudo killall coreaudiodThis forces the audio system to restart without rebooting the whole Mac. It fixes stuck-audio issues more reliably than almost anything else on this list, in my experience.
Step 4: Forget and reconnect Bluetooth devices
Go to System Settings > Bluetooth, and for any audio device (headphones, speakers, AirPods) that shouldn’t currently be active, click the info icon and select “Forget This Device.” Reconnect only when you actually need it.
Step 5: Reset NVRAM
Shut down, then hold Cmd+Option+P+R while powering on until you hear two startup chimes (Intel Macs only — Apple Silicon Macs reset relevant settings automatically on restart).
Step 6: Check System Settings > Sound > Output for missing devices
If “MacBook Pro Speakers” doesn’t even appear in the list, that’s a stronger sign of a driver or hardware issue rather than a simple setting, and it changes what you should try next.
What Actually Worked For Me
So this one turned out to be embarrassingly simple, though it didn’t feel that way at the time. Sound just stopped entirely, mid-YouTube video, no warning. I checked volume, checked mute, checked the output menu — internal speakers were selected the whole time, which made no sense.
Restarted the Mac fully, thinking that would clear it. It didn’t, not even close.
The actual fix came from running sudo killall coreaudiod in Terminal, something I’d forgotten was even an option until I saw it mentioned in an old forum thread. Sound came back within two seconds of running that command. Turns out a pair of AirPods I’d used the day before never fully disconnected in the background, and Core Audio was stuck trying to route sound to a device that wasn’t there anymore. Forgetting the device in Bluetooth settings afterward stopped it from happening again — mostly.
Advanced Fixes and Edge Cases
Check Console.app for coreaudiod crash logs. Search “coreaudiod” in the last 24 hours. Repeated crash entries point to a deeper driver conflict, often triggered by a specific third-party app like a screen recorder or audio routing tool (Loopback, Soundflower, and similar tools are common culprits).
Boot into Safe Mode to rule out third-party audio software. If sound works normally in Safe Mode, something you installed — usually an audio routing or recording app — is interfering with Core Audio at a level that’s hard to diagnose otherwise.
Run Apple Diagnostics for a hardware check. Shut down, hold D while powering on. It checks the speaker hardware directly and will flag an actual component failure, which no software fix will touch.
Check for a stuck audio MIDI configuration. Open Audio MIDI Setup (Applications > Utilities) and confirm the built-in output isn’t set to an unusual sample rate or disabled channel. This is rare, but it happens after some pro-audio app installs and quietly breaks default output.
What Rarely Works
Reinstalling macOS almost never fixes this, and it’s suggested constantly online for what’s usually a five-second Terminal fix. Resetting the SMC is also over-recommended for audio issues specifically — it helps with power and thermal problems far more than sound output, so don’t expect much from it here.
Prevention Tips
- Forget Bluetooth audio devices you’re not actively using instead of leaving them paired indefinitely
- Avoid eating or drinking directly over the keyboard, since the speaker grilles sit close by on most models
- Keep macOS updated, but wait a few days after major releases if you can, since audio driver bugs tend to get patched fast
- Learn the
sudo killall coreaudiodcommand — it’s the fastest fix for the majority of sudden silent-speaker cases
FAQ
Why does my MacBook show sound is playing but nothing comes out? That’s the classic Core Audio stuck-process symptom — the volume bar moves, but no actual audio reaches the speakers. Restarting coreaudiod fixes this most of the time.
Can a MacBook speaker fail permanently? Yes, though it’s less common than people assume. If Apple Diagnostics flags a hardware fault, or sound only comes from one side consistently, that’s a real hardware issue, not a settings problem.
Why does sound work with headphones but not speakers? That usually confirms it’s not a system-wide audio failure — the built-in speaker output specifically is affected, which points toward the output setting or a genuine speaker hardware issue rather than Core Audio.
Does spilling liquid on a MacBook always damage the speakers? Not always, but it’s a real risk, especially for anything sugary that dries and clogs the grille over time. If sound got muffled right after a spill, that’s not a coincidence.
Is it normal for sound to cut out briefly when connecting an external display? Yes, that’s normal — macOS switches audio output automatically when a display with speakers or HDMI audio connects, and it can take a second to settle.
Editor’s Opinion
Nine times out of ten it’s not the speakers at all, it’s Core Audio or a leftover Bluetooth connection nobody remembered. Try the killall command before you panic about hardware, seriously, it takes ten seconds. Wish I’d known that command years earlier instead of restarting my Mac like it was 2005.
