OBS Studio Setup for Console Streaming and Recording

OBS Studio is the open-source standard for capture-card streaming and recording. It is free, scriptable, and the only tool the major streamers and esports operations actually use in production. Streamlabs is built on top of OBS; everything that follows applies to either.

This guide assumes you have a working capture card already passing video to your PC — if you don’t, start with the PS5, Xbox, or Switch 2 capture transfer guides for the hardware setup, then come back here for the OBS configuration.

What this guide covers

I · OBS vs Streamlabs · the technical case

Streamlabs OBS (now “Streamlabs Desktop”) is a fork of OBS with a built-in alert engine, donation overlays, and a polished UI. For the casual streamer, it’s the easier on-ramp. For anyone serious about content creation:

• †OBS Studio uses less RAM, drops fewer frames, crashes less. We’ve A/B tested both on the same 9950X3D / 4090 rig over multi-day sessions.
• †OBS Studio is fully open-source. Streamlabs runs telemetry and ad-injection layers most users disable on first install.
• †Plugin ecosystem (advanced scene switchers, NDI inputs, GPU-accelerated filters) is broader on OBS Studio.
• †Updates ship faster on OBS Studio; Streamlabs lags behind upstream by 2–8 weeks.

Streamlabs has alert overlays. OBS does too via free plugins (StreamElements, Streamlabs widgets, custom HTML browser sources). The alert advantage is illusory.

Pick OBS Studio. The rest of this guide is OBS Studio configuration. Streamlabs users can follow it directly — every setting has the same name.

Download from obsproject.com. Install the 64-bit version. Open it.

II · Hardware Confirmation

Before opening OBS, confirm your capture card is feeding video to Windows.

The Windows Camera app shows every connected video device. Your capture card should appear as a selectable input. Switch to it; you should see your console output. If not, the issue is upstream of OBS — driver install, HDMI cable, HDCP toggle (PS5 only), or the card itself. Fix it before continuing.

III · Source Configuration

A “source” in OBS is anything you’re capturing — a video device, a window, a webcam, a microphone, a static image. The Sources panel sits at the bottom-left of the OBS interface.

Multiple consoles, one OBS profile

If you stream PS5 one day and Switch 2 the next, create separate scenes per console rather than separate OBS profiles. Each scene has its own Video Capture Device source pointing at the same physical capture card but configured for that console’s resolution. Switch scenes on the fly.

IV · Encoder Selection

The encoder converts raw video into compressed H.264 / HEVC / AV1 frames. Hardware encoders (NVENC, AMF, QuickSync) run on the GPU and barely touch the CPU. Software encoders (x264) run on the CPU and produce slightly better quality at a given bitrate at the cost of CPU load.

NVENC HEVC · for NVIDIA GPUs (Tony's 4090 included)

• †Encoder: NVIDIA NVENC HEVC (or AV1 if you’re on RTX 4000 series and your destination supports it — Twitch does not as of April 2026, YouTube does)
• †Rate Control: CQP for archival, CBR for streaming
• †CQ: 20 for archival (visually lossless)
• †Bitrate (CBR): 8000 Kbps for 1080p60 Twitch, 12000 Kbps for 1080p60 YouTube, 25000+ Kbps for 4K60 YouTube
• †Preset: P5 (Slow) for streaming, P7 (Slowest) for archival
• †Tuning: High Quality
• †Profile: Main10 if HDR, Main otherwise

NVENC is the right answer for any RTX 30/40/50 series card. It off-loads encoding entirely to the dedicated NVENC chip — your CPU stays free for the game and your GPU’s shader cores stay free for rendering.

AMF · for AMD GPUs

• †Encoder: AMD HW H.265 (HEVC) or AV1 on RX 7000/9000
• †Rate Control: CQP for archival, CBR for streaming
• †CQ: 22 for archival
• †Bitrate (CBR): same as NVENC
• †Quality Preset: Quality (not Speed; the visual difference is noticeable)

AMF has historically lagged NVENC on visual quality at the same bitrate. RDNA 3 / 4 closed most of the gap. For competitive streaming, AMF on a 7900 XTX or 9070 XT is fine.

x264 · CPU fallback

• †Encoder: x264
• †Rate Control: CBR for streaming, CRF 18 for archival
• †Preset: veryfast for streaming, slow for archival
• †Profile: high
• †Tune: zerolatency for streaming, leave blank for archival

x264 produces slightly higher visual quality than NVENC at equal bitrates, but it costs significant CPU. Skip x264 unless your GPU is so old it lacks a hardware encoder, OR you’re recording with the game off (offline editing prep) and have CPU to spare.

V · Audio Routing

Audio is where most console-streaming setups go wrong. The constraint: you want game audio + party chat + your microphone, mixed sensibly, with party chat audible to you but optionally muted to viewers.

The standard rig

Console HDMI ─────────► Capture card (game audio embedded)
                              │
                              ▼
                          OBS as
                       "Game Audio" source

Headset USB ────► PC ────► OBS as "Party Chat" + "Mic"

Phase A · Capture-card game audio

OBS automatically captures the audio embedded in the HDMI signal from your Video Capture Device source. Confirm in the Audio Mixer panel:

Phase B · Party chat (PS5 / Xbox / Switch 2)

Party chat audio is locked inside the console. Two ways to capture it:

Path A · USB headset on the console: Plug a USB headset into the console’s controller or front USB. Console outputs party chat to that headset. To get it into OBS, you need to physically split: headset cable into a splitter, splitter feeds your ears AND a 3.5mm-to-USB audio interface plugged into the PC. OBS captures the interface as a separate audio input.

Path B · Companion app: PS5 and Xbox both let you route party chat through the PlayStation App or Xbox app on PC. Configure the app to output to an audio device (e.g., a virtual cable like VB-Audio Cable), then add that virtual cable as an audio source in OBS. Party chat lives entirely on the PC, no splitter needed.

Path B is cleaner and what we recommend. PS5’s app-based party chat works since the 8.x firmware; Xbox’s has worked since 2023.

Phase C · Mic

Plug a USB microphone (Shure MV7+, RØDE PodMic USB, Elgato Wave:3) into the PC. Add as an Audio Input Capture in OBS. Set Audio Monitoring to Monitor Off for the mic — you don’t want to hear yourself in your own headphones with delay.

Phase D · Mute for stream vs personal

In Advanced Audio Properties, each audio channel has a Tracks toggle (1–6). Track 1 is the default broadcast/stream output. To mute party chat from viewers but keep it audible to you:

• †Game audio: Track 1 ✓ (broadcast), monitor on
• †Party chat: Track 1 ✗ (NOT broadcast), Track 2 ✓ (recording), monitor on
• †Mic: Track 1 ✓, Track 2 ✓, monitor off

Streaming uses Track 1 only. Local recording uses Track 1 + Track 2 (configured in Settings → Output → Recording → Audio Track). Result: stream viewers hear game + mic, no party chat. Local recording captures everything for post-production.

VI · Output Presets

Standard configurations for the three common destinations:

Twitch · 1080p60

• †Encoder: NVENC HEVC (or AV1 if streaming destination supports — Twitch HEVC/AV1 ingest is in beta)
• †Rate Control: CBR
• †Bitrate: 8000 Kbps
• †Keyframe Interval: 2 seconds (Twitch hard requirement)
• †Preset: P5 (Slow)
• †Profile: Main
• †Resolution (Output Settings): 1920×1080
• †FPS: 60

YouTube Live · 1440p60 or 4K60

• †Encoder: NVENC HEVC or AV1
• †Rate Control: CBR
• †Bitrate: 12000 Kbps for 1440p60, 25000 Kbps for 4K60
• †Keyframe Interval: 2 seconds
• †Preset: P5 (Slow)
• †Profile: Main10 for HDR, Main otherwise
• †Resolution: 2560×1440 or 3840×2160
• †FPS: 60

Archival · 4K60 HDR Recording

• †Recording Format: MKV (recoverable if OBS crashes mid-recording, unlike MP4)
• †Encoder: NVENC HEVC
• †Rate Control: CQP
• †CQ: 20
• †Preset: P7 (Slowest)
• †Profile: Main10
• †Resolution: 3840×2160
• †FPS: 60

After the recording finishes, remux the MKV to MP4 in OBS via

. Editors that don’t accept MKV (older Premiere, some Final Cut Pro versions) can then read the MP4.

VII · Scene Setup

Scenes group sources for one-click switching. Standard scene layout:

• †“Game Only” — just the capture card source, fitted to canvas. Use during cinematics, cutscenes, no-overlay moments.
• †“Game + Webcam” — capture card + webcam in a corner overlay. Default streaming scene.
• †“Game + Webcam + Chat” — adds a Twitch chat browser source. For interactive segments.
• †“BRB” — image overlay (“Be right back”) + ambient music source. For breaks.
• †“Starting Soon” — countdown timer + music. For pre-stream.
• †“Ending” — outro card + music. For session wrap-up.

Right-click the Scenes panel → Add. Build your sources within each scene. The Studio Mode toggle (top-right) lets you preview a scene before switching to it live — essential for clean transitions.

VIII · Troubleshooting

Dropped frames during streaming

Capture card black screen mid-session

Audio out of sync with video

OBS crashes when starting a stream

Stream is laggy / chat is delayed

Closing

OBS Studio is the right tool. Hardware encoder selection and audio routing are the two settings that separate a clean stream from a frustrating one. The rest is scene craft — and that improves with every stream you do.

For the capture card itself, see Best Capture Cards 2026. For platform-specific transfer paths and pre-flight settings, see the PS5, Xbox, and Switch 2 guides.