The OBS Replay Buffer keeps the last chunk of your gameplay in memory so that when something amazing happens, one hotkey saves just those moments to a clip, no full recording or editing needed. It’s the free alternative to Instant Replay and works whether you stream or not. Here’s how to configure it for reliable, high-quality clips.
Turn on the buffer
- Open OBS Settings > Output.
- Set Output Mode to Advanced.
- Go to the Replay Buffer tab and check Enable Replay Buffer.
- Set Maximum Replay Time to how many seconds you want to keep (30-120 is typical).
Assign a hotkey
Without a hotkey the buffer is useless in the heat of the moment.
- Go to Settings > Hotkeys.
- Find Save Replay and bind it to a spare key (a mouse side button or F-key works well).
- Also bind Start Replay Buffer so you can arm it quickly.
| Setting | Recommended | Note |
|---|---|---|
| Max replay time | 60 s | Long enough for most plays |
| Encoder | Hardware (NVENC/AMF/QuickSync) | Low performance hit |
| Bitrate | 40-70 Mbps (1080p60) | Higher = sharper, bigger files |
| Memory used | Scales with time + bitrate | 60s@50Mbps ≈ under 400 MB RAM |
Balance quality and memory
The buffer lives in RAM, so a longer time and higher bitrate use more memory. A 60-second buffer at 1080p60 and a sensible bitrate sits comfortably under half a gigabyte, which any modern gaming PC handles. Use a hardware encoder so buffering barely touches your frame rate.
Where clips are saved
Set the recording path in Settings > Output to a large, fast drive. Give saved replays a clear filename format so you can find that clutch moment later without opening every file.
Use it in practice
Before you start playing, press your Start Replay Buffer hotkey (or set OBS to start it automatically). Play normally. The instant something clip-worthy happens, tap Save Replay and OBS writes the last 60 seconds to disk while you keep playing. There’s no need to trim a long recording afterward.
Auto-start the buffer
In Settings > General, enable “Start replay buffer when OBS launches” (or use a startup automation) so you never forget to arm it and miss a highlight.
Turning clips into content
The Replay Buffer’s real value is that it removes friction. Because saving is a single keypress that captures only the last minute, you never sit through a two-hour recording hunting for the good moment. Set a buffer long enough to catch the build-up to a play, not just the kill, so your clips have context. Sixty seconds suits most games; bump it up for slower, strategic titles where the setup matters.
Build a light workflow around it. Point saved replays at a fast archive drive with a clear filename pattern including date and game, arm the buffer automatically at launch so you never forget, and periodically skim your saves to keep the best and delete the rest. With a hardware encoder doing the work, the performance cost is negligible, so you can leave it running every session. Over time you accumulate a library of highlights ready to trim for social clips or montages, all captured in the moment without interrupting your game.
FAQ
Does the Replay Buffer hurt performance?
With a hardware encoder, the impact is minimal because encoding runs on the GPU’s dedicated block and the buffer just holds recent frames in RAM. Software (x264) encoding costs more CPU, so hardware encoding is strongly recommended.
How long can my replay be?
As long as your RAM allows. Longer buffers at high bitrate use more memory, but 60-120 seconds at 1080p60 is easily handled by a typical gaming PC. Set it to comfortably cover the length of a good play.
Bottom line
Enable the Replay Buffer in Advanced output, set a 60-second window, bind a Save Replay hotkey, and use a hardware encoder writing to a fast drive. Arm it before you play and one keypress captures your best moments, giving you ShadowPlay-style clipping entirely free in OBS.
