Apex Legends Gameplay 4K 60fps No Commentary

Setting Up Clean 4K Recording for Apex

Most people try to record Apex Legends in 4K 60fps straight from their GPU and immediately run into issues. The game itself runs well on modern hardware, but capturing clean footage at that resolution and frame rate introduces compression artifacts, input lag during preview, and file sizes that eat storage fast. I learned this the hard way after wasting three weekends on failed exports and corrupted files. The approach that actually works involves configuring your capture software properly before you even launch the game. Start with OBS Studio using the NVENC H.264 (or HEVC) encoder if you have an NVIDIA card. Switch to x264 if you're on AMD or Intel. Set your base and output resolution to 3840x2160. Frame rate should be locked to 60. The bitrate is where most people mess up. For H.264 you want around 40 to 60 Mbps for visually clean 4K footage. If you switch to HEVC, you can drop that to 25 to 35 Mbps and still get nearly identical visual quality with roughly half the file size. CRF mode is better than CBR for recording if your storage can handle it, since it allocates bits where they matter instead of maintaining a constant rate that wastes space on static camera views.

Optimizing Apex Legends Gameplay 4K 60fps No Commentary

The word "commentary" in the title is straightforward - it means no voiceover, no chat logging, just pure gameplay. But there are other audio things you need to account for. Game audio will still record. Your mic should be disabled. Windows system sounds can sneak in if you have notifications set up. I disabled all Windows focus assist features and turned off sticky keys before recording. A single notification sound in the middle of a clip ruins the clean aesthetic people look for in these types of videos. Inside Apex, your video settings matter. Set your resolution to 3840x2160 if your monitor supports it, or use a higher render scale if you're running on a 1440p display but want a 4K source. Cap your in-game FPS to 60 or just below your monitor's refresh rate so it matches your recording target. Running triple the frame rate and downscaling during capture introduces unnecessary GPU load and can actually produce worse results than recording natively at 60fps. I ran into this exact problem last year - I was getting 180fps in ranked and trying to capture at 4K 60fps. The footage looked fine in playback but had weird stuttering patterns in fast weapon exchanges. Dropped the cap to 60fps in-game and the issue disappeared completely. Field of view is another setting that people ignore. Keep it between 90 and 110. Higher FOVs stretch the edges and make text and UI elements harder to read in 4K, which defeats the purpose of recording at that resolution. Lower FOVs compress the image unnaturally. 105 is a reasonable default that looks clean and preserves readability.

Performance Reality Check

4K recording at 60fps is heavy. Even on an RTX 4080, you're looking at roughly 10 to 15 percent GPU utilization from the encoder alone. If you're pushing ultra settings at native 4K inside the game while encoding simultaneously, you might dip below a stable 60fps gameplay cadence, which creates a mismatch with your capture target. The workaround is either recording at 1440p upscaled to 4K (the difference is nearly imperceptible on most displays) or dropping in-game settings slightly on resource-heavy components like shadows and post-processing effects. Storage is a practical concern that catches people off guard. A thirty-minute session recorded in 4K 60fps with HEVC at 30 Mbps will produce a file somewhere around 6 to 7 gigabytes. That scales linearly. Two hours of gameplay is roughly 25 to 30 gigabytes per file. Make sure your capture drive has the space before you start, and don't record to your main OS drive if you have a secondary SSD available. The encoder itself has settings that matter more than most guides mention. Look at the preset. P5 or P6 on NVENC gives the best quality-to-file-size ratio. Anything slower like P2 or P3 adds encoding time and marginal quality gains that are invisible in most gameplay footage. The profile should be high. The look-ahead option can stay enabled. Two-pass mode helps if you're planning to do any color grading afterward, but for raw gameplay it adds unnecessary encoding duration without visible benefit.

Common Problems and Fixes

Audio desync is the most annoying issue with 4K recordings. It usually happens when your audio sample rate doesn't match your buffer size or when OBS is competing with Windows audio processing for the same endpoint. Set your OBS audio bitrate to 320 kbps. Set your Windows audio format to 48000 Hz. Make sure there are no audio enhancements enabled in Windows sound settings for your recording device. If desync still occurs, add a small audio delay offset in OBS - typically between 50 and 200 milliseconds depending on your setup. I spent about forty minutes troubleshooting desync on a rig I thought was properly configured. The problem turned out to be a Realtek audio driver updating itself in the background and changing the sample rate mid-session. Another issue is dropped frames during intense firefights. This shows up as visible stuttering in playback even when your system metrics look fine. The fix is usually reducing your GPU shader cache size limit or clearing it entirely before recording. An oversize cache can cause stutters when OBS tries to write frames and the GPU is simultaneously managing shader compilation. I also disable Windows Game Bar and any background recording features, since they compete for the same hardware encoder and can cause frame drops or corrupt output files. If you're capturing on AMD hardware, the situation is similar but the encoder options differ. Use AV1 or HEVC encoding instead of H.264 for better efficiency. AMD's encoders have improved significantly but they still benefit from lower bitrates to achieve comparable quality. You may also need to adjust your presentation mode in the game - disable free sync or set it to a fixed range to avoid frame pacing issues during capture.

The biggest limitation of this setup is that it only works well if your hardware can sustain it. A system with an RTX 3060 or equivalent will struggle to maintain stable 60fps gameplay at 4K while simultaneously encoding. In those cases, targeting 1440p source and upscaling to 4K during post-production is the more practical approach. The final output looks the same on most platforms, and you'll have a much more stable recording process with fewer dropped frames and less stress on your system.