You finish the recording, hit play, and the video looks perfect. Then the audio track is dead silent.
That usually isn't a recorder failure. It's a source problem. Sound is often thought of as one thing, but screen recording tools usually treat it as at least two separate inputs: the sound coming from the device and the sound going into the microphone. If you pick the wrong one, or the app blocks one of them, you get silence, half the audio you expected, or a recording that only captures your breathing and keyboard clicks.
If you're trying to figure out how to get sound on a screen recording, start by identifying what you need to capture. A YouTube clip playing in a browser, your own narration over a tutorial, a game with your commentary, and a call inside a protected app are all different recording situations. The fix depends on that difference.
Table of Contents
- Why Is Your Screen Recording Silent
- Capturing Audio on Windows and Mac
- Recording Sound on Your iPhone and Android
- Troubleshooting Common No-Sound Issues
- How to Rescue Bad Audio After Recording
- Frequently Asked Questions About Screen Recording with Sound
Why Is Your Screen Recording Silent
Most silent recordings come from one misunderstanding. You wanted system audio, but only enabled the microphone. Or you wanted narration, but the recorder was only set to capture desktop sound.
The two audio types that matter
System audio is the sound your device is playing. Think video playback, game audio, app sounds, music, alerts, or the other person's voice in some calls.
Microphone audio is what your mic hears. That's your voice, room tone, keyboard noise, fan hum, and anything else physically happening around you.
If you mix those up, the result makes sense in hindsight:
- You recorded a tutorial and got no voice because the microphone wasn't enabled.
- You recorded a video and only heard yourself talking because the recorder captured the mic but not the app sound.
- You recorded a protected app and got silence because the app didn't allow its own audio to be captured.
Practical rule: Before you press record, say out loud what you need: “I need internal sound,” “I need my voice,” or “I need both.”
A quick way to diagnose the problem
Use this fast test before any real take:
| What you hear in playback | Most likely cause | What to change |
|---|---|---|
| Nothing at all | No audio source was enabled, or the source was muted | Check recorder audio settings and system volume |
| Your voice only | Microphone was on, internal audio wasn't captured | Enable system or app audio if the platform supports it |
| App sound only | System audio was captured, mic wasn't | Turn on microphone input |
| Silence from one specific app | App-level restriction | Try narration instead, or use a different workflow |
A lot of creators lose time because they troubleshoot the wrong layer. They reinstall apps, restart devices, and swap recorders when the underlying issue is simpler. The recorder is working. The selected source isn't the one they thought it was.
Silent recordings usually mean one of two things. You captured the wrong audio source, or the app refused to share its own sound.
Once you separate those two possibilities, how to get sound on a screen recording becomes much easier to solve.
Capturing Audio on Windows and Mac
Desktop is where audio problems get exposed fast. You finish a full tutorial, hit playback, and realize you captured the wrong source. On computers, that usually means one of two failures: the recorder grabbed your microphone but missed system sound, or it captured system sound and ignored your mic.
Windows is usually easier because the built-in tools expose more audio controls. Mac can produce clean recordings, but the defaults are less forgiving, especially if you expect internal app audio to behave like it does on Windows.
Windows with Xbox Game Bar
Xbox Game Bar is the quickest built-in option on Windows for recording screen activity with sound. It can handle app or desktop audio and microphone input, but only if those sources are enabled before the take.
Use this setup:
- Press Win + G to open Xbox Game Bar.
- Open the Capture widget.
- Check the Audio panel.
- Make sure desktop or system audio is active if you need app sound.
- Turn on the microphone if you want narration.
- Start or stop recording with Win + Alt + R.
A common miss happens inside the mixer. The recorder is open, the screen is being captured, but one source is muted or set too low to register. Microsoft Community guidance on recording Windows screen with sound points users to the audio mixer first for exactly that reason (Microsoft Community discussion on recording Windows screen with sound).
Here is the practical split I use:
- Recording a software demo: Enable desktop audio. Add mic only if you are explaining steps live.
- Recording a tutorial with narration: Watch the mic meter before you start. If the meter is flat, stop there.
- Recording a game: Make a short test clip. Some games, launchers, and anti-cheat setups affect capture behavior.
- Recording meetings or calls: Expect app-level limits in some tools, even if Game Bar is configured correctly.
If Windows audio fails, check the app output device too. I have seen recordings come back silent because the app was sending sound to a Bluetooth headset that disconnected mid-session while the recorder was listening to a different output.
Mac with built-in tools
On macOS, people usually start with the Screenshot toolbar or QuickTime Player. Both are fine for fast captures. The trade-off is audio flexibility.
Start with the built-in workflow:
- Press Shift + Command + 5 to open the Screenshot toolbar.
- Choose Record Entire Screen or Record Selected Portion.
- Open Options and verify your microphone selection.
- If you are using QuickTime Player, choose File > New Screen Recording and review the audio input before recording.
For microphone narration, this works well. For internal system audio, Mac users often assume the native recorder will pick it up automatically. That assumption causes a lot of silent takes. On Mac, built-in screen recording is most reliable for screen plus mic. If your project depends on app audio, test the exact workflow first.
That test should be short. Ten seconds is enough.
I treat Mac recording like a preflight check. Play the sound you need, record a sample, and listen back with headphones before you commit to the full session. It takes one minute and saves a complete retake.
Use this desktop checklist before every real recording:
- Confirm the source you need: system audio, mic, or both
- Play audio live before recording: if the app is silent, the file will be silent too
- Check level movement: no meter activity usually means the wrong source is selected
- Use headphones for narration: this cuts echo and speaker bleed into the mic
- Record a short sample: catch routing problems before the long take
- Keep a backup plan: if the capture is usable but noisy, thin, or uneven, you can often clean it up after the fact with a tool like ClearAudio instead of rerecording everything
That last step matters more than people think. Perfect capture is the goal. Rescue options are what save deadlines.
Recording Sound on Your iPhone and Android
Mobile recording feels simple because the controls are minimal. That's exactly why people miss the one setting that matters.
iPhone and iPad
On iPhone and iPad, the critical move is not just tapping the Screen Recording button. It's long-pressing it.
Apple community guidance says the built-in recorder supports audio through a microphone toggle that appears when you long-press the Screen Recording control in Control Center. That microphone must be enabled before you start if you want voice capture, and if it was off, there may be no audio to recover afterward (Apple-related guidance referenced here).
The working method is:
- Open Control Center.
- Long-press the Screen Recording control.
- Turn the Microphone on if you want narration.
- Start the recording.
Apple Community also notes that not all apps support recording sound when recording the screen, so microphone narration is the reliable fallback when an app won't expose internal audio to the recorder (Apple Community discussion on iPhone screen recording audio).
The common iPhone mistake
People tap the record button, assume audio is included, and only later learn the mic toggle was off. That's why so many iPhone recordings have clean video and no commentary.
Android
Android is less uniform because manufacturers skin the OS differently. The native path is usually in Quick Settings under Screen Recorder or a similarly named control.
What to look for:
- A toggle for device audio, media sounds, or similar wording
- A separate option for microphone
- A choice between recording one, the other, or both
If you don't see those options, your phone may expose fewer native controls, or the app you're recording may limit audio capture. On Android, the names vary, but the logic doesn't. You still need to decide whether you're capturing the phone's audio, your voice, or both.
If mobile audio matters, never trust the default state. Open the recorder options every time and confirm the source before you start.
Troubleshooting Common No-Sound Issues
This is the part most tutorials skip. You followed the steps, the recorder ran, and the file still has no usable sound. At that point, you need diagnosis, not another generic setup list.
When the setup is correct but the audio is still missing
The biggest blind spot is app-level restriction. Some apps don't allow their own audio to be captured during screen recording. Apple Community explicitly notes, “Not all apps support recording sound when recording the screen,” which explains why people can follow the normal microphone instructions and still end up with voiceover only or total silence (Microsoft Tech Community summary referencing that limitation).
That matters most when you're recording:
- Streaming apps
- Games with protected audio paths
- Calls or meetings
- Protected media or premium content
If one specific app always goes silent while everything else records fine, stop blaming the recorder. The app may be blocking capture by design.
A short walkthrough can help if you want another visual check before changing your setup:
What to check before you record again
Use this order. It catches most failures faster than randomly toggling settings.
Confirm the target source
Decide whether you need internal sound, mic narration, or both. If you haven't answered that first, everything after it is guesswork.Check mute states and levels
On Windows, the mixer can show a source as available while it is effectively muted or too low. On any platform, a low source can look like missing audio.Review permissions
If the recorder doesn't have microphone access, you won't get narration. If the OS blocks background capture behavior, you'll get partial results.Test the exact app
Don't test with a browser tab and assume a meeting app or streaming app will behave the same way.Record a short proof clip
Play it back immediately. If it's wrong, you've lost seconds instead of an entire session.
If only one app fails while other apps record normally, treat it as an app limitation first and a recorder problem second.
The advanced lesson is simple. Screen recording audio is not just about switches. It's about what the operating system allows, what the app exposes, and which source you armed before recording.
How to Rescue Bad Audio After Recording
Not every failed recording is a total loss. A lot of bad screen-recording audio is still salvageable if the sound exists but was captured poorly.
What can be fixed in post
Post-production can often improve recordings that suffer from:
- Background noise
- Low dialogue clarity
- Room echo
- Hum or hiss
- Distracting environmental sound mixed under speech
Cleanup tools prove their value. If the voice is present but ugly, you can often isolate speech, reduce noise, and make the recording understandable enough to publish without doing the whole session again.
The smart move is to separate two situations:
| Recording outcome | Can post fix it | Best response |
|---|---|---|
| Audio exists but sounds rough | Usually yes | Clean and enhance it |
| The file contains no voice because the mic was off | No | Re-record |
| App audio was blocked and never captured | No | Use a different recording method next time |
| Voice is present with noise and echo | Often | Reduce noise, tame echo, lift speech clarity |
What cannot be repaired
If the source was never captured, there is nothing to restore. No editor or AI tool can recover a microphone track that was off the entire time, or internal app audio that the platform never recorded.
That distinction matters because creators waste hours trying to “fix” a file that is structurally empty. If the waveform is flat or the only sound is room noise, stop chasing a miracle repair and decide whether the recording is worth replacing.
If the audio is there but messy, cleanup is worth it. If the important source is absent, move on faster.
Frequently Asked Questions About Screen Recording with Sound
Can I record app audio and my voice at the same time
Usually, yes, if your recorder can capture two different sources: system audio from the app and microphone audio from your mic. That distinction is the part people miss. If you only arm the mic, viewers hear you but not the app. If you only capture system audio, your narration disappears.
On Windows, built-in tools can often handle both. On Mac, it depends more heavily on the app and the recording method you use. In any setup, run a 10-second test first and play it back before your main recording.
Why does my recording sound echoey or distant
The mic probably captured your room, your speakers, or both. That happens fast when laptop speakers are playing out loud or the mic is too far from your mouth.
Use headphones. Put the mic closer. Lower fan noise and hard-room reflections if you can. If the recording is already done and the voice is still there, cleanup can often reduce echo, hiss, and background noise enough to save the take.
Can I record audio from any app
No. Some apps and streaming services block internal audio capture, even when the screen records normally. In those cases, the video file may be fine but the app audio track never gets written.
The practical fallback is simple. Record your microphone commentary, or switch to a capture method that supports the app you need.
Why did my iPhone recording save with no voice
The microphone was probably off before you started. On iPhone and iPad, that setting sits behind a long-press on the Screen Recording button, so it is easy to miss if you are in a hurry.
This is one of the most common failures I see. The screen records perfectly, the presenter talks through the whole demo, then the file comes back silent because the mic toggle was never enabled.
Why does my Windows recording have video but no sound
Usually the wrong input was selected, the source was muted, or the app audio was routed somewhere your recorder could not hear. Bluetooth devices can also cause this if Windows switches playback or input automatically.
Check the volume mixer, confirm the correct input and output devices, and make sure your recorder is set to capture the source you need. Desktop audio, microphone, or both.
Is the built-in recorder enough
For straightforward jobs, yes. If you need to capture a quick walkthrough with clean app audio and basic narration, the built-in recorder is often enough.
It starts to fall short when you need more control over audio routing, separate tracks, app-specific capture, or stronger editing tools after the fact.
If your screen recording has speech buried under hiss, hum, echo, or background noise, ClearAudio gives you a practical fallback after the recording is done. You can upload audio or video, tell it what to keep, such as dialogue or vocals, and clean up the track without rebuilding your entire workflow. It's a strong safety net for creators who cannot afford to throw away an otherwise solid take.