Adjust Video Quality for Game Clips Windows: Eight Settings That Fix the Two Problems Causing Washed-Out Recordings

Windows records game clips at whatever quality the Game Bar, your GPU driver, or your capture app decides is "balanced" unless you override it. The fix lives in four different places, and the one most people miss sits in the Xbox Game Bar's capture settings, where a single video quality dropdown caps every clip the app records — regardless of what your hardware can actually handle. Adjusting video quality means setting resolution, frame rate, bitrate, and encoder together, in that order, and confirming each one survives the app's defaults. Do it out of order and Windows quietly reverts half your changes.

The second problem is subtler. Even when you set 1080p at 60 frames per second, some clips still look soft or blocky, because the bitrate the Game Bar applies at "High" is lower than what fast-motion gameplay needs to avoid compression artifacts. That gap is where most complaints about "bad quality" originate, and no resolution setting fixes it. You have to know the bitrate, and you have to choose an encoder that doesn't throttle it.

Where Windows Stores Game Clip Quality and What Each Setting Controls

Xbox Game Bar keeps its capture settings in a dedicated panel, separate from Windows' general display settings and separate from your GPU control panel. Open it with Win+G, click the gear icon, and select Captures. That panel holds four quality controls: "Record this game's audio," "Capture length," "Video quality," and "Frame rate," plus an "Advanced" toggle that reveals bitrate options in newer Windows 11 builds. Changing resolution happens outside this panel, in Windows Settings under System > Display, because the Game Bar records at the display's active resolution — there is no separate recording resolution selector in the Game Bar itself.

That last point trips people up constantly. If your monitor runs at 1440p but you want 1080p clips to save disk space, lowering the in-game resolution or the display resolution before recording is the only way to get 1080p output from the Game Bar. Your GPU's driver software — NVIDIA App or the AMD Software: Adrenalin Edition — does offer explicit recording resolution controls, and that's one reason to use the driver recorder instead of the Game Bar for anything you plan to edit or upload.

The Game Bar's "Video quality" dropdown offers Standard, High, and a Custom option in current builds. Standard targets roughly 720p-equivalent bitrate behavior, High targets 1080p, and Custom lets you type a bitrate in megabits per second. According to Microsoft's own Game Bar documentation, the recorded clip's file size and quality scale directly with that bitrate figure — a clip recorded at 10 Mbps is roughly half the size of the same clip at 20 Mbps, with visible softness in fast pans. Treat the dropdown as a bitrate preset, not a resolution preset, and the rest of the settings fall into place.

Frame rate is the fourth control, and it's binary: 30 fps or 60 fps. Choosing 60 fps doubles the frames the encoder must process per second, so at a fixed bitrate each frame gets roughly half the data. That's the mechanical reason a 60 fps clip at the same "High" setting can look worse than a 30 fps clip of the same scene — not a bug, just arithmetic the dropdown hides from you.

Setting Resolution, Frame Rate, and Bitrate in the Right Order

Follow this sequence exactly. Each step assumes the previous one is already saved, because the Game Bar reads display resolution at the moment recording starts, not when you open the settings.

1: Set your display or in-game resolution first in Windows Settings > System > Display, or in the game's own graphics menu. This locks the capture resolution. 2: Open Win+G > Settings (gear) > Captures and set "Frame rate" to 60 fps only if your GPU sustains 60 fps in that game. A 30 fps capture of a 45 fps game looks smoother than a 60 fps capture fighting for frames. 3: Set "Video quality" to Custom and enter a bitrate. For 1080p60 gameplay, 20–25 Mbps holds up in fast motion; for 1080p30, 10–12 Mbps is adequate; for 1440p60, plan on 35–45 Mbps. 4: Toggle "Advanced" if your build shows it and confirm the encoder selection — hardware encoding (GPU) is the default and the correct choice unless you're simultaneously running a heavy GPU workload. 5: Record a 30-second test clip of the fastest-moving scene you can find, then watch it at full screen before recording anything you care about.

The failure case matters here: if you set 60 fps and a high bitrate on a laptop running on battery, Windows power management can drop the GPU's clock speed mid-recording, and the encoder produces a clip with stuttering frames that looks like a bitrate problem but isn't. Plug in before recording long sessions, or accept 30 fps on battery.

If the clip still looks soft after step 5, the likely culprit is that the game itself renders at a lower internal resolution than your display — common with upscaling technologies like DLSS, FSR, or dynamic resolution scaling. The capture sees the final upscaled image, so the softness is baked in. Check the game's resolution scale setting before blaming the recorder.

Game Bar Versus NVIDIA App Versus AMD Adrenalin: Which Recorder Gives You Real Control

All three tools record gameplay on Windows, and they differ in exactly which quality knobs they expose. The comparison below uses the controls each tool documents in its current release; confirm exact menu labels against the maker's site, since driver software renames panels between versions.

Pick the Game Bar when you want zero setup and clips for Discord or a quick share. Pick the driver recorder when you need a resolution different from your monitor, HEVC for smaller files at equal quality, or HDR preserved. Skip the driver recorder if you're on a work laptop with switchable graphics that the driver software doesn't fully manage — the Game Bar handles those hybrids more predictably.

One drawback worth naming for the NVIDIA App: HEVC recording produces files some older editing apps and social platforms reject outright, so the smaller file can cost you a re-encode later. H.264 remains the safer default for anything headed to an editor.

Calculating the File Size Your Settings Will Produce Before You Record

Bitrate is the only number you need to predict storage. File size in megabytes equals bitrate in Mbps multiplied by recording length in seconds, divided by eight. A 10-minute (600-second) clip at 20 Mbps comes to 20 × 600 ÷ 8 = 1,500 MB, or about 1.5 GB. The same clip at 45 Mbps for 1440p60 lands at 3,375 MB, roughly 3.4 GB.

Run that against your drive. A 500 GB SSD with 60 GB free holds about 40 ten-minute clips at 20 Mbps, or 17 at 45 Mbps. A two-hour recording session at 1440p60 and 45 Mbps consumes about 40 GB — enough to fill a small laptop drive in a single evening.

Microsoft's Game Bar documentation notes that "Captures" folder location is configurable in the same settings panel, so point it at a drive with headroom before a long session rather than discovering the limit mid-record. The Game Bar stops recording when the target drive fills, and the partial file is often unplayable.

Audio bitrate is negligible by comparison — typically 128–192 kbps — so don't factor it into storage planning. The video bitrate dominates everything.

Fixing Washed-Out, Blocky, or Stuttering Clips After the Fact

Three distinct symptoms map to three distinct causes, and misdiagnosing them wastes hours.

Washed-out or gray-looking clips usually mean an HDR game captured by a recorder set to SDR output. The Game Bar handles HDR inconsistently across Windows versions, and the result is a clip with lifted blacks. Fix: either record with a tool that captures HDR properly (the driver recorders, with HEVC selected), or disable HDR in Windows Settings > System > Display > HDR before recording SDR clips.

Blocky artifacts in fast motion mean insufficient bitrate for the frame rate. Double the bitrate and re-test; if the blocks persist, the encoder is dropping frames, not the bitrate. Check GPU utilization during recording — above roughly 95% sustained, the hardware encoder starts skipping, and the fix is lowering in-game settings or capping frame rate.

Stuttering playback in the clip itself, where the action jumps rather than flows, points to frame pacing problems at capture time, not encoding. Common causes: variable refresh rate interacting badly with the recorder, or a game running in borderless windowed mode that the capture API handles poorly. Switching the game to exclusive fullscreen often resolves it.

One edge case worth knowing: recording a game that itself runs below 30 fps produces a 30 fps clip with duplicated frames, which looks worse than the live experience. Capture at the game's actual frame rate where the tool allows it, or accept the duplication.

Matching Quality Presets to Upload Targets Instead of Maxing Everything

Maximum quality is the wrong default for most people, because every platform re-encodes what you upload. YouTube's recommended upload bitrate for 1080p60 SDR is 12 Mbps with H.264, per Google's own upload specifications — recording at 45 Mbps and uploading to YouTube wastes 73% of your bitrate, since the platform transcodes down regardless. Record at roughly double the platform's target (24 Mbps for 1080p60 YouTube) to survive the re-encode without carrying useless data.

Discord's free tier caps uploads at 10 MB per file in most configurations and compresses video aggressively; a 30-second 1080p60 clip at 20 Mbps is about 75 MB and won't fit without Nitro. Record short Discord clips at 720p30 and 6–8 Mbps, or trim before sending.

For archival footage you'll edit later, higher bitrate pays off — editing software re-encodes on export, and a low-bitrate source compounds artifacts through two generations. Archive at 1080p60 and 25 Mbps or better, then export at platform-appropriate settings.

The general rule: record at the highest quality your storage and editing workflow tolerate, then export down to each platform's spec. Recording at platform spec and exporting again loses quality twice.

Choosing an Encoder: Hardware, Software, and When Each Wins

Hardware encoding uses a dedicated block on your GPU — NVENC on NVIDIA cards, VCE or VCN on AMD, Quick Sync on Intel — and offloads compression from the CPU entirely. It's the default in every Windows recorder, and it's the right choice for live gameplay capture because it doesn't compete with the game for CPU cycles.

Software encoding (x264) produces smaller files at equal visual quality but costs CPU headroom, typically 10–30% of a modern multi-core chip at 1080p60. For recording while gaming, that cost shows up as frame drops in CPU-bound games. For recording non-game content or re-encoding an existing clip afterward, software encoding wins on file size.

Codec choice sits alongside encoder choice. H.264 is universally compatible; HEVC (H.265) produces roughly 25–50% smaller files at comparable quality, per the codec's own design specifications published by the ITU-T, but costs more GPU time and has patchier playback support on older devices. AV1 encoding exists on the newest GPUs and offers further efficiency gains, but editor and platform support is still uneven as of late 2026 — check your specific editing software's supported import formats before committing to AV1 archives.

Match codec to destination: H.264 for anything going to an editor you haven't verified, HEVC for archives and HDR, AV1 only if your whole pipeline supports it.

Laptop, Multi-GPU, and Capture Card Scenarios That Break Defaults

Laptops with hybrid graphics — integrated GPU driving the display, discrete GPU rendering the game — are the most common source of "my recordings look terrible and I can't figure out why." The capture API can hook the wrong GPU and record a low-quality composited stream. Fix: set the game to run on the discrete GPU in Windows Settings > System > Display > Graphics, and set the recorder to the same GPU where the tool allows it. The Game Bar generally handles this correctly; third-party tools sometimes don't.

External capture cards bypass the problem entirely. A card capturing the HDMI output records exactly what the display shows, at whatever quality the card supports — typically 1080p60 or 4K60 depending on model. The tradeoff is a second machine or a passthrough setup, and capture cards introduce their own latency and EDID quirks. Use one when you need console capture or flawless quality independent of PC load.

Multi-GPU desktops (render on one card, display on another) hit the same wrong-GPU problem. Confirm which adapter the recorder sees before a long session; a five-minute test clip reveals it immediately.

Virtual machines and remote desktop sessions are the hardest case. GPU passthrough setups can record fine, but standard VMs fall back to software rendering, and no bitrate setting rescues a clip rendered by a virtual display adapter.

Reading the Clip's Actual Bitrate Instead of Trusting the Setting

The setting you typed and the bitrate the file actually contains can differ, and the only way to know is to inspect the file. In Windows, right-click the clip, choose Properties, open the Details tab, and look for "Total bitrate" and "Frame rate." That figure is what the encoder produced, and it's the number that determines whether your upload will hold up.

If the file's total bitrate reads far below your Custom setting, the encoder throttled — usually because the GPU was saturated, the drive was too slow to accept the write stream, or a power-saving mode kicked in. Re-test with lower in-game settings or a faster target drive.

If the frame rate reads 60 but the clip stutters, the frames exist but arrived unevenly; that's the frame-pacing case covered earlier, not a bitrate shortfall.

VLC's Media Information panel (Tools > Media Information > Codec Details) gives the same figures with more detail, including the codec profile, which matters if a platform rejected your upload. Knowing the profile — High versus Main, for instance — helps when troubleshooting compatibility.

FAQ

Does adjusting video quality in Windows Settings change Game Bar recordings?

No. Windows Settings > System > Display controls the display resolution the Game Bar captures, but the quality dropdown, frame rate, and bitrate live only in the Game Bar's own Captures panel under Win+G. Changing display settings alone won't touch clip bitrate, and changing the Game Bar settings alone won't change capture resolution. Both panels have to be set deliberately.

Why do my 60 fps clips look worse than my 30 fps clips at the same quality setting?

At a fixed bitrate, 60 fps divides the available data across twice as many frames, so each frame gets roughly half the bits and fast motion shows more compression artifacts. Raising the bitrate proportionally — roughly double for 60 fps — restores the per-frame data. The Game Bar's High preset doesn't adjust for this, which is why Custom bitrate matters.

Can I record at 4K with the Xbox Game Bar?

Only if your display runs at 4K, because the Game Bar captures at active display resolution with no separate recording resolution selector. Even then, 4K60 capture needs a bitrate in the 60–80 Mbps range to avoid visible artifacts, and the Game Bar's Custom field accepts such values. Expect roughly 450 MB per minute at 60 Mbps, so a 10-minute clip eats about 4.5 GB.

Does HEVC recording actually halve my file size?

HEVC typically produces 25–50% smaller files than H.264 at matched visual quality, not a flat 50%, and the savings vary with scene complexity. The catch is compatibility: some older phones, editors, and social platforms won't import HEVC, forcing a re-encode that erases the savings. Verify your destination before switching codecs.

Why does my recording stop after a few minutes?

The Game Bar's default capture length caps recordings, and the setting is easy to overlook. In the Captures panel, "Capture length" offers fixed durations up to a maximum; set it to the longest option for sessions you intend to run long. A full target drive also halts recording, leaving a partial file that often won't play.

Is a capture card worth it over software recording?

A capture card records the display output independently of PC load, so game performance and recording quality stop competing. For console capture it's the only real option. For PC-only recording, the card's cost and passthrough cabling rarely justify it unless you're capturing at 4K60 with HDR consistently — cases where driver recorders sometimes fall short.

Do NVIDIA and AMD recorders use the same bitrate units as the Game Bar?

Yes — all three express bitrate in megabits per second, so a 20 Mbps setting means the same data rate across tools. The difference is where the tools apply it: driver recorders let you pair a bitrate with an explicit downscaled resolution, while the Game Bar ties bitrate to whatever the display is currently running.