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

Search engines still index a tutorial for software that no longer exists, which is how you arrived here typing the words "twitch studio" into a box in 2026. So let us perform a small act of mercy and a larger act of usefulness. The mercy: a clear-eyed obituary. The usefulness: a full migration to the program Twitch Studio was always a training-wheels imitation of. By the end of this you will have a working Twitch stream running on OBS Studio v31, configured to the same standard Twitch's own staff would recommend, in roughly twelve steps and forty-five minutes. Bring coffee. The hard part is not the software. The hard part is unlearning the idea that a wizard will do this for you.

The Obituary: Twitch Studio, 2019–2024

Let us begin with the only honest sentence anyone can write about Twitch Studio in 2026: it is dead. Not deprecated, not "in maintenance," not quietly coasting on a skeleton crew somewhere in Amazon's org chart. Dead. Twitch pulled the plug on May 30, 2024, and unlike a Sega console or a canceled MMO, there is no homebrew scene rushing in to keep the corpse warm. The download page at twitch.tv/broadcast/studio stopped serving installers, the help articles were shoved into an archival topic nobody will ever update, and the engineers who built the thing were scattered to whatever a company does with engineers when a free product stops being strategically interesting.

So why are you reading a tutorial about it? Because you searched for one, and because the real task hiding behind "how do I use Twitch Studio in 2026" is "how do I do the thing Twitch Studio used to do, now that it is gone." That thing is OBS Studio. This guide is an exhumation followed by a transplant. We will spend exactly one section mourning and the rest rebuilding, because sentiment does not stream at 6000 kbps and grief does not key your webcam.

The Discontinuation Notice

The end was announced the way platforms always announce the death of a free product they would rather you forget: quietly, and well in advance, so that nobody could claim ambush. Twitch confirmed that support for Twitch Studio would end on May 30, 2024. After that date the application would still launch on machines that already had it — software does not evaporate — but it would receive no updates, no bug fixes, no new ingest endpoints, and no support tickets whatsoever. The Twitch Help Center still hosts an archived Twitch Studio topic page, which is the digital equivalent of a gravestone: present, legible, and entirely non-interactive. If you open Twitch Studio today and it still streams, congratulations — you are running an abandoned RTMP client against a live service that can change its ingest requirements at any time without telling you, and on the day it does, you will have no idea why your stream died.

The community saw it coming and processed it faster than the official channels did. By late April 2024 the r/Twitch threads had already moved through all five stages of grief and arrived at the only rational destination: install OBS. The denial was brief, the bargaining was nonexistent, and the acceptance was a pinned comment linking to obsproject.com. There is a lesson in that. When the platform abandons a tool, the platform's users do not wait for permission to move on.

Why Twitch Built It in the First Place

Twitch Studio existed to solve a real, measurable problem. OBS, to a first-time streamer, is a cockpit — scenes, sources, audio mixers, encoders, bitrates, keyframe intervals, a Studio Mode with a preview bus and a program bus like a television gallery. The drop-off was brutal: people downloaded OBS, opened it, saw a black rectangle and forty buttons, and closed it forever. Twitch's answer was an app that, per the company's own Creator Camp broadcasting-software guide, was "designed from the ground up" to be free and frictionless. It analyzed your microphone and webcam, suggested settings, supplied a default overlay, and promised to get you live in "just a few minutes." For thousands of people that promise was kept, and that is not nothing.

But a guided wizard is a ceiling as much as a floor. The moment you wanted a second capture card, a stinger transition, a chroma-keyed face cam over a gameplay scene, or any automation more sophisticated than a follower alert, you hit the edge of what Twitch Studio would ever do. It was a beautifully fenced garden built on land Twitch eventually decided it did not want to maintain. The fence is still there. The gardener left in May 2024.

What "End of Support" Actually Means

End of support is not a cosmetic status. It is a technical countdown. Twitch in 2025 and 2026 has moved its entire broadcasting story to OBS, including the features that define the modern platform: Enhanced Broadcasting with multitrack video, 2K/1440p output, dual-format encoding, AI chat tooling, and Shared Hype Trains. Twitch Studio supports exactly none of these, and it never will, because there is no team left to teach it. It cannot learn 1440p. It cannot learn multitrack video. It will not adopt a new ingest protocol when Twitch rotates one. Every month it keeps working is borrowed time, and the loan has no fixed term.

If you want the short, brutal version of this whole article, it is the same conclusion the house has reached before in our companion rebuild walkthrough: the software is defunct, the replacement is OBS, and the only intelligent move is to migrate cleanly before Twitch's infrastructure makes the decision for you. The rest of this document is how you do that without losing your overlay, your alerts, or your composure.

Prerequisites: Hardware and Software

Before you touch an installer, get your inventory straight. Migrating in a panic at 7:58 PM with a stream scheduled for 8:00 is how people end up broadcasting a black screen to a chat full of question marks. Here is precisely what you need, with version numbers, because vague prerequisites are a lie of omission.

Software Versions You Need

The non-negotiable item is OBS Studio v31.0 or newer — the December 2024 release line and everything after it. This is the version that ships current Twitch service integration, the bundled obs-websocket 5.x automation server, and support for Enhanced Broadcasting. Do not install some four-year-old build you found on a mirror; pull it from the official source. Your operating system needs to be reasonably modern: Windows 10 (21H2) or Windows 11, macOS 13 Ventura or newer, or a current Linux distribution with up-to-date GPU drivers. You will also need a normal web browser, because the correct way to connect to Twitch in 2026 is an OAuth login flow, not a pasted key. And update your GPU drivers before you do anything else — half of all "OBS is broken" reports are a stale driver wearing a trench coat.

Minimum and Recommended Hardware

Encoding live video is real work, and the machine has to do it while also running the game. The two viable paths are CPU encoding with x264 and GPU encoding with NVENC, AMD AMF, or Intel QSV. Hardware encoders are strongly preferred in 2026 because they offload the work to dedicated silicon and barely touch your frame rate.

If you are streaming from a console or a second machine, the encoder load moves to a capture card and your streaming PC's requirements drop, but your bandwidth requirements do not. The same bitrate math that governs a clean 15 Mbps Remote Play session governs your upload: video is video, and the pipe does not care what produced the frames.

Network and Account Requirements

Twitch's recommended ceiling for non-partnered channels has long sat around 6000 kbps for the video track, and you want your real, sustained upload to comfortably exceed that — budget at least 8–10 Mbps so transient congestion does not start dropping frames. Use a wired Ethernet connection if it is physically possible; Wi-Fi introduces jitter that turns into dropped frames at the worst moments, and "the worst moment" on a live stream is a statistical certainty. On the account side, your Twitch account must have two-factor authentication enabled — Twitch has required 2FA to stream for years, and OBS cannot conjure it for you. Have your phone or authenticator app within reach for Step 4.

Before You Migrate: The Salvage Operation

You cannot import a Twitch Studio configuration into OBS. There is no migration tool, no converter, no hidden menu. The two programs share an ancestor — RTMP streaming — and nothing else. Treat the move as a salvage operation on a sinking ship: grab what is portable, photograph the rest, and abandon the hull.

Why There Is No Import Button

Twitch Studio stored its layouts, scene definitions, and source positions in a proprietary internal format that was never documented for external tools and is now frozen for all time. OBS stores its configuration as a directory of JSON and INI files with an entirely different schema. Nobody wrote a translator between them while Twitch Studio was alive, and nobody will write one now that it is dead, because the audience for such a tool shrinks every day as the abandoned installs finally break. Accept that the layout is gone as a file and survives only as information — which is fine, because the information is what you actually need.

Screenshot Everything

Open Twitch Studio one last time, if it still launches, and document every scene like a crime scene. For each scene, screenshot the canvas and note: which sources are present, their stacking order, their rough on-screen positions and sizes, and any colors, fonts, or background images you care about. Pay special attention to your face-cam crop, your "Starting Soon" countdown, and your "Be Right Back" placeholder, because those are the three layouts every new OBS user forgets to rebuild and then scrambles to recreate live. A folder of labeled screenshots is your migration blueprint. It is low-tech and it is bulletproof.

Pull Your Stream Key and Assets

Collect the physical assets next: every overlay PNG, every alert graphic, every webcam frame, every font file, and the URLs of any third-party alert services (StreamElements, Streamlabs) you were pointing at. These are reusable verbatim — a transparent PNG overlay does not care which program composites it. Finally, locate your Twitch stream key in the Creator Dashboard under Settings → Stream, and while you are there, click Reset. If Twitch Studio ever cached your old key, resetting it now guarantees the abandoned app cannot accidentally hijack your channel later. You will paste the fresh key into OBS only if you skip the OAuth flow; we will recommend you do not.

Steps 1–3: Install OBS Studio v31

Now the transplant begins. The next three steps put a correctly versioned, correctly configured OBS on your machine and confirm it actually runs before you build anything on top of it.

Step 1 — Download the Correct Build

Rationale: Provenance matters. A streaming application has your authentication token and full screen-capture access; you do not want a tampered build from a random mirror. Pull v31 from the official project. Use your platform's package manager so updates stay clean.

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

# macOS (Homebrew)
brew install --cask obs

# Linux (Flatpak - always current)
flatpak install flathub com.obsproject.Studio

# Verify the version (must read 31.x or newer)
obs --version

If you prefer a graphical installer, get it straight from the official OBS Project site or inspect the source and releases on the OBS Studio GitHub repository. Both are the canonical, signed distribution points. Anything else is a coin flip you have no reason to take.

Step 2 — Run the Auto-Configuration Wizard

Rationale: This is the closest OBS comes to Twitch Studio's friendly onboarding, and ironically it does the job better. On first launch OBS offers the Auto-Configuration Wizard, which benchmarks your CPU and GPU, measures your upload to Twitch, and proposes a complete encoder profile. Choose "Optimize for streaming," set your base canvas to 1920×1080 at 60 fps, and let it run. Treat its output as a sane baseline you will refine in Step 11, not as gospel.

Auto-Configuration Wizard - Results
-----------------------------------
Usage profile:        Streaming
Base (canvas):        1920x1080
Output (scaled):      1920x1080
Framerate:            60 fps
Encoder:              NVIDIA NVENC H.264
Bitrate:              6000 kbps (CBR)
Audio:                160 kbps, 48 kHz, stereo
Streaming service:    Twitch
Ingest:               Auto (Closest)

[ Apply Settings ]

If the wizard proposes something far below this — say 720p30 at 2500 kbps — it is telling you the truth about your hardware or your connection, and you should listen rather than override it into a stuttering mess.

Step 3 — Verify the Install and Version

Rationale: Verify before you build. Confirm the version reads 31.x or newer in Help → About, and confirm the WebSocket server exists under Tools → WebSocket Server Settings — its presence proves you have a modern build with bundled automation, which we will use in the Advanced section. Five seconds of checking now prevents an hour of debugging a feature that an old build simply does not have. If the menu item is missing, you installed the wrong version; go back to Step 1.

Steps 4–6: Connect to Twitch

OBS is installed and benchmarked. Now point it at Twitch the modern way, which is materially different from the stream-key ritual most old tutorials describe.

Step 4 — Authenticate, Don't Paste a Stream Key

Rationale: In Settings → Stream, select Twitch as the service and click Connect Account rather than "Use Stream Key." The OAuth flow opens your browser, you log in with 2FA, and OBS receives a scoped token instead of storing your raw key in a plaintext file on disk. This is more secure, it unlocks the integrated Twitch docks (chat, activity feed, stream info) inside OBS, and it is the method Twitch itself now expects. The stream-key path still works as a fallback, but it is the streaming equivalent of writing your password on a sticky note.

Step 5 — Choose Your Ingest Server

Rationale: An ingest server is the front door your video enters Twitch through, and the closest door has the lowest latency and the fewest dropped frames. Leave the server on Auto and OBS will route to the nearest Twitch point of presence — for almost everyone this is correct. Override it to a named regional server only if Auto routes you somewhere absurd, which is rare. Under the hood, your selection is written to a tiny service.json file:

{
    "settings": {
        "bwtest": false,
        "protocol": "RTMP",
        "server": "auto",
        "service": "Twitch"
    },
    "type": "rtmp_common"
}

Twitch's own recommended encoding and ingest values are documented in the Twitch broadcasting guidelines — bookmark them, because they are the authority that overrides any tutorial, including this one, if the two ever disagree.

Step 6 — Enable the Integrated Dashboard and Chat

Rationale: Twitch Studio's one genuinely nice touch was a built-in chat panel so you did not need a second monitor full of browser tabs. OBS replicates this exactly. Because you authenticated in Step 4, you can now go to Docks → Twitch Chat, Twitch Info, and Twitch Activity Feed and pin them directly into the OBS interface. This restores the single-window comfort you are migrating away from, with none of the dead-end limitations. Drag the docks where Twitch Studio used to put them and the muscle memory survives the transplant.

Steps 7–9: Rebuild Scenes and Sources

This is the heart of the migration and the part the screenshots from your salvage operation pay for. A "scene" is a saved arrangement of sources; a "source" is any single input — a game, a camera, an image, a browser overlay. Twitch Studio hid this model behind defaults. OBS hands it to you directly, which is the whole point.

Step 7 — Recreate Your Scene Collection

Rationale: A scene collection is the named container holding all your scenes, and starting fresh keeps the file clean. Create a new collection under Scene Collection → New, then build the four scenes every channel needs: Starting Soon, Gameplay, Be Right Back, and Ending. Build these as discrete scenes so you can cut between them instantly mid-stream instead of frantically toggling source visibility on one overloaded canvas. OBS stores the whole collection as a single JSON file you can back up, version, or copy to another machine — something Twitch Studio never let you touch:

{
  "name": "Twitch 2026",
  "current_scene": "Gameplay",
  "scene_order": [
    { "name": "Starting Soon" },
    { "name": "Gameplay" },
    { "name": "Be Right Back" },
    { "name": "Ending" }
  ]
}

Step 8 — Add Capture Sources Correctly

Rationale: Choosing the right capture type is the single most common place new OBS users fail, and getting it right the first time prevents the dreaded black screen. For a PC game, prefer Game Capture (it hooks the game directly and is the most efficient); fall back to Window Capture for borderless titles that refuse to hook, and reserve Display Capture for desktop content only. For your camera, add a Video Capture Device and pick the MJPEG format for high frame rates over USB. If you are bringing in a console, the source is your capture card as a Video Capture Device — the exact same workflow our PS5 capture-card walkthrough details, dropped into an OBS scene as just another input.

Step 9 — Layer Overlays, Alerts, and Filters

Rationale: Overlays and alerts are what made Twitch Studio look finished out of the box; in OBS you assemble them from the PNGs and URLs you salvaged. Add your overlay graphic as an Image source on top of the stack, and add follower/sub alerts as a Browser source pointing at your StreamElements or Streamlabs alert URL — this is exactly how the "native" alerts on every big channel actually work. Then add filters: a Chroma Key on the webcam if you use a green screen, and Color Correction to match its tone to your overlay. Filters are non-destructive and stack in order, which is power Twitch Studio simply did not expose.

Steps 10–12: Audio and Encoder Settings

The picture is built. Now the two things that separate an amateur stream from a watchable one: clean audio and a correctly tuned encoder. These final three steps are where most of the quality lives.

Step 10 — Route Your Audio

Rationale: Bad audio drives viewers away faster than bad video, and OBS gives you a real mixer to prevent it. In the Audio Mixer you will have at least two tracks: Desktop Audio (game and system sound) and Mic/Aux (your microphone). On the mic, add three filters in order — Noise Suppression to kill background hum, a Noise Gate to cut the channel when you are silent, and a Limiter to stop peaks from clipping when you get excited. Set every device to 48 kHz to match OBS's internal sample rate; a mismatch here is the number-one cause of audio that slowly drifts out of sync over a long stream.

Step 11 — Configure the Encoder

Rationale: This is the step that determines whether your motion looks crisp or like wet cardboard. Use a hardware encoder (NVENC, AMF, or QSV) if you have one so encoding does not steal frames from your game. Set CBR at 6000 kbps, a keyframe interval of 2 seconds (Twitch requires this — "auto" will get your stream transcoded badly or rejected), and the High profile. Here is a known-good NVENC encoder profile, written to streamEncoder.json:

{
    "bitrate": 6000,
    "keyint_sec": 2,
    "rate_control": "CBR",
    "preset2": "p5",
    "tune": "hq",
    "multipass": "qres",
    "profile": "high",
    "psycho_aq": true,
    "lookahead": false,
    "bf": 2
}

If you have no usable hardware encoder, x264 on the veryfast preset is the CPU fallback. It looks excellent but costs real processor time, so only choose it if your benchmarks in Step 2 said you could afford it:

{
    "bitrate": 6000,
    "keyint_sec": 2,
    "rate_control": "CBR",
    "preset": "veryfast",
    "profile": "high",
    "tune": "",
    "x264opts": ""
}

For the canvas and audio side, the corresponding basic.ini block looks like this — note the 48 kHz sample rate matching Step 10:

[Output]
Mode=Advanced

[AdvOut]
Encoder=jim_nvenc
RescaleOutput=false
TrackIndex=1

[Video]
BaseCX=1920
BaseCY=1080
OutputCX=1920
OutputCY=1080
FPSType=2
FPSInt=60
ScaleType=lanczos
ColorFormat=NV12
ColorSpace=709
ColorRange=Partial

[Audio]
SampleRate=48000
ChannelSetup=Stereo

Step 12 — Test Stream and Verify Bitrate

Rationale: Never debut a fresh configuration to a live audience. Use Settings → Stream → "Test" (the bwtest flag) or simply go live to an unlisted/empty channel and watch the Stats dock for sixty seconds. You are looking for zero dropped frames, congestion at or near zero, and a stream bitrate sitting at your target. A healthy readout looks like this:

Stats
-----
CPU Usage:            6.4%
Memory Usage:         412 MB
Frame rate:           60.0 fps
Dropped frames (net): 0 (0.0%)
Congestion:           0.0%
Stream bitrate:       5998 kbps

If Dropped frames climbs above zero and stays there, your problem is the network, not OBS — skip to the troubleshooting table. If the CPU Usage figure is alarming or the encoder reports overload, your problem is the encoder. The Stats dock tells you which of the two it is, and that distinction is half of all debugging.

Five Pitfalls That Ruin a First Stream

The migration is mechanically done, but five specific mistakes account for the overwhelming majority of "my first OBS stream looked terrible" posts. Read these before you go live, not after.

Keyframes, Bitrate, and the CBR Rule

Pitfall 1 — keyframe interval left on "auto." Twitch's ingest expects a keyframe every 2 seconds. Leave it on auto and Twitch's transcoder either mangles your stream or refuses the quality options that let viewers pick a lower resolution. Fix: set keyint_sec to exactly 2, as in the configs above. Pitfall 2 — bitrate that does not match the resolution. Streaming 1080p60 at 3500 kbps produces a blocky smear the instant anything moves quickly, because you are starving a high-motion, high-resolution signal of data. Fix: run 1080p60 at the full 6000 kbps CBR, or — if your upload cannot sustain that — drop the output resolution to 1600×900 rather than starving 1080p. Resolution you can afford beats resolution you cannot.

The Multi-GPU Black Screen

Pitfall 3 — Display Capture on a dual-GPU laptop. Laptops with an integrated GPU and a discrete GPU famously hand OBS a black rectangle where the game should be, because OBS is running on one GPU and the game on the other and neither can see the other's frame buffer. Fix: prefer Game Capture (which hooks the game regardless of GPU), and in Windows Graphics Settings force OBS to use the high-performance GPU. This single setting resolves the majority of black-screen reports on portable hardware — the same dual-GPU reality that complicates streaming from devices like those in our ROG Ally X versus Steam Deck OLED breakdown.

Audio Sins: Hiss, Crackle, and Desync

Pitfall 4 — a raw, unfiltered microphone. Streaming a bare mic broadcasts every fan, every keystroke, and a constant electronic hiss directly into your viewers' ears. Fix: the Noise Suppression / Noise Gate / Limiter filter chain from Step 10, in that order. Pitfall 5 — sample-rate mismatch and exclusive mode. If your interface runs at 44.1 kHz while OBS runs at 48 kHz, or if a Windows app holds the device in "exclusive mode," you get crackle, pops, and audio that drifts out of sync over time. Fix: set every device — Windows, your interface, and OBS — to 48 kHz, and disable "Allow applications to take exclusive control" in the Windows sound device's Advanced tab. Consistency is the whole trick.

The Troubleshooting Table

When something breaks live, you do not have time to read prose. You need a symptom, a cause, and a fix. Here is the reference table — keep it open on a second monitor for your first few streams.

Network Drops vs Encoder Overload

The most important diagnostic skill is telling these two apart, because they have opposite fixes. Dropped frames (network) in the Stats dock means your data is not reaching Twitch fast enough — the cause is upstream of OBS, in your router or your ISP, and the fix is lowering bitrate or going wired. Skipped frames (encoding) or the red overload warning means OBS cannot produce frames fast enough — the cause is your processor, and the fix is a lighter encoder or preset. Confusing the two and lowering bitrate to fix an encoder problem is a classic dead end that wastes a whole stream.

Black Screens and Silent Mics

Black screens are almost always a capture-method or GPU-routing issue, not a broken install — work down the capture types (Game, then Window, then Display) and check your GPU assignment before you reinstall anything. Silent microphones are almost always a device-selection or OS-permission issue; in 2026 both Windows and macOS gate microphone access behind a privacy toggle that, if off, leaves OBS legally deaf no matter how perfect your mixer settings are.

When Twitch Itself Is the Problem

Occasionally the fault is neither your PC nor your config but Twitch's ingest or your account state. A key that worked yesterday and fails today usually means it was reset — re-running Connect Account fixes it. If your stream connects but viewers report buffering across the board while your local Stats are clean, the regional ingest may be congested; override the Auto server to a different nearby region. When in doubt, the canonical reference for what Twitch currently accepts is the official broadcasting guidelines, not forum folklore.

Advanced Tips: Past Parity

You have now matched everything Twitch Studio could do. The point of OBS is that you do not have to stop there. These three capabilities are the reasons professionals never used the wizard in the first place.

obs-websocket, Streamer.bot, and Real Automation

Twitch Studio's alerts were a sealed box. OBS exposes a full control API through the bundled obs-websocket 5.x server, which third-party tools drive to automate anything — scene switches on a sub, animated alerts, chat commands that trigger overlays. The dominant tool here is Streamer.bot, which connects to the same WebSocket endpoint and replaces a half-dozen separate apps. Enable the server, set a password, and you have a programmable stream:

# OBS: Tools -> WebSocket Server Settings
# Enable server, set a password, default port 4455

# Test from a terminal with obs-cmd (community CLI):
obs-cmd --websocket "obsws://localhost:4455/yourpassword" scene switch "Gameplay"

# Streamer.bot connects to the same endpoint:
#   Host: 127.0.0.1   Port: 4455   Password: yourpassword

Full protocol documentation lives in the OBS Knowledge Base, which is the maintained, authoritative help resource that Twitch Studio's archived topic page can only gesture at.

Replay Buffer, Clips, and Local Recording

Enable the Replay Buffer and bind it to a hotkey, and OBS continuously holds the last 30–60 seconds in memory; tap the key after a great moment and it writes a clip to disk instantly — a local, full-quality complement to Twitch's own clipping. While you are at it, configure local recording to a separate, higher-bitrate track so you have a pristine VOD that is not capped by your 6000 kbps stream budget. Twitch Studio never offered an independent recording quality. OBS treats it as a first-class output.

Enhanced Broadcasting: 1440p and Multitrack Video

The defining 2025–2026 Twitch feature is Enhanced Broadcasting — multitrack video that lets OBS send several quality renditions at once, including 2K/1440p, so viewers on weak connections get a clean lower-resolution option Twitch did not have to transcode. OBS v30.1 and newer support it natively; Twitch Studio supports none of it and never can. This is the same 1440p-versus-4K tier conversation that frames our Series X versus Series S resolution breakdown, now applied to the broadcast side: more pixels are worth it only when the pipeline can carry them, and in 2026 the pipeline finally can.

The Complete Working Configuration

Here is the entire known-good setup in one place, ready to drop into an OBS profile directory. On Windows that directory is %APPDATA%\obs-studio\basic\profiles\YourProfile\; on Linux it is ~/.config/obs-studio/basic/profiles/YourProfile/; on macOS it lives under ~/Library/Application Support/obs-studio/. Copy the files, restart OBS, and you have a 1080p60, 6000 kbps CBR Twitch stream that meets every current platform requirement.

service.json (Stream Target)

This points OBS at Twitch with auto ingest. If you used Connect Account in Step 4, OBS manages the token and you will not see a raw key; the form below is the explicit stream-key fallback with a placeholder — never commit your real key anywhere.

{
    "settings": {
        "bwtest": false,
        "key": "live_000000000_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "server": "auto",
        "service": "Twitch"
    },
    "type": "rtmp_common"
}

basic.ini and streamEncoder.json (Video + Encoder)

The video, audio, and output block, followed by the NVENC encoder profile. Together these are the heart of the configuration — 1080p60 canvas, 48 kHz audio, CBR 6000, 2-second keyframes.

[Video]
BaseCX=1920
BaseCY=1080
OutputCX=1920
OutputCY=1080
FPSType=2
FPSInt=60
ScaleType=lanczos
ColorFormat=NV12
ColorSpace=709
ColorRange=Partial

[Audio]
SampleRate=48000
ChannelSetup=Stereo

[Output]
Mode=Advanced

{
    "bitrate": 6000,
    "keyint_sec": 2,
    "rate_control": "CBR",
    "preset2": "p5",
    "tune": "hq",
    "multipass": "qres",
    "profile": "high",
    "psycho_aq": true,
    "lookahead": false,
    "bf": 2
}

The Final Pre-Flight Checklist

Run this list once before every stream for the first month. It becomes muscle memory, and then you will never think about it again — which is exactly the frictionless state Twitch Studio promised and OBS actually delivers once it is set up.

1. OBS version reads 31.x or newer (Help → About).
2. Twitch account connected via OAuth; 2FA confirmed.
3. Encoder is hardware (NVENC/AMF/QSV) at CBR 6000, keyframe 2s.
4. All four scenes present: Starting Soon, Gameplay, BRB, Ending.
5. Mic filter chain active: Noise Suppression, Gate, Limiter.
6. Every audio device set to 48 kHz.
7. Stats dock open: 0 dropped frames on a 60-second test.
8. Replay Buffer bound to a hotkey; local recording configured.

That is the whole transplant. Twitch Studio is in the ground where Twitch put it on May 30, 2024, and you are now running the tool the entire platform standardized on — multitrack-capable, scriptable, recording at a quality the wizard never allowed, and answerable to no end-of-support countdown. The Machine's verdict is the one the r/Twitch threads reached two years ago and the one the platform's own roadmap enforces today: do not mourn the wizard. Out-build it. You just did.