To set up OBS Studio for Twitch, connect your account, add your game and microphone, then test the picture, sound and connection separately. Use the Auto-Configuration Wizard as a starting point. A higher resolution can wait until your setup handles an actual gaming session without trouble.
This guide focuses on a single-PC gaming stream. Most capture steps below use Windows; the source names differ on macOS and Linux. Start with one scene and a clear voice. You can add the webcam, alerts and overlays once that works.
1. Install OBS and check what your PC can handle
Get OBS from the official download page for your operating system. Installing the program does not prove your computer can also run your game and encode a stream. The OBS system requirements explain that the workload depends on the encoder, resolution, frame rate and scene complexity. There is no single graphics-card model that every Twitch beginner needs.
Use headphones for the setup, close applications you do not need and keep the first scene simple. That makes an unexpected sound or performance problem easier to trace.
2. Connect Twitch and run the setup wizard
In Settings → Stream, select Twitch and use Connect Account. Twitch describes this route in its OBS connection instructions. Keep stream keys out of screenshots and messages.
Open Tools → Auto-Configuration Wizard, choose streaming and work through its prompts. It considers your computer and connection; treat the suggested settings as something to test. The official OBS quick start shows the wizard and the basic setup.
3. Add a game source before building the layout
- Create a scene named Gameplay. In Sources, press + and add Game Capture on Windows.
- Launch the game, choose Capture specific window in the source properties and select its window. Check the result while the game is active.
- Resize the source in the preview. If you add a webcam or graphic later, place it above the game in the Sources list so it remains visible.
Game Capture is a Windows source. On macOS, use macOS Screen Capture; on Linux, use Window Capture. The OBS sources guide explains source order and resizing. Check a display-capture scene carefully: whatever appears on that display may become part of the broadcast.
4. Select the microphone and avoid duplicate audio
Open Settings → Audio and select your microphone by name under Mic/Auxiliary Audio. Speak and watch its meter. If nothing moves, check the selected device and the operating system’s microphone access. OBS’s audio setup steps cover manual device selection.
Capture each device once. If your microphone is already enabled globally, do not also add it as an Audio Input Capture source. Disable its global entry when switching to the scene-source route. OBS documents duplicate capture as a cause of echo.
Set the microphone or interface gain before balancing the OBS faders. Include a louder reaction and leave room before clipping. Record speech over loud gameplay and listen back: a moving meter does not tell you whether viewers can understand you. See the OBS audio mixer guide for level controls.
On a compatible Windows setup, Application Audio Capture lets you select an application’s sound. Disable Desktop Audio if it would capture that same sound again. Otherwise, your desktop mix may include other apps and notifications. Source availability and audio permissions differ by platform; verify the saved recording rather than assuming game sound is present.
5. Choose one stream configuration to test
Enhanced Broadcasting: if your OBS setup supports it, enable it under Settings → Stream in the Multitrack Video section. It can send multiple qualities and configure encoding automatically. Start with Auto; bandwidth and video-track limits are ceilings, not targets. Follow Twitch’s Enhanced Broadcasting guide and test the resulting load on your PC.
Classic H.264 stream: with Enhanced Broadcasting off, these are two examples from Twitch’s single-stream recommendations. Use the first as a modest test profile, not a promise that every PC or connection can sustain it. Set output resolution and frame rate under Settings → Video and the streaming encoder options under Settings → Output.
| Test profile | Output and frame rate | Video bitrate | Rate control / keyframes |
|---|---|---|---|
| A smaller starting profile | 1280 × 720, 30 fps | 3000 kbps | CBR / 2 seconds |
| A higher-load comparison, after testing | 1920 × 1080, 60 fps | 6000 kbps | CBR / 2 seconds |
These values describe the classic path. They are not universal Twitch limits or settings to copy into an automatically configured multitrack stream. Keep upload capacity available for your game and other network traffic.
6. Test locally, then check the Twitch connection
Start Recording saves a local test; Start Streaming normally sends your broadcast live. First record a short gameplay session with speech, a louder reaction and a scene change. Watch it back for black frames, unreadable layout elements, missing game audio and a voice buried under the game. Change one problem at a time.
A local recording does not test the route to Twitch. Use Twitch Inspector’s stream test for connection stability. Its manual stream-key method appends ?bandwidthtest=true to the key: that test does not appear online or send viewer notifications. It checks transmission rather than providing a private channel preview. Follow Inspector’s steps and remove the test suffix before your real broadcast.
If the test fails, fix the problem you actually see
- Black game capture: confirm the selected game window and check a recording while playing. Some fullscreen games stop rendering when you switch away. For incompatible games, try borderless/windowed mode with Window Capture. Use the game-specific capture troubleshooting guide.
- Network dropped frames: try a wired connection, reduce streaming bitrate and stop competing uploads. Follow OBS connection troubleshooting; raising encoder quality will not repair a network bottleneck.
- Encoding or rendering overload: limit the game’s frame rate, simplify the scene or reduce output resolution/frame rate. Even hardware encoding needs room for OBS to render the scene. See OBS performance troubleshooting.
- Viewers buffer but OBS reports no network drops: check viewer playback as well. A clean sender connection does not guarantee every viewer can play the same quality. OBS’s buffering guide explains the distinction.
Before the first public stream
- Play back the final recording with headphones: voice, game sound and mute controls should work as intended.
- Inspect the captured area for private windows, notifications and account details.
- Check the connection test, then use a normal Twitch connection for the real broadcast.
- Keep this working scene as your baseline before adding more sources or raising quality.
