You've got the Mac in front of you, the screen recording finished, and the file is silent. Maybe your voice is there but the app audio vanished, or maybe QuickTime captured nothing at all and you're trying to figure out whether you missed a setting, a permission, or the whole point of the tool. On modern macOS, QuickTime screen recording no sound usually isn't a broken app, it's a mismatch between what QuickTime records by default and the audio path you needed.
Table of Contents
- Why QuickTime Screen Recording Captures No Sound
- Check Microphone Permissions and QuickTime Input
- Run a Three-Test Audio Diagnostic on Your Mac
- Capture System Audio With a Loopback Driver
- When to Skip QuickTime and Use a Dedicated Recorder
- Preventing No-Sound Failures After macOS Updates
Why QuickTime Screen Recording Captures No Sound
QuickTime's silent recordings usually come from a routing problem, not a broken recording workflow. On macOS, QuickTime records the screen first and treats audio as a separate input source that must be chosen before you hit record, so the app expects you to open File > New Screen Recording and pick a microphone from the dropdown instead of assuming sound is active by default (Apple Support discussion).
What QuickTime is actually doing
The app is straightforward, which is part of the problem. If you start recording with no microphone selected, the video saves cleanly and the audio path stays silent. The recording looks normal, plays back normally, and still contains no usable sound.
Practical rule: if the recording is silent, first check whether QuickTime had a valid input source at all. Don't assume the app lost sound after the fact.
The next distinction is between mic audio and system audio on Mac. Your voice can be captured through a physical microphone, but internal sound from Safari, Music, Zoom, or a browser tab usually needs separate routing because QuickTime does not tap the Mac's output stream directly (Apple Community guidance on screen recording audio). Users who expect one recorder to capture everything usually run into that gap right away.
Why the symptom looks random
It feels random because the video still saves. In practice, the failure is predictable, and the fix depends on which path broke, microphone, system audio, or both. That is why so many Mac troubleshooting guides separate the problem into different checks instead of offering one generic audio fix (Mackeeper).
If your goal is narration only, the useful checks are QuickTime's input menu and macOS permissions. If your goal is to capture app sounds, the issue stems from routing, not a checkbox. That distinction saves time because it keeps you from chasing the wrong path.
A post-update permission reset can create the same silent result. After some macOS updates, QuickTime may still open normally while its microphone access has been cleared or deferred, so the recording session starts with no usable audio input even though nothing else looks obviously broken. When that happens, the failure is a permissions change, not a microphone problem, and it needs to be treated separately.
Sponsored by the makers
Tired of boring screen recordings?
Try Screen Charm.
Auto-zoom, motion blur, camera overlay, and background music. All built in. Record once, export a polished video.
See what it doesCheck Microphone Permissions and QuickTime Input
QuickTime cannot record voice unless macOS grants it microphone access, and recent macOS updates sometimes clear or delay that permission without any obvious warning. Start in System Settings > Privacy & Security > Microphone, confirm that QuickTime is enabled, then quit QuickTime fully and open it again so the change takes effect.
Confirm the permission first
Open System Settings, go to Privacy & Security, then Microphone. If QuickTime is turned off there, enable it, then quit QuickTime completely and relaunch it. If the app stays open, macOS may keep using the old permission state even after you change the setting.
If you use a USB microphone and need a practical setup reference, set up a USB mic on Mac walks through getting the device recognized before you chase QuickTime itself. For a fast local check, use the microphone test to confirm that the input is live before you open QuickTime again.
Then choose the input inside QuickTime
In QuickTime Player, go to File > New Screen Recording and click the small dropdown beside the record button. Choose Built-in Microphone or your external input before you start recording, because the selected input can stay wrong even after microphone access is allowed (Apple Support discussion).
If the dropdown stays on the wrong source, QuickTime can save a clean video file with no usable audio track.
A quick check usually tells you enough. Record a few seconds of speech, stop, then play it back right away. If your voice is audible, the microphone path is working and you can stop there. If the clip is silent, the problem is usually permission, input selection, or another app holding the microphone open.
For a clean device-specific troubleshooting sequence, the sound recording test guide is a useful companion because it follows the same test, replay, isolate approach used in real Mac support cases.
Run a Three-Test Audio Diagnostic on Your Mac
Don't debug this as one problem. Split it into mic-only, system-audio-only, and combined-audio tests, because each one points to a different failure class and saves you from swapping settings blindly.
Test the microphone path
First, record a few seconds of speech with the currently selected QuickTime input. If that file plays back with audible voice, the mic path is healthy. If it's silent or distorted, you're dealing with a permission, device, or app-conflict issue, not a loopback problem (SmoothCapture).
Test the system-audio path
Next, play a known Mac sound, then record while it's happening. A notification chime, a short track in Music, or another obvious internal audio source works as long as it's something you can identify on replay. If the clip comes back silent even though the Mac was making sound, the issue isn't your microphone, it's the way QuickTime handles internal audio on macOS (Apple Community guidance).
Diagnostic shortcut: voice working but app sound missing almost always means system-audio routing is the problem.
Test both together
Finally, record both at once. This catches mixed failures, where your mic works but internal audio does not, or where a recent permission change only broke one path. That combination test is especially useful after an update or a device change because it shows whether the failure is isolated or broad.
| Test | What to listen for | Likely branch |
|---|---|---|
| Mic only | Your voice is audible | Permission or input device |
| System audio only | App or Mac sound is audible | Loopback routing |
| Combined | Both sources stay audible | Setup is stable |
If you want a reference point for isolating recording issues on a Mac, sound recording test guide lays out the same kind of immediate replay check that works well before long sessions. The point is simple, a 30-second diagnostic beats ten minutes of guesswork.
Capture System Audio With a Loopback Driver
QuickTime can't grab Mac system audio on its own because it records from an input source, not from the Mac's output stream. To make internal sound recordable, you have to route it through a virtual loopback driver, then tell QuickTime to listen to that driver as if it were a microphone (Apple Community guidance).
BlackHole is the standard workaround
The common setup is BlackHole. Install the driver, open Audio MIDI Setup, and create a Multi-Output Device that includes both Built-in Output and BlackHole 2ch so you can hear audio while recording. Apple Community guidance specifically notes that both Built-in Output and BlackHole 2ch need to be included if you want monitoring and capture at the same time (Apple Community guidance on loopback routing).
After that, set macOS output to the Multi-Output Device, then return to QuickTime and choose BlackHole as the microphone in the recording dropdown. That creates the loop: system audio goes into BlackHole, QuickTime reads BlackHole as input, and the recording contains the internal sound.
A lot of people trip over small details here. The wrong channel count, a missing Drift Correction checkbox, or forgetting to relaunch after installing the driver can make the whole setup seem broken even when the parts are technically installed. The routing chain has to be exact.
What to use if BlackHole isn't your preference
If you want another path, iShowU Audio Capture is a common alternative. The trade-off is the same either way, extra setup buys you internal-audio capture inside QuickTime, but it also adds more places for macOS updates and device changes to break the chain.
The cleanest mental model is this. QuickTime takes a microphone input, not system output. Once you accept that, the rest of the setup makes sense instead of feeling arbitrary. For a more extended walkthrough of the routing side, capture system audio on Mac covers the same workflow in a dedicated guide.
When to Skip QuickTime and Use a Dedicated Recorder
QuickTime is fine when you only need a quick screen capture with your voice. It gets much less appealing when you need system audio regularly, because then you're maintaining drivers, routing devices, and permission state on every machine you touch. That setup time is exactly where support teams and course creators lose momentum.
The recurring pain is the workflow, not one broken setting
The same issues keep coming back. A macOS update resets permissions, the Multi-Output Device flips back to a different output, or the virtual driver needs attention again after a relaunch. Then you're back in Audio MIDI Setup instead of recording.
When the audio path matters every day, a recorder that treats internal sound as a first-class feature removes a lot of fragile setup.
For product demos, tutorials, and onboarding videos, that matters more than a pure QuickTime workflow. One option is studio-quality video in minutes if you're comparing recording styles and want to see how modern tools handle output more directly. Another is Screen Charm's QuickTime alternative, which records system audio natively, includes an editor, and is built for demo-style captures instead of driver juggling. Screen Charm also adds auto-zoom for product demos, which is useful when you're walking viewers through a UI and want the cursor movement to stay readable.
QuickTime's strength is still simplicity for basic screen plus mic recording. Its weakness is that it forces internal audio into a workaround. If you record product videos, lessons, or support walkthroughs often, that workaround becomes the primary cost.
Preventing No-Sound Failures After macOS Updates
Treat macOS updates as a reset event. After an update, microphone permissions can be cleared and audio routing can shift enough that the same QuickTime setup that worked yesterday now saves a silent file, as noted by ScreenCharm.
The post-update routine that helps
Use the same short sequence every time you update macOS:
- Re-check Microphone permission: Open System Settings > Privacy & Security > Microphone and make sure QuickTime is still allowed.
- Confirm the QuickTime input: Open File > New Screen Recording and verify the dropdown still points to the correct microphone.
- Verify the routing device: If you use BlackHole, reopen Audio MIDI Setup and make sure your Multi-Output Device still contains the expected outputs.
- Test immediately: Record a few seconds right after the update so you catch a break before a real session starts.
That routine matters because post-update failures keep state from the old setup only partway. QuickTime may open without complaint, while permissions or routing no longer match the machine you had before the update. On client Macs, that is the pattern I see most often, a clean launch followed by a silent file.
If your work is occasional and you only need your voice, QuickTime plus those two permission checks is enough. If you record system audio often, or you make demos and tutorials for a living, a dedicated recorder saves you from repeating the same repair after every major release. Mackeeper also points to the same practical split, voice-only recordings stay simpler, while system audio usually needs a different workflow.
