Mac Screen Recording Has No Sound? Fix It

The short answer

First decide what is missing: your voice, the computer’s sound, or all playback. Test each source separately. Then check permissions and the selected device, inspect the saved source, and compare it with the final export.

LumaTake Cleanup panel for filler words, silence, and audio. Beta interface may change.

Start with the symptom you can reproduce

Audio diagnosis
Symptom	First check	Next test
Voice is missing; app sound works	Microphone selection, mute state, and permission	Record spoken words with system audio off.
Voice works; app sound is missing	System-audio source and the app’s own playback	Record app sound with the microphone off.
Both seem missing	Playback output and volume, then captured tracks	Play a known-good file through the same output.
Source sounds fine; export is silent	Editor track mute, gain, and export choices	Export a short section with the intended audio enabled.
Sound is doubled or echoing	Speakers feeding the microphone, or duplicate sources	Use headphones and isolate each source.

If your voice is missing

Confirm the selected microphone is the device in front of you. A disconnected headset, changed USB device, or another available input can leave the recorder listening somewhere else. Check that the microphone is enabled and that the app has the required macOS permission.

After changing permissions or reconnecting hardware, reopen the recording session and make a fresh sample. A moving input meter is useful evidence, but the saved file is the check that matters. Do not proceed with a long take until spoken words are audible in that file.

If computer sound is missing

Play a short, recognizable sound in the app you are demonstrating. Confirm that your recorder supports system-audio capture for the selected source and that the option is enabled. If you are recording a window, ensure it is still the intended window.

Built-in Mac controls differ by version. Consult Apple’s current recording options; do not assume that selecting a microphone captures app sound. LumaTake’s audio controls provide separate microphone and system-audio choices.

If the problem appears only after editing

Compare the source recording with the exported file at the same moment. Inspect track mute, gain, and the edit range. If an audio track was cut or disabled, increasing the computer’s playback volume will not bring it back.

Temporarily simplify the edit to isolate the problem: one short section, the intended audio sources, and no unnecessary processing. Keep the original project so the diagnostic export does not replace your work.

Know when the source never existed

If the original file has no captured signal for the missing source, noise reduction or normalization cannot reconstruct it. Re-record the passage or add a new voiceover where appropriate. If the signal exists but is quiet, a level adjustment may help; listen for distortion and noise.

For the next take, use headphones and a repeatable source check. Capturing correctly once is less work than trying to repair an entire silent lesson.

Questions about this workflow

Will enabling the microphone capture internal audio?

Not directly. It can pick up sound from your speakers, but that is a room recording. Use a supported system-audio source for direct app sound.

Why did the microphone stop after changing devices?

The recorder may still have the previous input selected. Choose the current device again, check permissions, and verify a new saved sample.

Can I fix the file if it never recorded any sound?

You can add newly recorded narration or another appropriate audio source, but you cannot recover an uncaptured signal from the silent video itself.

About this guide

Published by LumaTake, the product described on this site. This guide covers LumaTake’s recording, editing, and publishing workflows. Platform account requirements and supported formats can change.