Screen recording has no sound? Check these steps in order

Contents
- The problem
- The fix
- Common sticking points
- Bottom line
- The technical mechanics: why this happens
- Screen share modes compared, and whether each one supports audio
- 5 critical audio mistakes people make when recording
- Zero audio accidents: a 5-step workflow for a flawless recording
- 7 advanced recording tips
- Final Audio-Sharing Decision Tree: The Best Choice for Each Situation
- Terminology Cheatsheet
- Frequently Asked Questions
If you recorded your screen in the browser and none of the music or video audio came through, the cause usually isn't microphone permission — it's that you never turned on screen (system and tab) audio sharing. Microphone recording and screen audio recording are completely separate permissions inside the browser, so allowing the mic doesn't automatically capture whatever was playing. Depending on how you shared your screen, the audio checkbox may not even appear. Reopen the share window and check the steps in order, and most cases clear up.
Quick summary ① Sound in a screen recording comes from two completely separate permissions: microphone audio and screen (system and tab) audio. ② In the screen share window, choose Tab or Entire Screen instead of Window — that's what makes the audio sharing checkbox appear. ③ Even when the checkbox shows up, it's often off by default. If you don't check it yourself, the screen records but the audio saves as silence.
The problem
You're recording a video tutorial or some gameplay with a screen recorder. You finish, open the file, and the picture is fine — but there's no sound at all. This happens even though you could hear the music or video clearly through your speakers the whole time you were recording.
At that point a lot of people assume it's a mic problem and go recheck microphone permissions. But the mic is a separate track that captures your voice, and it has nothing to do with background audio that's playing. The real cause is almost always that you never asked to share audio in the browser's screen share popup, or that the thing you shared (window, tab, or full screen) is a type that doesn't support audio.
That permission isn't decided by the web page's code — it's decided in the native picker the browser itself shows. So whatever tool you use (a screen recorder extension, the record feature in a video meeting app, and so on), you hit the same wall the same way, and you get past it the same way.
The fix
You don't need another tool. Just follow these steps in order and most cases resolve.
- Start by picking a different way to share. When the screen share popup opens, you'll usually see tabs across the top: 'Entire Screen / Window / Tab'. Sharing a single app window often doesn't show the audio checkbox at all, so choose Tab or Entire Screen instead.
- Turn on the audio checkbox yourself. Below the list of things you can share there's a checkbox labeled 'Share audio' or 'Share tab audio', and many browsers leave it off by default, so it's easy to miss. Look at it with your own eyes and confirm it's checked before you start sharing.
- Make sure you're sharing the tab that's actually making noise. If you have several tabs open and the music is coming from one of them, sharing a different tab captures nothing. Also click the speaker icon on the tab to check that the tab isn't muted on its own.
- If you want your voice in the recording too, turn on the mic option separately. Microphone recording is a completely separate permission from screen audio, so if your recording tool has an option like 'Record microphone audio too', you have to switch it on to get your voice mixed in. Your voice won't come through from screen audio alone.
- If mic access is denied or you don't have a mic, the recording doesn't stop. It keeps going with screen audio only, just without your voice.
You can walk through these steps exactly as written with our tool.
Free · no install · record your screen and sound right in the browser

Common sticking points
| Situation | Cause | Fix |
|---|---|---|
| Sharing a single window (one app) | The audio sharing checkbox never appears | Start sharing again and pick Tab or Entire Screen |
| Saw the checkbox but didn't click it | It's off by default | Click the checkbox yourself before you start sharing |
| Only turned on the mic option | Mic and screen audio are separate permissions | Check the audio sharing checkbox as well |
| Audio is playing in a different tab than the one you shared | The shared tab and the tab playing sound aren't the same | Select the exact tab the sound is actually coming from |
| Mic permission denied or no mic | Only the voice track is missing | Screen audio still records normally |
Bottom line
When a screen recording comes out silent, it's usually not a malfunction — it's the order in which you handle permissions. Remember that the mic captures your voice and screen (tab or system) audio sharing handles whatever is playing; they're different switches. Switch your share mode to Tab or Entire Screen and turn on the audio checkbox, and that alone fixes most cases.
Free · no install · record your screen and sound right in the browser
The technical mechanics: why this happens
Capturing screen and audio in the browser looks like a simple button click, but underneath there's a whole layer of permission control and APIs. Understanding why the permissions are split, and why audio doesn't come through in 'Window' mode, is the first step toward a flawless recording.
How the Web MediaDevices API splits things up
The two most important APIs for handling media streams on the web are getUserMedia and getDisplayMedia.
- getUserMedia: Used to access physical hardware input devices such as webcams and microphones. It handles capturing the user's voice (microphone) and nothing else.
- getDisplayMedia: Used to capture a visual display surface (Display Surface) — screen, window, or tab — along with the audio that comes from it.
These two APIs work completely separately for security and privacy reasons. So allowing microphone permission doesn't record the sound from your screen, and accepting screen audio sharing doesn't record your voice through the mic. To combine the two, you have to call both APIs and then merge (mix) the audio tracks programmatically.
MediaStream and audio tracks
When you successfully accept screen and audio sharing through getDisplayMedia, the browser returns a MediaStream object. Inside that object, the video track and the audio track are each stored as arrays.
If the user didn't click the audio sharing checkbox, no audio track is created in that MediaStream at all, or it arrives empty. The recorder only has a video track, so it encodes into a container format such as WebM — which means the final file physically contains no audio stream.
OS-level audio routing and the limits of window capture
This is where a lot of people get stuck. "Why can I share audio from a tab or the entire screen, but when I capture a specific app window, the audio sharing checkbox doesn't even show up?" That goes beyond browser limits and into the audio architecture of the operating system (Windows, macOS, Linux). An OS can easily intercept the master audio mix coming out of the whole system (entire screen audio sharing), and a browser can separate out the audio nodes of tabs it renders itself (tab audio sharing). But extracting and intercepting only the audio coming from one specific application outside the browser (for example, a KakaoTalk window, an Excel window, or a Steam game window) is very difficult, both for security and structural reasons, without an advanced OS-level audio loopback API or a virtual audio cable driver. That's why major browsers such as Chrome simply disable audio capture in 'Window' share mode and hide the checkbox.
WebM and the Opus codec
The captured screen and audio tracks are compressed (encoded) by the browser's built-in media recorder (MediaRecorder). The audio almost always uses the 'Opus' codec. Opus is a next-generation audio codec that delivers both ultra-low latency and high sound quality, and its compression efficiency is excellent — it captures very clean audio without inflating the video file size much when you record your screen. If the audio track is missing, that Opus compression step never runs at all.
Screen share modes compared, and whether each one supports audio
When you record your screen, the browser offers three share modes (tab, window, entire screen). Compare what each one does and whether it captures audio, then pick the right mode for the job.
| Share mode (surface) | Audio supported? | What audio gets captured | Best use case | Critical limits and drawbacks |
|---|---|---|---|---|
| Chrome/Edge tab (Tab) | Yes (O) | Only the sound playing inside the tab you selected. | Recording a single web page such as a web app (Figma, a browser game) or a YouTube video. Best for privacy. | If you switch to another tab or an outside app, both the video and the audio cut out. |
| Window | No (X) | Audio capture is impossible. (The checkbox doesn't even appear.) | Silent tutorials, Excel screens, and other purely visual content where no sound is needed. | All audio is blocked at the source. Never use it when you need sound. |
| Entire screen | Yes (O) (varies by OS) | Everything the computer sends to your speakers: system pings, messenger notification sounds, and all other audio. | Complex tutorials where you move between several programs and browser windows while explaining. | It also records private system sounds, like KakaoTalk notification chimes and error beeps you didn't want. (Limited in some environments, such as macOS.) |
As the table shows, choosing Window mode on a recording that needs audio is the root cause of every problem. Always pick Tab or Entire screen, and turn the audio permission on.
5 critical audio mistakes people make when recording
Even with great gear and good tools, one small slip can ruin the whole result. Check yourself against the five most common audio recording mistakes.
- Falling for Window share mode: You think, "I'll show just this window, nice and clean," pick Window mode, and record without ever noticing there's no audio checkbox. It's the most common mistake and the most damaging.
- Ignoring the share audio checkbox: You picked Tab or Entire screen, but you click Share on autopilot without ticking the small "Share tab audio" or "Share system audio" checkbox tucked at the bottom. Many browsers don't turn it on by default.
- Missing that the source tab is muted: You right-clicked the browser tab and chose "Mute site," or the web player (YouTube, for example) is set to volume 0, and you record anyway. An audio track gets created, but at zero volume, so you end up with silence.
- Confusing the microphone with system audio: You assume, "I allowed microphone access, so the computer's sound will be recorded too." The microphone only picks up your voice. Sound playing inside the computer doesn't get recorded cleanly unless it leaves the speakers and comes back in through the mic (which causes echo).
- Recording for a long time with no test first: You record an important hour-plus seminar or lecture and skip the 10-second test recording and audio check at the start. If something goes wrong, you can't get that back.
Zero audio accidents: a 5-step workflow for a flawless recording
If you have an important recording coming up where one mistake is one too many, drill this 5-step workflow until it's automatic.
- Step 1: Pre-check the source audio Before you record, listen through speakers or headphones to confirm the website or program you're recording actually plays sound, and check that the volume mixer isn't at 0.
- Step 2: Select your mode strategically In the popup that appears after you hit the screen record button, clearly choose either Chrome tab or Entire screen, whichever fits your goal. If you need audio, never click Window.
- Step 3: Turn the audio permission on explicitly Click the "Share tab audio" or "Share system audio" checkbox at the bottom of the popup and look for the blue checkmark before you click Share.
- Step 4: Decide whether to mix in the mic If you want to add your own commentary, turn on the "Turn on microphone" button in the recording tool's UI separately, and click Allow on the browser's mic access popup.
- Step 5: Run a 10-second micro test Before the real recording, record about 10–15 seconds of moving the screen and playing sound. Stop, open the file, and listen to confirm the audio is mixed with the left and right channels balanced. If it passes, start the real recording.
7 advanced recording tips
Beyond fixing missing audio, here are seven tricks the pros use to get studio-clean results.
- Wear headphones whenever the mic is on: If you play sound through speakers while the mic is on, the speakers feed back into the mic and cause howling and faint echo. Wear earbuds or headphones while recording for better audio quality.
- Turn on Do Not Disturb when capturing Entire screen: When you capture the entire screen with system audio, notification sounds from messengers like KakaoTalk, Slack, and Discord get recorded too. Turn on your OS's Do Not Disturb mode to block surprise audio interruptions.
- Use advanced tools to mix audio on separate tracks: With professional software like OBS Studio rather than the browser's built-in recorder, you can record game audio (desktop audio) and your voice (mic) on separate tracks, then adjust the volume of each one in post.
- Keep the tab focused while recording a tab: Some older browser engines stop (throttle) audio rendering for a shared tab when that tab goes to the background or becomes inactive, to save resources. Keep the source tab in the foreground when you can.
- Watch for sample rate mismatches: If you use an external audio interface, set the mic and speaker sample rates to 48000Hz (48kHz) in the Windows sound control panel. That prevents slight pitch shifts, sync drift, and popping noises in the recording.
- Leave headroom by keeping volume around 70–80%: If you record with system audio or YouTube playback at 100%, peaks can clip and distort the sound. Keeping the source volume near 70% is safer for headroom.
- Check Chrome vs. Edge vs. Safari compatibility: Tab audio sharing works most reliably in Chromium-based browsers (Chrome, Whale, Edge). Apple Safari and some mobile environments offer limited support for the tab audio sharing API, or handle it differently, so use Chrome for anything important.
Final Audio-Sharing Decision Tree: The Best Choice for Each Situation
Here's a practical decision tree that lets you pick the right sharing mode and audio setting in one second.
- Situation A: "I want to record web-based gameplay and capture only the game sound." ➔ Choose [Tab] + check [Share tab audio] + mic OFF. (The cleanest, most privacy-friendly setup.)
- Situation B: "I'm showing PPT slides and narrating a lecture in my own voice. The slides themselves have no sound." ➔ Choose [Entire screen] or [Window] + mic ON. (You don't need screen audio, so leaving it unchecked is fine.)
- Situation C: "I'm switching between an Excel window and a Zoom meeting, and I want to record both my voice and the other person's voice." ➔ Choose [Entire screen] + check [Share system audio] + mic ON. (The hardest setup, since it merges mixed system sound with your mic.)
- Situation D: "I'll record a silent Photoshop drawing session and add BGM in Premiere later." ➔ Choose [Window] + mic OFF. (Captures that single window perfectly, with no wasted audio resources.)
It looks complicated, but once you know this decision tree, you won't panic in any unexpected situation — you'll build the right audio setup every time.
Terminology Cheatsheet
Understanding the key terms around screen recording and web media technology will improve your troubleshooting skills exponentially.
- getDisplayMedia: The standard web API a browser calls to capture video and system audio from a screen, window, or tab. This API is what triggers the screen-sharing popup.
- getUserMedia: An API that directly accesses your webcam and microphone devices to get a media stream. Its security requirements are strict, so it only works over HTTPS.
- MediaStream: A pipeline object through which video and audio data flow in real time. The recorder (MediaRecorder) takes this stream and bakes it into a video file.
- Audio Track: An independent flow of sound data inside a MediaStream. When you record your screen, the mic track and the system audio track can exist separately.
- Tab Audio: Isolated audio that plays inside one specific browser tab, not the whole computer. It's a big win for privacy.
- System Audio: The sum of all sound mixed by the Windows or macOS operating system and sent to your speakers.
Frequently Asked Questions
Beyond missing audio, here are clear answers to the deeper questions that come up most often in real use.
Q1. I'm on a Mac (macOS), and when I share the "Entire screen," the system audio checkbox doesn't appear at all. Why?
A1. Because of macOS's sandboxed security architecture, Chrome is blocked by default from intercepting system-wide audio. To record full system audio on a Mac, you need to install virtual audio cable software such as BlackHole or Loopback and route your audio output through it. Note that when you use "Tab," tab audio still shows the checkbox and records normally on a Mac.
Q2. I turned on tab audio sharing and my mic at the same time, but in the recording my voice and the screen sound are slightly out of sync.
A2. This happens because of the latency difference between two different input sources: a virtual browser audio node and physical USB microphone hardware. Most browser-based recorders compensate internally, but if your CPU is overloaded and frames drop, the sync can drift. The fix is to close unnecessary background programs to free up system resources, and lower your recording resolution from 1080p to 720p to reduce the load.
Q3. I definitely checked the audio sharing box, but when I record a paid online course site or Netflix, the screen comes out black or there's no sound.
A3. That isn't a permissions mistake or a tool bug — it's blocked on purpose by DRM (Digital Rights Management). Netflix, Disney+, paid online course sites, and similar services use hardware-level DRM such as Widevine, which blocks the browser capture API (getDisplayMedia) from accessing their video and audio frames at the source. This is normal security behavior, and browser recording can't get around it.
This article was adapted from our Korean original. Read the Korean original