How to Clip With Elgato: Turning Recordings Into Highlights

You just pulled off the play of the night on your PS5 — a clean 1v3 to close the round — and your Elgato recorded every frame of it. Three hours later the session is one long MP4 in your capture folder, and the great moment is buried around the 47-minute mark. Somewhere. Now you get to scrub for it.

Here is the part every ranking page on how to clip with Elgato buries, so we will say it plainly up front: Elgato's software does not find your highlights for you. Not 4K Capture Utility, not the newer Elgato Studio, not the legacy Game Capture HD app — none of them has any kill detection, highlight detection, or auto-clip feature of any kind. They record, and they let you trim by hand on a timeline. That is the entire toolset. If you want the kills found for you, you either scrub the VOD yourself or add a scanner that reads the recording after the fact.

This guide covers how to clip with Elgato end to end: which Elgato app you are on in 2026 (one is officially end-of-life), the capture settings that keep your kill feed legible, how to trim by hand in Elgato's tools, and the one automated path for a local recording — a computer-vision scan that finds every kill in the file without uploading it anywhere.

Which Elgato software are you actually using?

Three apps carry the Elgato name, and which one you have changes every button below.

• Elgato Game Capture HD — the original. Most of Elgato's editing documentation, including the New Video from Timeline Selection trim workflow, still describes this app.
• 4K Capture Utility (4KCU) — the app most HD60 and 4K60 card owners have used for years. Records, has a Library and a basic timeline, and includes Flashback Recording.
• Elgato Studio — the 2025 replacement, now the app Elgato actively ships and develops.

The 2026 fact no clipping article mentions: 4K Capture Utility is on Elgato's official Legacy / End-of-Life list. It is replaced by Elgato Studio and gets no further development or bug fixes — still downloadable, but frozen, as Elgato spells out on its legacy software page. One consequence: 4KCU has a known recording bug with NVIDIA drivers 591.44 and newer that will not be patched. The software you clip with may be abandoned — one more reason not to build your highlight workflow around its manual timeline.

Step 1 — Capture settings that keep the kill feed sharp

Whether you trim by hand or scan later, both live or die on recording quality. The kill feed is small on-screen text, and a starved bitrate smears it into mush. These are the settings we recommend for your Elgato 4K Capture Utility clips — the same values apply in Elgato Studio, and Elgato lists every option in its Software Interface guide:

By default, 4KCU saves to your Windows Videos folder in a 4K Capture Utility subfolder; you can change the destination in the app's capture settings. Note that path — you import the MP4 from it in Step 4.

Step 2 — Record: full session or Flashback Recording

Two ways to capture, and the choice matters:

Full-session recording — hit record at the start, stop at the end, and you get one continuous MP4. This is the right choice if you plan to scan later, because a scanner wants the whole session, not pre-cut fragments.

Flashback Recording — 4KCU keeps a rolling buffer in the background so you can save a moment you already played. Press Ctrl+Shift+F and it saves roughly the last 30 seconds; the buffer is configurable from 5 minutes up to 4 hours.

Flashback sounds like it solves the highlight problem, but it is still fully manual: you press the hotkey after every good play, mid-fight, every time, and the one you forget is always the best one. Set a long buffer and only hit the key at the end, and you are back to scrubbing a huge clip. It is the loop Reddit threads describe: people babysit a replay-buffer hotkey so they do not have to scrub through hours of footage, then still miss kills.

Step 3 — Clip manually in Elgato's software (and where it breaks down)

Elgato's built-in editing is honest, basic timeline trimming. Here is the real walkthrough:

1. Open the Library tab and select your recording.
2. Scrub the timeline playhead to the start of the moment you want.
3. Use the scissors — Split Segment At Playhead — to cut, or drag the trim handles at each end inward.
4. To carve out a single moment, select the range and choose New Video from Timeline Selection (Game Capture HD's wording; Elgato Studio's equivalent does the same job).
5. Export the trimmed clip to a file, or share it out.

For one clip, this is fine. Now do it on a three-hour VOD with eight kills scattered through it: you have to find each moment first — scrubbing the whole recording — before trimming a single one. Elgato gives you good scissors and no map. This is where Elgato's documentation stops, and the community advice becomes "just mark timestamps as you play" or "just use DaVinci Resolve" — both of which still leave the finding to you.

Step 4 — Auto-find every kill in the recording with GameClipper

This is the step Elgato leaves out. To find kills in an Elgato recording automatically, you point a scanner at the file the capture card already produced and let it read the kill feed for you. We built GameClipper Advanced to do exactly that — our product, a Windows 10/11 desktop app, and not a recorder. It starts where Elgato stops: the MP4 in your capture folder.

Why it is the only automated option matters: the popular auto-clippers — Medal, Outplayed, NVIDIA Highlights — detect kills by hooking the game process on your PC. When the game runs on a console and reaches your PC only as an HDMI capture, there is no process to hook, only pixels. Software that reads those pixels is the single automated path — the mechanism is in our kill feed detection guide.

1. Import the MP4 from your 4KCU recording folder. Length does not matter — whole-session VODs are the point.
2. Calibrate once per game. Pause on any frame where the kill feed is visible, draw a box around the feed, and capture your in-game name. It is saved as a reusable profile, so your next VOD of that game skips straight to scanning.
3. Scan. A computer-vision pass reads the kill feed region across the entire file and flags every line where your name is the killer, with OCR name confirmation keeping false positives near zero — a teammate's kill in the same feed will not become your clip.
4. Everything stays local. No streaming account, no Twitch broadcast, no cloud upload, no queue. The footage never leaves your machine.

Tuning and trimming happen without re-scanning. Adjust match sensitivity, lead-in and lead-out per clip (4 seconds in, 2 out is a solid default), scan rate, and minimum clip length — results recompute live, with no second pass. Preview any clip, nudge its start and end, trim, drop, or restore. Then export with GPU NVENC: a 1080p 16:9 montage with hard cut, fade, or crossfade transitions, or a 9:16 vertical for Shorts and TikTok using a blurred pillarbox so the HUD and kill feed are never cropped — here is how the blurred pillarbox keeps the HUD on screen. An NVIDIA GPU is recommended for the fastest exports, not required.

To be transparent on price: the free version does full detection, scanning, editing, and export forever with a small watermark on exports; a one-time $19 (sign in with Google to activate) removes it, and there is no subscription.

Elgato vs the automated clippers: which works on a capture-card VOD?

If you are shopping for capture card clipping software, the question that matters is whether it can find kills in a local recording without making you stream or upload first. Here is the field:

The split is clear. Eklipse can take a local file, but only by uploading it to Eklipse's servers and waiting in a cloud processing queue on a monthly plan — a lot of ceremony, which is why players look for Eklipse alternatives. Medal detects only games running on your PC, so console footage through a capture card is invisible to it. A local scan on the file your Elgato already produced is the only automated path that never asks you to upload your footage or wait in a queue.

Troubleshooting Elgato recordings

• Nothing records, or the recording is black, on newer NVIDIA drivers: 4KCU has a known recording bug with drivers 591.44 and above. Because 4KCU is frozen, the fix is Elgato Studio or a driver rollback — the bug will not be patched.
• Footage looks washed out or grey: that is HDR on an SDR pipeline, which looks flat and crushed and costs the kill feed contrast. Turn HDR off at the source and record SDR.
• Running low on disk: capture eats storage fast. At a healthy 1080p60 bitrate, budget roughly 50-100 MB per 30 seconds — about 6-12 GB per hour — and 4K60 several times that.
• Choppy preview but the file plays fine: the live preview can stutter under CPU or USB load while the recording is smooth. Check the exported file before assuming a bad capture, and play off your TV passthrough.

The record-to-highlights checklist

Run this once and the whole pipeline becomes routine:

1. Prefer Elgato Studio over the frozen 4K Capture Utility.
2. Set 1080p60 minimum, HDR off, a hardware encoder, and a healthy bitrate.
3. Record the full session as one MP4 — save Flashback (Ctrl+Shift+F) for one-off grabs only.
4. Import that MP4 into GameClipper Advanced from your recording folder.
5. Calibrate once: box the kill feed, capture your in-game name, save the profile.
6. Scan the whole VOD, then tune lead-in, lead-out, and minimum length live and drop the weak clips.
7. Export 16:9 for YouTube and 9:16 with the blurred pillarbox for Shorts and TikTok.

Elgato is a genuinely great recorder — that was never the problem. The gap is that it hands you a beautiful three-hour file and no idea where the good parts are. Fill that gap with a scan and the manual scrubbing disappears. The free version of GameClipper Advanced does the full detect-edit-export loop with a small watermark on exports, so you can prove the workflow on last night's Elgato recording before paying anything. For the whole console pipeline, start at our hub on auto-clipping console gameplay, or grab the app from the download page.