You finish a perfect take, hit stop, play it back — and there is no audio. A silent screen recording is one of the most frustrating problems in screen capture, partly because there is no single cause. The sound could be missing because of a toggle, a permission, a browser limitation, an OS setting, or even your headphones.
This guide walks through nine concrete fixes, in the order you should try them. Each one targets a specific reason a screen recorder ends up with no sound, so you can find your culprit quickly and get back to recording with both your microphone and your system audio working.
Diagnose it fast: symptom to fix
Before you change settings at random, match what you are hearing to its most likely cause. This table maps the three common symptoms — no audio at all, missing voice, or missing system sound — to the fix that usually solves them.
| Symptom | Likely cause | Fix |
|---|---|---|
| No sound at all | Audio toggles off or "share audio" unticked | Fixes 1 & 2 |
| My voice is missing | Mic permission denied or wrong input device | Fixes 3, 4 & 7 |
| System/app sound is missing | App muted, or browser can't capture system audio | Fixes 5 & 6 |
| Audio cuts out with headphones | Bluetooth profile switched to hands-free | Fix 8 |
Fixes 1–3: toggles, share-audio and permissions
Fix 1: Turn on the system audio toggle
The simplest cause is also the most common. Most recorders keep System Audio and Microphone as separate switches, and at least one is usually off by default. Open your recorder, look for both toggles, and switch on whichever sources you actually need before you start. If you only want narration, enable the mic; if you are capturing a video or call, enable system audio too.
Fix 2: Tick the "share audio" checkbox in the dialog
This is the fix almost everyone misses. When a browser recorder starts, the browser pops up its own native "Choose what to share" dialog — and there is a small Share tab audio or Share system audio checkbox in the corner that is unticked by default. If you skip it, your recorder's own toggle does nothing, because the browser never hands the sound over.
Fix 3: Grant microphone permission in the browser
If your voice is missing, the browser may have silently blocked microphone access. Look for a small microphone icon in the address bar — if it has a red slash, click it and choose Allow. You can also open your browser's site settings, find the recorder's URL, and set Microphone to Allow. Reload the page after changing it so the new permission takes effect.
Fixes 4–6: input device, muted app and browser support
Fix 4: Select the right input device
Many machines have more than one microphone — a built-in array, a webcam mic, a headset, and sometimes a virtual device. If your recorder defaulted to one that is unplugged or pointed away from you, you will get silence or a barely audible track. Open the microphone dropdown in your recorder (or your OS sound settings) and pick the device you are actually speaking into, then say a few words and watch the input level meter move.
Fix 5: Make sure the app you are capturing is not muted
System audio capture records what your computer is playing. If the specific app — a browser tab, a media player, a game — is muted, the recording will be silent even though everything else is configured correctly. On Windows, open the Volume Mixer (right-click the speaker icon) and confirm the app's slider is up and not muted. On a Mac, check the app's own volume control and the system output level.
Fix 6: Confirm your browser supports system audio
Not every browser can capture system audio, and this trips up a lot of people. Chrome and Edge on Windows can share full system audio; Firefox and Safari cannot capture system-wide sound and offer limited or no tab-audio sharing. If you are stuck on Firefox or Safari and need internal audio, switch to a Chromium browser. Our walkthrough on recording internal audio in a browser covers exactly which option to choose in each one.
| Browser | Microphone | System / tab audio |
|---|---|---|
| Chrome | Yes | Yes (tab and full screen) |
| Edge | Yes | Yes (tab and full screen) |
| Firefox | Yes | Limited / no full system audio |
| Safari | Yes | No system audio capture |
Fixes 7–8: OS privacy and Bluetooth
Fix 7: Check OS-level microphone privacy settings
Even when the browser permission is granted, your operating system can block microphone access globally. On Windows, open Settings › Privacy & security › Microphone and make sure both "Microphone access" and "Let desktop apps access your microphone" are on. On macOS, open System Settings › Privacy & Security › Microphone and tick your browser. After changing either, restart the browser so the recorder picks up the new permission.
Fix 8: Fix the Bluetooth headset profile issue
Wireless headsets use two profiles: high-quality stereo (A2DP) for playback, and a low-quality "hands-free" profile that activates the microphone. When a recorder requests your mic, the headset can flip to hands-free mode — which degrades or kills the system audio stream, leaving you with thin or missing sound. The reliable fix is to use wired headphones or earbuds while recording. Alternatively, record your mic separately or capture system audio through the share dialog so the headset stays in A2DP.
Fix 9: Verify with a quick test recording
Before you commit to a long take, prove your audio works. Record a deliberate 10-second test: say "testing one two three" out loud, and play a short clip with sound (a YouTube video works well). Stop, play it back, and listen for both your voice and the system sound. This 30-second habit saves you from re-recording a ten-minute tutorial that turned out silent.
A test pass also catches subtler issues — an echo from capturing both your mic and your speakers, or one channel being far louder than the other. If your voice is clear but system sound is missing, revisit Fixes 5 and 6; if it is the reverse, revisit Fixes 3, 4 and 7. The clean way to avoid the whole guessing game is a recorder that shows both audio sources up front, so you can confirm each one is armed before you start. You can open Screen Recorder Pro and run a quick audio test in your browser right now — no install, both audio sources clearly toggled, and processing stays local on your machine.
If you are setting up captures on a specific platform, our companion guides go deeper on getting sound right end to end: see recording your screen on Windows 10 and 11 and screen recording on a Mac with audio. Once your toggles, permissions and device are sorted, missing-audio problems disappear — and you can record with full sound every time.
Frequently Asked Questions
Why does my screen recording have no sound?
The most common cause is a disabled audio toggle or an ungranted microphone permission. In browsers, you must also tick the "share audio" checkbox in the share dialog. A browser recorder that exposes both system audio and mic options makes this easy to verify.
Why is my microphone not recording in a screen recorder?
Either the browser permission was denied, your OS privacy settings block mic access, or the wrong input device is selected. Check the mic icon in the address bar, then your system privacy settings, then confirm the correct microphone is chosen in the recorder.
How do I record system audio in a screen recorder?
Enable the system-audio option and tick "Share tab audio" or "Share system audio" when prompted. Note that Firefox and Safari cannot capture full system audio — use Chrome or Edge. See our internal audio guide for details.
Why is there no sound when recording on Windows?
Check that the app you are capturing is not muted in the Windows Volume Mixer, that microphone access is enabled under Settings > Privacy, and that your Bluetooth headset is not stuck in a call profile that disables its microphone or speaker stream.
How do I fix no sound with a Bluetooth headset?
Bluetooth headsets switch to a low-quality "hands-free" profile when the mic is active, which can break audio. Use wired headphones for recording, or set your headset to the high-quality A2DP profile and record system audio through the share dialog instead.