Annodex logo AnnodexNotes for people who make media
Stream Setup

Recording a Local Backup in OBS While You Stream Live

A friend streamed a two hour board game session, promised the group a highlight reel, then opened the platform VOD the next morning and found a 720p re-encode with three visible stutters and the music section silenced by an automated...

An OBS output settings window showing separate streaming and recording tabs beside an external drive and a notepad of session timecodes

A friend streamed a two hour board game session, promised the group a highlight reel, then opened the platform VOD the next morning and found a 720p re-encode with three visible stutters and the music section silenced by an automated copyright mute. The stream itself had looked fine live. The recording she needed to edit from did not exist.

Streaming and recording are two different outputs, and most software will happily do both at the same time. The local file is encoded before your upload ever touches the internet, so it carries none of the network damage, none of the platform re-encode, and none of the retention limits. Setting this up takes about ten minutes once, and it is the difference between a stream that disappears and a stream you can cut into a month of short videos.

What the platform VOD actually gives back

The archive on a streaming site is a copy of what arrived at the ingest server, not a copy of what left your room. If your encoder skipped frames or your upload hiccuped, those gaps are baked into the file permanently. This is the same set of counters behind dropped frames on stream, and the VOD is where their damage becomes irreversible.

The bitrate ceiling matters as much. Most people stream 1080p at 6000 to 8000 kbps because that is what a home upload sustains. A local recording has no such limit: at constant quality on a modern GPU encoder, a 1080p60 file typically lands between 20 and 30 Mbps. That is three to four times the data for the same picture, which is the difference between footage that holds up after a crop and a zoom and footage that smears the moment you push it.

Then there is retention. Depending on your account tier and settings, a VOD may sit for 14 days, 60 days, or until you remember to click export. Automated audio muting can remove whole minutes without warning. And multi-track audio is gone: the VOD carries one mixed stereo pair, so you cannot pull your voice away from the game sound later.

Setting up the second output without choking the first

In OBS the control you want is Settings, Output, Advanced mode, which splits Streaming and Recording into separate tabs. The simple mode option that says Same as stream is the one to avoid, because it just saves the compressed broadcast you already have.

Give the recording its own encoder where you can. If your GPU has a hardware encoder, point the stream at it and leave the recording on the same encoder with its own rate control, since current GPUs handle two simultaneous sessions without measurable load. On a machine with only a CPU encoder, set the recording to a faster preset rather than a slower one. A slightly larger file costs disk space, and a stalled encoder costs the broadcast.

For rate control, constant quality beats a fixed bitrate for recordings. CQP around 18 to 20 on an NVIDIA encoder, or CRF 18 to 20 on x264, gives a file that spends bits where the motion is. Set the container to MKV or to the hybrid MP4 option, never plain MP4. A plain MP4 that loses power mid-write is unreadable, and remuxing MKV to MP4 afterwards takes seconds and is lossless.

Two more settings people skip. Under Audio Track, tick tracks 1 through 3 for the recording even if the stream only uses track 1, so your microphone, game audio and any guest call land on separate tracks in the editor. And set the recording path to a different physical drive from your scratch disk, so a single slow drive is not writing the capture and reading your sources at once.

Why the replay buffer is not a backup

The advice you see most often is to run the replay buffer instead and clip the good moments as they happen. I use the replay buffer constantly and it still does not replace a full recording. It holds a rolling window, usually 20 to 60 seconds, in memory. You get the moment you noticed, and nothing before or after it.

Almost everything worth editing needs the surrounding context. The reaction two minutes later, the setup line somebody said before the clip starts, the quiet beat you only recognise as an ending when you watch it back. A replay buffer clip gives you a punchline with the joke removed, and no amount of clever cutting puts that back.

There is a second habit worth arguing with: downloading the VOD and treating that as the archive. It is better than nothing, and it is a lossy copy of a lossy copy with the audio flattened. Keep the download as your index if you like, by all means, then edit from the local file. Run both and the download becomes a quick way to find timecodes in a two hour session.

The eight minute check before you go live

Do this in order. It takes about eight minutes the first time and under two minutes afterwards.

  1. Check free space against the session length. At 25 Mbps a recording consumes roughly 11 GB per hour. A three hour stream wants 35 GB plus headroom, so keep at least 60 GB free on the target drive.
  2. Start a 60 second test recording with the stream offline, stop it, and open the file in your editor. Not in a media player. The editor is where a broken container or an odd frame rate shows itself.
  3. Confirm the audio tracks landed separately. Drop the test file on a timeline and look for three audio lanes. If you see one, the track boxes were never ticked.
  4. Watch the encoder load on a 90 second live test. If skipped frames climb while recording but stay flat without it, move the recording to a faster preset or lower the quality a notch.
  5. Set the filename format in Advanced settings so every file arrives named by date, time and show. Default names are a trap you discover a week later.
  6. Press record before you press go live, every time. The order is the whole habit. Start recording, check the red indicator, then start the stream.

Naming and filing so the footage is findable in March

A folder containing 40 files called Recording 2026-11-16 09-14-22 is technically an archive and practically a shrug. In OBS the filename format field accepts tokens, and something like %CCYY-%MM-%DD_%hh-%mm_boardgames produces a name that sorts by date and tells you what it is.

My own rule is one folder per month, a text file in it listing each session with two or three timecodes I noted while live, and a hard stop at 90 days before the raw files move to an external drive. The timecode notes are the part that pays off. Thirty seconds of typing during the stream saves twenty minutes of scrubbing later, and I have never once regretted writing them down.

Once a session has been cut into something finished, the raw stream and the project want different treatment. The guides under stream setup cover the capture end, and the longer term question of what to keep is the subject of archiving a finished edit.

FAQ

Does recording locally hurt stream quality?

On a GPU hardware encoder, rarely in any way you can see. On a CPU encoder sharing cores with a game, it can, which is why the 90 second live test with the skipped frame counter visible is worth doing before you trust the setup.

MKV or MP4 for the recording?

MKV, or the hybrid MP4 option if your version offers it. Both survive a crash mid-recording. Remux to MP4 afterwards from the File menu if your editor prefers it, which takes seconds and changes nothing about the picture.

How much disk space should I plan for?

Around 11 GB per hour at 1080p60 constant quality, more if your scenes are busy. Budget double the session length in free space so a long overrun does not stop the capture.

Can I record in a higher resolution than I stream?

Yes, by setting the recording output to the base canvas resolution while the stream downscales. It costs extra encoder work and gives you room to reframe in the edit, which is useful for vertical clips cut from a horizontal stream.

OV
Ottilie Varga

Ottilie cut documentaries for a decade before she started writing about editing workflow. She cares about folder structures, proxy files and the boring habits that let an editor think about story instead of storage.

More posts by Ottilie

More in Stream Setup

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto