How to Reduce Compression Artifacts in Game Capture: Proven Ways That Work (2026)

Compression artifacts are what make a clean game capture look blocky, smeary, or washed out after you hit record. You will see them as macroblocking in dark areas, banding in skies, mosquito noise around sharp edges, and soft detail during fast motion. You cannot eliminate compression entirely unless you record lossless, which is impractical for most PCs, but you can reduce visible artifacts to the point where they are unnoticeable on YouTube or in local playback. Expect the biggest gains to come from bitrate and codec choice, not from small filters or post-processing. As capture hardware and encoders have matured in 2026, even mid-range GPUs can now record visually lossless footage if you configure them correctly.

Quick Wins

Start here if you want fast results before diving into full tuning. These changes take under five minutes and address the most common causes of blockiness and banding.

Step-by-Step Tuning

Apply these in order. Each method follows the same structure so you can test, verify, and roll back safely. Work on a single test game with both dark scenes and fast motion for consistent evaluation.

1. Raise Bitrate or Switch to Quality-Based Rate Control

What causes it: Low bitrate is the number one cause of macroblocking. Most default profiles use CBR 8,000 to 12,000 Kbps for streaming compatibility, which starves a 1440p or 4K recording during motion. The encoder discards detail to stay under the limit.

How to check: In OBS Studio, go to Settings > Output > Recording and note Rate Control and Bitrate. In NVIDIA App Overlay (Alt+Z > Settings > Video Capture) check Bit Rate. In AMD Software: Adrenalin Edition > Record & Stream > Recording Settings check Bitrate. If you see CBR under 20,000 Kbps at 1080p60 or under 40,000 Kbps at 1440p60, you are bitrate-limited.

What to do: For local recording only, do not use streaming CBR. In OBS Studio > Settings > Output > Output Mode: Advanced > Recording tab: Set Encoder to NVIDIA NVENC HEVC, AMD AMF HEVC, or AV1 if available. Set Rate Control to CQP or CQP-like Constant Quality. Set CQ Level / QP to 18 to 20 for high quality, 16 for near-lossless, 22 to 24 for smaller files. If your encoder only offers CBR, set Bitrate to 40,000 to 60,000 Kbps for 1080p60, 60,000 to 80,000 Kbps for 1440p60, and 100,000 to 140,000 Kbps for 4K60. Set Keyframe Interval to 2 seconds. Apply and restart the recording.

Trade-off: File size grows 3x to 6x. A 10-minute 1440p60 CQP 18 file can be 15 to 30 GB. You need fast storage and more editing disk space.

How to undo: Return to Settings > Output > Recording and set Rate Control back to CBR and Bitrate to your previous value, or restore your OBS Profile via Profile > Previous Profile.

2. Switch Codec from H.264 to HEVC or AV1

What causes it: H.264/AVC is less efficient at preserving fine detail at the same bitrate. Grass, foliage, rain, and particle effects break into blocks first on H.264 because the codec needs more bits to describe high-frequency detail.

How to check: Record a 30-second clip panning through foliage or a smoky scene. Right-click the file > Properties > Details or open in MediaInfo and check Video Format. If it says AVC/H.264 and you see blockiness, a modern codec will help. Check GPU support: NVIDIA RTX 40/50 series and AMD RX 7000/9000 series support HEVC and AV1 hardware encoding. Intel Arc A-series and newer also support AV1.

What to do: In OBS Studio > Settings > Output > Recording: Set Encoder to NVIDIA NVENC HEVC (H.265) or NVIDIA NVENC AV1, or AMD HW HEVC / AV1. Set Preset to P5 Quality or P6 Slow and Tuning to High Quality. For GeForce Experience / NVIDIA App: Alt+Z > Settings > Video Capture > Codec > HEVC. For AMD Adrenalin: Settings > General > Codec Type > HEVC or AV1. Keep Audio at AAC 320 Kbps so you are only testing video.

Trade-off: HEVC and AV1 require more GPU encoder load and may not be supported by all editors or playback devices. AV1 is the most efficient but can stutter on older CPUs during timeline scrubbing unless you use proxy media.

How to undo: Set Encoder back to NVIDIA NVENC H.264 or AMD HW H.264 in the same menu. No restart required.

3. Correct Chroma Subsampling, Color Range, and Bit Depth

What causes it: Wrong color settings cause banding and color bleed. Recording in 4:2:0 with Limited range when your game renders Full range crushes blacks and creates stepped gradients in skies. Some guides suggest 4:4:4 for better text, but it increases bitrate demand and can worsen artifacts if bitrate is not raised.

How to check: In OBS Studio > Settings > Advanced > Video: Check Color Format, Color Space, and Color Range. Play a gradient-heavy scene like a sunset sky. Pause the recording and look for banding. In Windows > Settings > System > Display > Advanced Display, verify if HDR is on. If HDR is on, you should be capturing 10-bit.

What to do: For SDR capture: Set Color Format to NV12, Color Space to Rec. 709, Color Range to Full. In Settings > Output > Recording, ensure Rescale Output is unchecked. For HDR capture: Set Color Format to P010, Color Space to Rec. 2100 / PQ, Color Range to Full. Keep the encoder in 10-bit mode (P010). In NVIDIA Control Panel > Change Resolution > Output Color Format: set to RGB or YCbCr444 and Output Dynamic Range to Full, then let OBS handle the conversion to NV12/P010.

Trade-off: Full range can look washed out if you upload without proper flagging, and P010 files are larger and need an HDR-aware editor like DaVinci Resolve or Premiere Pro with HDR enabled.

How to undo: In Settings > Advanced > Video, set Color Format back to NV12, Color Space to 709, Color Range to Limited, and click Apply.

4. Lock Resolution: Disable Output Rescaling and FPS Mismatch

What causes it: Downscaling on the encoder or capturing at a different resolution than your game forces a real-time scale that softens the image and magnifies compression artifacts. Frame rate conversion has a similar effect.

How to check: In OBS Studio > Settings > Video: Note Base (Canvas) Resolution and Output (Scaled) Resolution. In Settings > Output > Recording: Check if Rescale Output is checked. In game, check Display > Resolution. If they do not match, or if Rescale is enabled, you are scaling twice.

What to do: Set Base and Output Resolution to the same value as your game. For example, if you play at 2560×1440, set both to 2560×1440. Go to Settings > Output > Recording and uncheck Rescale Output. Set Common FPS Values to an integer that matches your recording target: 60 or 120. Avoid 59.94 unless you need NTSC compatibility. If you must downscale for file size, do it in Settings > Video > Output Resolution only, set Downscale Filter to Lanczos (36 samples), and leave Rescale Output unchecked.

Trade-off: Native resolution recordings are larger and harder to edit on lower-end systems. You gain sharpness but lose convenience.

How to undo: Re-enable Rescale Output in Settings > Output > Recording or set Output Resolution back to 1920×1080 if you need smaller files.

5. Tune Encoder Preset, B-Frames, and Look-Ahead

What causes it: Fast or Low Quality presets skip analysis to save encoder time. This shows as shimmering edges and reduced detail retention in motion, even at high bitrates.

How to check: In OBS Studio > Settings > Output > Recording with NVENC: Check Preset, Tuning, and Multipass Mode. With AMF: Check Quality Preset and Pre-Analysis. Record a high-motion test and zoom to 200 percent in VLC (Tools > Effects and Filters > Video Effects > Magnification) to see edge stability.

What to do: For NVIDIA NVENC: Set Preset to P5 Quality or P6 Slow (Quality), Tuning to High Quality, Multipass Mode to Two Passes (Quarter Res). Enable Look-ahead and set B-Frames to 2 to 4. Psycho Visual Tuning: On. For AMD AMF: Set Quality Preset to Quality, set B-Frames to 3, enable Pre-Analysis and Adaptive MiniGOP, set Max B-Pictures to 3. For Intel Quick Sync / Arc: Set Target Usage to Quality and B-Frame count to 3. Apply and test in the same scene.

Trade-off: Slower presets use 5 to 15 percent more encoder and memory resources and can cause encoding lag if you are GPU-bound. If you see Encoding Overload in the OBS status bar, step back to P5 Quality.

How to undo: Set Preset back to P3 Medium / Balanced or Quality Preset back to Balanced, and disable Look-ahead.

6. Remove Capture Interference: Game Capture vs Display Capture and Overlays

What causes it: Using Display Capture or Window Capture instead of Game Capture adds an extra compositor layer, which can introduce color shifts and force GPU copy overhead. Overlays that inject sharpening or HDR tone-mapping also re-process the frame before encode.

How to check: In OBS Studio > Sources: Check if you are using Game Capture. Press Alt+Tab during capture and note if FPS drops or if OBS shows Capture Interference warning in Stats (View > Stats). Check for active overlays: Discord > Settings > Game Overlay > Enable in-game overlay, Steam > Settings > In Game > FPS Counter, and NVIDIA Overlay.

What to do: In Sources, click + > Game Capture > Create New > Mode: Capture Specific Window or Capture Any Fullscreen Application > Check SLI/Crossfire Capture Support off, Anti-cheat hook on, Capture Cursor unchecked if you do not need it. Keep Display Capture as a separate Scene, not layered under Game Capture. Disable extra sharpening: NVIDIA App > Graphics > Game Filters off, AMD Adrenalin > Gaming > Graphics > Radeon Image Sharpening off for capture sessions. Set Windows Game Mode to On and Game DVR Capture off via Windows > Settings > Gaming > Game Mode and Captures > Background Recording Off.

Trade-off: Game Capture does not capture launchers or desktop popups. You will need to switch Scenes for non-game content.

How to undo: Re-enable overlays in their apps and change OBS Source back to Display Capture if you prefer ease of use.

7. Record to the Right Container on Fast Storage

What causes it: Recording to a slow drive or to MP4 directly causes encoder backpressure. The encoder drops quality to keep up, and if the PC crashes, MP4 files become unplayable, which is often mistaken for corruption artifacts on the next attempt.

How to check: In OBS Studio > Settings > Output > Recording: Note Recording Path and Recording Format. Check drive speed: Open Task Manager > Performance > Disk and watch Active Time during recording. If it stays above 90 percent, your drive is the bottleneck. File location default is C:\Users\YourName\Videos.

What to do: Set Recording Format to MKV or Fragmented MP4 (hybrid MP4). Set Recording Path to an NVMe SSD or a secondary SSD, not an HDD or USB 2.0 drive. Path example: D:\Captures\OBS\. Enable Settings > Advanced > Automatically Remux to MP4 so MKV is converted to MP4 after recording stops (File > Remux Recordings also works manually). Set File Name Formatting to %CCYY-%MM-%DD %hh-%mm-%ss to avoid overwrites.

Trade-off: Fragmented MP4 and MKV files may need remuxing before some editors import them cleanly, adding one extra step.

How to undo: Set Recording Format back to Standard MP4 and path back to C:\Users\YourName\Videos.

Measure Before and After

Do not judge by eye only on a small preview window. Use a repeatable method. First, create a 30-second benchmark scene: load a game with a static menu, a dark interior, and an outdoor pan with foliage. Save that save file so you can replay it identically.

In OBS Studio > View > Stats, enable Dropped Frames, Encoding Lag, and Rendering Lag. Record with your old settings once, then again after each change above. Keep audio unchanged.

For visual comparison, open both files in VLC Media Player. Use Tools > Effects and Filters > Video Effects > Sharpen off, and compare at 100 percent zoom, not fullscreen. Pause on the same frame using shortcut E for frame-by-frame advance. Look for block edges in shadows, banding in gradients, and held texture detail on walls during motion.

For technical verification, check the file with MediaInfo. Confirm Video > Format, Bit rate, Width/Height, Frame rate, and Color space match what you intended. In DaVinci Resolve > Media Page, right-click clip > Clip Attributes > Video to verify data rate and color management. Log each change in a text file in your captures folder such as D:\Captures\capture_log.txt with the setting and your qualitative observation, for example, CQP 18 vs CBR 12k – less macroblocking on foliage pan.

Finally, test your upload target. If you upload to YouTube, upload an unlisted 60-second test. YouTube re-encodes everything, so judge your local file before upload. If your local file is clean but the YouTube version blocks, your local settings are correct and the platform compression is the limit.

What Not to Do

Do not add post-capture sharpening, de-noising, or detail filters to hide artifacts. Filters like Sharpen, LUT intensity over 100, or aggressive Color Correction in OBS > Filters amplify the block edges and make encoding harder. Fix the bitrate and codec first, then add color only if needed.

Do not record at 120 FPS and then re-encode to 60 FPS in the same pass to save bitrate. Capturing at double frame rate halves the bits per frame at a fixed bitrate and creates stutter if the game cannot sustain it. Record at your delivery frame rate. If you need slow motion, record at 120 FPS at a proportionally higher bitrate (roughly 1.8x to 2x the 60 FPS bitrate) and deliver in a separate project.

Do not set CQP or QP to 0 to 10 thinking it will be perfect. Levels below 14 produce huge lossless-like files that can exceed your SSD write speed and cause encoder stalls. You will get dropped frames that look like freezes, which are worse than any artifact.

Do not enable both H.264 software x264 encoding on the CPU and hardware NVENC at the same time for the same capture, or stack two recorders such as OBS and ShadowPlay simultaneously. They contend for the same frame buffer and lower effective quality. Pick one recorder per session.

Do not raise in-game sharpness, film grain, chromatic aberration, or lens distortion to mask softness. Film grain is intentionally high-frequency noise and will dramatically increase required bitrate. Turn film grain off in game Graphics > Post Processing before capture, then add it back in edit if desired.

FAQ

Why does my 4K game look great live but blocky in the recording?

Your live render is uncompressed before it hits the display, while the recording is heavily compressed. At 4K60, CBR 12,000 to 20,000 Kbps is far too low and the encoder throws away detail in motion. Switch to HEVC or AV1 with CQP 18 to 20 or raise CBR to 100,000 to 140,000 Kbps for local files. Also confirm you did not leave Rescale Output checked in OBS Studio > Output > Recording, which would downscale your 4K to 1080p before encoding and then upscale on playback, softening the result.

Should I use MKV, MP4, or MOV for game capture?

Use MKV or Fragmented MP4 for recording, then deliver as standard MP4. MKV survives crashes without corrupting the entire file and supports HEVC and AV1 cleanly. In OBS Studio > Settings > Output > Recording, select MKV and enable Automatically Remux to MP4 in Settings > Advanced. MOV is fine on Mac with ProRes but offers no advantage for hardware NVENC/AMF recording on Windows and can cause audio sync issues in some editors.

Does 10-bit and HDR capture reduce banding?

Yes, when the game actually outputs HDR. If Windows > System > Display > HDR is on and the game runs in native HDR (not Auto HDR), capturing in P010 10-bit with Rec. 2100 preserves gradients and reduces visible banding compared to 8-bit NV12. To use it, set OBS Studio > Advanced > Video to P010 and ensure your Encoder is set to HEVC or AV1 10-bit. If you capture SDR content in P010, you will not reduce banding and will only increase file size and editing overhead.

Will a higher encoder preset fix artifacts without raising bitrate?

Only up to a point. Changing from Max Performance to Quality or Slow improves motion analysis and efficiency, so artifacts lessen modestly at the same bitrate. Once bitrate is the bottleneck, no preset can invent bits that are not there. Raise bitrate or switch to quality-based rate control first, then use the slowest preset your system can handle without Encoding Overload. If Task Manager > Performance > GPU > Video Encode usage hits 95 to 100 percent, step back one preset level.