Why Your Screen Recording Has No Sound (and How to Fix It)
You turned system audio on, hit record, and the video came back silent anyway. Here is why that happens depending on whether you capture a tab, a window, or your whole desktop — and what to do about it.
You toggle system audio on, hit record, do the walkthrough, and export — and the video plays back with no computer sound at all. Your narration might still be there if the mic was on, but the app noise, the video you were reacting to, the notification sound you wanted to demonstrate — gone. It feels like a bug. Most of the time, it isn’t.
What you’re running into is a real, long-standing limitation in how browsers capture audio, and it changes depending on what you choose to record, not just whether you flipped a toggle.
Three ways to capture, three different audio paths
When you record your screen, you’re usually choosing between three sources — a browser tab, an application window, or your entire desktop. They sound like three flavors of the same thing. Under the hood, they get your audio in completely different ways.
- A browser tab has its own dedicated audio graph inside Chrome. When you capture a tab, the browser hands you that tab’s sound directly — no operating system involvement required. This is why tab audio is the most reliable option: it works essentially the same way on every platform, and it’s usually preselected for you.
- A window or your entire desktop works differently. There’s no single app graph to tap into — the browser has to ask the operating system for a copy of whatever audio is currently playing on the system, a feature usually called loopback audio. Whether that’s even possible depends entirely on the OS.
That second part is the whole story. Windows and ChromeOS expose a system-level audio loopback that browsers can use, so capturing your entire screen (or, on newer Chrome versions, a specific window) with sound generally works. macOS has never exposed anything equivalent at the OS level — there’s no built-in way for an application to “listen in” on the Mac’s system audio output without a separate virtual-audio-device driver. That’s not a Chrome bug or a ScreenKit limitation; it’s a gap in how the operating system itself is built, and it’s the same reason dedicated Mac utilities like BlackHole or Soundflower exist in the first place — to plug a hole the OS leaves open.
Why this isn’t something an extension can patch over
It’s tempting to assume a “good enough” recorder should just handle this, but no browser-based tool can request audio the operating system won’t hand over. If you’re capturing your whole desktop or a specific window on a Mac, there is currently no system audio to capture — full stop, regardless of which extension or app you’re using. Tab capture sidesteps the whole problem because it never asks the OS for anything; it takes the audio straight from the tab that’s already playing inside the browser.
That’s a useful rule of thumb if system audio is the one thing you actually need in a given recording: when you can capture the tab instead of the window or the whole screen, do it. If you’re demoing a web app or reacting to a video playing in a browser tab, tab capture gets you sound with the least friction on every platform.
What happens when the recorder can’t get the audio it asked for
Even when audio should be available, a display or window picker can still reject the request — a driver quirk, a permissions prompt the user dismissed, an OS version that doesn’t support it for that particular surface. Rather than fail the whole recording over an audio track it can’t get, ScreenKit falls back to capturing video only and lets the recording continue. That’s the sensible behavior — a silent recording beats no recording — but it also means you won’t get an error message telling you what happened. The capture just quietly proceeds without sound.
That’s exactly why the quick five-second test recording is worth doing every time you change what you’re capturing, not just once when you first set up your microphone. A test that passes for a tab capture doesn’t tell you anything about whether a desktop capture on the same machine will include sound.
A quick reference
- Recording a tab and need its sound? This is the safest combination on any platform — tab audio capture doesn’t depend on OS-level loopback support at all.
- Recording a window or your whole desktop on Windows or ChromeOS? System audio is generally available; make sure the toggle is on before you start.
- Recording a window or your whole desktop on a Mac? Don’t count on system audio coming through. If the sound matters, switch to capturing the specific browser tab instead, or plan to narrate over the recording with your microphone.
- Recording came out silent and you’re not sure why? Check which source you captured first — it’s the most common explanation, more common than a missed toggle or a permissions issue.
The takeaway
A silent recording usually isn’t a sign that something went wrong with your recording setup — it’s a sign that the combination of capture source and operating system you picked doesn’t support system audio in the first place. Once you know that tab capture is the one path that works everywhere, you can choose your capture source with sound in mind instead of finding out after the fact.
Recording something that needs its sound? Add ScreenKit to Chrome and capture tab, window, or desktop video with microphone and system audio — free, local, and no watermark.