A FragCut alternative
with no clip quota.

Their computer and a meter. Or your computer and no meter.

FragCut is a browser product. You upload a file or point it at a Twitch VOD, their servers do the detection and the rendering, and finished clips come back. Nothing to install, no graphics card to own, and it works the same from a MacBook, an office laptop or a machine with an AMD card in it. For a lot of people that is the whole ballgame, and we are not going to pretend otherwise.

CutBench is a Windows app that never sends the file anywhere. Transcription, audio-event detection, scene detection, HUD state detection, ranking, trimming, captioning and rendering all happen on your own NVIDIA GPU. The recording stays on your drive, party voice and all. There is no account to create before you can process a session, and no queue behind other people's uploads.

The second split is the bill. FragCut is billed monthly, and on the cheaper plan the month comes with an allowance: 30 clips, reset each month, with unused credits not rolling over. CutBench is one payment on Steam and then nothing. That difference compounds the more footage you have, which is the situation most people shopping for a tool like this are actually in.

The axes that actually decide it.

FragCut figures read from fragcut.io/pricing on 14 August 2026: Creator at $19.99 per month with 30 clips per month, Pro at $49.99 per month with unlimited clips, both listing source videos up to 4 hours, credits resetting monthly and not rolling over, and a 7-day money-back guarantee for first-time subscribers. The turnaround figure is FragCut's own stated 15 to 30 minutes for a local upload. Blank cells mean the feature is not offered, not that it is offered badly. Plans change, so check the vendor page before you buy.

What 30 clips a month actually means.

Thirty clips a month is one clip a day. If you play three evenings a week and record all of them, the allowance, not the footage, becomes the thing that decides how much of your material ever gets looked at. You start rationing: only the session you think was good, only the fight you already remember. Which quietly puts you back in charge of finding the moments, and finding the moments is the job you were paying to hand off.

There is a second-order effect worth naming. When each clip has a price, you stop generating the marginal one, and the marginal clip is where the surprises live. Nobody rations their way to the moment they had forgotten about. The Pro plan at $49.99 per month removes the cap, and if you are producing at that volume it may well be worth it, but it is $599.88 over a year against $34.99 once.

CutBench has no credits. There is nothing to reset, nothing to roll over, and no plan to upgrade to when you get busier. Run the same session five times with different settings if you want; the only cost is your own GPU time and some disk. Creator at $19.99 per month comes to $239.88 over a year, so the one-time license is paid back in under two months against the cheaper plan.

Both prices above are as displayed to us on the date given. Regional pricing, tax and promotions move these numbers around, so treat them as a checkpoint rather than a quote.

What is actually being detected.

Rust is the hard case for any clipper, because a Rust session is mostly not a highlight. Hours of farming and building sit between the moments worth posting, and the moments themselves are badly shaped: a raid is long and loud and the payoff is a few seconds somewhere in the middle, and the best fights often end with you dead.

So it is worth being precise about what CutBench does and does not do, because the category is full of language that implies more than it should. There is no text recognition in the pipeline. Nothing reads a kill feed, a scoreboard, a damage number or any other text on screen. Anyone claiming to count your kills from the feed is doing something CutBench does not do.

What it does use, in plain terms:

• Game audio events. Gunfire, explosions and the general shape of a firefight. In Rust that is what separates a raid from the two hours of gathering that paid for it.
• Speech. Your voice and your party's, transcribed locally, which is where most of the comedy and nearly all of the usable captions come from.
• Scene changes. Cuts, deaths, respawns and hard visual transitions, used to work out where a moment actually starts and stops.
• A trained HUD classifier. It recognises the wounded screen, the death screen, the inventory, the map and farming. Wounded and death are strong signals that something just happened; inventory, map and farming are strong signals that nothing did.

That last one is the piece that matters most on a survival game. Recognising the boring states is how the boring states stop reaching the top of your list. Each clip comes back already trimmed to its payoff, cropped to 9:16, captioned and labelled with a hook, so the review is a couple of minutes rather than an evening. There is a fuller write-up on the Rust clip maker page, and the same engine is tuned for ARC Raiders, with a generic profile on everything else.

When FragCut is the better pick.

What going local costs you.

Running everything on your own machine buys privacy, no meter and a one-time price. It charges you in hardware and patience. Worth knowing before you buy:

• Windows and NVIDIA only. Windows 10 or 11, 8 GB of RAM, 30 GB of free disk, and an NVIDIA GPU with 6 GB of VRAM and CUDA 11.8 or newer, meaning an RTX 2060, RTX 3050 8GB or RTX 4050 and up. 16 GB of RAM and a card with 10 GB of VRAM or more is the comfortable configuration.
• No AMD, no Intel Arc, no Mac, no Linux. There is no fallback path and no browser version. If that is your setup, a hosted tool is the right answer.
• It is not instant. A 3-hour session runs roughly 2 to 5 hours on an RTX 3060 class card, against FragCut's stated 15 to 30 minutes. You start it and leave. What comes back is a whole session's worth of clips rather than one.
• No Twitch VOD import. CutBench works on files you already have on disk. If your footage lives on Twitch and not on your drive, FragCut's link import is a step CutBench does not replace.
• Your PC is busy while it works. Best run overnight or while you are away, not mid-raid.
• The models ship inside the build. After that it works with no connection at all.

What you get by going local.

• No meter, ever. No credits, no monthly allowance, no upgrade prompt when you get busier. Process the same session five times if you feel like it.
• Nothing is uploaded. A 3-hour capture is a large file, and on the local route it never leaves the drive it was recorded to. No upload wait, no account, no copy of your party chat on a server you do not own.
• One-time license. Bought once on Steam. No renewal date, and nothing stops working at the end of a month you forgot to pay for.
• No source length limit. Whatever fits on your disk is a valid input. There is no 4-hour ceiling to plan your recording around.
• Honest about mechanism. No text recognition, so no claims about reading your kill feed. Audio events, speech, scene changes and a trained HUD classifier, which is what the ranking actually runs on.
• Works with no internet. The models ship inside the build, so the whole thing runs on a plane.

FragCut-switcher FAQ.