Montage Workflow

How to Record Gameplay for YouTube on PC

If you want to record gameplay for YouTube on PC that looks sharp, the recorder you pick matters far less than the settings you feed it. Any of the three free tools in this guide produces the same thing — a video file — and a file captured at the right bitrate holds up whether you cut it by hand or run it through a scanner later.

So this is not a download-our-software pitch. We check the one piece of hardware that actually determines your performance cost, set up ShadowPlay and OBS with real numbers, and explain why recording whole sessions beats hunting for the clip button mid-fight. Getting a clean file on disk is the first step in the larger job of building a gaming montage.

What You Need Before You Hit Record

Three things decide whether recording ruins your frame rate or barely registers: your GPU's hardware encoder, free disk space, and a mic you have actually tested. Skip the encoder check and you will blame the game for stutter that your recorder caused.

  • A hardware video encoder. This is the setting every ranking guide leaves out and the one that matters most. NVIDIA GPUs have NVENC, AMD has AMF/VCN, and Intel Arc or recent iGPUs have Quick Sync (QSV). These are dedicated chips that compress video without stealing frames from the game. The alternative, x264 software encoding, runs on your CPU and competes with the game for cycles — that is what tanks FPS. If you have any modern GPU, you already own a hardware encoder; you just have to select it. We cover the trade-off in depth in NVENC versus CPU encoding.
  • 50 GB or more of free space, ideally on a fast drive. Good-quality gameplay runs 15–25 GB per hour (exact numbers below). A cheap 2 TB drive holds weeks of weekend sessions.
  • A mic, recorded to its own track. Even if you are making a faceless montage, capturing voice or game audio on a separate track gives you room to balance levels in editing. More on multi-track setup in the OBS section.

Pick Your Recorder: Three Free Options That All Make a Video File

You do not need to buy a recorder. Three free tools cover every PC, and all three output a standard MP4 or MKV you can edit or scan afterward. The only real differences are how much control you get and how much performance overhead you pay.

RecorderPerformance overheadSettings controlMulti-track audioReplay buffer
Xbox Game BarLow to moderateLimited presetsNo (single mix)Yes (Background recording)
NVIDIA App / ShadowPlayVery low (~1–5%)Presets plus manual bitrateYes (separate mic track)Yes (Instant Replay)
OBS StudioLow with NVENCFullYes (up to 6 tracks)Yes (Replay Buffer)

Xbox Game Bar (zero install)

Built into Windows 10 and 11, so there is nothing to download. Press Win + Alt + R to start and stop a recording, or Win + G to open the overlay. The limits are real, though: it cannot capture some fullscreen-exclusive games, its quality options top out quickly, and it mixes all audio into one track. Bump it up under Settings → Gaming → Captures: set video quality to High and frame rate to 60 fps.

NVIDIA App / ShadowPlay (lowest overhead)

If you own an NVIDIA card, this is the least intrusive option on the list. It records through NVENC with an overhead most players never feel, and the overlay is two keystrokes away. Open it with Alt + Z. It is a two-click recorder once configured, which is why most NVIDIA owners use it over anything else.

OBS Studio (maximum control, any GPU)

Free, open source, and the most capable of the three. It works with NVENC, AMD AMF, or Intel QSV, so it is not tied to one brand of GPU. You get custom encoders, multi-track audio, crash-safe recording, and a replay buffer. The trade is a ten-minute first setup; the OBS quick start guide walks through it.

ShadowPlay Recording Settings (NVIDIA App)

NVIDIA folded ShadowPlay into the NVIDIA App, but the recording engine is the same. Open the overlay with Alt + Z, go to Settings → Video Capture, and set these:

  • Quality: High (or Custom, to unlock manual bitrate). The presets are fine, but Custom is what lets you set the number that matters.
  • Bitrate: 50 Mbps for 1080p60. This is the single value that keeps small HUD text crisp during motion; the default is often lower and smears fast fights.
  • Resolution: In-game. Match your monitor's native resolution so the kill feed records at full pixel size. Downscaling shrinks the text you may want to read later.
  • Frame rate: 60 fps. Standard for gameplay; 30 fps looks choppy on fast games.
  • Separate mic track: on. The NVIDIA App can save your mic to its own track, so you can balance voice against game audio in the editor instead of being stuck with a baked mix.

By default your files land in Videos\[Game Name], and you can change that folder in the same panel. To record continuously, start a manual recording with Alt + F9 instead of using Instant Replay — more on why that matters below.

OBS Recording Settings for Kill Montages

OBS defaults are tuned for streaming, not for local montage source files. Switch to Settings → Output → Output Mode: Advanced, open the Recording tab, and set these six things:

  • Encoder: NVENC H.264 (or HEVC), not x264. Hardware encoding is the whole reason OBS barely dents your frame rate.
  • Rate Control: CQP, not CBR. For a local file you want constant quality, not a constant bitrate ceiling; CQP spends bits only where the picture needs them.
  • CQ Level: 18. Visually lossless for most games at roughly half the file size of CQP 12. Go to 16 for grainy or very fast titles, 20 if space is tight.
  • Preset: P5 (Quality) or higher, tuning High Quality. On a modern GPU this costs almost nothing and sharpens motion.
  • Resolution and FPS: native, 60 fps, no downscale. In Settings → Video, set Base and Output resolution equal so nothing is scaled.
  • Recording Format: MKV, with Automatic Remux to MP4 enabled. This is crash insurance: an interrupted MP4 recording is unrecoverable, but MKV keeps everything up to the last written frame, and OBS remuxes it to MP4 for you afterward.

For audio, use two tracks — track 1 for game audio, track 2 for your mic — at 192 kbps each. Separate tracks let you duck game audio under voice, or mute the mic entirely for a music-only montage, without re-recording. Assign the tracks in Settings → Output → Audio and enable them per-source in the Advanced Audio Properties mixer.

Settings That Keep the Kill Feed Legible

Here is the part every recorder guide skips: bitrate is not just about looking nice, it is about whether the small text on your HUD survives high-motion combat. Video compression spends its bits on movement. During a chaotic fight — screen shake, particle effects, fast strafing — a low bitrate runs out of budget and the first thing to blur is fine detail like kill-feed names and kill counters. Those are exactly the pixels you care about, both for viewers and if you plan to find every kill in the VOD afterward instead of scrubbing by hand.

The fix is headroom. These local targets all sit well above YouTube's recommended upload bitrate on purpose — you want more quality on disk than you upload, so editing never compounds the compression. Match the numbers to your recording resolution:

Resolution / FPSShadowPlay bitrate (CBR)OBS setting (CQP)Approx. storage / hour
1080p6050 MbpsCQP 18~22 GB (CBR)
1440p6080 MbpsCQP 18~36 GB (CBR)
4K60130 MbpsCQP 18~58 GB (CBR)
Tip: Record at your monitor's native resolution, never a downscale. A 1080p recording of a 1440p game shrinks every HUD element, which makes the kill feed harder for both your viewers and any scanner to read. Capture at native, then let YouTube handle downscaling for people watching on smaller screens.

Record the Whole Session, Not Hotkey Clips

The community default is to clip only the good moments — Instant Replay, the Game Bar clip button, ShadowPlay's save-last-30-seconds — to save storage. It feels efficient and it is a trap for montage makers, for two reasons.

First, you have to remember to press the key after a good play, mid-match, while someone is pushing you. You will forget, and the buffer only reaches backward a fixed number of seconds, so a long multikill run gets its opening chopped off. The slide-cancel setup, the flank that made the triple possible — the part that makes a clip montage-worthy usually happened before the buffer starts. Second, clips give you no context to choose from later; a full recording lets you decide what was worth keeping once the adrenaline fades.

The objection is always storage, so do the math. A 1080p60 recording at 50 Mbps is about 22 GB per hour — a three-hour session is roughly 66 GB. That sounds like a lot until you price a 2 TB drive at well under $100: it holds around 90 hours of that footage, which is months of weekends. And OBS with CQP recording usually lands well below 22 GB per hour, because quiet moments between fights barely cost anything. Storage is a solved problem; the missed multikill is not.

Here is the payoff, and it is the one product mention in this guide: the recorder you choose does not matter to what comes next. We build GameClipper Advanced, a Windows 10/11 app that scans a finished VOD for kills entirely on your own machine. You draw a box around the kill feed once and capture your in-game name, and it finds every kill in the whole recording using computer vision. Because it reads the video file, ShadowPlay, OBS, Game Bar, and capture-card footage all feed it equally well — a VOD-based kill scanner genuinely does not care which recorder made the file. Nothing uploads; your footage never leaves the PC. The free version does the full scan, edit, and export with a small watermark, and a one-time $19 unlock (sign in with Google to activate) removes it. No subscription. That is why this whole article stayed recorder-neutral.

A scanned gameplay VOD with every detected kill listed as a reviewable clip in GameClipper Advanced
A full session recorded once, then scanned: every kill in the VOD becomes a reviewable clip, no matter which recorder made the file.

Your Pre-Flight Checklist

Run this two-minute check before a real session so you never discover a broken setting after the fact:

  • Do a 2-minute test recording of actual gameplay, not the menu, and watch it back.
  • Confirm your hardware encoder is selected (NVENC / AMF / QSV), not x264.
  • Check that both audio tracks captured — game on one, mic on the other — and that levels are not clipping.
  • Verify the recording is at native resolution and 60 fps, with no downscale.
  • Open the test clip and confirm the kill feed is readable at 100% zoom during a fight, not just when standing still.
  • Check free disk space against the storage-per-hour table for the length of session you plan to play.
  • Note the output folder so you are not hunting for the file later.
  • Confirm your in-game frame rate stayed stable while recording; if it dropped, switch to the hardware encoder.

From Footage to Finished Montage

Get these settings right once and recording becomes the boring, reliable part of the process: a hardware encoder for near-zero overhead, 50 Mbps or CQP 18 so the kill feed stays sharp, native resolution, and a full-session recording instead of scattered hotkey clips. The file that comes out is future-proof — edit it now, scan it later, or turn it into vertical cuts for Shorts and TikTok whenever you like. With a clean VOD on disk, the next step is assembling it, which we walk through end to end in how to make a gaming montage from VOD to upload.

Frequently asked questions

Should I record gameplay in 1080p or 4K for YouTube?

Record at your monitor's native resolution. For most players that is 1080p, and YouTube compresses 1080p uploads cleanly. If your monitor runs 1440p or 4K, record there, because YouTube gives higher-resolution uploads a better codec. Never upscale 1080p footage to 4K; you gain file size and nothing else.

What is a good bitrate for recording 1080p 60fps?

For local recording, 50 Mbps with a constant bitrate keeps HUD text and kill-feed names crisp during fast motion. In OBS, CQP 18 reaches the same visual quality at a smaller, variable file size. Both sit far above YouTube's roughly 12 Mbps upload target, which is intentional headroom for editing.

Does OBS affect FPS while gaming?

Barely, if you use your GPU's NVENC encoder instead of x264. NVENC offloads compression to dedicated silicon, costing roughly 1 to 5 percent of your frame rate. CPU-based x264 encoding is what causes stutter, because it competes with the game for processor cycles. Always pick the hardware encoder for gameplay capture.

Is ShadowPlay or OBS better for recording?

ShadowPlay (the NVIDIA App) is simpler and has the lowest overhead: two clicks and you are recording. OBS gives full control, including custom encoders, multi-track audio, crash-safe MKV recording, and support for any GPU. Use ShadowPlay if you own an NVIDIA card and want zero fuss; use OBS when you need those extra features.

How much storage does recording gameplay use?

At 1080p60 and 50 Mbps, roughly 22 GB per hour. OBS with CQP recording is variable and often lands lower, around 10 to 18 GB per hour, because calm moments cost almost nothing. Budget a 2 TB drive and you will hold weeks of sessions before needing to clear space.

What software do YouTubers use to record gameplay?

Most PC creators use the NVIDIA App (ShadowPlay) or OBS Studio, both free and both using hardware encoding. Xbox Game Bar is the no-install fallback built into Windows. Paid recorders exist, but none of the three free options limit your recording quality, so few montage makers pay for one.

Keep reading