STREAMING GUIDE / STREAM TOOLS

OBS Replay Buffer: save the moment that just happened

Create a short rolling capture, save it on demand, and verify that the clip contains the right picture and audio. No third-party replay plugin is needed to save clips.

START HERE

Enable Replay Buffer in OBS Output settings, choose a short duration, assign Save Replay in Hotkeys, and start the buffer. Let it fill, then save and inspect a clip. Starting the buffer and saving a replay are separate actions; enabling the setting alone does not preserve a moment.

1. Choose what you actually want to preserve

Replay Buffer is useful when you want the moments immediately before pressing a key without keeping a full-session recording. It does not reconstruct events from before capture started. Saving a clip is also different from automatically showing an instant replay to viewers.

Begin with a 30-second target and your ordinary recording composition. If you want clean gameplay without overlays, plan that capture layout separately; the normal buffer records the output it is configured to receive. For a first test, avoid additional replay scripts or scene-switching automation.

2. Verify ordinary recording first

Make a short standard recording with game sound and microphone speech. Open it and check the resolution, audio, and chosen save folder. Fix a broken recording path or missing audio before adding a rolling buffer.

Use a folder that exists, is writable, and has room for several test files. Check the recording format and editor compatibility with the OBS recording-format guide. If you use separate audio tracks, make sure the clip includes a convenient full mix as well as any isolated tracks you need for editing.

3. Enable, start, and save as three separate steps

  1. Open OBS settings and locate Replay Buffer under Output. The exact arrangement depends on Simple or Advanced output mode. Enable it and select the maximum replay time.
  2. Check the memory allowance for your mode: Simple mode displays an automatic memory estimate based on your replay duration and quality, while Advanced mode exposes a Maximum Memory (Megabytes) field. Start with a modest cap and a short duration rather than reserving most of your system's RAM.
  3. In Hotkeys, assign a distinct Save Replay key combination. Avoid keys already used for muting, scene changes, or an important in-game action.
  4. Apply the settings and start the replay buffer from OBS's controls. Confirm the control now indicates it is running.
  5. Allow more than the target duration to pass, perform an identifiable test action, then save the replay.

OBS's overview documents separate start, stop, and save controls. An Elgato replay workflow also describes configuring the duration and memory budget; its optional replay-widget script is not required for simple file saving.

4. Set the budget with a realistic scene

A longer or more demanding capture requires more resources. Test while the game, camera, browser sources, and streaming encoder are doing their normal work, not only with a static desktop. Watch whether capture performance changes after the buffer starts.

For a rough constant-bitrate illustration, 20 megabits per second for 30 seconds contains about 75 megabytes of video data before audio and overhead. That arithmetic is not a universal memory setting: variable-quality encoding can grow substantially during complex motion. Use actual OBS estimates and saved results for your configuration.

If the saved clip is shorter than expected, first confirm the buffer had enough time to fill and that its memory cap did not become the limiting factor. Increase duration or memory gradually. If gameplay or encoding performance suffers, reduce the recording workload or duration and retest.

5. Check hotkeys in the situation where you need them

Try saving once with OBS focused, then once while the game has focus. If only the first works, investigate key conflicts or the operating system's input permissions rather than changing the video encoder. On macOS, review the permissions OBS requests for global input; Linux desktop and display-server behavior can differ.

A hardware button can use the official Stream Deck plugin's replay-save action, avoiding a keyboard shortcut collision. Keep a visible running-state check in your pre-stream routine: a perfectly assigned save button cannot retrieve a period that was never buffered.

Inspect two clips and restart once

Save a clip containing a spoken label, a game sound, and a visible scene change. Open it and check its duration, beginning, end, and audio tracks. Then wait and save a second clip to confirm files are not unexpectedly overwritten.

Restart OBS and repeat the start/save check. Write down whether your workflow starts buffering automatically or requires a manual step. To show saved clips live, add and test a separate playback workflow after file capture is reliable; saving a replay alone does not put it on air.

To estimate how much RAM OBS Replay Buffer needs for your bitrate and clip length (plus GB/hour disk usage), check the OBS bitrate & Replay Buffer RAM calculator.

Sources & version notes

Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.