How to clip Rust, the multiplayer survival game from Facepunch, not the programming language: record the wipe, drop the whole file in, and CutBench ranks the raids, roams and PvP into vertical Rust clips with captions, on your own Windows PC. Force wipe, online raids, door camps, roads at night.
Search for how to clip Rust and half the results are about the programming language, so here is the disambiguation up front. This page is about Rust the multiplayer survival game by Facepunch: the naked beach spawn, the 2x2 that grows into a compound, the monthly force wipe on the first Thursday, the raid that starts at three in the morning while half the team is asleep.
CutBench is a Windows desktop app that watches a recording of that and cuts out the parts worth posting. You record with whatever you already use, whether that is OBS, ShadowPlay, Game Bar or Medal. You point CutBench at the file. It ranks the moments, renders 9:16 vertical Rust clips with burned-in captions, and writes a title, hook and hashtags for each one. Nothing is uploaded to a server on the way, because the whole thing runs on your own computer already sitting in your machine. If you want the wider picture first, the CutBench overview covers the pipeline for every game.
This is the part most clip tools get wrong about the game. A Rust session is not a match that ends in a win or a loss anyone can point at. It is a long, uneven stretch of survival with a handful of spikes buried in it, and the spikes do not announce themselves.
Roughly speaking, an evening of Rust gives you four or five moments that a viewer would actually watch, and they are scattered across hours of footage you do not want to scrub through. That scrubbing is the job CutBench takes off your hands.
Generic clip tools cut on volume spikes, but a loud moment isn't always a good one. CutBench has no special knowledge of Rust. It finds the raid because a raid builds and pays off, not because it knows what C4 is. What holds a viewer is the same shape in every game, so it lands on the online raid that pops, the roam that turns, and the fight you actually won, not just the loudest 10 seconds. On a Rust session, that comes out like this:
The same stack runs on ARC Raiders and on everything else. There is no list of supported games and nothing to select. A title with no page of its own goes through exactly the same way.
Rust wipe day lands on the first Thursday of the month, when force wipe hits, and it is the single best day of the Rust calendar to record, because the density of real moments per recorded hour is at its peak. Here is the whole loop, from hitting record to a clip that is live.
Repeat it the following Thursday and the one after. There is no per-clip credit meter, no monthly export cap and no quota to plan around, so a heavy wipe month costs exactly the same as a quiet one.
Honest answer: it throws most of it away, and that is the feature. Dead air goes out first. A six-hour stretch of sulfur runs, upkeep and base building produces very few candidates, and the ones it does produce are the contacts inside it, the moment the node run turns into a fight, or the moment a naked chases you across the road.
That is a different job to a highlight tool built for a game with rounds and a winner at the end. Rust never marks the interesting part, so the finding has to happen afterwards. The practical result is that you can hand it the whole session, farming and all, instead of pre-trimming to the bits you half remember. Handing it more footage does not cost more money; it costs time on a card that was bought to play Rust and sits idle every hour it is not playing.
One more consequence worth knowing: because everything happens after the fact, there is no capture overlay running while you play, so your in-game frame rate is untouched during the wipe itself.
No tool reads Rust perfectly, and a page that claims otherwise is selling you something. These are the real limits, stated up front rather than discovered later.
The fair question to ask before buying is what your own wipes are actually made of. If they are mostly quiet trap kills, base tours and building, the list above is what to expect. If they are raids, roams and PvP, there is plenty in a session to work with, and nothing to enable first.
The game. CutBench clips gameplay from Rust, the multiplayer survival game by Facepunch. It has nothing to do with the Rust programming language and does not work on code.
Yes, and there is nothing to enable first: there is no list of supported games, because nothing in CutBench changes depending on the game. It finds the raids, fights and payoffs in the session, trims them, crops to 9:16 and burns in the captions.
No. Drop a full session and CutBench finds the moments for you, with no in-game hotkeys and no manual marking. It ranks candidates by how likely each is to perform.
A 3-hour session takes roughly 2 to 5 hours on an RTX 3060 class GPU. It runs after you finish playing, so most people start it and leave it overnight.
It drops them. Dead air goes out first, and only the contacts inside that stretch come back as candidates. You can hand it the whole session instead of pre-trimming.
Often not. A kill with nothing loud and no reaction gives it very little to go on, so quiet moments are the weakest case. Loud raids are the strongest.
Yes. Buy once on Steam, with no subscription and no per-clip credits.
No. Everything runs locally on your own computer. Your footage never leaves your PC.
Windows 10 or 11 and an NVIDIA GPU with 6 GB VRAM and CUDA support, such as an RTX 2060, RTX 3050 8GB or RTX 4050. 8 GB of RAM minimum, 16 GB recommended, and 30 GB of disk space. AMD and Intel Arc are not supported, and there is no macOS or Linux version.
The whole pipeline, running on your own PC. One purchase on Steam, no subscription, no per-clip credits.