Most of the time you can restore sound in under five minutes: confirm internal speakers are selected as the output device, disconnect every external audio accessory, check for hidden mute, and restart CoreAudio. If those steps don’t bring sound back, the issue likely sits deeper in macOS configuration or, less often, in the speaker hardware itself, and the checklist below walks through both paths in order.
TL;DR:
- Most macOS sound issues are caused by incorrect output routing, muted settings, or connected accessories, and can often be fixed within minutes.
- External displays or virtual audio devices can silently take over audio output, even after disconnection, requiring manual re-selection of internal speakers.
- Restarting CoreAudio or resetting NVRAM/SMC addresses the majority of software-related silent speaker problems before considering hardware repair.
- A stuck optical output switch or liquid exposure may physically block sound, often identifiable by a red light in the headphone jack, indicating hardware faults.
- Hardware failures like speaker module problems or damaged audio ICs are less common but require professional diagnosis and repairs for resolution.
Before touching Terminal or worrying about a repair bill, run through this list in order. It resolves the majority of cases where speakers not responding on a MacBook turns out to be a settings problem rather than a broken part.
According to Apple’s own troubleshooting guidance, the majority of MacBook speaker complaints trace back to output routing, accidental mutes, or a connected accessory. Hardware failure is the minority explanation, which is good news if you’re staring at a silent laptop right now.
macOS treats audio output like a switchboard, and it doesn’t always default to the speakers built into your MacBook. Every time you connect a new device, from a Bluetooth speaker to a USB dock with a headphone port, macOS adds it to the list of possible output destinations and sometimes switches to it automatically.
Open Apple menu → System Settings → Sound → Output to see the full list. You’ll find three controls that matter:
External displays are the sneakiest culprit. Plug a MacBook into an HDMI monitor with built-in speakers, and macOS may quietly reroute all system audio to that monitor, even after you unplug it, if the connection drops without a clean disconnect. Virtual audio devices installed by conferencing or screen-recording software behave the same way, sitting in that output list and occasionally grabbing priority.
To test cleanly, play a short audio clip in QuickTime Player and a completely separate one in Safari. If neither produces sound through the speakers you selected, the fault sits below the app layer, likely in CoreAudio itself or in the hardware, which is exactly what the next section addresses.
When output routing looks correct but sound still won’t come through, the fix usually lives in a stuck audio process or stale system settings rather than anything physical. Work through these in order, since each one is progressively more invasive.
sudo killall coreaudiod. This force-restarts the macOS audio engine in seconds without requiring a full reboot, and it’s often the single most effective fix for a MacBook that suddenly went silent mid-session. Restarting the CoreAudio process clears frozen audio buffers that build up after a Bluetooth device drops or an app crashes while holding the audio stream open.Pro Tip: Run the CoreAudio restart command twice, back to back, if the first attempt doesn’t produce sound immediately. Occasionally the process needs a second kill to fully clear a stuck buffer, and it costs you nothing but a few seconds.
Software fixes handle most cases, but a small set of MacBook speaker problems come down to something you can see or feel. Check these before assuming you need a repair appointment.
Among repair intake cases involving no-sound complaints, a stuck optical jack switch shows up often enough that technicians check it before anything else once the software checklist has been exhausted. If the insert-and-remove trick doesn’t clear the red light permanently, or if you’ve had any liquid exposure, that’s your cue to stop troubleshooting and get a professional opinion rather than keep pressing on a physical fault you can’t fix with a restart.
Run Apple Diagnostics before deciding you need professional repair. Shut down, then power on while holding the D key until the diagnostics screen appears. Apple Diagnostics scans internal hardware, including the audio system, and flags specific component failures with a reference code.
Book a repair appointment rather than continuing to troubleshoot if any of these apply; for expert help, consider professional repair services available in Atlanta and beyond.
Confirmed hardware faults typically mean speaker module replacement, audio IC-level component repair, or in more serious cases, logic board work, particularly after liquid exposure causes corrosion. Apple also outlines official repair pathways, including Self Service Repair for experienced users and certified repair for guaranteed genuine parts.
MacBooks don’t use separate, user-installable audio drivers the way Windows laptops do. The audio driver is baked into macOS itself, which means “updating drivers” here really means updating macOS or resetting the audio subsystem that’s built into the operating system.
Go to System Settings → General → Software Update and install anything pending, since Apple periodically ships fixes to CoreAudio and related frameworks inside routine updates. If you’re on an older macOS version and speakers stopped working after a specific app install, check whether that app installed its own audio kernel extension or virtual driver, something conferencing tools, DJ software, and screen recorders commonly do.
You can spot these in System Settings → Privacy & Security, under any extension-loading permissions, or by checking Activity Monitor for unfamiliar audio-related background processes. Removing a third-party virtual audio driver usually means uninstalling the app that installed it, not manually deleting files, since Apple’s System Integrity Protection blocks casual tampering with core audio components anyway. If uninstalling the suspect app restores sound, you’ve found your answer without touching a single system file.
Creating a second test account is one of the fastest ways to rule out a corrupted user-level setting without touching anything system-wide. Go to System Settings → Users & Groups, add a new standard account, log out, and log into the new one.
Play a system sound or a short video clip immediately. If speakers work fine under the new account, the problem lives in your original account’s audio preferences, not in macOS or the hardware itself. That points you toward a corrupted preference file, typically something in ~/Library/Preferences related to sound, or a login item quietly loading a virtual audio device every time you sign in.
If the silence follows you into the fresh account too, you’ve just eliminated an entire category of possible causes. That’s useful information even if it’s not the fix itself, since it means the fault sits in macOS system settings, CoreAudio, or hardware, not in anything specific to your login. Delete the test account once you’re done; it was only there to isolate the problem.
Audio MIDI Setup is a utility most MacBook owners never open, tucked away in Applications → Utilities, and it controls audio device configuration at a level below the Sound settings panel. It rarely causes problems on its own, but certain apps, particularly music production software or video editing tools, can leave it in a strange state.
Open Audio MIDI Setup and look at the device list on the left. Check that your built-in output shows a sample rate that makes sense, typically 44.1 kHz or 48 kHz, and that no aggregate device or multi-output device has been created and left active by mistake. An aggregate device combining your speakers with a disconnected USB interface can cause macOS to route audio into a configuration that produces no sound at all.
If you spot an unfamiliar aggregate or multi-output device, select it and remove it using the minus button at the bottom of the window, then go back to System Settings → Sound and reselect internal speakers directly. This utility is a secondary check, worth opening only after the standard Sound settings and CoreAudio restart haven’t solved things, but it catches a specific class of routing problem that nothing else in this guide will.
Bluetooth is one of the most common invisible causes of MacBook speakers not working, because macOS doesn’t always fall back cleanly to internal speakers once a paired device disconnects. You hang up a call on paired earbuds, walk away, and the MacBook stays silent even though nothing is actively connected anymore.
Open Control Center, click Bluetooth, and check for any device still listed as connected or recently used. Turn Bluetooth off completely for ten seconds, then back on. If a specific device keeps causing this, go to System Settings → Bluetooth, click the info button next to that device, and select “Forget This Device” to fully clear the pairing rather than just disconnecting it.
For a more complete reset, turn off Bluetooth, restart the Mac, and leave Bluetooth off for your first test. If speakers work with Bluetooth disabled and fail again once you turn it back on, you’ve confirmed the module itself, or a specific paired device, is the trigger. Re-pair the device from scratch afterward rather than relying on the old pairing, since a corrupted pairing profile is often what caused the routing conflict in the first place.
Corrupted file permissions rarely cause audio problems on modern macOS versions, since Apple’s APFS file system and System Integrity Protection lock down core system files more tightly than older HFS+ setups did. Still, permission conflicts in your own user-level Library folder can occasionally interfere with how audio preferences load at login.
Open Terminal and run sudo killall coreaudiod first, since that alone resolves most cases people assume are permission-related. If sound still won’t work and you suspect a deeper conflict, check Disk Utility’s First Aid tool by selecting your startup disk and clicking Run under the First Aid tab. This scans your APFS volume for structural errors, though it addresses disk health generally rather than audio permissions specifically, since macOS doesn’t expose a direct command for repairing audio-file permissions the way older systems once did with the disk utility’s “Repair Disk Permissions” feature.
If First Aid reports errors it can’t fix while the Mac is running normally, that’s a signal worth taking seriously beyond just the sound issue, since it points toward broader file system problems on the drive itself.
Third-party apps cause more silent-speaker cases than most users expect, usually by installing a virtual audio driver or grabbing exclusive control of the audio stream. Conferencing tools, screen recording software, DJ and music production apps, and some VPN clients with built-in audio routing features are the most frequent offenders.
These apps typically install a virtual audio device that sits alongside your real speakers in the Sound settings output list. If that app crashes or exits improperly, its virtual device can get stuck as the active output selection, and macOS keeps trying to send audio there instead of falling back to internal speakers automatically.
The fix is usually straightforward: check System Settings → Sound → Output for any unfamiliar device names, especially ones referencing recording or streaming software you don’t remember installing intentionally. Reselect internal speakers manually, then quit and reopen the suspect app to see if it recreates the conflict. If it does consistently, updating that app or removing it entirely resolves the loop. Safe Mode, covered earlier, remains the fastest way to confirm a third-party conflict is the actual cause before you go hunting through individual apps one by one.
Since 2006, we’ve watched the same pattern repeat across thousands of MacBook speaker complaints walking through our doors in West LA: the overwhelming majority resolve through software, not parts. Genuine hardware failure, a blown driver, corroded audio IC, or optical jack that won’t clear, makes up a smaller slice of what we see, but it does require component-level work rather than another restart.
That’s exactly why we run Free Diagnostics before quoting anything. If your MacBook needs a board-level fix, our policy is simple: no recovery, no charge applies to data recovery work, and diagnostics never cost you anything upfront regardless of what we find.
One thing we’ll say plainly: if silence coincides with any liquid exposure, or you’re worried about the data on that drive, stop all disk writes immediately. Don’t keep restarting, don’t run more diagnostics scripts, just power it down and call. We offer same-day appointments specifically because corrosion and drive stress compound with every hour a wet or failing Mac stays powered on.
— Kaya
If you’ve run through CoreAudio restarts, NVRAM resets, and Safe Mode testing and your MacBook is still silent, you’re looking at a hardware issue that needs hands-on diagnosis, not another software trick. Macwestlosangeles has been handling exactly this kind of speaker module replacement, audio IC repair, and logic board work since 2006, right from our shop at 12041 Wilshire Blvd, Ste 26, sitting between the 405 and Santa Monica, minutes from UCLA and the Getty Center. We serve Brentwood, Westwood, Venice, Hollywood, and Culver City in addition to West LA, Santa Monica, and Beverly Hills.
Every repair starts with Free Diagnostics, so you know exactly what’s wrong before you commit to anything, and our no recovery, no charge policy protects you if data recovery is part of the job. We offer same-day appointments for speaker failures, liquid damage, and logic board issues, because a Mac sitting dead on a shelf for a week helps nobody. Call 310-866-0828 to book a diagnostic slot, or check out our MacBook repair service page to see what a typical drop-off and turnaround looks like before you come in.
Apple’s own guidance covers the fundamentals well: start with internal speaker troubleshooting for output and connection checks, then run Apple Diagnostics if software steps don’t resolve anything. For the specific optical-jack red light issue, the iFixit community thread documents the exact symptom and workaround in detail.
Restart CoreAudio with sudo killall coreaudiod in Terminal, or restart the Mac entirely. On Intel MacBooks, an NVRAM reset (Option + Command + P + R at startup) often clears persistent audio configuration problems.
Check System Settings → Sound → Output to confirm internal speakers, not a disconnected Bluetooth device or phantom HDMI monitor, are actually selected. macOS sometimes keeps routing audio to a device that’s no longer active until you manually reselect the correct output.
Rule out mute and volume first, then check the headphone jack for a red optical light, since a stuck optical switch silences internal speakers completely. If the red light won’t clear after several insert-and-remove attempts, the fault is hardware and needs professional repair.
Run through volume checks, disconnect external devices, restart CoreAudio, and test in Safe Mode to rule out third-party software conflicts. If sound stays silent after all of that, run Apple Diagnostics and book a same-day diagnostic appointment with Macwestlosangeles if it flags a hardware fault.
It’s usually software. Misrouted output, Bluetooth conflicts, and stuck configuration cause the majority of cases, while true hardware failure, a damaged speaker or stuck optical jack switch, accounts for a smaller share that needs professional repair.
Follow a data-first sequence to cool a Mac safely after thermal shutdown, stop disk writes…
Protect your files first. Use a five minute checklist to fix a read only external…
Learn safe, model aware iMac power supply repair: LED 1 checks, a 10 second capacitor…
SD card unreadable? Stop using it and image the card first to preserve files. Run…
Protect files and fix the Mac prohibitory symbol. Follow Recovery and Disk Utility steps, and…
Stop disk writes and locate your password, Apple ID, or 24-character recovery key to unlock…