About This Software

Raw footage in. Ranked clips out.

CutBench is a Windows app that reads a whole gaming session and hands back the parts worth posting. Point it at a three-hour Twitch VOD, leave it, come back to 10-15 vertical clips, subtitles already burned in, best ones first. You were going to play anyway. This is what turns the session into TikToks, Shorts and Reels without an editor. It runs on your own GPU and the footage never leaves your drive.

Turn gameplay into growth

• Post every day without the grind. One session is a week of shorts, so playing and posting stop competing.

• Ranked by virality. Every clip gets a score and one line saying why, so tonight's three pick themselves.

• Made for socials. Vertical 9:16, subtitles burned into the picture, a title and hashtags written for TikTok, Shorts and Reels.

• Built for gamers, not marketers. The scoring was tuned on kills, clutch plays and the talking between friends, not on conference talks and product launches.

Subtitles in the language you speak

CutBench listens to the recording and writes down what was said, in the language it was said in. Speak Russian and the subtitles come out Russian; speak German and they come out German. Nothing is translated, so the words on screen are yours. Every clip also gets a subtitle file, so you can fix a word before posting.

The menus and buttons in CutBench itself are English. The text it writes into your clips is in the language spoken on the recording, whatever that turns out to be.

Why CutBench

• Local first. The raw session stays on your drive: your voice, the game audio, every embarrassing rage moment. Making the clips never sends any of it anywhere.

• No subscription. One payment, and that is it.

• No usage limits. No monthly minutes and no credits per clip, because the card doing the work is yours.

How it works

Point it at a recording and leave it running. It works through the session on your own GPU, reading the picture as well as the sound, and judges each moment against the others from that session instead of against a volume meter.

• Whole session in. A three-hour VOD or an OBS capture straight off the drive, not a clip already picked out.

• A short list, in order. Each clip already trimmed to where the moment starts and ends.

• Ready to post. 9:16 for Shorts, Reels and TikTok, 16:9 for YouTube, subtitles burned in, post text suggested.

• Your footage stays put. The recording never leaves the disk, and cutting it up needs no internet.

When it finishes, the output folder has the finished videos, a score and a reason for each, suggested post text, and an order to work through.

It reads the picture as well as the sound

Loudness alone does not make the cut. What is on screen counts too, so it lands on moments worth posting rather than on noisy ones. All of it runs locally on your GPU.

What you get per session

• 10-15 ranked vertical clips from a three-hour recording

• Every clip in 9:16 (Shorts, Reels, TikTok) and 16:9 (YouTube)

• Burned-in subtitles in several styles, plus an editable subtitle file beside each clip

• A suggested title, description and hashtags for each clip

• A virality score and a one-line reason for each clip

Then a calendar takes over

Connect YouTube and TikTok once. New clips land on a calendar as they are made, so one session turns into a week of posts nobody has to remember.

• YouTube goes out by itself. The clip is uploaded when you schedule it and goes live at its slot, with CutBench closed and your PC free.

• TikTok is waiting in your drafts. At slot time the clip is already in the TikTok app, one tap from live. That is deliberate: videos posted through the API take a reach penalty; drafts you publish yourself do not.

• A missed day catches itself up. Slots that went by while CutBench was shut are picked up the next time you open it.

Anti-features

• No timeline. If you wanted to drag clips by hand, you would already be in an editor.

• No cloud processing. Your recordings are yours and they stay where they are.

• No "AI face filter" or "AI voice change". CutBench looks for moments that already happened rather than inventing them.

Made for

Streamers and creators who want their gameplay to pay off on social media, and anyone sitting on hours of footage who wants a steady run of shorts without learning an editor, paying every month, or handing it to a third party.

Local-first guarantees

• No telemetry: nothing about how you use it is collected or sent anywhere.

• No mandatory account: the Steam client on your own machine confirms you own CutBench.

• No required internet: making clips works offline. Connecting your accounts and publishing need one.

AI content disclosure

CutBench uses pre-trained AI models that run on your own device for visual scene understanding, audio event detection and text generation (clip titles, descriptions and hashtags). All models are bundled with the app, run on your GPU, and never transmit your input or output to any third-party service. No third-party AI service is contacted. Clips you choose to publish go to your own YouTube and TikTok accounts and nowhere else.

AI Generated Content Disclosure

The developers describe how their game uses AI Generated Content like this:

CutBench is a video application that runs on the user's own computer. The application's core feature is based on pre-trained AI models. These models are included with the application and run only on the user's computer. They analyze gameplay video that the user recorded on their own computer: they recognize what is happening on screen, turn spoken words into text and detect audio events. For each clip the models then generate a short title, short text for the social media post and hashtags. All processing happens on the user's own computer. The application does not contact any third-party AI service, and it does not upload user content for processing. Some of the artwork on this store page (the capsule images, the hero image and the library images) was created with the assistance of tools that generate images using AI, and was then reviewed and edited by hand. The screenshots on this store page were taken from the running application and are not generated images.