Recording Apex Legends Highlights Without Losing Your Mind
I used to manually clip moments from my Apex Legends sessions using OBS, and it was miserable. You sit there watching replay after replay, scrubbing through timestamps, hoping the fight didn't stutter right before the kill. That changed when I actually learned how to set up proper gameplay highlight recording. This is Apex Legends Gameplay Highlights Part 1 of what ended up being a much longer workflow, and I'm going to walk through it exactly as I use it now. This isn't some official guide or a game feature. It's just the first phase of my clipping routine. The idea is simple: capture clean footage during a full match, then isolate the meaningful segments afterward. Most people skip the capture quality piece and go straight to editing, which is why their clips look like garbage. I start by making sure my overlay is minimal. Crosshair, frame counter, maybe a timer. Nothing else. The moment you stack too many HUD elements on top of the game, it eats into your frame budget and introduces input lag that you'll feel more than see. I run OBS at 1080p 60fps with NVENC encoding, x264 medium preset, and a bitrate of 20,000 kbps. That sounds high but Apex is a fast game with a lot of visual noise, especially during team fights near Storm Point or World's Edge. Lower bitrates turn everything into a mosaic at that point.
The Problem I Ran Into
There's a specific issue that costs most streamers and recorders more time than anything else: the round end cutscene. Apex puts a ~15 second highlight reel between matches, and it overwrites whatever was on your screen. I spent three weeks wondering why my recordings kept having these weird transitions mid-fight. Turns out the game itself pauses the render pipeline for a couple of frames during that transition, and if you're using any kind of GPU-based scaling or sharpening filter, it corrupts the buffer. The workaround is dumb but effective. Disable all post-processing in NVIDIA Inspector for the Obs64 process. Keep it enabled for the Apex process itself if you want the visual bump, but strip it from OBS. The recording stays clean and the game still looks fine when you're watching it directly. I record the entire match from spawn to final circle, usually 10 to 20 minutes depending on how long the game lasts. Then I pull it into DaVinci Resolve and use the audio waveform to find the peaks. Gunfire, ability cues, and movement noise create distinguishable spikes in the track. I don't need to watch the whole thing. I scan for clusters of spikes that indicate sustained combat, skip the looting and travel sections, and mark those points as subclips. This usually takes me about eight to twelve minutes for a full match. I've done it faster, but eight minutes is realistic when you're not rushing and double-checking your markers. The initial recording phase is the variable part. If you're playing short maps like Illipsis or small custom lobbies, you might only have three minutes of actual content to sort through. Larger circles with more rotation time stretch it out.
Common Pitfalls
The biggest mistake I see people make is trying to record at 4K resolution because it looks nice on YouTube. Apex doesn't render enough texture detail at that resolution to justify the file size and render times. You're not gaining anything visible in the final upload. Stick to 1080p. The game's art direction works at that resolution, and your timeline in your editor won't choke on playback. Another thing: don't rely on automatic motion detection in your editing software to find action. Apex has constant camera shake from movement and abilities. The algorithm picks up footstep camera micro-jitters as "motion events" and ends up highlighting empty hallway runs instead of the actual fights. Manual waveform scanning is more accurate and honestly not that slow once you get used to it. If you need help setting up the initial recording configuration, search for "Apex Legends Gameplay Highlights Part 1" to find updated template files from the community. The ones that are a year old or more tend to use outdated encoder settings that don't play well with newer driver versions.
Get the Full Details
