How to clip ARC Raiders without touching a hotkey mid raid: play the session you were going to play anyway, then drop the recording in. CutBench reads the whole file, ranks the firefights, ARC encounters and clutch extractions, and hands them back as vertical ARC Raiders clips with captions. No timeline to scrub.
The usual advice for clipping an extraction shooter is to hit a hotkey the moment something good happens. That advice is backwards for this game. The moment you would want to save is almost always the moment your hands are busiest, and pressing an extra key during a three-way fight at an extraction point is a good way to turn the clip into a death screen. The alternative is to record everything and sort it afterwards. That is the short answer to how to clip ARC Raiders without losing the fight you were trying to save.
This is the part that makes ARC Raiders awkward to clip by hand. The game is built on a slow rhythm and the interesting part is a small fraction of it. A raid opens with a drop and a long, quiet approach. Then looting, which is mostly menus and footsteps. Then contact, which may be with machines, may be with another squad, and often turns out to be nothing at all. Then either a run for an extraction point or a death, followed by the loadout screen and the queue for the next one.
Stretch that over an evening and you have a recording where most of the runtime is approach, inventory and travel, punctuated by short bursts that matter. Scrubbing that timeline by hand is the actual work, and it is the reason most people's footage folder never becomes anything. A ranking pass exists to do that scrubbing so you only look at the candidates.
The rhythm also explains why a naive cut on the loudest audio spike does not work here. The loudest second of a raid is frequently a Rocketeer volley that missed you entirely while you were already sprinting away. What makes an ARC Raiders clip is the resolution, not the noise. Whether you got out, whether the other squad let you go, whether the thing chasing you actually caught you.
CutBench's ranking is fine-tuned on ARC Raiders footage. It reads the on-screen action and listens to the recording, then scores candidate moments on how they build and, more importantly, how they end. These are the shapes it is looking for.
ARC Raiders produces a kind of clip that most shooters cannot: two strangers talking through a standoff over proximity voice. Someone shouts that they are friendly. Someone offers to trade. Someone lies, and you find out about four seconds later. Those exchanges are frequently better content than the gunfight they replace, and they are completely invisible to any tool that only looks for muzzle flashes and volume spikes.
CutBench reads the picture as well as the sound in the same pass, so a moment is judged on more than how loud it got. The transcript then becomes the caption track, which matters because most of the people who will see the clip are watching it without sound. A silent viewer still gets the exchange.
One practical caveat, because this is a recording setup question rather than a software one: it can only hear what your recorder captured. If your capture includes desktop or game audio on the same track, proximity voice comes through and gets transcribed. If you record game audio to a separate track, or your party chat lives entirely in Discord on another device, that audio is not in the file and nothing can recover it. Worth checking your OBS or ShadowPlay audio settings once, before a long session, rather than after.
No ranking pass understands your raid the way you do, and the honest version of this page says so. These are the failure modes we know about in ARC Raiders footage specifically.
The way to think about it: the ranking is there to cut a three hour recording down to the handful of candidates worth your attention, not to decide for you which of those you post. Most of the value is in not scrubbing the timeline.
Yes. CutBench's ranking is fine-tuned on ARC Raiders footage. It reads the on-screen action and game audio to find firefights, ARC encounters, and clutch extractions, then cuts them into vertical clips.
Record the session end to end with ShadowPlay, OBS or the Xbox Game Bar and keep the full file. Drop that file into CutBench and leave it running. It scores the session and returns ranked vertical clips with captions, so you review candidates instead of scrubbing a three hour timeline.
No. Drop a full session and CutBench finds the moments for you. No in-game hotkeys, no manual marking. It ranks candidates by how likely each is to perform.
Whatever your recorder captured is what it can work with, so proximity exchanges end up in the captions. If your recorder captures game audio on a separate track, or your voice chat runs through another device, that audio is not in the file and cannot be recovered.
Roughly two to five hours on an RTX 3060 class GPU, depending on the card and the footage. It is designed to be started and left alone rather than watched.
Yes. Buy once on Steam. No subscription, no per-clip credits. A free demo runs the full pipeline with a small watermark.
No. Everything runs locally on your NVIDIA GPU. Your footage never leaves your PC.
Windows 10 or 11 and an NVIDIA GPU with 6 GB of VRAM and CUDA support, plus 8 GB of RAM and 30 GB of free disk. AMD and Intel Arc GPUs are not supported, and there is no macOS or Linux build.
Start with the free Demo. It runs the same ranking on your own PC and watermarks the exports, so you can see what it pulls out of one of your own sessions before you decide. Buy once when you're ready to drop the watermark.