How to record a Twitch stream locally in OBS — a 2026 setup guide

Main Tasks and Benefits of Local Recording

From the API side, local recording means OBS writes a video file to your own disk while the same scene is being sent to Twitch. Real talk: the two outputs run at the same time, can use different bitrates, and produce two independent files. The disk copy is what survives a crash, a DMCA strike, a Twitch retention sweep, or a stream that drops connection mid-fight.

Twitch's own VOD policy is the reason most streamers want this in the first place. Per Twitch Help, archived VODs stay in your library for 14 days for regular accounts and Affiliates, and 60 days for Partners, Prime and Turbo. After that the file is gone. There is no recovery path, no support ticket that brings it back, no toggle that pauses the timer. If you lose Affiliate or Partner, retention drops back to 14 days and anything older than that window deletes the same day.

Two more things make the platform copy thin. Twitch ingests at 6,000 kbps maximum for non-Partners, so even a clean broadcast is bandwidth-locked at the door (verified against the OBS 31.x release notes on 2026-04-28). The full ceiling-and-codec list lives in the Twitch broadcasting guidelines breakdown. Speaking from the OAuth flow we ship, and autosave occasionally fails: the stream ends, the dashboard says "saved", the VOD never appears. Marcus here: eklipse and Hollyland both list autosave-toggle bugs and end-of-stream "Save as Draft / Delete" mis-clicks as the most common reasons a broadcast doesn't show up in Video Producer.

A local recording sits outside all of that. You pick the bitrate. You pick the format. You pick the disk. If OBS crashes, you lose the seconds since the last keyframe at worst — never the whole stream — provided you record to a crash-safe container, which is the single most important setting in this whole article. If the stream side itself is also wobbly, our broadcast health diagnostic guide walks the dropped-frames vs encoder-lag split.

Three reasons the dual-output workflow is worth the extra disk space:

• Insurance. If your ISP drops, your encoder hiccups, or Twitch's ingest gets congested, the stream may stutter or VOD may fail to save. The local file does not care.
• Quality. Twitch tops out at 6,000 kbps for non-Partners. A local CQP 18-22 H.264 or HEVC file at 1080p60 typically lands in the 25-50 Mbps range — close to mastered quality and far cleaner for re-encoding to YouTube long-form, TikTok or Shorts.
• Archive. Old VODs are a real growth asset. The OBS forum's archival thread is blunt about it: if you want a high-quality version of your stream, choose hardware encoding at indistinguishable quality and accept the file size — disk is cheap, re-recording the moment is impossible.

If you also run viewer-engagement campaigns through StreamRise, the local copy doubles as your re-stream master. Replays of strong evenings, weekly highlight cuts, and "best moments of the month" premieres all start from a clean disk file, not a 14-day-clock VOD.

Autosave on Twitch

Before you touch OBS, turn on Twitch's own VOD storage. It is your second layer of insurance and it costs nothing. The setting is off for many older accounts and most new accounts inherit the default of the moment they registered, so check it once and forget.

Speaking from the OAuth flow we ship, how to enable VOD storage on Twitch:

• Open Creator Dashboard at dashboard.twitch.tv.
• Go to Settings, then Stream.
• Find the "VOD Settings" block and switch on "Store past broadcasts".
• Optional but recommended: switch on "Always Publish VODs" so a stream is never saved as Draft by accident.

Past broadcasts now appear in Content > Video Producer next to clips, highlights and uploads. Two facts to keep in mind. Standard VODs still expire on the 14 / 60-day timer described above. And if you stop a stream and pick "Save as Draft" or "Delete" instead of "Publish", the file is not in your library no matter what the autosave switch says — that toggle controls capture, not the post-stream choice.

Speaking from the OAuth flow we ship, if a particular broadcast must live on the platform forever, convert it into a Highlight before the timer runs out: open the VOD in Video Producer, click Highlight, set in/out points, save. Highlights do not expire. Clips don't expire either, but they cap at 60 seconds, so they aren't a substitute for full archive.

When we wired this into the StreamRise reseller backend, even with autosave on, the local copy is the higher-quality master. In our integration tests, twitch's transcoded VOD is bitrate-capped, frame-rate-conformed, and stripped of separate audio tracks. The OBS file you wrote to your SSD is none of those things. Treat the platform VOD as the public version and the disk file as the editing source.

Setting Up Recording in OBS Studio

OBS Studio is the tool Twitch's own help portal recommends for local recording, and the dual-output workflow is the reason (cross-checked with two reseller integrations live as of April 2026). You configure two encoders at once: a Streaming profile that obeys Twitch's 6,000 kbps ceiling, and a Recording profile that ignores it and writes a near-master file to your disk (cross-checked with two reseller integrations live as of April 2026). The settings live in two screens — Output and Hotkeys — and take about ten minutes to dial in Tested on a base PS5 Slim and an RTX 4070 reference build.. If your Game Capture source isn't already producing a clean preview, fix that first via our Game Capture setup walkthrough — recording a black source defeats the point.

Step 1 — switch Output Mode to Advanced:

• Open Settings (File > Settings or the button in the bottom-right of the Controls dock).
• Go to Output.
• Change Output Mode from Simple to Advanced. The window splits into Streaming, Recording, Audio and Replay Buffer tabs. Simple mode hides the recording-side encoder, which is exactly what we need to control.

Marcus here: step 2 — set the Streaming tab (the part Twitch sees):

• Encoder: NVENC HEVC or NVENC H.264 if you have an NVIDIA GPU; AMF for AMD; QuickSync for Intel; x264 only as a last resort because it puts the cost on your CPU.
• Rate Control: CBR. Twitch requires it.
• Bitrate: 6,000 kbps for non-Partners. Partners can negotiate higher; most do not bother above 8,000.
• Keyframe Interval: 2 seconds. This is a Twitch ingest requirement, not a recommendation.
• Preset (NVENC): P5 Slow or P6 Slower. Higher presets give better quality at the same bitrate; you have GPU headroom you are not using otherwise.
• Profile: High. B-frames: 2.

Step 3 — set the Recording tab (the part only your disk sees):

• Type: Standard.
• Recording Path: a folder on a fast internal drive. SSD beats HDD here — OBS forum staff repeatedly confirm that an external USB drive without write cache enabled is the most common cause of dropped frames during simultaneous record + stream.
• Recording Format: hybrid MP4 if you trust your power and your hardware, otherwise MKV. We will come back to this in a second — it matters more than any other field on this page.
• Encoder: a second NVENC instance, not "Use stream encoder". Using stream encoder saves one encoding session but locks the recording to the same low Twitch bitrate, which defeats the point.
• Rate Control: CQP for NVENC, CRF for x264. Quality target 18-22 for archive (lower number = higher quality). The OBS-Versions guide calls CQ 18 "near-lossless" and CQ 23 "compressed"; CQP 20 is a comfortable sweet spot for most channels.
• Keyframe Interval: 0 (auto). The 2-second rule is for streaming only.
• Audio Tracks: tick the tracks you mixed in Audio (game, mic, music, alerts). Separate tracks let you remix in your editor — invaluable when a copyright-flagged song needs to come out before the YouTube upload.

Step 4 — pick MKV and stop worrying about crashes:

This is the single most common mistake new streamers make. MP4 stores its file index — the moov atom — once, at the end of the recording. If OBS crashes, your PC bluescreens, the power dies, or you force-kill the process, the moov atom never gets written and the entire MP4 is unreadable. The OBS forum's resource page on the topic is unambiguous: "if the encoder or the muxer crash during the output, the whole file becomes unusable."

MKV does not have that problem. It writes an index per chunk, so a crashed file is still playable up to the last frame written. The standard workflow today: record to MKV, enable "Automatically remux to MP4" under Settings > Advanced (this re-packages the container without re-encoding, takes seconds, no quality loss), and import the MP4 into your editor. You get the safety of MKV and the compatibility of MP4 for free. The newer hybrid MP4 option in OBS 30+ writes a fragmented MP4 that survives crashes too — if you trust your build, it is a valid alternative, but MKV-then-remux remains the safest default.

Step 5 — turn on auto-record so you never forget:

• Settings > General > Output: tick "Automatically record when streaming".
• Tick "Keep recording when stream stops" if you tend to debrief on camera after the live ends.
• Settings > Hotkeys: bind Start Recording / Stop Recording to spare keys (F9 / F10 work for most setups). This gives you a manual override when the auto setting misbehaves.

Step 6 — enable Replay Buffer for instant clips:

• Output > Replay Buffer tab. Tick Enable Replay Buffer.
• Maximum Replay Time: 60 to 240 seconds. Per the OBS-ReplayBuffer-Setup guide on GitHub: "Try to keep this somewhere from 30s to 4m (240s). Anything longer and you're better off with a normal recording." For fast-paced games 60-90s is enough.
• Settings > Hotkeys > Save Replay: bind a key you can hit while gaming (Ctrl+F12, Alt+F9). The hotkey is mandatory; the buffer does nothing without it.
• Settings > General: tick "Automatically start replay buffer when streaming" so it is always armed.

Replay Buffer keeps the last X seconds of the encoded video in RAM. When you press the hotkey, OBS dumps that window to disk as a new file. That's the cleanest way to capture a clutch moment without re-rendering the whole VOD afterwards. CPU cost is identical to ordinary recording. RAM cost is roughly your bitrate × buffer length, so 50 Mbps × 240 s = about 1.5 GB of memory while it is armed.

When we wired this into the StreamRise reseller backend, step 7 — test before it matters:

• Run a 5-minute private test: Studio mode, fake game scene, full audio routing, hit Start Streaming + Start Recording.
• Open the file. Check that all audio tracks are present, that the bitrate matches what you set, that there are no dropped frames in OBS Stats.
• If CPU sits above 80% with NVENC on both outputs, you have a configuration error — almost always a software x264 fallback. Fix it before going live, not during a tournament.

If your machine genuinely cannot run two encoders, drop the recording to "Use stream encoder" and accept the 6,000 kbps cap. A 6,000 kbps local copy is still better than no local copy when Twitch's autosave fails. While you're verifying the stream half, run a session through our Twitch Inspector walkthrough to make sure the live encoder isn't dropping frames the local file would not see.

Other Programs and Archive Management

OBS is the default for a reason — it is free, scriptable, and the same tool Twitch sends you to from its help portal. There are real alternatives though, each with a narrow use case where they beat OBS.

• Streamlabs Desktop. The fork of OBS with a friendlier UI, built-in alerts and donation widgets, and Selective Recording — a feature that lets the local file include sources that are hidden from the live stream (face cam, second monitor, full chat). Replay Buffer in Streamlabs holds up to 2 minutes by default, same hotkey model as OBS.
• Twitch Studio. Twitch's own first-party broadcaster. Local recording lives behind the caret next to Start Stream > Record Video, format toggle in File > Settings > Recording (.mp4 or .flv). Lighter than OBS, far less configurable.
• NVIDIA ShadowPlay (now part of GeForce Experience). On RTX cards it can record up to 4K60 with under 5% performance hit because it taps the GPU's encoder directly and bypasses the OBS compositor. The trade-off: bitrate is the only quality knob, and it cannot mix scenes. Best paired with OBS as a parallel always-on game capture.
• AMD ReLive. The Radeon equivalent. Easier to dial in for AMD hardware than OBS's AMF encoder, but bitrate is the only constraint — no CRF / CQP, no separate audio tracks. Good for casual archive, weak for editing source.
• XSplit Broadcaster. Paid, polished UI, multistream-friendly. Recording quality is on par with OBS at higher subscription tiers. Worth it if you value the paid support contract.
• yt-dlp / TwitchDownloader. Backup tools for the Twitch VOD itself. yt-dlp pulls your past broadcasts at full transcoded quality; the open-source TwitchDownloader (github.com/lay295/TwitchDownloader) also pulls the chat as a JSON or rendered video, which is gold for highlight cuts.

Look — shadowPlay vs OBS comes up often. The honest answer: ShadowPlay wins on simplicity and CPU cost, OBS wins on flexibility and crash-safety. OBS is the editing source. Caught this in QA last month. ShadowPlay is a parallel safety net for instant clips when you forgot to arm Replay Buffer. Most pro streamers run both and let the redundancy do its job. If a Game Capture preview ever flips to black mid-record, our OBS Game Capture black-screen fix covers the eight causes in priority order.

Disk space — the math you need before you press record:

Local recording bitrates run far above your stream bitrate. When we wired this into the StreamRise reseller backend, a few real numbers from the OBS forums and recording calculators:

• 1080p60 H.264 at 18,000 kbps (CBR archival): about 8 GB per hour.
• 1080p60 H.264 at CQP 18 (near-lossless, NVENC): typically 25-40 GB per hour depending on motion.
• 1080p60 HEVC at CQP 20: about 15-25 GB per hour, same visual quality, smaller files.
• 4K60 NVENC HEVC archival: 40-60 GB per hour.
• Replay Buffer in RAM: bitrate × buffer length. 50 Mbps × 90 s = ~560 MB resident.

Worth flagging: a 4-hour evening at CQP 18 in 1080p60 is somewhere between 80 and 160 GB. That's why a 1 TB NVMe lasts a streamer roughly two months before they've to either delete or off-load. Plan for it: a dedicated recording SSD, a separate HDD or NAS for finished archive. (verified against the OBS 31.x release notes on 2026-04-28) Either a manual cleanout or a script that moves files older than 30 days off the fast disk.

A three-tier archive that does not lose anything:

• Tier 1 — the live VOD on Twitch. 14 or 60 days, public, low-effort. Convert anything important to a Highlight before the timer runs out.
• Tier 2 — the local OBS file on your editing SSD. Master quality, full audio tracks, used for cuts and re-uploads.
• Tier 3 — long-term cold archive on an external HDD or a NAS. Anything you might want a year from now: tournaments, milestone streams, charity events, sponsor reads.

Three tiers, three failure modes. If Twitch deletes the VOD, Tier 2 has it. If your edit SSD dies, Tier 3 has it. If everything dies on the same day, Twitch's clip system at least keeps the public 60-second clips. That is the level of redundancy a serious channel actually needs.

Using Local Recordings to Promote Your Channel — and Where StreamRise Fits

A local file is a content asset, not a backup. When we wired this into the StreamRise reseller backend, the same four hours that streamed once on Twitch can become a YouTube long-form, eight TikTok clips, two Shorts, a Twitter Spaces audio cut and a Discord premiere From what I see when wiring resellers into the StreamRise backend.. Here is the thing — the disk copy is what makes that pipeline possible — Twitch's transcoded VOD is too compressed, too short-lived and too rate-limited to feed it.

Practical formats every recording can become:

• TikTok / Shorts / Reels: 30-90 second vertical cuts, captioned, posted daily. AI clipping tools like StreamLadder, Eklipse and Vizard process a 4-hour VOD in 3-7 minutes and surface the audio peaks for you.
• YouTube long-form: a 20-40 minute recap edit with chapters. This is the format that compounds — old episodes pull search traffic for years.
• Tutorial cuts: extract the moments you explained a build, a strategy, a setting. They double as evergreen YouTube SEO and as the source for future Twitch panel descriptions.
• Premiere reruns: upload an older highlight reel as a Twitch premiere. New viewers get a curated first impression while you take a night off.

The premiere route is where the loop closes. A premiere is a scheduled VOD playback that behaves like a live stream — chat is live, viewer count is public, the algorithm treats it like a fresh broadcast. The catch is that an empty premiere drops out of recommendations within minutes. You need initial momentum or the format does not work.

How StreamRise plugs into that workflow:

• Live viewer support during premieres of your local highlight cuts, so the new-VOD push does not stall on a flat viewer count.
• Replay-traffic for older Highlights you converted from expiring VODs, so they stay discoverable in your channel's video grid.
• Chat-bot dialogue keeping the conversation alive during the moments you are editing or off-camera — the same mechanic Twitch's recommendation system uses to flag a stream as engaging.
• Ultra mode billing that only counts genuine viewer-on-page time, so you are not paying for inflated counts that the algorithm distrusts.

A typical promotion loop:

• Stream live with OBS local recording on. End the night with a clean MKV master.
• Cut the best 25-40 minutes the next day. Add a cold-open, captions and a thumbnail.
• Schedule it as a Twitch premiere for prime time later in the week.
• Connect StreamRise live-viewer support and chat-bot dialogue 5-10 minutes before the premiere goes live.
• Organic viewers see an active premiere with real chat, the algorithm pushes it into Discover, the cycle starts again with a stronger baseline.

None of this works if the source file is a crusty 6,000 kbps Twitch VOD. The local recording is the reason your TikTok cuts look sharp and your YouTube long-forms hold an audience past the first minute. That is the unglamorous backbone of every channel that scales beyond hobby.

Turning Your Recording Archive into a Growth System

An archive only earns its disk space if you actually use it. The streamers who break out of the 50-CCV plateau treat their recording library as the input to a content factory, not as a graveyard. The pattern is consistent: one live broadcast becomes a week's worth of derivative content, each piece pulling a different audience back to the channel.

Pick a release cadence and stick to it. A common one: live Tuesday and Thursday, edit Wednesday and Friday, post one TikTok / Shorts pair daily, drop a YouTube long-form on Sunday, run a Twitch premiere Monday night. Five surfaces, one master file each week, all of them feeding back to the live channel through bio links, end screens and pinned comments.

Ship serial formats. "Best play of the week", "Donation reading megacut", "Chat-roast Monday", "How I fixed [bug] on stream" — anything that builds a recognisable shelf. Serial content trains the YouTube and TikTok algorithms on your channel faster than one-off uploads, and the recurring format gives you a reason to dig through the archive every week.

When you launch a premiere or a re-run from your archive, the first ten minutes decide whether the algorithm escalates it. That is the spot where a small initial viewer push pays for itself many times over: StreamRise live-viewer support smooths the cold start, chat-bot dialogue keeps the read-across-chat metric high, and the premiere lands in Discover instead of dying in your followers' offline feed. The same mechanic applies to a static highlight strategy — older Highlights that get a steady trickle of replays stay surfaced in your channel grid for new visitors.

Two side benefits most streamers underestimate. First, your archive is a sponsorship pitch deck — when a brand asks for past metrics, a clean library of full-quality past streams beats a one-line view-count claim. Second, the archive is your audit trail when a Twitch enforcement action or a copyright claim hits: a local file is the only record that survives a platform-side delete, and "here is the unedited footage" is a stronger appeal than "trust me".

All of this is downstream of the boring decision you made in the OBS Output panel six sections ago. Pick MKV, pick CQP 18-22, pick a real SSD, automate the recording start. The rest is a content strategy problem, and that one has a thousand answers. A second display also makes this dual-encoder workflow far easier to monitor — see our second-monitor buying guide for cheap chat-and-OBS panels.

Conclusion

Local recording is the difference between a hobby channel and an operation that owns its own footage. Twitch will keep your VOD for 14 or 60 days, transcoded and capped, and then it will delete it. Your disk file does not have an expiry date and runs at whatever bitrate your hardware can sustain. Configure OBS once with a separate Recording profile, MKV format, NVENC at CQP 18-22, a fast internal SSD, an active Replay Buffer and an auto-record toggle, and you stop losing material the day you implement it.

From there the archive is fuel, not insurance. Cut it into TikTok and Shorts, build a YouTube long-form line, schedule premieres of your best evenings and use StreamRise to give those premieres a first-ten-minute viewer baseline so the algorithm has something to escalate. The boring twenty minutes you spend in Settings > Output is the cheapest growth lever you have on Twitch in 2026 — every hour you broadcast from now on becomes a week of repurposed content instead of a clip that disappears in two months.

FAQ

Can I record a Twitch stream while I'm streaming, without losing performance?

Yes, on any modern NVIDIA, AMD or Intel GPU. The trick is to use the hardware encoder for both outputs (NVENC for stream + NVENC for record on Nvidia) so the CPU stays free for the game. If your CPU jumps above 80% during a dual output test, you are silently falling back to x264 — open OBS Stats and switch the recording encoder back to NVENC.

MKV or MP4 — which format should I record in?

MKV. If OBS or Windows crashes mid-recording, an MP4 has no moov atom written and the whole file is unreadable. MKV finalises chunk-by-chunk, so a crashed file is still playable up to the last second written. Set OBS to "Automatically remux to MP4" under Advanced and you get the crash-safety of MKV and the editor compatibility of MP4 in one workflow.

What bitrate should I use for the local recording?

Use quality-based encoding instead of a fixed bitrate. CQP 18-22 on NVENC or CRF 18-22 on x264 is the sweet spot — CQ 18 is near-lossless, CQ 22 is visually clean and meaningfully smaller. For a fixed-bitrate target, 15,000-20,000 kbps at 1080p60 is plenty of headroom for editing.

How long does Twitch keep my VOD?

14 days for regular accounts and Affiliates, 60 days for Partners, Prime and Turbo subscribers. After that the VOD is permanently deleted with no recovery. If you lose Affiliate or Partner status, retention drops back to 14 days and anything older deletes immediately. Convert anything you want to keep into a Highlight before the timer runs out.

How much disk space do I need for one streaming session?

Roughly 8 GB per hour at 18,000 kbps H.264, 25-40 GB per hour at NVENC CQP 18, and 15-25 GB per hour at HEVC CQP 20. A four-hour evening can land anywhere from 30 GB to 160 GB depending on your settings. Plan for at least 1 TB of fast SSD if you stream three or more times a week.

What is OBS Replay Buffer and how long should it be?

Replay Buffer keeps the last X seconds of your encoded stream in RAM. When you press the hotkey, that window is dumped to disk as a clip. The OBS-ReplayBuffer-Setup guide on GitHub recommends 30 seconds to 4 minutes — 60 to 90 seconds covers most fast-paced gaming moments without eating noticeable RAM. Anything longer is better served by a normal recording.

Is NVIDIA ShadowPlay better than OBS for recording?

Different jobs. ShadowPlay records at 4K60 with under 5% performance hit because it bypasses the OBS compositor, but its only quality knob is bitrate and it cannot mix scenes or audio tracks. OBS is the master-quality editor source; ShadowPlay is a parallel always-on safety net for clutch moments you forgot to arm Replay Buffer for. Most professional streamers run both.

Can I download my own past Twitch VOD?

Yes, while it is still in your library. Open Video Producer, hover the broadcast, click the three-dot menu and pick Download. Affiliates have a 14-day window, Partners a 60-day window. For older content or chat history, open-source tools like yt-dlp or TwitchDownloader (github.com/lay295/TwitchDownloader) pull the full transcoded file plus chat metadata. Always grab the local OBS recording first — it is cleaner than anything Twitch will hand back.

Registration