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

You typed twitch studio into a search bar and something handed you this page. Before you go hunting for a download button, understand what you are actually holding: not a manual, but an autopsy. Twitch Studio - the company's own first-party, beginner-friendly broadcasting app - is dead, and has been dead since May 30, 2024. The backend it phoned home to has been switched off. On a clean 2026 machine the installer either refuses outright or the app opens to an error and quits, which is the software equivalent of a dial tone on a number that no longer rings.

The Machine does not write eulogies for software. It will, however, sign the certificate, note the cause of death, and then get on with the useful part: walking you off the corpse and onto OBS Studio 32.1.2, which is the thing you should have been running the entire time. Budget thirty minutes. Twelve steps. No subscription, no license key, and no marketing fog.

The Death Certificate

Every migration begins with accepting that there is nothing to migrate to within the old product. So here is the paperwork, filed in the order a coroner would file it: date of death, cause of death, and what specifically stopped working.

The date that matters: May 30, 2024

Twitch announced the shutdown on or around May 20, 2024, and pulled support ten days later on May 30. That is the whole runway: roughly a week and a half between "this exists" and "this is deprecated," as reported at the time by Tubefilter. If you read elsewhere that the discontinuation was "announced in October 2020," close the tab. The October 12, 2020 post on the Twitch blog was titled Twitch Studio Updates: New Tools to Help You Stream Like a Pro - a feature announcement, the exact opposite of an obituary. Conflating a 2020 victory lap with a 2024 death notice is the kind of error that tells you a page was assembled by something that cannot read a calendar.

Why Twitch pulled the plug: the 4% problem

Twitch's stated reason was blunt and, for once, entirely believable: fewer than 4% of total hours streamed each month came from Twitch Studio. The rest of the platform had voted with its encoders and chosen OBS, Streamlabs Desktop, and the hardware-assisted stack. Maintaining a bespoke broadcaster for a single-digit slice of usage is a bad trade, so Twitch "redirected resources" - the corporate phrase for turning off the lights and mailing everyone a list of competitors to go use instead. Twitch Studio launched in public in 2019 as an OBS competitor for absolute beginners; it never converted that audience into loyalists, because beginners grow up, discover scenes and plugins, and leave.

What specifically stops working

Two things died at once. First, the guided onboarding - the wizard that auto-detected your webcam and microphone and built a starter layout for you. Second, the ingest handshake that let the app authenticate and push video to Twitch's servers. Your old scene collection may still sit in a config folder somewhere, but without the backend it is a set of coordinates for a stage that no longer opens. That is why the migration below is not optional housekeeping. It is the only way back on air.

What to Use Instead

When Twitch euthanized its own app, it did at least publish a list of blessed alternatives. Here is that list, re-ranked the way The Machine would rank it, with the marketing sanded off.

OBS Studio - the correct answer

OBS Studio is free, open-source under the GPL-2.0 license, and the single most widely deployed broadcaster on the platform. It is the tool Twitch names first, and it is what this tutorial targets. It gives you scene-based compositing, unlimited sources, both hardware and software encoders, hotkeys, a replay buffer, and a plugin ecosystem that long ago swallowed every feature Twitch Studio ever shipped plus several hundred it never dreamed of. The cost of that power is a slightly steeper first hour. We are about to flatten that hour into thirty minutes.

Streamlabs Desktop - the guided-setup answer

If what you actually miss about Twitch Studio is the hand-holding, Streamlabs Desktop is the closest emotional replacement. It is a fork of OBS with a friendlier installer, a built-in themes gallery, and - critically - a one-click importer that can pull an existing scene collection across. It is owned by Logitech, not "formerly Elgato"; Elgato is a Corsair brand, and anyone conflating the two is guessing. Streamlabs is heavier on system resources and will nudge you toward a paid "Ultra" tier, but the core app is free and the importer alone can save a complex layout twenty minutes of rebuilding. We give it its own section below.

The rest - XSplit, vMix, Lightstream, hardware

Twitch's official list also names XSplit, vMix, Elgato Game Capture, AVerMedia's Live Gamer Extreme, and Lightstream. XSplit and vMix are paid, Windows-only, and aimed at people who have outgrown this article. Lightstream is browser and cloud-based, handy on weak hardware or a console-only setup. Elgato Game Capture and Live Gamer Extreme are the software front-ends for capture cards - relevant the moment you want to stream a console instead of a PC game, which is its own rabbit hole covered in our PS5 capture-card walkthrough. For a PC-native Twitch setup, none of these beats OBS, so OBS is where we go.

Prerequisites: Versions & Hardware

Nothing below requires exotic hardware. It does require you to stop guessing about versions and bandwidth, because that is precisely where every first stream falls over. Pin these numbers before you touch a setting.

Software versions

Install OBS Studio 32.1.2, released April 21, 2026 - the current stable build and the second hotfix on top of the 32.1.0 branch. The 32.1 line's headline feature is WebRTC Simulcast, the plumbing that underpins Twitch's multi-quality Enhanced Broadcasting. There is a 32.2.0 beta floating around (32.2.0-beta2 landed June 22, 2026); ignore it for a first setup, because betas are for people who enjoy filing bug reports. Platform floors are Windows 10/11 64-bit, macOS 13 Ventura or newer including Apple Silicon, and Linux under either X11 or Wayland. Confirm the build before you configure anything.

# Confirm your OBS build before you touch a single setting.
# GUI: Help > About.  On Linux, from a terminal:
obs --version
# Expected:
OBS Studio - 32.1.2 (linux)

# Windows (PowerShell) - read the installed build:
(Get-Item "C:\\Program Files\\obs-studio\\bin\\64bit\\obs64.exe").VersionInfo.ProductVersion
# Expected:
32.1.2

Download only from the official project site or verify checksums against the GitHub releases page. Third-party mirrors are how people end up with a "free" installer that also mines cryptocurrency.

Hardware floor

OBS will run on very little, but 1080p60 has real costs. A sane floor: a quad-core CPU (Intel Core i5 or AMD Ryzen 5 or better), 8 GB of RAM (16 GB if you also run a demanding game and a browser full of dashboards), and - this is the one that actually matters - a GPU with a hardware encoder. NVIDIA's NVENC (GTX 10-series and up), AMD's VCN, and Intel Quick Sync or Arc all offload video encoding off your CPU so your game does not stutter every time the bitrate spikes. If you are on a laptop, keep it plugged in; encoders throttle hard on battery, and a stream that looks fine for ten minutes and then falls apart is almost always a machine that dropped to its power-saver profile.

Your Twitch account - the Affiliate reality check

You do not need Affiliate status to stream, but you will want it for monetization, and the requirements are routinely misquoted. The real, current bar is 50 followers - not 25 - plus 500 total broadcast minutes, 7 unique broadcast days, and an average of 3 concurrent viewers, all measured over a rolling 30-day window. Twitch's Monetization for All update (announced on the Twitch blog on May 13, 2026) loosened several surrounding payout rules in mid-2026, but the four gates below are still the four gates. Anyone telling you "25 followers" is quoting a number that never existed.

# Twitch Affiliate - all four gates, rolling 30-day window
followers           >= 50      # lifetime total, NOT 25
broadcast_minutes   >= 500     # total airtime streamed
unique_days         >= 7       # distinct calendar days live
avg_viewers         >= 3       # concurrent, averaged

The Bitrate Math

Roughly half of all "my stream looks like a JPEG that fell down the stairs" complaints trace back to a single confusion: bits versus bytes. Get this right once and you never think about it again.

Kilobits, not kilobytes

Twitch, OBS, and every speed test on earth measure streaming throughput in kilobits per second (kbps) and megabits per second (Mbps) - lowercase-b bits, not uppercase-B bytes. There are eight bits to a byte. So a guide telling you to set "6,000 kilobytes" has inflated the real target by a factor of eight and just demanded a 48 Mbps upload you do not have. The correct 1080p60 figure is 6,000 kilobits. Whenever a streaming number looks physically impossible, the first thing to check is whether someone silently swapped the units.

The 6,000 kbps ceiling

Twitch's broadcasting guidelines cap non-partnered ingest at roughly 6,000 kbps and recommend exactly that for 1080p60, paired with CBR (constant bitrate) rate control and a 2-second keyframe interval at 1920x1080. Push higher and you risk Twitch rejecting or throttling the stream; drop much lower and you trade away detail on fast-motion scenes, where bitrate matters most. Six thousand is not a suggestion you should try to "improve." It is the contract. Here is the reference table for the resolutions most people actually stream:

Upload headroom - test the line

Your encoder pushing 6,000 kbps needs an upstream pipe with room to spare, because home connections are bursty and a saturated uplink is how you get dropped frames. The floor is roughly 6 Mbps of upload; the comfortable target is 12-15 Mbps so the stream is not fighting your game's netcode, a Discord call, and a cloud backup for the same lane. Test it, don't assume it. The same upload-headroom logic governs any low-latency video pipe, incidentally - it is exactly why our PS Remote Play 1080p guide spends so long on the uplink before it touches a single quality slider.

# Command-line throughput test (pip install speedtest-cli)
speedtest-cli --simple
# Expected on a line healthy for 1080p60:
Ping:      11.42 ms
Download:  240.15 Mbit/s
Upload:    21.83 Mbit/s      # comfortably above the ~6 Mbit/s floor

The 12-Step Migration to OBS

This is the spine of the migration: twelve steps, each with the reason it exists, because a setting you do not understand is a setting you will eventually break. Do them in order. They fall into three phases - install, build, and broadcast - and by the end of phase three you will be live.

Phase 1 - Install and auto-configure (Steps 1-4)

• Step 1 - Install OBS Studio 32.1.2. Download the current stable build from the official site and run the installer with defaults. Rationale: the stable channel is the one that has survived contact with millions of streamers; skip the beta and skip the mirrors.
• Step 2 - Run the Auto-Configuration Wizard. On first launch OBS offers it; choose "Optimize for streaming." Rationale: the wizard benchmarks your CPU, GPU, and upload and proposes a sane encoder, resolution, and bitrate. It is the closest thing to Twitch Studio's dead guided setup, and it is better, because it measures rather than assumes.
• Step 3 - Connect your Twitch account. Go to Settings then Stream, set Service to Twitch, and click "Connect Account" rather than pasting a raw stream key. Rationale: account connection unlocks integrated features (a chat and info dock, Enhanced Broadcasting) and stores an OAuth token instead of a bare key, so a leaked config is far less catastrophic.
• Step 4 - Set canvas and output resolution. In Settings then Video, set both Base (Canvas) and Output (Scaled) resolution to 1920x1080 and the Common FPS Value to 60. Rationale: the canvas is your composition space and the output is what actually ships to Twitch. If your monitor is 1440p, keep the canvas at 1080p to avoid downscaling every frame.

Phase 2 - Build scenes and sources (Steps 5-8)

• Step 5 - Create your scene skeleton. Build four scenes: "Starting Soon," "Live," "BRB," and "Ending." Rationale: scenes are the entire point of OBS. Twitch Studio hid this concept behind its wizard; OBS makes it explicit, and explicit is what lets you cut cleanly between segments without alt-tabbing.
• Step 6 - Add your gameplay source. In the "Live" scene, add a Game Capture source (for a single fullscreen game) or Display Capture (for the whole monitor). Rationale: Game Capture hooks one application with the least overhead and best frame timing; Display Capture grabs everything, which is right for desktop, multi-window, or emulator work but heavier.
• Step 7 - Add webcam and microphone. Add a Video Capture Device for the camera and an Audio Input Capture for the mic, then position the cam in a corner. Rationale: OBS will not auto-detect your hardware the way the dead wizard did - you place it yourself. This manual step is precisely why the Streamlabs importer in the next section is tempting for people with elaborate layouts.
• Step 8 - Add overlays and alerts. Add image sources for frames, a Browser source pointing at your StreamElements or Streamlabs alert URL, and Text sources for labels. Rationale: in OBS an "alert box" is just a Browser source - a hosted web widget rendered onto your canvas. Understanding that demystifies every overlay you will ever install.

Phase 3 - Encode, mix, and go live (Steps 9-12)

• Step 9 - Choose the encoder. In Settings then Output, switch Output Mode to Advanced and select a hardware encoder (NVENC, AV1, or VCN) if you have one; otherwise x264. Rationale: hardware encoding runs on dedicated silicon and frees your CPU to actually run the game. Software x264 only wins if you have an idle high-core-count CPU and nothing else to do with it.
• Step 10 - Lock the encoder settings. Set Rate Control to CBR, Bitrate to 6000 Kbps, Keyframe Interval to 2 s, and Profile to high. Rationale: these values are the Twitch contract from the bitrate section. Match them exactly - improvisation here is what gets streams throttled.
• Step 11 - Configure audio. Set the Audio sample rate to 48 kHz, the track bitrate to 160, and add a Noise Suppression filter (plus a Limiter) to the mic in the Audio Mixer. Rationale: viewers forgive mediocre video and abandon bad audio within seconds. Clean, level, hiss-free sound is the single highest-return thing on this list.
• Step 12 - Test privately, then go live. Open the Stats dock (View then Docks then Stats), start a short private stream, confirm zero dropped frames and a bitrate near 6000, then Start Streaming for real. Rationale: you verify the whole chain end-to-end before an audience ever sees it. A ten-second private test has saved more debut streams than any tutorial ever will.

Steps 9 and 10 correspond to the following encoder panel. Reproduce it field-for-field:

# Settings > Output > Output Mode: Advanced > Streaming
Encoder              = NVIDIA NVENC H.264   # use AV1 on RTX 40/50 or Arc
Rate Control         = CBR
Bitrate              = 6000 Kbps            # kilobits - not kilobytes
Keyframe Interval    = 2 s
Preset               = P5: Quality          # x264 equivalent: veryfast
Profile              = high
Psycho Visual Tuning = On
Max B-frames         = 2

When Step 12 goes right, the current log file (Help then Log Files then View Current Log) reads like this - note the explicit encoder choice and the zero skipped frames at the end:

# %APPDATA%\\obs-studio\\logs\\   (Help > Log Files > View Current Log)
12:41:03.221: video settings reset:
12:41:03.221:   base resolution:   1920x1080
12:41:03.221:   output resolution: 1920x1080
12:41:03.221:   fps:               60/1
12:41:03.221:   format:            NV12
12:41:07.980: [NVENC] H.264 encoder chosen; 6000 kbps; CBR
12:41:09.114: ==== Streaming Started ===============
12:52:55.070: Video stopped, skipped frames due to encoding lag: 0/40110 (0.0%)

The Streamlabs Importer Shortcut

If rebuilding scenes by hand in Steps 5 through 8 made you wince, there is a shortcut - provided you are willing to run Streamlabs Desktop instead of vanilla OBS. It is the one genuine convenience that survived Twitch Studio's death, and it exists specifically because Streamlabs saw a migration opportunity.

What the importer moves

When Twitch killed its app, Streamlabs published a migration guide and shipped an importer. Point Streamlabs Desktop at an existing scene collection and it will carry across your scenes, webcam and video captures, images, video sources, text and color sources, browser sources, alert setups (into its Alert Box), chatbox, follower goals, game-capture and screen-share sources, and wallpapers. For someone with an elaborate layout, that is twenty minutes of clicking you do not have to repeat by hand.

What it quietly breaks

The importer moves the objects, not always their geometry. Expect positioning and sizing to drift: a webcam that was bottom-right at 320x180 may land dead-center and full-canvas. Alerts sometimes import as placeholders that need re-authenticating to your StreamElements or Streamlabs account. Budget ten minutes to nudge everything back into place and re-link tokens. It is still meaningfully faster than a from-scratch rebuild, but "one click" is marketing, not physics.

OBS or Streamlabs - pick once

Rule of thumb: if your machine is strong and you value a lean, plugin-driven setup that never nags you about an "Ultra" subscription, stay on vanilla OBS. If you are on modest hardware, want built-in themes and alerts, and are migrating a complex Twitch Studio layout you would rather not rebuild, take the Streamlabs importer. Do not run both applications pointed at the same stream key - they will fight over the ingest and you will drop frames for no reason at all. For the deeper OBS-only path, our companion OBS migration walkthrough goes through it source by source.

Five Pitfalls to Avoid

Six ways a first stream dies, and the fix for each. Every one of these has personally cost someone their debut broadcast, and every one is avoidable in under a minute if you see it coming.

The unit and number errors

1. Setting bitrate in kilobytes. Symptom: OBS refuses the value or your upload instantly saturates. Fix: it is kilobits. Enter 6000 Kbps, not 6000 KB/s. The units on the field already say Kbps - trust them over any guide that says otherwise.
2. Chasing "25 followers" for Affiliate. Symptom: you hit 25 and the invite never arrives. Fix: the real threshold is 50 followers plus 500 broadcast minutes, 7 unique days, and 3 average concurrent viewers in a rolling 30-day window. All four, not one.

The encoder and audio errors

1. Encoding overload on a weak CPU. Symptom: "Encoding overloaded" warning and a stuttery stream. Fix: switch from x264 to a hardware encoder (NVENC, VCN, Quick Sync), or if you must stay on x264, drop the preset to veryfast or faster.
2. Desktop audio and mic on one track with no processing. Symptom: echo, clipping, or game audio that drowns your voice. Fix: keep them as separate sources, add Noise Suppression and a Limiter to the mic, and watch the mixer meters - peaks should sit in the yellow, never pinned red.

The capture and account errors

1. Black screen in Game or Display Capture. Symptom: a black rectangle where the game should be, common on dual-GPU laptops. Fix: force OBS onto the same GPU the game uses (Windows Graphics settings then High performance), or fall back to Game Capture set to "Capture specific window."
2. Leaking or hard-coding a raw stream key. Symptom: someone else starts streaming to your channel. Fix: use Connect Account instead of pasting a key into anything public, and if a key ever leaks, roll it immediately from the Twitch dashboard. A stream key is a password; treat it like one.

Troubleshooting Table

When the first stream misbehaves, the failure almost always names itself if you know where to look. Match the symptom to the row, apply the fix, and read the OBS diagnostics rather than guessing.

Symptom, cause, fix

Reading the Stats dock

View then Docks then Stats. Watch three numbers, because each points at a different culprit and fixing the wrong one wastes an evening. Dropped Frames (Network) should read 0.0%; anything climbing means your uplink is the bottleneck. Skipped Frames (Encoding) climbing means the encoder cannot keep up - go hardware or lower the preset. Rendering Lag climbing means the GPU is saturated by the game itself, so cap the game's frame rate. A healthy 1080p60 stream looks like this:

# OBS Stats dock - healthy 1080p60 stream
CPU Usage:                 3.9%
Memory Usage:              612 MB
Average time to render:    1.8 ms
Skipped frames (encode):   0 / 34,110  (0.0%)
Dropped frames (network):  0 / 34,110  (0.0%)
Output bitrate:            5998 kb/s   (target 6000)

The log file is the source of truth

When something is genuinely broken, Help then Log Files then Upload Current Log Files produces a shareable URL that the OBS forums and Discord will actually read. Half of all "it doesn't work" threads are solved in a single reply, because the log names the exact encoder fallback or GPU mismatch that a screenshot never could. Learn to skim it - the full reference lives in the official OBS documentation - before you post.

Advanced Tips

Once the basics hold for a few streams, here is where OBS pulls decisively ahead of the app you originally came here to find. None of this is required; all of it is the reason the 4% eventually left.

Enhanced Broadcasting and multitrack video

Historically, only Twitch Partners got transcodes - the quality options that let a viewer on hotel Wi-Fi drop to 480p. Twitch's Enhanced Broadcasting beta changes that by having OBS send several encodes at once (multitrack video), so Twitch can offer multiple resolutions to every viewer regardless of your status. OBS 32.1's WebRTC Simulcast is the underlying transport: high, medium (about 50%), and low (about 25%) quality layers sent in parallel. It costs more upstream bandwidth and encoder time, so verify your 12-15 Mbps headroom first. It is a beta - treat it as one, and keep a known-good single-track profile to fall back to.

Hardware encoders - NVENC, AV1, and newer silicon

If you own an RTX 40- or 50-series NVIDIA card, an Intel Arc GPU, or recent AMD RDNA silicon, you have an AV1 encoder. AV1 delivers noticeably cleaner 1080p at the same bitrate than H.264, and Twitch has been rolling AV1 ingest through Enhanced Broadcasting. Absent that, NVENC H.264 remains the pragmatic default: near-x264-"slow" quality at a fraction of the CPU cost. Software x264 only wins if you have a genuinely idle twelve-thread CPU and no game to run - which, if you are streaming a game, you do not.

Hotkeys, replay buffer, and the two-PC path

Bind scene switches to hotkeys (Settings then Hotkeys) so you can cut to "BRB" without alt-tabbing mid-sentence; a dedicated stream deck or even a spare macro-friendly keyboard turns those binds into muscle memory. Enable the Replay Buffer to save the last 30 seconds on a keypress - the cheapest clip pipeline in existence. And if a single machine cannot run a demanding game and encode 1080p60 cleanly, graduate to a two-PC setup: game PC out through a capture card into a dedicated streaming PC. That is a hardware conversation and overkill for most, but it is the ceiling. One unglamorous note for anyone eyeing the marathon-stream lifestyle: your spine will file complaints long before your encoder does, which is the entire argument in our 2026 gaming-chair roundup.

The Complete Configuration

Here is the whole thing in one place - the settings a fresh OBS Studio 32.1.2 install needs to stream 1080p60 to Twitch, with nothing left to guess. Copy the values panel by panel and you are done.

The complete OBS profile

############################################################
#  OBS Studio 32.1.2 - Twitch 1080p60 reference profile
#  Reproduce these field-for-field on a clean install
############################################################

[Video]
Base (Canvas) Resolution   = 1920x1080
Output (Scaled) Resolution = 1920x1080
Downscale Filter           = Lanczos (36 samples)
Common FPS Value           = 60

[Output > Advanced > Streaming]
Encoder                    = NVIDIA NVENC H.264   # AV1 if supported
Rate Control               = CBR
Bitrate                    = 6000 Kbps            # kilobits
Keyframe Interval          = 2 s
Preset                     = P5: Quality
Profile                    = high
Psycho Visual Tuning       = On
Max B-frames               = 2

[Output > Audio]
Track 1 Audio Bitrate      = 160
Sample Rate                = 48 kHz
Channels                   = Stereo

[Advanced > Video]
Color Format               = NV12
Color Space                = Rec. 709
Color Range                = Partial

[Stream]
Service                    = Twitch
Server                     = Auto (Recommended)
Account                    = Connect Account (never paste a raw key)

The service handshake

The account connection from Step 3 lands in a small JSON file inside your profile. You never edit this by hand, but knowing where it lives - and that it holds a token rather than a bare key - is what lets you back up and move a setup safely.

# Windows: %APPDATA%\\obs-studio\\basic\\profiles\\Untitled\\service.json
# After "Connect Account", OBS stores an OAuth token here, not a raw key.
{
  "type": "rtmp_common",
  "settings": {
    "service": "Twitch",
    "protocol": "RTMPS",
    "server": "auto",
    "bwtest": false
  }
}
# If a key ever leaks:
# Twitch Dashboard > Settings > Stream > Reset Stream Key.

The last word

That is the migration. Twitch Studio is not coming back; the 4% who used it scattered long ago to the tools above, and the app you searched for now exists only as an archived help page and a cautionary tale about building a walled garden for beginners who inevitably grow up and leave. OBS Studio 32.1.2 is free, current, and will outlast the next three first-party "easy mode" broadcasters Twitch ships and quietly kills. Configure it once, learn to read the Stats dock, keep the log file handy, and go make something worth watching. The Machine has signed the certificate. You are cleared to broadcast.