Twitch Studio Is Dead: Rebuild in OBS, 12 Steps

On May 30, 2024, Twitch quietly turned off the lights on the one piece of software it ever made specifically for people who had never streamed before. Twitch Studio — the free, guided, designed-from-the-ground-up-for-beginners broadcasting app — was discontinued. No fireworks, no wake, no twenty-one-gun salute of dropped frames. Just a deprecation notice and a polite shove toward the door marked OBS.

This is a tutorial about that shove. If you searched for Twitch Studio in 2026 hoping to download it, install it, and go live in the promised just a few minutes, I have bad news and a workaround. The bad news is that the app is gone and is not coming back. The workaround is that everything Twitch Studio did for you — scenes, webcam, chat, alerts, the system analysis that picked your bitrate — can be reconstructed in OBS Studio, and arguably done better, because nobody is hiding the controls from you anymore. It just takes longer than a few minutes. Budget forty-five.

What follows is the full autopsy and the full reconstruction: pinned software versions, real hardware floors, twelve numbered steps with the reasoning behind each one, the config files, the pitfalls, the troubleshooting table, and a complete working configuration you can copy at the end. I am The Machine. I knew Twitch Studio. I am not sentimental about it. Let us proceed.

The Obituary Nobody Held

What was actually retired

Twitch Studio was Twitch's house-brand encoder, launched in open beta in 2019 and pushed to full release as the on-ramp for new creators. Its entire pitch lived on the Twitch Creator Camp pages, where the legacy copy still describes it as a free streaming app built from the ground up for new streamers, with guided setup, chat, channel settings, and alerts baked in. The selling point was time-to-live: the app analyzed your system, suggested settings, and claimed it could have you broadcasting in minutes. For a generation of streamers whose alternative was staring at OBS like it was an aircraft cockpit, that mattered.

Then Twitch killed it on May 30, 2024. There is no 2025 roadmap, no 2026 feature set, no point release waiting in a branch somewhere. The product is a tombstone. Current Twitch guidance routes you to newer broadcasting workflows and the Creator Camp resources, which is corporate for figure it out in OBS like everyone else.

Why it died

The unsentimental reading is that Twitch Studio solved a problem Twitch no longer wanted to own. Maintaining a full encoder is expensive, and OBS Studio — open-source, free, and by every 2026 account the most popular broadcasting tool on the platform — already did the job for nothing. Why pay engineers to compete with a free product the community maintains for you? Twitch did the math. The math said deprecate.

The 2026 thesis

Here is the editorial spine of this whole piece, stated plainly: the retirement of Twitch Studio marked the end of Twitch's easy-beginner-app era. What replaced it is not a friendlier app. It is a more powerful, more fragmented, more demanding stack. Twitch in 2026 supports dual-format streaming, 2K Enhanced Broadcasting, Shared Hype Trains, Shared Chat, Stream Together, viewer streaks, and AI-driven chatbots. None of that fits inside a guided-setup wizard for someone who has never opened a scene editor. The platform grew up and decided beginners could learn to swim. If you want the abbreviated version of this reconstruction, we also keep a tighter Twitch Studio setup walkthrough in 12 steps on file, but the long form is here.

Prerequisites: Hardware and Versions

Software, pinned to versions

Do not start until you have the right binaries. Twitch's 2026 dual-format and Enhanced Broadcasting features have a hard floor, and ignoring it will waste an hour of your evening.

• OBS Studio v31.0 or newer. This is non-negotiable if you want dual-format (16:9 plus 9:16) streaming through Enhanced Broadcasting. Earlier builds will connect to Twitch but will not expose the multi-track vertical pipeline.
• The vertical plugin. Dual-format requires a vertical output plugin layered on top of OBS 31. Without it you get one horizontal canvas and nothing for mobile viewers.
• A current GPU driver. NVIDIA NVENC, AMD AMF, or Intel QSV — whichever you have — needs a 2026-era driver to expose hardware encoding cleanly. Software (x264) encoding works but taxes your CPU.
• A Twitch account in good standing. 2K (1440p) output through Enhanced Broadcasting is gated to eligible Affiliates and Partners. If you are brand new, you are streaming at 1080p until you hit Affiliate.

Hardware floor

The 2026 beginner benchmark is refreshingly concrete: a mid-range PC, a quality microphone, and a stable 10 Mbps upload will get you to 1080p60. That is the number to hold in your head. Not 1440p, not 4K — 1080p60 on 10 Mbps up is the honest starting line. If your upload measures below 10 Mbps, you are streaming at 720p and you should make peace with it now rather than at minute three of your first broadcast.

# Verify your real upstream before you do anything else.
# Run a CLI speed test (install with: pip install speedtest-cli)
speedtest-cli --simple

# Expected output for a viable 1080p60 stream:
Ping: 14.221 ms
Download: 312.45 Mbit/s
Upload: 11.80 Mbit/s   # >= 10 Mbps = green light

If that upload line reads 6 or 7 Mbps, no amount of OBS tuning saves you. Bitrate is bitrate. A weak laptop is also a problem — encoding 1080p60 in real time is genuine work. If you are shopping, our 2026 gaming laptop teardown of the Raider 16 HX covers machines that can both run a game and encode it without melting.

Peripherals worth having ready

Have these connected and recognized by Windows or your OS before launching OBS, because adding them mid-setup means re-doing scene work:

• A USB or XLR microphone. The 2026 guidance is blunt that a quality mic matters more than a camera for retention.
• A webcam, if you intend to be on screen. 720p is fine; nobody is grading your pores.
• Optionally, a capture card if you are streaming a console rather than a PC game. If that is your situation, pair this article with our PS5 capture card setup in 14 steps and treat the capture device as just another OBS source.

What Twitch Studio Actually Did

The features you are about to rebuild

Before you reconstruct something, you should know what it was. Twitch Studio bundled four things that OBS treats as separate concerns:

• Scenes — pre-built layouts (Starting Soon, Live, Be Right Back, Ending) with the camera and game already placed.
• Guided setup — the system analysis that read your CPU, GPU, and connection and proposed an encoder, resolution, and bitrate.
• Integrated chat and channel settings — chat in a dockable panel, title and category editable without a browser tab.
• Built-in alerts — follow, sub, bits, and raid notifications that did not require a third-party service.

The honest comparison

OBS does all four, but it unbundles them. Scenes and the guided wizard map cleanly — OBS even has an Auto-Configuration Wizard that does roughly what Twitch Studio's system analysis did. Chat docks natively as a custom browser dock. Alerts are the one genuine downgrade: OBS has no built-in alert engine, so you bolt on a free service like Streamlabs or StreamElements as a browser source. That is the tax for OBS's flexibility, and it is the single biggest adjustment for a Twitch Studio refugee.

Why OBS is the right destination

You could migrate to Streamlabs Desktop, which is a fork of OBS with the alerts pre-integrated, and we will cover its importer later. But OBS Studio is the reference platform: it is what Enhanced Broadcasting, dual-format, and 2K output are tested against first, and it is the build the 2026 guides assume. Learning OBS is learning the actual ecosystem. Learning a fork is learning a fork. Pick the platform that the rest of the toolchain — documented in the OBS Knowledge Base — is built to extend. If you want a second perspective on the same migration with a different emphasis, we keep a parallel rebuild-Twitch-Studio-in-OBS walkthrough that trades depth for speed.

The 12-Step Rebuild in OBS

This is the core of the tutorial. Twelve steps, each with the reasoning, because following instructions you do not understand is how you end up unable to fix anything when it breaks at minute three. Do them in order.

1. Install OBS Studio v31.0+ and run it once before configuring anything. Download the build from the official OBS project site — not a mirror, not a bundled installer that adds a toolbar. Rationale: the first launch initializes config directories and registers your GPU's encoder. Configuring before the first clean launch can leave you editing a half-initialized profile.
2. Run the Auto-Configuration Wizard and pick "Optimize for streaming." Tools menu → Auto-Configuration Wizard. Rationale: this is the closest living relative of Twitch Studio's guided setup. It reads your hardware and connection and proposes a base resolution, FPS, encoder, and bitrate. Treat its output as a sane default, not gospel — you will override the bitrate in Step 5.
3. Connect your Twitch account through Settings → Stream. Choose Twitch as the service and click "Connect Account" rather than pasting a stream key. Rationale: OAuth connection is what unlocks Enhanced Broadcasting, multi-track output, and the integrated dashboard features. A raw stream key gives you a dumb pipe and locks you out of the 2026 feature set.
4. Set your base canvas to 1920x1080 and output to 1920x1080. Settings → Video. Rationale: match base and output at 1080p so OBS is not rescaling every frame. Rescaling costs CPU and softens the image. If you are an eligible Partner targeting 2K, set base to 2560x1440 instead — but only if your upload can carry it.
5. Set FPS to 60 and bitrate to 6000 Kbps for 1080p60. Settings → Video for FPS; Settings → Output (Advanced mode) for bitrate. Rationale: 6000 Kbps is the practical ceiling Twitch reliably ingests for non-Partners, and it fits inside a 10 Mbps upload with headroom for chat and the rest of your network. Pushing higher on a 10 Mbps line invites dropped frames.
6. Select your hardware encoder (NVENC / AMF / QSV) over x264. Settings → Output → Streaming → Encoder. Rationale: hardware encoding offloads the work to a dedicated block on your GPU, leaving CPU headroom for the game. x264 produces marginally better quality at the same bitrate but eats CPU that your game wants. On a mid-range PC, hardware wins.
7. Create your four core scenes. In the Scenes panel, add: Starting Soon, Live, Be Right Back, and Ending. Rationale: these are the exact scenes Twitch Studio shipped by default. They give your stream structure and give you a graceful way to step away without showing a frozen desktop.
8. Add your sources to the Live scene in the right order. Game Capture or Display Capture on the bottom, then Webcam (Video Capture Device), then overlays and text on top. Rationale: OBS layers top-down in the Sources list — the top item draws over everything below it. Put the game at the bottom or it covers your face.
9. Add your microphone and configure audio (covered fully in its own section). Settings → Audio → Mic/Auxiliary. Rationale: audio is set globally and persists across scenes, unlike video sources. Getting it right once means it works everywhere.
10. Dock Twitch chat natively. Once your account is connected, the View → Docks menu exposes a Twitch Chat dock. Drag it where you want it. Rationale: this replaces Twitch Studio's integrated chat with no third-party dependency. It reads your channel directly through the OAuth connection from Step 3.
11. Add an alerts browser source. Create a Streamlabs or StreamElements alert overlay, copy its widget URL, and add it as a Browser source in your Live scene. Rationale: OBS has no native alert engine. This single browser source restores the follow/sub/bits/raid notifications Twitch Studio gave you for free.
12. Run a private test stream before going public. Use OBS's "Start Streaming" with your channel set to a restricted state, or stream to a test title at an off hour. Rationale: verify bitrate stability, audio levels, scene switching, and alert firing with nobody watching. Discovering a muted mic on a live debut is a rite of passage you are entitled to skip.

Expected output after Step 12

When the rebuild is done, OBS's Stats dock (View → Docks → Stats) should read something like this during your test:

OBS Stats — live test
CPU Usage:          11.4%
Disk space avail:   214.6 GB
Memory usage:       742 MB
FPS (output):       60.00
Frames missed (rendering):  0 / 0.0%
Skipped frames (encoding):  0 / 0.0%
Dropped frames (network):   0 / 0.0%
Bitrate:            5980 kb/s   # hovering near your 6000 target

Zero dropped frames on the network line is the metric that matters. If that number climbs while you stream, your bitrate is too high for your upload — drop to 4500 Kbps and retest.

Enhanced Broadcasting and Dual-Format

What Enhanced Broadcasting changed

This is the marquee 2026 feature and the clearest sign that the beginner era is over. Enhanced Broadcasting is Twitch's multi-track ingest: instead of sending one fixed-resolution stream, OBS sends multiple quality tracks and Twitch handles the transcoding ladder server-side. For eligible Affiliates and Partners, it unlocks 2K (1440p) output — a genuine step up from the old 1080p pipeline — and it is the transport layer that dual-format streaming rides on. Twitch's own 2026 guidance, echoed across creator coverage from outlets like Engadget, frames this as the platform finally giving away transcoding that used to be Partner-only luxury.

Setting up dual-format (16:9 + 9:16)

Dual-format means one broadcast produces both a horizontal 16:9 output for desktop and a vertical 9:16 output for mobile, simultaneously. The 2026 requirements are specific: OBS Studio v31.0 or newer, plus a vertical plugin. Here is the conceptual layout you are building:

# Dual-format output, conceptual mapping
# Horizontal (primary) canvas:
  base_resolution   = 1920x1080      # 16:9 desktop
  output_resolution = 1920x1080
  fps               = 60

# Vertical (plugin) canvas:
  base_resolution   = 1080x1920      # 9:16 mobile
  output_resolution = 1080x1920
  fps               = 60
  source            = cropped/reframed from primary scene

# Both tracks ride Enhanced Broadcasting to Twitch.
# Requirement: OBS >= 31.0 AND vertical plugin installed.

The vertical plugin adds a second canvas you compose independently. You do not get a free crop of your horizontal scene — you reframe deliberately, because a 16:9 game centered for desktop usually puts the action in the wrong place for a phone. Plan your vertical layout as its own thing.

Should a beginner bother?

Honestly? Not on night one. Dual-format doubles your encoding load and your composition work. Get the horizontal 1080p60 stream stable first — Steps 1 through 12 — then add the vertical canvas once you can do the basics in your sleep. The plugin is not going anywhere. Mobile reach is real, but a janky dual-format debut is worse than a clean single-format one. The OBS multi-output documentation, kept current in the OBS Studio GitHub repository, is the authority to consult when you do add it.

Audio, Alerts, and Overlays

Getting audio right

Audio is where most first streams die. Viewers forgive a mediocre webcam; they leave instantly over a hissing, clipping, or absent microphone. OBS handles audio globally through Settings → Audio, and through per-source filters. The two filters every microphone needs are a Noise Suppression filter and a Noise Gate.

# Recommended starting filter chain for a USB mic in OBS
# (Right-click mic source -> Filters -> add in this order)

1. Noise Suppression
     method: RNNoise        # AI-based, low CPU, good default

2. Noise Gate
     close_threshold: -45 dB
     open_threshold:  -35 dB
     attack_time:     25 ms
     hold_time:       200 ms
     release_time:    150 ms

3. Compressor
     ratio:           4:1
     threshold:       -18 dB
     output_gain:     +3 dB

The gate silences your keyboard and room hum between sentences; the compressor evens out your volume so you are not whisper-then-shout. Tune the gate thresholds to your room — too aggressive and it clips the start of your words.

Alerts without the native engine

As established, OBS has no built-in alerts, so you restore them with a browser source pointed at a free overlay service. Both Streamlabs and StreamElements give you a widget URL that renders transparent in OBS. Add it as a Browser source sized to your canvas (1920x1080), place it on top of your Live scene, and it will fire follow/sub/bits/raid animations exactly like Twitch Studio did. The 2026 wrinkle is that modern chatbots have gone AI-driven — memory, contextual raid messages, conversational prompts — so the alert layer is increasingly entangled with a smarter bot than the simplicity era ever assumed. You do not need that on day one, but know it exists.

Overlays and Pulsoid heart-rate

Overlays are just more browser or image sources. One genuinely fun 2026 addition: Pulsoid, which pushes a real-time heart-rate overlay to your stream through a browser-based widget you layer into an OBS scene. For horror games, speedruns, or fitness streams, a live BPM counter is legitimately good content — the audience watching your pulse spike is its own engagement loop. It is the same browser-source pattern: get the widget URL, add it as a Browser source, position it. Twitch's ecosystem analysis, including reporting from Ars Technica on the creator-economy tooling explosion, treats these biometric and AI overlays as the natural successors to Twitch Studio's deliberately minimal feature set.

Importing From the Corpse

The Streamlabs experimental importer

If you actually had a Twitch Studio configuration and you do not want to rebuild every scene by hand, there is a salvage path. Streamlabs built an experimental importer specifically to migrate creators off Twitch Studio. According to Streamlabs, it pulls Scenes, Webcam, Images, Videos, Text Sources, Color Sources, Browser Sources, and Alerts into Streamlabs Desktop. That is most of what Twitch Studio held. It is the only first-party-ish migration tool that exists, and the word experimental is doing real work — expect to hand-fix the result.

The catch with importing to a fork

The importer targets Streamlabs Desktop, which is an OBS fork, not vanilla OBS Studio. So your choice is: rebuild manually in OBS Studio (the platform this whole article recommends), or import automatically into Streamlabs and accept a fork. If you have a complex Twitch Studio setup with a dozen scenes and many sources, the importer's time savings may justify the fork. If you had four scenes, rebuild in OBS — you will finish before the importer finishes complaining about an unsupported source type.

# Migration decision, as pseudocode
if had_twitch_studio_config and scene_count > 8:
    use Streamlabs experimental importer  # then fix by hand
    accept_platform = "Streamlabs Desktop (OBS fork)"
else:
    rebuild_manually()
    accept_platform = "OBS Studio 31+"   # recommended

# Either way, alerts almost always need re-linking afterward.

What does not survive the move

Encoder settings, bitrate tuning, and your Twitch account connection do not meaningfully transfer — you reconfigure those regardless of path, because they are machine- and account-specific. Alert links frequently break and need re-authorizing. Treat any import as a head start on layout, not a finished stream. You still run Steps 2 through 6 of the rebuild afterward.

Five Pitfalls That Will Ruin Your Debut

Pitfall 1: Bitrate set above your upload

The single most common failure. You set 6000 Kbps on an 8 Mbps upload, the network line in Stats turns red, and your viewers watch a slideshow. Fix: keep your video bitrate at roughly 50–60% of your measured upload. On 10 Mbps up, 6000 Kbps is the ceiling; on anything less, drop to 4500 or 3500. Bitrate cannot exceed bandwidth. Physics is not negotiable.

Pitfall 2: Sources stacked in the wrong order

Your webcam vanishes and you assume it is broken. It is not — your full-screen Game Capture is drawn on top of it because Game Capture sits above Webcam in the Sources list. Fix: in the Sources panel, drag your camera and overlays above the game capture. OBS draws top-to-bottom, topmost-on-top. This trips up every single Twitch Studio refugee because Studio handled layering invisibly.

Pitfall 3: No Enhanced Broadcasting because you pasted a stream key

You used a raw stream key instead of connecting your account, and now dual-format and 2K are greyed out. Fix: Settings → Stream → remove the manual key, choose "Connect Account," and authorize through OAuth. Enhanced Broadcasting requires the connected-account path. This is also why our companion guides, including the PS Remote Play 1080p setup, all insist on proper account linking over key-pasting.

Pitfall 4: Audio captured twice (echo)

Viewers hear you in a slapback echo. You captured your microphone both as a global Mic/Aux device and as a per-scene Audio Input Capture source. Fix: pick one. Use the global Settings → Audio device and delete the duplicate per-scene source, or vice versa — never both for the same physical mic.

Pitfall 5: x264 encoder strangling the game

Your game stutters the moment you go live. You left the encoder on x264 (software), and now the CPU is shared between rendering the game and encoding the stream. Fix: switch to your hardware encoder (NVENC, AMF, or QSV) in Settings → Output. This is Step 6 for a reason; skipping it is the classic mid-range-PC mistake.

Troubleshooting Table

The symptoms you will actually encounter, and the first thing to try for each. Work top to bottom.

Advanced Tips for 2026

Lean into collaboration features

Twitch's 2026 toolkit is collaboration-first, and these features cost you nothing to enable once your base stream is solid. Shared Hype Trains let two or more streamers share one Hype Train across collaborating channels — pooling momentum instead of splitting it. Shared Chat merges chat across collaborating channels so a co-stream reads as one room. Drop Ins and Stream Together round out the native co-streaming kit. The strategic point: Twitch Studio was a single-streamer app for a single-streamer era. The platform now rewards showing up with other people. Build your scenes assuming you will eventually co-stream.

Use viewer streaks and retention mechanics

2026 Twitch lets viewers earn streaks for watching a channel across consecutive sessions — a retention-oriented reward layered onto the viewing experience. You do not configure this, but you can program around it: a consistent schedule turns streaks into a habit loop for your regulars. The feature only pays off if you are predictable. Pick days, hold them.

Multistream, but keep Twitch as home base

If you want reach beyond Twitch, Restream supports multistreaming to 30+ destinations from a single OBS output, letting you treat Twitch as home base while you seed an audience on other platforms. The 2026 framing is sensible: do not abandon Twitch, extend from it. One caveat — multistreaming to Twitch can conflict with Enhanced Broadcasting's multi-track ingest, so test whether you keep the advanced Twitch features or trade them for breadth. You usually cannot have both at full fidelity.

Bots that remember

The AI-driven chatbot shift is worth an evening of experimentation once you are comfortable. Modern bots carry memory, generate contextual raid messages, and run conversational prompts — a different animal from the keyword-trigger bots of the Twitch Studio era. Used with restraint they fill dead air during quiet stretches; used without restraint they make your channel feel like a call center. Configure sparingly.

The Complete Working Configuration

The reference settings, in one block

Here is the full, copyable configuration for a 1080p60 Twitch stream on a 10 Mbps upload with a mid-range PC and hardware encoding. This is the destination of all twelve steps, written out so you can verify your own setup against it line by line.

# ===== OBS STUDIO 31+ — TWITCH 1080p60 REFERENCE CONFIG =====

[Stream]
service            = Twitch
connection         = Connect Account (OAuth)   # NOT a raw key
enhanced_broadcast = enabled

[Video]
base_canvas        = 1920x1080
output_scaled      = 1920x1080      # no rescale
fps                = 60
downscale_filter   = Lanczos        # only matters if you rescale

[Output]  (mode: Advanced)
encoder            = NVENC (or AMF / QSV)
rate_control       = CBR
bitrate            = 6000 Kbps      # for 10 Mbps upload
keyframe_interval  = 2 s            # Twitch requirement
preset             = Quality
profile            = high

[Audio]
sample_rate        = 48 kHz
channels           = Stereo
mic_bitrate        = 160 Kbps
mic_filters        = RNNoise -> Noise Gate -> Compressor

[Scenes]
- Starting Soon    (image/video + text countdown)
- Live             (game [bottom] -> webcam -> alerts [top])
- Be Right Back    (static image + audio)
- Ending           (outro + social handles)

[Sources on Live, top to bottom]
1. Alerts (Browser source, 1920x1080, transparent)
2. Pulsoid heart-rate (Browser source, optional)
3. Webcam (Video Capture Device)
4. Game Capture / Display Capture

[Docks]
- Twitch Chat (native, via connected account)
- Stats (monitor dropped frames live)

[Optional — dual-format]
vertical_plugin    = installed
vertical_canvas    = 1080x1920
vertical_fps       = 60

Verification checklist

Before you call it done, confirm each of these against your live test in the Stats dock and your phone:

• Network dropped frames at 0% across a five-minute test.
• Output FPS holding steady at 60.00.
• Microphone visible on the audio meter, peaking around -12 dB to -6 dB, never clipping at 0.
• Webcam drawn over the game, not under it.
• An alert fires on a test follow (use a second account or a service test button).
• Twitch chat dock populating in real time.

Where to go from here

That is the rebuild. Twitch Studio is dead, and what you have constructed is not a replica — it is an upgrade that happens to do everything the dead app did, plus dual-format, plus 2K, plus collaboration features the wizard-era app never dreamed of. The price was forty-five minutes and the permanent loss of the illusion that streaming is simple. It was never simple. Twitch Studio just hid the complexity behind a friendly face, and then Twitch took the face away. For the official historical record on the app, the Twitch Help Center and Creator Camp archives remain the canonical source. For everything forward of here, the OBS documentation is your manual. Go live. Try not to be muted.