Tarkov Auto Clip: Your Kills, Not Your Deaths

You extract from a 40-minute Streets raid with three PMC kills, load the VOD that night to clip them, and hit the problem every Tarkov player runs into: nothing marks where the kills were. No kill feed scrolled. No hitmarker flashed. The only thing the game ever put on screen about those fights was the Survived banner after you exfil'd. That's the reason the Tarkov auto clip tools you've tried keep handing you your deaths instead of your kills. The death screen is the one thing they can actually see.

Here's the honest version most "Tarkov clipper" pages won't give you: in main raids, PvE, and Arena, a kill leaves no on-screen trace. Any tool that promises to detect your kills from the footage alone is either reading the post-raid results banner (which fires on deaths and extracts, not kills) or guessing from audio and "AI intensity" heuristics. The one thing that truly knows you got a kill is the game engine itself.

Transparency up front: we make GameClipper Advanced, a Windows 10/11 app, and we'll be straight about where it fits. It is not what detects your Tarkov kills, because nothing on Tarkov's screen can be read as one. It's the fully offline editor that turns the kill footage you captured, from NVIDIA's Highlights, a raid VOD, or your own clips, into a finished vertical kill reel without a frame leaving your PC. The free version runs the whole edit-and-export pipeline forever with a small watermark. Below is the accurate map of what works, mode by mode.

Why every Tarkov auto-clipper hands you your deaths

Hypetrigger is the closest thing to a pixel-based EFT clipper, and it's the clearest proof of the problem. Its only Escape from Tarkov trigger is "death / raid ended": it watches a small region for the white results banner and clips roughly 15 seconds before it. That isn't a design failure, it's the honest ceiling of screen-reading in Tarkov, where the results banner is the only reliable on-screen event. A pixel tool can clip the moment you died or extracted, and nothing else.

Outplayed, which auto-clips through Overwolf's per-game event hooks, simply doesn't support EFT. Players have begged on the ideas board for years: "Highlights for Escape from Tarkov" (OP-I-7832) and a separate death-highlight request (OP-I-9136) carry the same complaint, that raids run 30-45 minutes, fights last 5-10, and finding your kills afterward is brutal. Medal records Tarkov and clips on a hotkey, but automatic event detection is a request on its feedback board, not a feature.

So the "kills, not deaths" gap isn't laziness, it's data: deaths and extracts print a banner on screen; kills print nothing.

What actually shows on screen when you get a kill in Tarkov

Before trusting any tool's claim, know what the game renders when you kill someone. It's less than you'd think.

Main raids (PMC and Scav)

No kill feed. No hitmarker. No "enemy down" popup. This is deliberate: BSG built Tarkov so you're never certain your shots landed until the body stops moving or you loot it. Your XP doesn't tick live. The combat and EXP breakdown, your kills and headshots, appears only on the post-raid results screen after you extract or die. Mid-raid, on screen, a kill is invisible. That uncertainty, the gear fear, the "did I actually drop him," is the whole point of the design, and it's exactly what starves a pixel scanner.

EFT Arena

Arena is more competitive, but its HUD is just as minimal by design: no traditional kill feed, no elimination ticker. Team-remaining counts and round score live on in-world screens (the half-red, half-blue TVs on each map), not an overlay. Players have asked BSG to add a killcam and feed to Arena, which tells you there isn't one. Screen-reading detection has nothing extra to grab in Arena either.

PvE mode

PvE runs the same HUD as live raids, just against AI, so the same rule holds: no on-screen kill signal, results only at the end. To a scanner, PvE footage looks identical to a live raid.

The one real kill signal. If nothing's on screen, how does anything know? The game engine. Tarkov integrates NVIDIA's Highlights, which fires on your kills and deaths and auto-saves short clips from the game code, not the HUD. That's why community tools like tarkov-kill-confirmer and tarkov-kill-detector work by watching NVIDIA's Highlights output folder, and why the game's own log file (which stat overlays parse) is the other place a kill is recorded. That's the layer to capture from, not the screen. One caveat: NVIDIA folded ShadowPlay and Highlights into the NVIDIA App in 2025, so confirm Highlights still fires in your build.

Why audio and "AI intensity" can't rescue it

Cloud clippers lean on two claims for Tarkov, and both fall apart here. Clypse markets "gunshot & hit confirmation audio" detection, but main-raid Tarkov has no hit-confirmation sound to detect, and no hitmarker to hear. Worse, a raid's audio is a constant wash of gunfire from fights that aren't yours, three buildings away, plus suppressed weapons that barely register. An audio model can't tell your Killa drop from a distant Scav firefight across Interchange.

FragCut is vaguer still, promising that "AI tracks the intensity." Intensity of what? In a game where your tensest moments are often dead silent, holding an angle in dorms, intensity is just noise. Neither approach has an anchor that reliably means "you killed someone in Tarkov," so both clip broadly and let you sort it out, after you've uploaded a four-to-six-hour VOD and waited in a queue.

The honest workflow: capture the kills, then assemble offline

Given all of the above, here's the pipeline that actually produces a kills-only reel.

1. Capture from the layer that knows

Turn on the engine-level capture that fires on kills, either NVIDIA Highlights set to save kills, or just record the whole raid with the NVIDIA App, ShadowPlay, or OBS. If you record full raids, keep the post-raid results screen in frame: it lists how many kills you got, so you know how many to hunt for.

2. Pull your kills out of the raid

From a Highlights folder you already have short clips, one per kill. From a full raid VOD, use log-based kill timestamps (stat overlays expose them) or the post-raid kill count to jump to each fight instead of scrubbing 40 minutes blind. It's the same navigate-don't-rewatch problem we cover in how to find kills in a VOD, just harder because Tarkov gives you no feed to anchor on.

3. Build the reel locally

Drop those clips or VOD segments into GameClipper Advanced. It's a hand-editable timeline: preview each kill, nudge the start and end, trim the walk-up, drop the ones that don't land. Then auto-assemble the montage with hard cuts, fades, or crossfades, and export with GPU NVENC, 1080p 16:9 plus a vertical 9:16 cut that uses a blurred pillarbox, so your health bar, thermals, and loot are never cropped out of frame. Nothing uploads; the whole thing runs on your machine.

Fully offline, nothing running during your raid

This is the part this community actually cares about. Cloud clippers make you hand over your footage: upload a four-to-six-hour VOD or paste a Twitch link, then wait 15-30 minutes in a queue on someone else's servers. GameClipper Advanced never uploads anything; it reads a file already on your disk and writes the export next to it.

On ban paranoia, let's be fair: ordinary recording software was never the risk. BattlEye, the anti-cheat Tarkov uses, states plainly that non-hack programs, OBS, Fraps, overlays and the like, are not banned. The reason to prefer a local, after-the-raid tool isn't ban-dodging; it's that nothing new is injected into your game and nothing runs while you play. Our app doesn't even open until the raid is over: no overlay, no hooks, no upload. If keeping footage on your own machine is the priority, that's the same logic we lay out in whether Medal.tv is safe.

Recording settings for 30-45 minute raids

Full-raid recording is the right call in Tarkov precisely because fights are long and rare. A replay buffer tuned to 30-60 seconds, perfect for an arcade shooter, chops the front off the five-minute Labs fight that's the entire point of the clip. Record the whole raid and pull clips after the fact.

Storage math so you plan the disk, not the panic: at 1080p60 with an NVENC bitrate around 30-40 Mbps, a 40-minute raid is roughly 9-12 GB, and AV1 or HEVC on a modern NVIDIA card roughly halves that. Five raids lands near 50-60 GB, so keep a scratch drive and delete the dry Factory runs the next morning. Record at native resolution and encode on the GPU so recording never costs you frames mid-fight; if you're weighing the encoder, we compared them in NVENC vs CPU encoding.

Tarkov auto clip tools compared

An honest field as of mid-2026. Note that the only entry that genuinely detects your kills is the engine-level one, and the cloud tools' "detection" rests on signals Tarkov doesn't really produce.

If you want the same screen-reading detection working the way it should, point it at a game that actually renders a feed. Our kill feed detection hub explains the method, which does the automatic heavy lifting in titles like Delta Force. Tarkov just isn't one of them, and we'd rather say so than sell you an "AI" that pretends otherwise.

Stop scrubbing 40-minute raids for your three kills

The honest pipeline, compressed:

1. Capture kills from the layer that knows: NVIDIA Highlights set to save kills, or record the full raid with any recorder.
2. Pull your kills using Highlights clips, log timestamps, or the post-raid kill count, so you jump to each fight instead of rewatching the raid.
3. Drop them into GameClipper Advanced, trim on the timeline, auto-assemble with transitions, and export 1080p 16:9 plus a vertical 9:16 cut that never crops the HUD.

And because no cloud page will tell you what it costs: the free version of GameClipper Advanced does all of this forever with a small watermark on exports. A one-time $19 purchase removes it (sign in with Google), with no subscription, no clip caps, and no upload queue. Download it free, drop in last night's Highlights clips or that Streets VOD, and build your kill reel without a frame leaving your PC. Want the watermark gone? Here's the pricing.