How To Record Screen On Windows

Tips
1

I’ve been trying to record my screen on my Windows PC for tutorials, but I’m confused by all the different options and settings. Some tools lower the video quality or don’t capture system audio correctly. Can someone walk me through the simplest and best ways to record my screen on Windows, including built‑in tools and any reliable free software?

2

Here is what works well on Windows without trashing quality or audio.

  1. Built‑in Xbox Game Bar
    • Press Win + G to open.
    • If it does not open, turn it on in Settings > Gaming > Xbox Game Bar.
    • To start recording: Win + Alt + R.
    • Check audio:

    • Click the audio icon in the Game Bar.
    • Make sure “System sounds” and your mic both use the right device.
      • Limitations:
    • No desktop-only recording, it needs an app or window.
    • No easy webcam overlay.
      • Good for quick tutorials on a single app. Quality is solid, around 1080p, and audio sync is usually stable.

  2. OBS Studio (better control)
    • Free from obsproject.com.
    • For screen + system audio + mic:

    • Add “Display Capture” for full screen.
    • Add “Audio Output Capture” for system sound.
    • Add “Audio Input Capture” for mic.
      • For clean output:
    • Settings > Video
      • Base (Canvas): your monitor resolution, e.g. 1920x1080.
      • Output (Scaled): same as base for best sharpness.
      • FPS: 30 or 60.
    • Settings > Output > Recording
      • Type: Standard.
      • Recording format: mkv or mp4.
      • Encoder:
        • If you have Nvidia, pick NVENC (new).
        • If AMD, pick AMF.
        • If Intel iGPU, pick QSV.
        • If none, pick x264 and use “veryfast” preset to avoid lag.
      • Bitrate examples:
        • 1080p 30 fps: 8000 to 10000 kbps.
        • 1080p 60 fps: 12000 to 16000 kbps.
          • If your system audio does not record, check:
    • Settings > Audio, set “Desktop Audio” to your output device.
    • Windows Sound > Playback > set correct default device.
      • OBS gives you the best control over quality. No weird compression like some cheap tools.

  3. ShareX (lightweight option)
    • Good if you want smaller files.
    • Install, then Task settings > Screen recorder.
    • Use FFmpeg for recording.
    • Pick your monitor, then pick audio source.
    • Quality will depend on encoder and bitrate, but it is easy to tweak.

Simple setup suggestion for tutorials
• Use OBS.
• 1920x1080, 30 fps, NVENC, 10000 kbps.
• Test a 10 second clip.
• Check text readability and audio sync.
• If your PC lags, drop to 720p or 5000 kbps.

If system audio still fails, you might need a virtual cable tool like VB-Audio Cable, then set Windows output to that cable and record it as desktop audio in OBS. That fixes weird driver setups on some machines.

3

If you’re doing actual tutorials (not just quick clips), I’d lean a bit differently than @sognonotturno in a couple spots, especially about relying too much on the Game Bar.

Here’s a setup that keeps quality high and avoids audio headaches, without redoing the same steps already posted:

  1. Use a dedicated scene layout
    Instead of just “capture the screen,” plan your frame:

    • One scene: full display capture, cursor visible
    • Second scene: same display + small webcam in a corner
    • Third scene: just the app window, no desktop clutter
      Then use hotkeys to switch scenes while recording. This makes your tutorials feel edited even before you touch an editor.

  2. Prioritize audio chain before video
    A lot of people obsess over 1080p vs 1440p and ignore the fact that their mic sounds like it’s in a metal trashcan.

    • In Windows Sound settings:
      • Playback: set the exact device you use (headphones/speakers), not “Default”
      • Recording: set your real mic and disable every other random “microphone” to avoid routing issues
    • In your recorder:
      • Only enable one desktop audio source and one mic source to avoid echo/doubling
        Test by recording 5 seconds and checking:
    • No echo
    • Your voice is about as loud as system audio, not buried under it

  3. For crisp text in tutorials
    A lot of “blurry” output is just scaling problems:

    • Record at the same resolution you’re displaying (if your monitor is 1920x1080, record/export at 1920x1080)
    • Avoid recording 4K and uploading 1080p unless you really know what you’re doing with scaling and bitrate
    • Use 30 fps for tutorials with mostly static content; 60 fps is overkill for a lot of teaching stuff and can introduce stutter if your PC is midrange

  4. Don’t always chase tiny file sizes
    Tools that “auto optimize” are often just butchering your bitrate. If your upload bandwidth is decent:

    • For tutorials: 1080p @ 30 fps with 8–10 Mbps video bitrate is a nice sweet spot
    • Audio: 160–192 kbps AAC is usually enough so voices don’t sound crunchy
      You can compress later when editing instead of letting the recorder ruin it up front.

  5. System audio sanity check trick
    Before recording a whole tutorial:

    • Play a YouTube video or a song
    • Record 5–10 seconds
    • Stop, watch it back
      If you don’t hear system audio clearly there, don’t even bother continuing. Fix:
    • Make sure only one app is “using” the output device exclusively (uncheck “Allow applications to take exclusive control” in the device’s Advanced tab if needed)
    • Double check your recorder isn’t set to a disabled or virtual device by mistake
      I almost never bother with virtual cables unless I’m doing something weird like splitting audio tracks.

  6. Editing workflow that saves your sanity
    Especially for tutorials:

    • Record in a robust format (mkv or similar) so a crash doesn’t nuke the whole file
    • Then remux or export to mp4 after the recording
    • Pull that into a simple editor:
      • Cut out “dead time”
      • Normalize audio loudness so your tutorials are consistent across videos
        Staying organized here matters more for quality than obsessing over encoder choice.

  7. Quick rule-of-thumb presets for tutorials

    • Screen size: record at your real monitor res
    • FPS: 30
    • Bitrate: ~10 Mbps video, 160–192 kbps audio
    • One desktop audio device, one mic
    • Use scenes if you need webcam or closeups

If something’s still off, describe specifically:

  • “Audio is delayed by X seconds”
  • “Text looks fuzzy even though I picked 1080p”
  • “System audio works in everything except X app”

Those details are what actually help dial in the right combo of settings next.

4

Skip the Game Bar for anything beyond quick clips. It is fine for grabs, but for real tutorials it is too limited and flaky with audio routing.

Here is how I’d approach it a bit differently from @sognonotturno, focusing on getting consistent results without juggling endless settings.

  1. Decide what kind of tutorials you are making

    • Fast “how to click this” guides: prioritize simplicity, low setup, minimal editing.
    • Longer courses with chapters and overlays: prioritize control, multi‑track audio, stable formats.

    For the first category, a lightweight recorder is better than a full streaming suite. For the second, a scene‑based tool is worth the learning curve.

  2. Use one tool for capture, another for cleanup
    Trying to get perfect output straight from the recorder is where most people burn time.

    • Record “safe”: higher bitrate, lossless or near‑lossless audio, no heavy filters.
    • Edit afterward: trim silence, fix volume, add callouts, then export once.

    This avoids recompressing three times and saves you from tweaking 15 obscure encoder options for every video.

  3. Tackle audio at the operating system level
    I disagree a bit with the idea of only touching settings inside the recorder. Windows can sabotage you quietly.

    • In Sound > App volume and device preferences, make sure your browser, tutorial app, and recorder all use the same output device.
    • Turn off “Enhancements” and “Spatial sound” on your main playback device. These can color your audio so your voice mix sounds fine locally but muddy to viewers.

  4. Keep frame rate boring
    For tutorials, the fancy option (60 fps) often creates problems: bigger files, harder editing, and choppy captures on weaker GPUs.

    • Stick to 30 fps unless you are showing fast UI animations, games, or motion‑heavy apps.
    • If cursor trails or animations look jittery, try 48 fps instead of jumping straight to 60.

  5. Avoid scaling during capture
    A big cause of fuzzy text: people record at one resolution and scale inside the recorder or in Windows display settings.

    • Set Windows display scaling to 100% while recording if possible.
    • If text is too small on screen, increase app zoom (like 125 percent in your browser or editor) instead of global scaling.

  6. Separate tracks when possible
    Even if you do not think you need it now, recording mic and system audio to separate tracks can save a tutorial if one is too loud.

    • Set mic to track 1, system audio to track 2.
    • In your editor, you can quickly pull the system track down a few dB without touching your voice.

  7. Quick troubleshooting rules

    • System audio missing: check if any app has “exclusive mode” enabled in its device properties and uncheck it.
    • Voice quieter than system: raise mic gain a little in Windows, not just in the recorder, so your waveform is healthy from the start.
    • Sudden frame drops: close hardware‑accelerated apps like some browsers or chat tools during recording.

  8. On using a generic “How To Record Screen On Windows” setup
    A sensible default profile for that topic would be:

    • Resolution: match monitor, usually 1080p.
    • FPS: 30.
    • Video bitrate: about 10 Mbps for clarity.
    • Audio: AAC 160–192 kbps.
    • One desktop device, one mic, optional separate tracks.

Pros of this kind of “How To Record Screen On Windows” focused approach:

  • Predictable quality and clear text.
  • Simple enough you can reuse the same preset every time.
  • Good audio control without complicated virtual routing.

Cons:

  • Not optimized for ultra low file sizes.
  • Requires a separate editing pass if you want tight, polished tutorials.
  • Less plug‑and‑play than Game Bar for one‑off clips.

If you post which recorder you picked and your exact resolution / fps / bitrate, it is much easier to spot why your current captures look soft or why system audio keeps acting up.