How to Screen Record on Windows 11 with Audio

Published by Rescreen, which makes one of the products discussed. How we source and update these guides.
To record your screen on Windows 11 with audio, open Snipping Tool, choose video recording, select the area you need, and enable the microphone, computer audio, or both before starting. Stop the recording, save it, and play the file back. For a game or app, Xbox Game Bar provides a keyboard-driven recording route. For a browser demonstration that needs editing afterward, Clipchamp offers another workflow.
The most useful first decision is what the viewer should hear. Your voice comes from a microphone; a video's soundtrack or an app's sound comes from computer playback. A recording can contain one while missing the other. Before a long take, make a short sample with a spoken sentence and an identifiable sound from the app you intend to show.
This guide covers those three Windows workflows and the checks that distinguish a microphone problem from a playback-capture problem. It follows the linked Microsoft documentation, checked on 14 October 2026, rather than claiming a hands-on Windows benchmark. If you are on a different operating system, use the Mac screen-recording and audio guide.
Choose what you need to record
Begin with the output you need, not a long list of recorder features. A quick explanation of one setting needs a different capture boundary from a demonstration that moves between several windows. Write down the screen area, required sounds and final destination before opening the recorder. That gives you a small, testable recording brief.
| Task | Route | First check |
|---|---|---|
| Capture a selected screen area | Snipping Tool | Set voice and PC-audio controls before Start. |
| Record a game or app | Xbox Game Bar | Choose the audio scope and microphone state. |
| Record and edit a web demonstration | Clipchamp | For the personal-account route below, share a browser tab with its audio. |
For example, a demonstration of a music player needs direct playback audio. A spoken explanation of a spreadsheet may need only your microphone. A lesson explaining an audible warning needs both. Treat those as separate acceptance criteria: “the picture looks right” cannot tell you whether either audio source was saved.
Keep irrelevant windows outside the capture area and enlarge labels that the viewer must read. If the task includes a menu near the edge, open it before recording and check that it stays inside your chosen region. Do the same for any confirmation that appears after a click. These small rehearsals prevent a technically successful recording from missing the action it was supposed to explain.
Check voice and computer sound separately

Connect the microphone you intend to use before selecting it in the recorder. A headset, webcam and laptop can each provide a microphone, so a device being available is not enough: choose the one you actually want. If you reconnect hardware between takes, check the choice again instead of assuming the earlier selection still applies.
For microphone access, open Settings → Privacy & security → Microphone. Enable microphone access and the relevant app permission; desktop apps also depend on the desktop-app access setting. Microsoft explains these controls in its microphone-permissions guide. A browser can additionally request permission for the recording website, as described in Microsoft's camera and microphone privacy documentation.
Confirm that Windows can hear the selected microphone
Before changing recorder settings, run the operating system's own input test. Following Microsoft's microphone setup and test instructions, open Settings → System → Sound. Under Input, select your microphone and open its properties. In Input settings, choose Start test, speak normally, then choose Stop test and Play. Adjust Input volume if needed.
If that sample contains your voice but the screen recording does not, concentrate on the recorder's input selection, mute state and permissions. If the Windows sample is also silent, resolve the microphone connection or input problem first. A successful Windows test confirms that input for this sample; it does not prove the recorder has permission or that computer playback will be captured.
Recording in the browser? Run our free microphone test in the same browser first. It asks for the microphone the way a browser recorder does, shows the level, plays back a five-second sample and explains a blocked, silent or distorting input. Like the Windows test, it checks the microphone only, not computer playback.
Make a sample with three recognizable moments
Use this short exercise before your real take. It is a suggested test script, not a measured result from our equipment:
- Start recording the actual app or tab you will use.
- Say, “This is the microphone check,” while the app is quiet.
- Stop speaking and play a short sound in that app.
- Speak once while the sound continues, then stop and save.
- Play the saved file with headphones. Identify your voice, the app sound and the moment they overlap.
For narration-only work, the app sound should be absent if you disabled playback capture. For a silent demonstration with app audio, your voice should be absent if you disabled the microphone. For both, each should be recognizable without one obscuring the other. This makes the test useful even when intentional silence is the correct result.
Record with Snipping Tool
Snipping Tool is the direct route for selecting an area of the screen. Microsoft's video-snip instructions describe the capture sequence, and its audio-control announcement documents separate PC sound and microphone support. Audio support subsequently appeared in the Windows 11 feature rollout; older tutorials saying Snipping Tool never records sound do not describe that capability.
- Find Snipping Tool in Start. Select its video-recording mode, then New. The direct recording shortcut is Windows + Shift + R.
- Select the region containing the actions you will demonstrate.
- Before starting, inspect the audio controls. Enable PC audio for application playback. Select and unmute your preferred microphone for narration, or leave it muted when voice is unwanted.
- Select Start, perform the task, then select Stop.
- Review the preview and save the recording to a location you can find. Open that saved copy and run the voice/playback check above.
A selected microphone can still be muted. Chris Menard demonstrates that distinction in his Windows 11 Snipping Tool tutorial on YouTube, around 1:16–1:50. The video also walks through stopping and saving. Its interface may differ from your installed version, so use the microphone name and mute state as the checks rather than relying on a button's exact position.
Keep your trial small enough that rerecording it is painless. If you need three windows in the finished explanation, include a transition between them in the sample. If an important panel falls outside your chosen region, change the framing before making the full recording. Do not wait until the final edit to discover that a necessary step was never visible.
Record an app with Xbox Game Bar
Microsoft documents Game Bar for recording a game or app. Its keyboard recording guide provides the shortcuts and sound settings below.
- Open the game or app you want to capture, then press Windows + G.
- In Game Bar settings, find the capture/audio options. Select All when the recording needs game, app and system sound.
- Check the microphone state. Windows + Alt + M toggles it; avoid pressing the shortcut blindly when you already have the correct state.
- Return to the target app and press Windows + Alt + R to start. Use the same shortcut to stop.
- Look in Videos → Captures for the MP4, then play it back.
Plan around the target app, not an assumed recording of everything you can see on the desktop. If your demonstration requires a file picker, another window or a desktop transition, include that exact action in the trial. Choose a selected-area Snipping Tool recording when that better matches the visible task.
Broad audio capture also needs a careful listening check. Close unrelated playback before taking the sample and listen for sounds that do not belong in the explanation. Keep the required sound source active during the test; silence in an app that was not playing anything tells you nothing about whether capture works.
Record a browser tab with Clipchamp
The following path follows Microsoft's Clipchamp screen-recording instructions for personal accounts. For shared playback audio, those instructions specify browser-tab capture. Do not assume a window or entire-screen selection includes the same sound.
- Open Clipchamp in the browser containing your demonstration tab. In a project, choose Record & create → Screen.
- Allow the needed microphone access and select your input. Disable microphone recording if you only want tab sound.
- Press the record button. In the sharing picker, select the target browser tab, enable audio sharing and select Share.
- Perform the demonstration, then select Stop sharing. Preview it and choose Save and edit, or retake it.
- Finish any edits, select Export and save the resulting MP4. Listen to that export as well as the preview.
Work and school accounts have separate instructions on the same support page. Follow the section matching your account rather than combining controls from different versions.
Fix missing or doubled audio
Keep the failed sample until you know what went wrong. Compare its symptoms with the intended source, change one setting, and repeat the same exercise. Changing the microphone, playback app and recorder at once makes it harder to identify which change helped.
| What you observe | Check next | What a pass establishes |
|---|---|---|
| Windows microphone test is silent | Connection, selected input and input volume in Windows Sound settings. | Voice reaches Windows through that microphone. |
| Windows hears voice; recorder sample does not | Recorder input, mute state and app or site permission. | The recorder includes narration in its sample. |
| Voice records; the audible app sound does not | PC-audio setting, Game Bar audio scope, or shared tab and audio toggle. | The intended playback source reaches the recording. |
| Preview sounds right; exported file does not | Correct file/version, editor track mute or volume, and a fresh export. | The delivered file retains the required sound. |
These checkpoints narrow the investigation; they are not proof of a single cause. For example, hearing a video through speakers does not prove its audio reached the recorder directly: the microphone might have picked up the room. Repeat the playback-only portion with headphones and the microphone muted when checking direct computer-audio capture.
The app sound is there, but your voice is missing
Check the recorder's selected microphone and mute state first. Then inspect the Windows permission and, for browser recording, the site's microphone permission. If the input itself is uncertain, use Settings → System → Sound → Input to inspect the device. Microsoft's microphone troubleshooting guide covers device and access checks. Increasing the loudness of the finished clip cannot recover speech that was never captured.
Your voice is there, but computer playback is missing
Replay a known sound from the exact source you intend to capture. Check that playback capture was enabled rather than only the microphone. In the browser workflow above, revisit the selected tab and its audio-sharing control. A visible page and an audible soundtrack are separate requirements. If the source itself is silent, solve that playback problem before changing recording settings.
The sound echoes or arrives twice
Try the same sample with headphones instead of speakers, and listen for a change. This helps distinguish room sound reaching the microphone from sound included directly in the recording. Also stop any recording preview that is playing during the new take. Do not immediately apply noise reduction: first establish whether the unwanted sound is a second copy of the wanted audio.
The controls do not match these instructions
Check that you are in video mode rather than screenshot mode, and verify the installed app and Windows versions. Look for available official app updates before concluding that an older interface represents the current feature set. On a managed work computer, ask your administrator if an app or permission is restricted. Record the exact missing control or error message so troubleshooting can address a specific failure.
Check the saved file before sharing

A preview inside the recording app is only one checkpoint. Open the saved or exported file separately, move to the section where voice and playback overlap, and listen at an ordinary volume. Check the start and end as well: an explanation that begins mid-word or stops before the result appears can be confusing even when its sound sources are correct.
- Picture: the required menu, pointer action and result are visible and readable.
- Voice: the intended microphone was recorded, with no missing opening or closing words.
- Playback: the required app sound is present, and unrelated audio does not distract from it.
- File: the saved copy opens and finishes playing outside the recorder.
- Handoff: the recipient can find and open the correct file or access the intended share link.
Name the source take and final version differently, and retain the source when you plan further edits. Note the recorder, selected microphone and capture scope alongside it. These few details make a later pickup easier to match, especially if you change headsets or move from an app demonstration to a browser tab.
Keep a short record of the test
Download the audio recording test log (CSV) to record your own checks in a spreadsheet. It is a blank worksheet, not a set of measured results. Enter the recorder, microphone, capture scope and saved filename, then mark each required check as pass or fail. Use “not required” for an intentionally disabled sound source.
Keep one copy for each setup you compare. In the “change before retry” column, name the single setting you changed; in the result column, describe what you actually heard or saw. For example, “voice present, app sound absent” is more useful than “audio broken.” When the sample passes, keep that file beside the finished take so you can compare a later problem against a known result from your own setup.
If the recording is becoming a lesson, continue with the tutorial-video workflow and practice script for planning, pacing, captions and delivery. Establish that the picture and both required sound sources survive the saved-file check first; editing is much easier when the source take contains everything the viewer needs.