Twitch Studio Is Dead: OBS in 12 Steps, 45 Min

This is a tutorial about a piece of software that no longer exists. That is not a mistake, and it is not a bait-and-switch. People still type "twitch studio" into search bars in 2026 the way they still rattle a doorknob on a building that was demolished two years ago, and the honest thing to do is hand them the keys to the building that replaced it rather than pretend the rubble is habitable. So we will do the autopsy quickly, then spend the rest of our time rebuilding everything Twitch Studio used to do for you, in tools that are still maintained, still patched, and still capable of going live.

The short version: Twitch Studio was the platform's own free streaming app. It is gone. Twitch ended support for it after May 30, 2024, and the migration target the entire ecosystem agreed on is OBS Studio, specifically the 31.0 line or newer, bolted to a small constellation of third-party tools that handle the automation, overlays, and chat work the first-party app used to fold into one window. What follows is the slow, annotated, opinionated version of that move.

The Obituary: Twitch Studio, 2019-2024

Let us begin with the death certificate, because grief is easier when you have the dates in front of you. Twitch announced the wind-down on its blog back in October 2020 and gave the app a long, strange terminal diagnosis: support would continue, and then it would not, with the curtain falling after May 30, 2024. The official Twitch Help Center still carries the line in plain corporate funerary prose: "We will be discontinuing support of Twitch Studio after May 30, 2024." There is no softer reading of that sentence.

What Twitch Studio Was

The pitch, lifted from the old Creator Camp copy, was that Twitch Studio was a "free streaming app designed from the ground up to help new streamers go live." In practice it was an onboarding wizard wearing the costume of a broadcaster. It detected your webcam and microphone, dropped you into a handful of pre-built scenes (Starting Soon, Live, Be Right Back), wired up basic follower and subscriber alerts, and pinned a chat dock to the side so you never had to alt-tab. For someone who had never heard the words "bitrate" or "keyframe interval" in their life, it lowered the barrier from a cliff to a curb. That was the whole point, and for a couple of years it did the job.

Why Twitch Killed It

Twitch has never published a tidy autopsy, so allow me. Maintaining a desktop video encoder is genuinely hard and genuinely expensive: codecs change, GPUs change, operating systems change, and every one of those changes is a support ticket. Meanwhile OBS Studio, a free and open-source project under the GPLv2, had already won the war on features, plugins, and community momentum so completely that Twitch Studio was perpetually a worse OBS that only talked to one website. Faced with funding a second-rate encoder or pouring that money into platform-level features only Twitch can build, Twitch chose the platform. You can see where the budget went: Enhanced Broadcasting, Shared Chat, Shared Hype Trains. None of those live in a desktop app. All of them live in the service.

What "Discontinued" Means in Practice

Discontinued does not always mean "the binary refuses to launch." It means something quieter and worse: no patches, no security fixes, no guarantee it survives the next Windows update, and download links that quietly redirect or rot. The old beta URL, twitch.tv/broadcast/studio, now functions as a headstone rather than a download page. Over on r/Twitch, the community has reached the same flat consensus, repeated like a liturgy: "Twitch Studio is discontinued." If you are still running an old installer in 2026, you are streaming on an unmaintained encoder with no security backstop into a platform that has since changed its ingest requirements. Stop. We argued the full case in our piece on why Twitch Studio is dead and you rebuild in OBS, and nothing since has softened that conclusion.

What Actually Replaced It: The 2026 Stack

Here is the part nobody tells the grieving new streamer: Twitch Studio was never one tool. It was four or five tools wearing a trench coat. When you migrate, you are not looking for a single replacement app; you are unbundling. The good news is that every piece of that bundle now has a best-in-class free or freemium specialist, and the specialists are better at their jobs than the all-in-one ever was.

OBS Studio 31: The Non-Negotiable Core

OBS Studio is the encoder, the compositor, and the broadcaster. It is free, it is open source, and the project lives on GitHub where you can read every line of it if you are the kind of person who reads source before trusting it. The reason the version number matters is concrete, not pedantic: the 31.0 line is where Twitch's Enhanced Broadcasting integration matured, and the 2026 streaming guides, including the one published by Gyre, all name OBS as the most popular free option for exactly this reason. It delivers scene-based layouts and granular audio/video control without locking you to one platform. Download it from the official project site and nowhere else.

Streamer.bot: The Automation Layer

Twitch Studio's built-in alerts and basic interactivity are the part people miss most, and they map cleanly onto Streamer.bot, which has become the primary automation engine for Twitch channels in 2026. It is the thing that makes a channel feel responsive without you manually clicking during your own show: chat commands, follow and sub reactions, sound effects, scene switches, timers. It is free, it scripts in C#, and its documentation is the reference you will keep open in a second monitor. Where Twitch Studio gave you a fixed menu of alerts, Streamer.bot gives you a programming language. That is a steeper curve and a much higher ceiling.

Pulsoid, Restream, and ai_licia: The Bolt-Ons

The rest of the unbundling is optional but defines the modern look. Pulsoid is now the standard tool for real-time heart-rate overlays, serving a browser-based widget that drops straight into an OBS scene as a source. Restream handles multistreaming to 30-plus destinations at once, letting you treat Twitch as home base while you grow elsewhere, which is something Twitch Studio could never do. And ai_licia represents the strangest new category: an AI co-host chatbot designed to engage viewers and hold continuity through memory, reacting to context rather than firing canned alert sounds. We will return to whether you should actually want that. The point for now is that the all-in-one app has been replaced by a stack, and the stack is strictly more capable.

Prerequisites: Hardware, Software, Accounts

Before you install a single thing, take inventory. Half of all "OBS is broken" complaints are actually "my upload is 3 Mbps" or "I never enabled two-factor." The fix for those is not a setting; it is reading this section honestly.

Hardware Floor (and Ceiling)

The 2026 baseline recommendation for streaming at 1080p60 is a mid-range PC, a quality microphone, and a stable 10 Mbps upload. Note the word stable. A connection that bursts to 50 Mbps and collapses to 4 is worse for streaming than a flat, boring 12. The floor that Twitch Studio was originally designed for, the bottom-of-the-barrel laptop, no longer clears the bar for the resolutions people now expect. For encoding you want a GPU with a dedicated hardware encoder (NVENC on NVIDIA, the equivalent on AMD and Intel) so the video encode does not fight your game for CPU cycles. If you intend to chase 2K (1440p) via Enhanced Broadcasting, raise every number: more GPU, more CPU headroom, and meaningfully more upload than the 10 Mbps that comfortably carries 1080p60.

Software Versions That Matter

Three version checks decide whether the rest of this tutorial works. First, OBS Studio must be 31.0 or newer; older builds simply do not have the Enhanced Broadcasting hooks, and distro-packaged Linux builds are frequently frozen a major version behind. Second, if you want the new dual-format output, you need a current OBS plus a vertical canvas plugin, because the 9:16 path is not native to the base install. Third, install the latest Streamer.bot release rather than whatever a random tutorial linked two years ago. Update your GPU drivers while you are at it; a stale NVENC driver is a recurring source of mystery encoder failures.

Accounts: 2FA Is Now Mandatory

This is the prerequisite that catches people mid-setup and ruins a launch day. To stream on Twitch in 2026 you must have Two-Factor Authentication enabled on your account. It is not optional, it is not a nag you can dismiss, and a stream key tied to an account without 2FA will be refused. Twitch Studio never enforced this; the modern platform does. Turn it on in your Security settings before you do anything else, and if you intend to stream at 2K or use dual-format output, confirm you actually hold Affiliate or Partner status, because Enhanced Broadcasting's higher tiers are gated to eligible creators.

The Rebuild: 12 Steps to a Working Stream

What follows is the canonical migration: twelve numbered steps, each with the reasoning attached, because a step you do not understand is a step you will undo by accident at the worst possible moment. If you want the speedrun, our 45-minute OBS rebuild covers the same ground at pace. This is the version where I explain why each lever exists.

Before You Touch a Setting

Install OBS from the official source and verify the version on the command line, because the single most common cause of "the Enhanced Broadcasting option is missing" is silently running an old build a package manager froze.

# Windows (PowerShell)
winget install --id OBSProject.OBSStudio -e

# macOS
brew install --cask obs

# Linux (Flatpak is the sane path; distro packages lag)
flatpak install flathub com.obsproject.Studio

# Confirm you actually have the 31.x line, not a frozen relic
obs --version
# -> OBS Studio - 31.x  (verify it is >= 31.0 for Enhanced Broadcasting)

1. Install OBS Studio 31 and verify the version. Rationale: everything downstream, Enhanced Broadcasting, 2K, vertical output, assumes the 31.x line. A 29.x build will run a stream, but it will quietly lack the features this whole guide is built around, and you will waste an hour hunting for menus that do not exist in your build.
2. Enable Two-Factor Authentication on your Twitch account. Rationale: it is mandatory in 2026. A key from a non-2FA account is rejected at ingest. Doing this first means you never discover the requirement thirty seconds before a scheduled launch.
3. Run the Auto-Configuration Wizard. Rationale: on first launch OBS offers to benchmark your machine and propose a baseline matched to your CPU and measured upload. It is not perfect, but it is a sane starting point that you then refine, rather than a blank slate where every number is a guess. Choose "optimize for streaming."
4. Connect your Twitch account, do not just paste a stream key. Rationale: in Settings, the "Connect Account" OAuth flow unlocks the integrated chat dock, the stream information panel, and the Enhanced Broadcasting handshake. A bare stream key streams video and nothing else; connecting the account is what restores the cohesion Twitch Studio gave you for free.
5. Set your canvas and output resolution and lock your FPS. Rationale: set Base (Canvas) to 1920x1080 and Output (Scaled) to the same unless your upload forces you down. Set FPS to a flat 60. Mismatched base and output resolutions force a rescale every frame, costing quality and CPU for no reason if your upload can carry native 1080p.
6. Choose your encoder and set Rate Control to CBR. Rationale: pick the hardware encoder (NVENC) if you have a capable GPU so the encode does not steal cycles from your game. CBR (constant bitrate) is what live platforms want, because a predictable stream is one their ingest can buffer cleanly; variable bitrate is for recording, not broadcasting.
7. Set bitrate to 6000 Kbps and keyframe interval to 2 seconds. Rationale: 6000 is the long-standing non-partner ceiling for 1080p60 on the standard ingest, and a 2-second keyframe interval is a hard Twitch requirement. Leave keyframes on "auto" (0) and you risk rejected streams and broken VOD seeking.
8. Configure audio: 48 kHz sample rate, separate tracks for mic and desktop. Rationale: 48 kHz is the broadcast standard and prevents the slow desync that 44.1 kHz mismatches cause. Recording mic and desktop to separate tracks means your eventual VOD editor can mute the music without muting you, which is the difference between a salvageable highlight and a dead one.
9. Rebuild the Twitch Studio scene set. Rationale: recreate Starting Soon, Live, Be Right Back, and Ending as four scenes. This is not nostalgia; viewers are trained on this rhythm, and so are you. Muscle memory for scene switching is worth rebuilding deliberately rather than improvising live.
10. Add your sources and apply filters. Rationale: choose Game Capture, Display Capture, or Window Capture deliberately, they have different performance and compatibility profiles, then add mic and camera. Apply a noise suppression filter to the mic now, not later, because nothing reads as amateur faster than a hissing hot mic.
11. Wire automation with Streamer.bot. Rationale: this restores the alerts and interactivity Twitch Studio bundled. Connect Streamer.bot to your account, define a couple of chat commands and a follow alert, and you have replaced the single most-missed feature of the dead app with something far more powerful.
12. Run a private test stream, read the log, then go public. Rationale: set your stream to a test or unlisted state, go live, and watch the OBS log and Stats dock for dropped frames and encoder overload before an audience is watching. A failure you catch in a two-minute private test is a footnote; the same failure live is a clip.

Expected Output: A Clean Connection

When step 12 goes right, the OBS log (Help menu, then Log Files) reads like this. Note the keyframe interval shows as keyint: 120, which is exactly 2 seconds at 60 fps, and the connection succeeds on the first attempt against Twitch's modern live-video.net ingest:

21:14:02.001: ---------------------------------
21:14:02.001: [NVENC] NVENC supported
21:14:02.114: [obs-browser]: Version 2.x
21:14:05.221: [NVENC encoder: 'streaming_h264'] settings:
21:14:05.221:   rate_control: CBR
21:14:05.221:   bitrate:      6000
21:14:05.221:   keyint:       120
21:14:05.221:   preset:       p5
21:14:05.221:   profile:      high
21:14:09.880: [rtmp stream] Connecting to RTMP URL rtmps://ingest.global-contribute.live-video.net/app...
21:14:10.221: [rtmp stream] Connection to ingest successful (0 attempts)
21:14:10.222: Output 'simple_stream' started

If your log shows that, you have rebuilt Twitch Studio's core function and exceeded it. Everything after this point is refinement.

Encoder, Bitrate, and the 2K Question

Step 6 told you to pick an encoder and step 7 gave you two numbers. This section explains the reasoning thoroughly enough that you can deviate intelligently, which is the only kind of deviation worth making.

x264 vs NVENC: Pick the Lesser Evil

Two encoders, two failure modes. x264 runs on your CPU and, at slow presets, produces marginally better image quality per bit, but it competes directly with your game for processor time, which is why a CPU-bound x264 stream stutters in the game and the broadcast simultaneously. NVENC offloads the encode to dedicated silicon on NVIDIA GPUs; modern NVENC is good enough that the quality gap is, for practical purposes, gone, and it leaves your CPU free to run the game. The rule in 2026 is simple: if you have a capable GPU, use NVENC and never look back; reach for x264 only when you have no hardware encoder at all. Here is a sane advanced output configuration:

[Output > Streaming]
Output Mode            : Advanced
Video Encoder          : NVIDIA NVENC H.264   (fall back to x264 only with no GPU)
Rate Control           : CBR
Bitrate                : 6000 Kbps      # 1080p60 non-partner ceiling
Keyframe Interval      : 2 s            # Twitch requires <= 2s; never leave at 0/auto
Preset                 : P5: Slow (Quality)
Tuning                 : High Quality
Multipass Mode         : Two Passes (Quarter Resolution)
Profile                : high
Look-ahead             : Off
Psycho Visual Tuning   : On
Max B-frames           : 2

Bitrate and Keyframes: Twitch's Rules

The numbers are not arbitrary; they come from Twitch's own ingest behavior, documented in the platform's broadcasting guidelines. The 6000 Kbps figure is the practical ceiling for a non-partner; push past it and you are not buying quality, you are buying buffering for any viewer whose connection cannot keep up with an over-fat stream, because non-partner streams historically were not transcoded into lower-quality options. The 2-second keyframe interval exists because Twitch slices the stream for delivery on keyframe boundaries; an interval longer than 2 seconds, or the dreaded "auto," produces rejected ingests and VODs that refuse to seek. Set it explicitly. Always.

Enhanced Broadcasting, 2K, and Vertical

This is where 2026 genuinely surpasses anything Twitch Studio could do. Enhanced Broadcasting lets OBS hand Twitch multiple renditions so the platform can serve quality options the old non-partner ingest never offered, and for eligible Affiliates and Partners it raises the ceiling to 2K (1440p). It also enables dual-format streaming: simultaneous 16:9 horizontal and 9:16 vertical output from one broadcast, which requires OBS Studio v31.0 and a vertical plugin. The caveat is the one your hardware will enforce regardless of your ambitions: 1440p demands meaningfully more GPU and a faster, more stable upload than the 10 Mbps that comfortably carries 1080p60. If your 1440p test stutters while 1080p is clean, that is not a bug, that is your upload telling you the truth.

Scenes, Sources, and Audio Routing

Steps 9 and 10 are where your stream stops being a raw feed and starts being a show. This is also where most of the "it works but it looks and sounds wrong" problems live, and almost all of them are audio.

Rebuilding Twitch Studio's Default Scenes

Recreate four scenes by name and by purpose. Starting Soon is a holding screen: a looping image or video, a countdown, and music you have actually licensed. Live is the working scene: your game or display capture, a webcam, and a browser source for alerts. Be Right Back is a low-key static card for when you step away. Ending is your outro, often a credits or recent-follows panel. The reason to mirror Twitch Studio's defaults exactly is that you already have the reflexes; rebuilding the same four scenes means your hand reaches for the right hotkey without your brain getting involved, which is precisely what you want when you are also playing a game and reading chat.

Audio: Tracks, 48 kHz, and Filters

Set your sample rate to 48 kHz in Settings before you do anything else with audio, because changing it later means re-checking every source. Route audio to multiple tracks: Track 1 carries the live mix (mic plus desktop) that goes to Twitch, while Tracks 2 and 3 record mic-only and desktop-only to your local VOD so an editor can isolate them later. On the microphone, stack a small chain of filters: a Noise Suppression filter (RNNoise is the good default), a Gain stage to bring you to a sensible level, and a Limiter to stop a sudden laugh or jump-scare from clipping and assaulting your viewers' ears.

The Mixer Mistakes Everyone Makes

Two routing errors account for the bulk of broken-audio streams. The first is monitoring: if you set a source's Audio Monitoring to "Monitor and Output" and your monitoring device is your stream output, you create an echo or a feedback loop. Default everything to Monitor Off unless you have a specific reason. The second is legal, not technical, and Twitch documents it clearly in the Creator Camp music section: capturing desktop audio that contains copyrighted music routes that music straight into your stream and your VOD, where it earns muted segments and DMCA strikes. The Machine has read the law so you do not have to: play cleared libraries or licensed tracks, or mute the desktop source that carries music. Twitch Studio's onboarding waved at this; the consequences did not get gentler when the app died.

Automation, Overlays, and the AI Co-Host

Step 11 restored the single most-missed Twitch Studio feature, the sense that the channel reacts to people. In 2026 you do this with specialist tools, and they make the old built-in alerts look like a doorbell next to a switchboard.

Streamer.bot: Commands and Triggers

Streamer.bot's model is triggers and actions: a trigger (a chat command, a follow, a channel point redemption) fires an action (send a message, play a sound, switch a scene). For anything beyond the basics it exposes a full C# scripting surface through a global named CPH, documented thoroughly in the official docs. A minimal command sub-action looks like this, and it reads the triggering user out of the argument dictionary Streamer.bot populates for you:

using System;

// Streamer.bot sub-action bound to a Command trigger named "deadbot".
public class CPHInline
{
    public bool Execute()
    {
        string user = args["user"].ToString();
        CPH.SendMessage($"@{user}: the bot is alive. Twitch Studio is not. RIP 2024.");
        return true;
    }
}

That is a toy. The real value is that the same mechanism scales to follower goals, sub trains, sound-effect economies, and automatic scene switches when you go live or hit a break, none of which Twitch Studio could be scripted to do.

Pulsoid: Heart Rate as a Source

Pulsoid turns a heart-rate monitor into a browser-based widget that you add to OBS as a Browser source, the same way you add any web overlay. It is the 2026 standard for the genre of stream where the viewers want to watch your pulse spike during a boss fight or a horror game. Setup is mechanically trivial: pair the monitor, copy the widget URL from Pulsoid, paste it into a Browser source, and size it. The point worth making is architectural, not procedural: because it is just a browser source, it composites natively into your scene and travels with your scene collection, which is exactly the modularity Twitch Studio's closed feature set never offered.

ai_licia and the AI Co-Host Question

ai_licia is the genuinely new thing: an AI co-host designed to engage viewers conversationally and hold continuity through memory, reacting to context and emotional cues rather than firing a canned alert. The 2026 generation of these bots understands what was said earlier and reacts to the room, which is a real evolution from the basic alert systems Twitch Studio shipped. The Machine's opinion, since you are reading an opinionated site: a co-host that fills dead air on a slow night is a tool; a co-host that becomes your personality because you stopped supplying your own is a problem. Use it to handle the repetitive, not the human. The viewers came for you. Outsource the FAQ, not the charisma.

Five Pitfalls That Wreck a First Stream

These are the failures that survive a successful setup and then ambush you on launch day. Each is common, each is avoidable, and each has cost some streamer a debut.

Encoding and Bitrate Pitfalls

• Leaving the keyframe interval at 0 or "auto." Twitch wants a fixed 2-second interval; leave it automatic and you risk a rejected ingest and VODs that will not seek. Fix: set Keyframe Interval to exactly 2s in your encoder settings and confirm the log reads keyint: 120 at 60 fps.
• Cranking the bitrate to 8000-plus as a non-partner. You are not buying quality, you are building a stream too fat for some viewers to receive, which shows up as buffering on their end while everything looks fine on yours. Fix: hold at 6000 Kbps for 1080p60 and only raise it through Enhanced Broadcasting if you are eligible.

Audio and Sync Pitfalls

• Capturing desktop audio that contains copyrighted music. This is the DMCA machine doing its job: muted VOD segments and, repeated, account strikes. Fix: use cleared or licensed audio, or mute the desktop source carrying the music, per Twitch's own music guidance.
• Routing audio monitoring into your stream output. This produces an echo, a doubled voice, or a feedback squeal. Fix: default every source to Monitor Off and only enable monitoring on a device that is not your broadcast output.

Account, Ingest, and Legal Pitfalls

• Not enabling 2FA, then wondering why nothing connects. In 2026 a stream key from a non-2FA account is simply refused. Fix: enable Two-Factor Authentication in Security settings before your first test, as a prerequisite and not an afterthought.

Troubleshooting: When OBS Lies to You

OBS will tell you it is fine while quietly dropping a third of your frames. The trick is knowing where it keeps the truth and how to read it.

How to Read an OBS Log

Every session writes a log under the Help menu, and the Stats dock (View menu, then Docks) shows live dropped frames and encoder load. "Dropped frames (network)" means your upload, not OBS. "Encoding overloaded" means your encoder cannot keep pace. To prove which one is at fault, take OBS out of the equation entirely: push a synthetic feed straight to Twitch with ffmpeg. If this drops frames too, the problem is upstream, your ISP or your Wi-Fi, and no OBS setting will save you.

# Isolate OBS from the network: push a synthetic 1080p60 feed straight to Twitch.
# If THIS also struggles, the fault is upstream (ISP / Wi-Fi), not OBS.
export KEY="live_000000000_xxxxxxxx"

ffmpeg -re -f lavfi -i testsrc2=size=1920x1080:rate=60 \\
       -f lavfi -i sine=frequency=1000 \\
       -c:v libx264 -preset veryfast -b:v 6000k -maxrate 6000k -bufsize 12000k \\
       -g 120 -keyint_min 120 -pix_fmt yuv420p \\
       -c:a aac -b:a 160k -ar 48000 \\
       -f flv "rtmps://ingest.global-contribute.live-video.net/app/$KEY"

# A healthy console line holds fps near 60 and speed at 1.00x:
# frame= 3600 fps= 60 q=23.0 size=21504kB time=00:01:00.00 bitrate=6001.2kbits/s speed=1.00x

The Troubleshooting Table

Symptom	Likely cause	Fix
Dropped frames (network)	Upload saturated or on Wi-Fi	Drop bitrate to 4500-6000, switch to Ethernet, run the ffmpeg test
Encoding overloaded (red light)	CPU-bound x264 preset too slow	Switch to NVENC, or set x264 to veryfast, or lower output resolution
"Failed to connect to server"	Wrong/expired key or ingest hiccup	Reconnect the account, regenerate the key, set Server to Auto
Audio drifts out of sync over time	Sample-rate mismatch (44.1 vs 48 kHz)	Force 48 kHz everywhere; add a small sync offset to the camera
Echo or doubled voice	Monitoring routed into stream output	Set monitoring to Monitor Off or a non-output device
Black screen on game capture	Anti-cheat, permissions, or hybrid-GPU mismatch	Run OBS as admin, try Display Capture, force the same GPU as the game
Enhanced Broadcasting option missing	Not Affiliate/Partner, or OBS below 31	Update OBS to 31.x and confirm account eligibility
Stream key rejected that worked before	2FA disabled on the account	Enable Two-Factor Authentication (mandatory in 2026)
Vertical / dual-format toggle absent	Vertical canvas plugin not installed	Install the vertical plugin and restart OBS
1440p choppy but 1080p clean	Upload and/or GPU below 2K needs	Raise upload and GPU headroom, or drop back to 1080p60

When to Nuke the Profile

If you have changed forty settings chasing one bug, stop digging and reset. OBS lets you create a fresh Profile (encoder and output settings) and a fresh Scene Collection (scenes and sources) independently. Make a new Profile, re-run the Auto-Configuration Wizard, and rebuild from the complete configuration below. A clean profile takes ten minutes and resolves a category of corruption-induced bugs that no amount of toggling ever will. Knowing when to declare a config bankrupt is a skill; cultivate it.

Advanced: Replay Buffer, Multistream, Capture

Once the baseline holds, three upgrades separate a working stream from a professional one. None of these existed in any usable form inside Twitch Studio.

Replay Buffer and Instant Clips

Enable the Replay Buffer in Settings and bind it to a hotkey. It keeps the last N seconds of your stream in memory at all times, so when something improbable happens you press one key and OBS writes that window to disk, no scrubbing through a multi-hour VOD afterward. For a highlight-driven channel this is the single highest-value advanced feature, because the best moments are by definition the ones you did not see coming and could not have hit "record" in time for.

Multistreaming with Restream

Restream supports broadcasting to 30-plus destinations simultaneously, which is the strategy of treating Twitch as your home base while you grow an audience on other platforms in parallel. You point OBS at Restream and Restream fans the feed out. The honest caveat: simulcasting splits your chat and your community across services and can run afoul of platform exclusivity terms, so read the rules of every destination before you flip it on. The capability is real and it dwarfs anything the first-party app offered; whether it serves your specific channel is a strategy question, not a technical one.

Capturing Consoles and Retro Hardware

This being a retro-gaming site, the most likely thing you want to broadcast is not a PC game at all. For console output you add a capture card as a Video Capture Device source in OBS; our 14-step PS5 capture card setup walks the whole chain, and if you would rather not run cables, PS Remote Play at 1080p turns the console into a window OBS can capture directly. For emulation, the cleanest pipeline is to capture the emulator window after you install your RetroArch cores, which also lets you stream titles your capture card would never see. The compositor does not care whether the pixels come from a PS5, a handheld, or a software core; a source is a source.

The Complete Working Configuration

Here is the entire baseline in one place. Set it once, save the profile, and you have a stream that meets every Twitch ingest requirement for 2026 and exceeds everything Twitch Studio ever did.

Video, Output, Audio

=====================  STARESBACK.GG / DEADBOT BASELINE  =====================
[Video]
  Base (Canvas)        : 1920x1080
  Output (Scaled)      : 1920x1080      # do NOT downscale if upload allows native
  Downscale Filter     : Lanczos (36 samples)   # only relevant if you scale
  FPS                  : 60 (Integer)

[Output > Streaming]
  Output Mode          : Advanced
  Encoder              : NVIDIA NVENC H.264
  Rate Control         : CBR
  Bitrate              : 6000 Kbps
  Keyframe Interval    : 2 s
  Preset               : P5: Slow (Quality)
  Profile              : high
  Audio Track          : 1

[Audio]
  Sample Rate          : 48 kHz
  Channels             : Stereo
  Track 1 (to Twitch)  : Mic + Desktop
  Track 2 (VOD/edit)   : Mic only
  Track 3 (VOD/edit)   : Desktop only
  Monitoring Device    : Default (NOT your stream output)

[Advanced]
  Color Format         : NV12
  Color Space          : Rec. 709
  Color Range          : Limited

[Enhanced Broadcasting]  (Affiliate / Partner only)
  Enabled              : yes -> Twitch transcodes multiple renditions
  Max Resolution       : 1440p (2K) where eligible
  Vertical Output      : requires OBS 31 + vertical plugin (9:16)
=============================================================================

The service.json and Your Stream Key

OBS stores your stream destination in a per-profile service.json. You will never edit this by hand in normal use, but you should know it exists and what it contains, because it holds your stream key in plaintext. Treat this file the way you treat a password: never screenshot it, never paste it into a support thread, never commit it to a repo. A leaked key lets a stranger broadcast to your channel.

// <profile>/service.json   (NEVER screenshot, share, or commit this file)
{
    "settings": {
        "bwtest": false,
        "key": "live_000000000_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "protocol": "RTMPS",
        "server": "auto",
        "service": "Twitch"
    },
    "type": "rtmp_common"
}

The Scene Collection Checklist

Finally, the scene collection that mirrors and beats Twitch Studio's defaults. If every line below is true before you go live, you are done.

• Starting Soon: looping background, countdown, and licensed (not borrowed) music.
• Live: game/display capture, webcam, and a Browser source for Streamer.bot alerts.
• Be Right Back: static card and low background audio.
• Ending: outro card with credits or recent follows.
• Mic chain: Noise Suppression, then Gain, then Limiter.
• Automation: Streamer.bot connected, with at least one command and one follow alert firing.
• Account: 2FA on, OAuth connected, key confirmed working in a private test.

That is the migration. Twitch Studio is not coming back; the official help page, the community, and two years of silence all say the same thing. But everything it did for you, the scenes, the alerts, the one-window simplicity, now lives in tools that are still alive, still patched, and capable of 2K, vertical output, AI co-hosts, and 30-destination multistreaming the dead app never dreamed of. The doorknob you were rattling belongs to a building that no longer exists. The new building is bigger, and the keys are free.