Rage Replay
Scream. Clap. React. Your clip is already saved.
Start new thread
Anton Tkalenko

Rage Replay - Scream. Clap. React. Your clip is already saved.

by•
Rage Replay is a lightweight Windows replay recorder that continuously keeps a rolling gameplay buffer and saves clips when you react. Use hotkeys, voice triggers, clap detection, or rapid mouse movement to capture moments instantly. Supports NVENC, AMD AMF and Intel QSV with automatic fallback for older hardware. No accounts, no cloud — just local MP4 clips and low system overhead.

Add a comment

Replies

Best
Anton Tkalenko
Maker
📌
Hey everyone 👋 I'm the solo developer behind Rage Replay. The idea came from a problem I kept seeing over and over: people miss great gaming moments because OBS wasn't running, ShadowPlay silently stopped recording, or they simply forgot to start recording before playing. Instead of building another traditional screen recorder, I focused on one goal: making sure the clip exists when you need it. One of the most interesting features ended up being reaction-based triggers. Rage Replay can save clips using voice peaks, clap detection, or rapid mouse movement, because in many cases your reaction is the best indicator that something worth saving just happened. I also spent a lot of time testing different hardware configurations to make the recorder behave consistently across NVIDIA, AMD, Intel and older systems. Everything runs locally. No accounts, no cloud uploads. I'd love to hear what you're currently using for replay recording and what annoys you most about existing solutions.
Josimar Valderrama

The reaction trigger is the best part here.

Most missed clips happen because you only realize something was worth saving after you screamed, laughed, or slammed the mouse. Using that reaction as the save signal makes a lot of sense for games, especially when OBS or ShadowPlay was not running.

What annoys me most with replay tools is silent failure. If Rage Replay can make it obvious that the buffer is active, recording is healthy, and hardware fallback is working, that alone would make it easier to trust during a long session.

Anton Tkalenko
Maker

@josimar_valderrama Appreciate this comment — especially the part about silent failure.
That’s exactly one of the problems I wanted to solve with Rage Replay.

A lot of replay tools technically work until the one moment you actually need the clip and realize the buffer died 40 minutes ago, the encoder crashed silently, or the recording desynced.

The reaction trigger came from the same idea: most “save that” moments are emotional reactions first, conscious decisions second.

I’m currently improving visibility around recorder health, buffer state, and fallback handling for long sessions specifically because trust matters more than raw feature count in this kind of software.

Really valuable feedback — thanks for taking the time to write it.