OBS Replay Buffer: How to Set Up Instant Replays (2026)
OBS Replay Buffer setup guide: configure hotkeys, buffer length, and save instant replays for esports broadcasts without dropping frames.
If your stream cuts back to live the moment a clutch ends, you''re losing the most valuable five seconds of every round. The OBS Replay Buffer is the single feature that separates a hobby broadcast from one that feels produced, and most casters either leave it off or run it with defaults that drop frames the moment they hit save. This guide walks you through configuring the OBS Replay Buffer for esports — the right duration, encoder choice, hotkeys, scene wiring, and a dual-PC pattern that mirrors how tier-1 production trucks handle instant replays. By the end you''ll have a workflow you can run solo on a single tower or scale to a two-machine rig without rewriting your scenes.
What the OBS Replay Buffer actually does
The OBS Replay Buffer is a rolling in-memory recording. OBS keeps the last N seconds of your program output in RAM and writes nothing to disk until you trigger ''Save Replay.'' That''s the whole trick — there''s no disk I/O during normal streaming, so the cost is almost entirely memory. The official OBS documentation covers the basic toggle under Settings → Output → Replay Buffer, but the defaults are tuned for general streaming, not esports pacing.
For tactical shooters (CS2, Valorant), 20 seconds is the sweet spot — long enough to capture the pre-fire setup, the engagement, and a beat of reaction. For Rocket League, 12–15 seconds covers a full goal play. For MOBAs, push to 30 seconds so you can rewind into the rotation that set up the kill. A 1080p60 buffer at a 6,000 kbps bitrate uses roughly 15 MB per second of footage in RAM, so a 30-second buffer reserves around 450 MB. On a 32 GB system that''s invisible; on a 16 GB streaming rig, plan accordingly.
OBS replay buffer settings that actually hold up under load
Open Settings → Output, switch Output Mode to Advanced, and on the Recording tab set Type to Standard, Format to mkv, and Encoder to ''Use stream encoder.'' Sharing the encoder eliminates a second NVENC or x264 session, which is the most common cause of frame drops the instant you hit save. MKV is non-negotiable: if your PC crashes mid-clip, the file is still playable. You can remux to MP4 later from Tools → Remux Recordings.
Then on the Replay Buffer tab, set Maximum Replay Time to your game''s value (20s for tac shooters), and Maximum Memory to roughly 1.5× the bitrate-per-second × duration, in MB. Leave the Prefix/Suffix fields alone, but set a Replay Buffer Filename Formatting string like replay_%CCYY-%MM-%DD_%hh-%mm-%ss so saved clips sort chronologically in your file browser — critical when you need to rebuild a scene mid-show.
- Bind ''Save Replay'' to a single hotkey under Settings → Hotkeys — use a Stream Deck key if you have one, otherwise pick something you''ll never hit by accident (F9 works).
- Keep Process Priority at Normal. ''Above Normal'' starves the game and adds input lag for the player you''re observing.
- If you''re on NVENC, enable Psycho Visual Tuning and set Preset to P5 (Slow). Quality goes up, encoder load barely moves.
- Disable the in-game NVIDIA ShadowPlay overlay. Two replay systems fighting over the same encoder will drop frames.
Wiring the OBS replay buffer into a clean scene transition
Saving the clip is half the job. The other half is showing it without the dead-air gap that screams ''amateur.'' Create a scene called REPLAY with three sources: a Media Source pointing at your latest replay file, a stinger transition for the entry, and a lower-third overlay that says ''REPLAY.'' On the Media Source, check Restart playback when source becomes active and Close file when inactive. This forces OBS to re-read the file every time the scene activates, which is what makes the same source play the newest clip on each trigger.
The trick: instead of pointing the Media Source at a specific file, point it at a fixed path like C:\OBS\replays\latest.mkv, then run a tiny PowerShell or AutoHotkey watcher that copies the newest file in your replay folder to latest.mkv whenever a new one lands. Three lines of script, and your replay scene always plays the clip you just saved. Pair it with a Stinger transition under Scene Transitions and the cut looks indistinguishable from the replay wipes you see on a partnered tournament broadcast.
Dual-PC OBS replay buffer setup for serious esports broadcasts
Once you''re producing a real show — a tournament you''re running on HUDrift, a regular weekly cast, or a multi-game event — a single PC starts to bottleneck. The cleanest split is to keep the gameplay capture and live program on your main rig and run the replay buffer on a secondary machine receiving an NDI feed from the main. The secondary PC has no game running, so it can run a longer buffer (60–90 seconds) and a higher-quality recording without affecting the live broadcast at all.
Install the DistroAV NDI plugin on both machines. On the main PC, add a Dedicated NDI Output filter to your program scene. On the secondary, add an NDI Source pointed at the main''s output, then enable the Replay Buffer there with its own hotkey routed over the network with a tool like Deckboard or a second Stream Deck. The result is a dedicated replay operator workflow that mirrors how regional leagues handle it — one person watches the game, another rides the replay buffer and feeds clips back into the program over a return NDI feed.
Common OBS replay buffer problems and how to fix them fast
Two failure modes account for almost every ''it worked yesterday'' support thread. First: saved clips are zero bytes or corrupt. This is almost always a permissions issue on the recording path — point the buffer at a folder you own (not Program Files or a OneDrive sync folder), and confirm Windows Defender Controlled Folder Access isn''t blocking OBS. Second: the buffer silently stops working after a scene collection import. Replay Buffer settings live per scene collection, so importing or switching collections without re-enabling the buffer leaves it off. Check the status bar at the bottom of OBS — if you don''t see ''Replay Buffer: Active,'' it isn''t running.
Frame drops the moment you hit save almost always trace to encoder contention. Confirm Recording is set to ''Use stream encoder,'' close any second capture tool (NVIDIA app, AMD ReLive, Discord''s Go Live), and watch the Stats window during a save. If CPU usage spikes past 70% on save, your bitrate or buffer duration is too high for the rig — drop the buffer to 15 seconds and re-test before touching anything else.
Where the OBS replay buffer fits in the rest of your broadcast stack
The Replay Buffer is one piece of a production stack — overlays, scoreboards, and bracket graphics carry the show between plays. If you want to see how the replay scene fits next to live brackets and score tickers, the HUDrift overlay packs include the lower-thirds and stingers used in the examples above, and the download page covers the OBS plugin pieces (NDI, stream-encoder hooks) you''ll want installed before you start wiring scenes. For a side-by-side of how production tools compare on replay features specifically, the HUDrift vs. alternatives breakdown covers it.
Ready to ship? Enable the buffer, set your duration, bind a hotkey, build the replay scene, and run a private test stream tonight. Save five replays in a row, switch to the scene each time, and confirm the newest clip plays every transition. If it does, you''re ready to use this on a real cast — and the next time something insane happens on your broadcast, you''ll catch it.
Frequently Asked Questions
- How long should the OBS replay buffer be for esports?
- For tactical shooters like CS2 and Valorant, 20 seconds is the standard — it captures the setup, the engagement, and a beat of reaction without bloating memory. Rocket League works well at 12–15 seconds since plays resolve faster. MOBAs benefit from 30 seconds so you can rewind into the rotation that set up the kill. Match the buffer to how long the story of a play actually takes in your game.
- Does the OBS replay buffer cause lag or frame drops?
- Not on its own. The buffer lives in RAM and writes nothing to disk until you save, so the only ongoing cost is memory. Drops almost always come from encoder contention — running the Recording output on a separate encoder, or having a second capture tool like NVIDIA ShadowPlay active at the same time. Set Recording to ''Use stream encoder'' and disable other capture tools to fix it.
- Where are OBS replay buffer files saved?
- They save to the path set in Settings → Output → Recording → Recording Path, using the filename format defined under Advanced. By default that''s your user Videos folder. Point it at a dedicated folder you own — not Program Files, not a OneDrive-synced folder, and not anywhere Controlled Folder Access protects — or saves will silently fail with zero-byte files.
- Can I use the OBS replay buffer with a dual-PC setup?
- Yes, and it''s the recommended pattern for serious broadcasts. Send an NDI feed from your gaming PC to a secondary production PC, then enable the Replay Buffer on the secondary. The production machine has no game running, so it can hold a longer buffer (60–90 seconds) and record at higher quality without touching the live broadcast. A dedicated replay operator can then trigger clips on demand.
- What''s the difference between OBS replay buffer and NVIDIA ShadowPlay Instant Replay?
- ShadowPlay records continuously to disk at the OS level and is independent of your stream. The OBS Replay Buffer records the same program output your viewers see — overlays, scene composition, alerts — and stays in memory until you save. For broadcasts, the OBS buffer is the right tool because the saved clip already contains your production layer; ShadowPlay clips give you raw gameplay without any of it.
