Your Mac recording came out silent — how to find out why
The call is over and the file is quiet. Before you try anything, work out which kind of silence you have — completely empty, or missing only the other person. They have different causes and only one of them is a settings problem.
- If the recording has your voice but not the other person’s, nothing is broken. QuickTime, Voice Memos and ⌘⇧5 record microphones only. Apple’s doc for the screenshot toolbar lists one audio control: “Below Microphone, select the microphone you want to use so that a checkmark appears next to it. To turn off the microphone, select None.”
- A virtual audio device like BlackHole has to be chosen twice — as your Mac’s output, and as the recorder’s input. Set only the output and you get a silent file and silent headphones.
- Closing a MacBook’s lid cuts the microphone in hardware. Apple’s platform security doc says the design prevents “any software—even with root or kernel privileges in macOS” from engaging the mic while the lid is shut.
- macOS 26 Tahoe’s built-in screen recording captures only the left channel from several external interfaces (Focusrite Scarlett 8i6, 4i4, Vocaster One, Apogee Symphony Desktop), and the reporter confirmed it still happens on 26.1.
- No software can recover audio that was never captured. The most useful thing a recorder can do is check the finished file against what it captured and tell you it is short — which is what Narada’s Incomplete verdict is.
Two different problems get described as “no sound”, and they need different fixes. Play the file and listen for yourself: if you can hear your own voice but not the other person’s, the tool you used was never capable of capturing them, and no setting will change that. If the file is entirely empty, something in the chain was pointed at the wrong place or switched off.
Work through the table, then read the matching section.
Start here
| What you hear in the file | Most likely cause | Section |
|---|---|---|
| Your voice, nobody else’s | The tool records microphones only | 1 |
| Nothing at all, from a screen or audio recorder | Input set to None, or to a device with no signal | 2 |
| Nothing at all, and you installed BlackHole or Loopback | The virtual device is your output but not the recorder’s input | 3 |
| Nothing at all, from a third-party app that used to work | Missing or stale System Audio Recording permission | 4 |
| Your voice missing, other side present | The microphone was off — possibly in hardware | 5 |
| One channel only, or a file that starts and then goes dead | A device conflict, or one of two current macOS defects | 6 |
1. The tool only ever recorded your microphone
This is the common case and it is not a misconfiguration. macOS treats sound going into a microphone and sound coming out of your speakers as separate things with separate privacy rules, and Apple does not expose the second one in its own recording tools.
You can check the documentation rather than take my word for it. Apple’s page for the macOS screenshot toolbar gives exactly one audio instruction: “Below Microphone, select the microphone you want to use so that a checkmark appears next to it. To turn off the microphone, select None.” QuickTime Player’s audio recorder lists two controls, “Microphone: Choose a microphone (if you have more than one available)" and a Quality setting. That is the whole surface.
So a ⌘⇧5 recording of a Zoom call contains you, plus whatever leaked out of your speakers into the mic. If you were wearing headphones there is no leak path, which is why the file sounds like a monologue.
The test: does the file contain your voice, at normal volume, and nothing else? Then this is your cause and the fix is a different tool. Recording system audio on a Mac covers the two routes that work.
2. The input was None, or the wrong device
Check the setting rather than assuming it. ⌘⇧5's audio menu has a None entry, and a recorder left on it produces exactly this file. Same for the device itself: an app can be politely recording from a webcam mic in another room, or from an interface whose input gain is at zero.
The test, which takes about fifteen seconds:
- System Settings → Sound → Input.
- Select the device your recorder is set to use.
- Talk, or play a video if the device is a loopback device.
- Watch the input level bar.
If the bar does not move, no recorder is going to hear anything. The problem is upstream of your software. If it does move, the device is fine and the recorder’s own input selection is what to look at next.
While you are at it: macOS shows an orange dot near the menu bar whenever something is using the microphone. If you record and no dot appears, the mic was never opened.
3. BlackHole is your output, but nothing is listening
The virtual-device route has one step people miss. BlackHole is, in its own vendor’s words, “a modern macOS virtual audio loopback driver that allows applications to pass audio to other applications with zero additional latency”. Loopback means it has an output side and an input side, and you have to wire both.
The usual failure looks like this: output switched to BlackHole, recorder left on the built-in microphone. Your Mac’s audio dutifully goes into BlackHole, your headphones go quiet, and the recorder captures a room. You get a silent file and a silent call, which is how people notice.
The correct arrangement:
- In Audio MIDI Setup, build a Multi-Output Device containing your real output and BlackHole. Skip this and you record the audio without hearing it.
- Set your Mac’s output to that Multi-Output Device.
- In the recorder, set the input to BlackHole.
- Check step 3 again. It is the one that gets forgotten.
4. The permission is missing, or was granted to a version that no longer counts
Any third-party app capturing your Mac’s output needs a real macOS permission for it. Apple’s own wording: “Some apps and websites can access and record the screen and audio on your Mac… You can allow apps to record both your screen and audio, or just your audio.”
Go to System Settings → Privacy & Security → Screen & System Audio Recording and look for the app. Three things worth knowing:
- If you remember granting something years ago under a differently named entry, check that it is still listed here. Old grants do not always survive a macOS upgrade.
- Toggles sometimes refuse to stick. Removing the app from the list with the minus button, quitting it completely, and relaunching so it asks again works more reliably than fighting the switch.
- Apps installed through Homebrew and run from a symlink can show up greyed out or not at all.
An audio-only recorder still lives in this panel, because Apple put screen and audio behind one control. That is not a sign the app is recording your screen.
5. The microphone was off, and nothing told you
Several unrelated ways to end up here:
- You muted yourself in the meeting app. Zoom’s mute is a client-side mute, so the mic still opens and still captures — but a hardware mute button on a headset or interface cuts the signal, and so does a physical switch. Different failure, same silent result.
- The lid was closed. This is a hardware fact, not a setting. Apple’s platform security documentation describes a hardware microphone disconnect on all Apple-silicon Mac laptops and Intel laptops with the T2 chip: the mic is turned off whenever the lid is closed, and the design prevents “any software—even with root or kernel privileges in macOS” from engaging it.
caffeinatekeeps your Mac awake. It does not bring the microphone back. For a long in-person recording with the lid shut, use an external USB mic. - Input volume at zero, in Sound → Input, usually after someone used the machine for something else.
6. A device conflict, or one of two current macOS defects
If the file starts fine and then dies, or arrives with one channel, you are past the configuration causes.
Something else claimed the device. Some interfaces and virtual drivers do not share nicely, and a conference app that grabs the input can leave a second recorder with nothing. Quit everything, start the recorder first, then the meeting app, and see whether the level meter behaves differently.
Tahoe's left-channel defect. Apple’s built-in screen recording captures only the left channel from several external multichannel interfaces — reported on Focusrite Scarlett 8i6 (3rd gen), 4i4, Vocaster One, Apogee Symphony Desktop and UAD hardware, with the poster’s own summary: “Audio is recorded only in the left channel (Input 1). The right channel is silent.” OBS captures stereo correctly from the same hardware, so it is not the interface. The reporter confirmed the problem survived into macOS 26.1.
The Sequoia zero-buffer regression. A developer report on Apple’s forums describes HAL-plugin system-audio capture going silent on macOS 15: “with the latest macOS 15 Sequoia, all audio buffer values are zero.” It was filed as FB15620713, and the workaround — set the default audio device after the capture session starts running — belongs to the app, not to you. If a capture tool you rely on went silent around that macOS, that is the bug to point its developer at.
Two minutes before the call that matters
Do this once and most of this page stops applying to you:
- Start a test recording with the exact setup you intend to use, headphones included.
- Play something with sound, and say a sentence.
- Stop, and listen to the file. Not the level meter, not the app’s “saved” message. The file.
- Confirm you can hear both your voice and the other audio.
That one file catches every configuration cause above — sections 1 to 5. What it cannot catch is a recording that starts correctly and dies halfway through, which is section 6.
What no tool can fix, and what a good one does instead
Audio that was never captured is gone. There is no repair path, no undelete, no reconstruction — a silent file has nothing in it to recover. This is worth being blunt about, because a lot of pages on this subject imply otherwise.
What software can do is stop lying to you about it. macOS audio genuinely fails mid-recording: another process reshapes the device graph, a Bluetooth route changes, Core Audio drops cycles under load. When that happens, the usual outcome is a file that opens, plays, and holds a fraction of the meeting, presented as a completed recording.
Narada is a meetings recorder that captures your microphone and your Mac’s output as two separate streams, with no virtual device to install and no Screen Recording permission — it uses a Core Audio process tap, so it asks for Microphone and System Audio Recording only. It is not immune to any of the above. What it does is compare each finished recording against what the capture reported submitting, and when the numbers disagree it marks the recording Incomplete and names the reason: microphone stopped early, system audio stopped early, device stalled, gap between parts. It cannot get the audio back. It can stop you finding out three weeks later that the file you were relying on is four minutes long.
Recording is free in Narada; the requirement is macOS 15.6 or newer.
Sources
- Apple Support, Take a screenshot or screen recording on Mac — “Below Microphone, select the microphone you want to use so that a checkmark appears next to it. To turn off the microphone, select None.” — https://support.apple.com/guide/mac-help/take-a-screenshot-or-screen-recording-mh26782/mac
- Apple Support, Record audio in QuickTime Player on Mac — the Microphone and Quality controls, and nothing else — https://support.apple.com/guide/quicktime-player/record-audio-qtpf25d6f827/mac
- Apple Support, Control access to screen and system audio recording on Mac — “You can allow apps to record both your screen and audio, or just your audio.” — https://support.apple.com/guide/mac-help/control-access-screen-system-audio-recording-mchld6aa7d23/mac
- Apple Platform Security, Hardware microphone disconnect — lid-closed mic cut-off on Apple-silicon and T2 laptops — https://support.apple.com/guide/security/hardware-microphone-disconnect-secbbd20b00b/web
- Existential Audio, BlackHole — “a modern macOS virtual audio loopback driver…" — https://existential.audio/blackhole/
- Apple Community thread 256163770 — Tahoe left-channel-only screen recording with external interfaces, still present on 26.1 — https://discussions.apple.com/thread/256163770
- Apple Developer Forums thread 767333 — “all audio buffer values are zero” on macOS 15 Sequoia, FB15620713 — https://developer.apple.com/forums/thread/767333
Every one of these was fetched and checked on 4 August 2026.
Questions people ask about this
Why does my Mac screen recording have no sound?
Most often because the built-in recorder only captures a microphone. Apple’s help text for the screenshot toolbar offers a Microphone menu and a None option, and nothing else — so if you were recording a video call, the other side’s audio was never in scope. If your own voice is missing too, the input was set to None or pointed at a device that was not picking you up.
How do I test whether my Mac is actually capturing audio?
Open System Settings → Sound → Input, pick the device your recorder is using, and speak or play something. The input level bar moves when audio is arriving. If it does not move there, no recorder will hear anything either.
I installed BlackHole and the recording is still silent. What did I miss?
Almost always the input side. BlackHole is a loopback device, so it has to be your Mac’s output and the recorder’s selected input. If you only changed the output, the audio went into BlackHole and nobody was listening at the other end.
Can I get the missing audio back?
No. If it was never written to the file, it does not exist anywhere. You can sometimes recover a file that plays at the wrong speed or a file whose header is wrong, but silence is silence.
Does a mid-recording failure ever happen on macOS even with the right setup?
Yes. Audio devices get reshaped by other apps, Bluetooth routes change, and Core Audio can drop cycles under load — any of which can end one stream while the recording appears to continue. That is why it is worth using a tool that measures the finished file instead of assuming it worked.
Try it on your next call
Narada records your Mac's audio and your microphone, transcribes on-device, and hands you the decisions and follow-ups. Free to use, no account, no bot in the meeting.