Auto-Clip Console Gameplay From a Capture Card

You hit the collat of your life on PS5. Your capture card recorded every frame of it, the passthrough never stuttered, and the whole session is sitting on your PC as a clean MP4. Then you open Medal to grab the clip — and there is nothing there. No auto-clip, no highlight, no notification. Medal sat silent through the best play you have made all month, because as far as Medal could tell, no game was ever running.

That is not a settings problem, and reinstalling will not fix it: no software installed on your PC can auto clip console gameplay the way it auto-clips PC titles. Medal Auto-Clip, Outplayed, NVIDIA Highlights, and SteelSeries Moments all promise to automatically record kills, assists, and downs — and they deliver on PC — but every one of them works by hooking into the game process running on your machine. When the game runs on a PS5 or Xbox, that process does not exist on your PC. There is nothing to hook, so there is nothing to detect. Ever.

The only automation that can work on console footage is software that reads the pixels in the recording itself. This hub maps the entire console-to-PC pipeline — console to capture card to OBS to a file on disk — shows how to scan that file so software finds every kill for you, compares all nine tools console players ask about (two of them partially work, and we will say so), and prices out the workarounds honestly.

Why Medal, Outplayed, and NVIDIA Highlights can never auto-clip console gameplay

PC auto-clippers feel like magic, so it is worth being precise about how each one actually detects a kill:

• Medal.tv Auto-Clip watches for supported games launching on the same Windows machine and reads events from the running game.
• Outplayed is built on Overwolf's game events API — a per-game integration that reports kills, deaths, and assists straight from the game process.
• NVIDIA Highlights goes a step further: the developer has to build NVIDIA's SDK into the game, and the game code itself tells the driver a highlight just happened.
• SteelSeries Moments and Insights Capture follow the same pattern — event detection from titles running locally on the PC.

Every one of these is a process hook. They need the game executable alive on the same computer as the clipping software. Now trace the console signal path: the game runs on your PS5's silicon, and your capture card hands your PC an HDMI stream — pixels and audio, nothing else. No process to attach to, no events API, no memory to read. Pointed at a capture-card feed, a process hook sees the equivalent of a video player, and video players do not get kills. It is also why searches for PS5 apps for automatic kill recording come up empty: nothing on the console side exposes kill events either, so the automation has to happen on your PC, on the recording.

Medal is the clearest case, because console players keep asking. Medal has no capture card as a recording source at all — that exact feature has sat as an open request on Medal's own feedback board for years (requests 3191 and 3931). You can import PS5 and Xbox share-button clips into Medal for trimming and sharing, but no detection ever runs on imported files. We cover the full picture in Does Medal.tv work on console?

None of this is a bug or a missing toggle. It is architecture. A tool built on process hooks can only add console support by becoming a completely different kind of tool.

The only automation that works on console footage: reading the pixels

An HDMI recording contains exactly two things software can analyze: the video track and the audio track. Any real automation for console gameplay has to work on one of those — there is no third option.

The audio route is what Eklipse's voice trigger does: you say a phrase like "Clip It" while streaming and that moment gets marked. Handy, but notice what it is — a manual trigger where your voice replaces a hotkey. Nothing detects the kill; you do, and you have to remember to speak up every single time.

The video route is computer vision on the kill feed. Every major shooter prints one — Warzone, Apex, Fortnite, Valorant, CS2, Battlefield, PUBG, Delta Force. When your name appears on the killer's side of a feed line, that is evidence of your kill, burned into the pixels of the recording itself. Software can step through the file, watch the kill feed region, and find every one of those moments after the fact.

That is exactly what we built GameClipper Advanced to do, and we would rather name the mechanism than call it AI magic: it runs a computer-vision scan over the kill feed region you calibrate, with OCR confirmation of your in-game name, so a teammate's kill in the same feed does not become your clip. The mechanics — regions, matching modes, and why name confirmation pushes false positives to near zero — get a full write-up in our kill feed detection guide. Because it reads the feed instead of hooking a process, it is game-agnostic: any game with an on-screen kill feed works, with no per-game integration required.

Reading pixels has one property process hooks can never match: it does not care when or where the game ran. A PS5 session from last night, an Xbox VOD from last week, a friend's capture-card recording — if there is a kill feed in the frame, the scan finds the kills. Nothing has to run during the session, and nothing has to stream.

The console-to-PC pipeline, step by step

Here is the full path from controller to a scannable file. If you already have MP4s on disk, skip ahead to the scan.

1. Console settings: flip one switch or your card records black

On PS5, go to Settings → System → HDMI → Enable HDCP and turn it off. HDCP is copy protection on the HDMI output, and most capture cards will show a black screen for games until it is disabled. Xbox does not apply HDCP to gameplay (only to streaming apps), so no change is needed there.

2. The capture card: a recorder, not a clipper

A capture card does exactly one job: it turns the console's HDMI output into a video device your PC can record. It does not detect anything and it does not clip anything. The Elgato HD60 X is the usual reference point — 1080p60 capture with 4K60 passthrough, so you keep playing at full quality on your display while the card feeds the PC — but any card from AverMedia or others that shows up as a video device in Windows works for this pipeline. Our Elgato clipping workflow guide covers card setup end to end.

3. OBS settings that keep the kill feed readable

Record with OBS Studio: add a Video Capture Device source, pick the capture card, and set the canvas to 1920x1080 at 60 fps. For recording quality, NVENC H.264 at CQP 20-23 (or CBR at 25-40 Mbps if you prefer predictable file sizes) is plenty. Quality matters more than usual here, because detection reads text-sized UI elements — a starved bitrate that smears the kill feed hurts both your VOD and the scan.

Record the entire session as one file. The old advice for this exact problem was OBS's Replay Buffer plus a hotkey. That still works as a manual baseline, but it is exactly the labor we are trying to delete: you must press the key after every kill, and the one you forget is always the play that mattered.

4. No capture card? Use the console's own DVR

You can run this whole workflow without a card. The PS5 continuously buffers up to the last 60 minutes of gameplay, saveable from the create button, and Xbox has its own Game DVR captures. Get those files onto your PC — we walk through every transfer route in how to transfer PS5 clips and full VODs to your PC and getting Xbox clips to PC — and they scan exactly the same as capture-card footage. The card's advantages are unlimited length, higher bitrate, and no console storage juggling.

Either way, the pipeline ends in the same place: an MP4 on your PC's disk. That file is the input for everything below.

Scan the capture-card VOD with GameClipper Advanced

GameClipper Advanced is our Windows 10/11 desktop app, and to be transparent up front: it is our product, the free version keeps full detection, editing, and export forever with a small watermark, and a one-time $19 removes the watermark. It is not a recorder — it exists precisely for the file your capture card just produced. Everything runs locally and offline; your footage never leaves your machine.

1. Import the VOD. Load the MP4 — an OBS recording, an Elgato file, or a transferred console capture. 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. That is saved as a reusable profile, so your next VOD of the same game goes straight to scanning.
3. Scan. The 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.
4. Tune without re-scanning. Adjust match sensitivity, lead-in and lead-out per clip (4 seconds in, 2 seconds out is a solid montage default), scan rate, and minimum clip length. Results recompute live from the finished scan — there is never a second pass to wait for.
5. Review the timeline. Preview any clip, nudge start and end points, trim, drop the ones you do not want, restore anything you change your mind about.
6. Export. GPU NVENC export produces a 1080p 16:9 montage with hard cut, fade, or crossfade transitions — or a 9:16 vertical version for Shorts and TikTok that uses a blurred pillarbox, so the HUD and kill feed are never cropped. An NVIDIA GPU is recommended for the fastest exports, not required.

Every tool, honestly: what actually works on capture-card footage

Here is the whole field in one table, including the two tools that partially work. The detection method column explains everything else.

So the precise claim — the one no tool page states plainly — is this: no process-hooking tool will ever auto-clip kills from console gameplay, because the process it needs runs on the console. Pixel and audio analysis are the only possible routes. AssistantGG genuinely runs pixel analysis live on a capture-card feed (Windows, around 36 supported games, freemium with a €11.99/month tier), and Eklipse genuinely processes console streams after you go live. GameClipper Advanced is the one that scans a file already sitting on your disk — offline, no stream, any game with a kill feed.

The workarounds, and what each one costs you

Stream first, clip later (Eklipse)

Eklipse's console flow: stream your session to Twitch, Kick, or YouTube, end the broadcast, and let Eklipse process the platform VOD. It works — and if you already stream, it is a sensible pipeline. If you do not, count the costs: you need a public, audience-facing channel just to get clips; Twitch's roughly 8 Mbps ceiling for 1080p60 means Eklipse analyzes a compressed copy of your gameplay instead of your clean local recording; and your highlights wait on a cloud processing queue. Going live to an empty channel as a clipping workaround is a lot of ceremony for a highlight reel — the full breakdown is in our Eklipse alternatives guide.

Detect live while you play (AssistantGG)

AssistantGG analyzes the capture-card feed in real time on Windows and lists compatibility with Elgato, AverMedia, and Sveon cards for PlayStation, Xbox, and Switch. The honest limits: detection only happens while the app is running during the session. Yesterday's recording is invisible to it, because its VOD mode only accepts Twitch, YouTube, and Kick links — not local files — and the full feature set sits behind a monthly subscription.

Replay Buffer plus a hotkey (OBS)

Free, reliable, and fully manual. OBS keeps the last N seconds of the capture-card feed in memory and writes them to disk when you press a hotkey. Nothing is detected for you — in a three-hour session you will forget at least once, and you will not find out until you check the folder.

Share-button clips into Medal

The create button on PS5 and Xbox's capture feature save short clips you can import into Medal for trimming and sharing. That is editing, not detection — you still have to notice every kill yourself, capture it in the moment, and live within the console DVR's length and quality caps.

Go deeper: every guide in the console-to-PC cluster

This hub is the map; the spokes below are the turn-by-turn directions for each stage of the pipeline:

• Transfer PS5 clips and full VODs to your PC — USB, the PS App, and working around the 60-minute buffer.
• Get Xbox clips to PC and beat Game DVR's limits — OneDrive, USB, and capture-length workarounds.
• How to edit console gameplay on PC — the complete post-scan editing workflow.
• Medal.tv alternatives that keep your clips local — for players moving off the cloud-first tools.
• Convert 16:9 gameplay to 9:16 without cropping the HUD — how the blurred pillarbox keeps the kill feed on screen for Shorts and TikTok.
• How to make a gaming montage from VOD to upload — turning the detected clips into something worth posting.

From console kill to posted clip: the checklist

Run down this list once and the whole pipeline becomes routine:

1. PS5 only: turn off HDCP under Settings → System → HDMI.
2. Connect console to capture card, card to PC, passthrough to your display.
3. In OBS, record 1080p60 with NVENC at CQP 20-23 — one file for the whole session.
4. No card? Save console DVR captures and transfer them to your PC instead.
5. Import the MP4 into GameClipper Advanced.
6. Calibrate once: box the kill feed, capture your in-game name, save the profile.
7. Scan the whole VOD and let every detection land on the timeline.
8. Tune lead-in, lead-out, and minimum clip length — live, with no re-scan.
9. Preview, trim, or drop clips until only the good ones remain.
10. Export 16:9 for YouTube, and 9:16 with the blurred pillarbox for Shorts and TikTok.

The free version of GameClipper Advanced does every step above — full detection, scanning, editing, and export, forever, with a small watermark on exports — so you can prove the pipeline on your own footage before spending anything. If the watermark bothers you, removing it is a one-time $19, not a subscription. Download it here, feed it last night's VOD, and let the software do the rewatching.