How to Set Up OBS Studio: First Stream Checklist

Install OBS and let the wizard establish a baseline

Use the official download rather than a bundled installer from a third-party site. On first launch, the Auto-Configuration Wizard asks whether the priority is streaming or recording, considers the computer’s hardware and can test network conditions for streaming. Run it again from Tools → Auto-Configuration Wizard whenever you need a clean baseline.

The wizard is not a production acceptance test. It cannot know the full scene complexity, the venue’s competing traffic, a capture device’s behavior over two hours or the destination’s event settings. Save the result as a named profile, then test it with the sources and workload that will actually run.

Create a scene collection another operator can understand

A scene is a complete on-air layout. Sources are the camera, display, window, image, browser, media file or audio device inside it. For the first setup, create three scenes at most:

• Program: the normal camera, screen or gameplay layout.
• Standby: a clear slate used before the show or while a source is repaired.
• Break: optional holding content with the intended audio behavior.

Name every source by what it represents, such as “Host camera” or “Slides,” rather than leaving several entries named Video Capture Device. Lock sources after positioning them. The official Sources Guide documents the current capture types and transform controls.

Make the audio path simple enough to hear and troubleshoot

Watch the Audio Mixer while speaking at the level expected during the event. A moving meter proves signal activity, but it does not prove that the correct microphone is selected, the sound is clean or the audience mix includes every source. Make a local recording and listen on headphones.

On macOS 13 or later, OBS 30 and newer can use the macOS Audio Capture source for desktop or per-application sound. Earlier macOS versions may require another audio-routing method. Use the current OBS macOS audio guide rather than an old virtual-cable tutorial.

Set video dimensions from the source and destination contract

The Base (Canvas) Resolution is the space in which scenes are composed. The Output (Scaled) Resolution is the raster sent or recorded. Set the canvas to a production size that fits the main sources, then choose an output the computer, uplink and destination can sustain. Upscaling a small or soft source does not create missing detail.

Use 30 fps when that meets the content and delivery requirement. Use 60 fps when motion benefits, the source truly produces it and the combined render, encode and network test remains stable. A slide presentation or talking head does not automatically improve because it consumes twice as many frames.

For a streaming profile, follow the destination’s current codec, resolution, frame-rate, keyframe and bitrate rules. Use the OBS bitrate guide to choose a stable output instead of copying a preset from an unrelated channel.

Choose the encoder with headroom for the whole show

OBS exposes only encoders available on the machine. A supported hardware encoder often preserves CPU capacity for scene composition, browser sources and applications. A software encoder such as x264 can still be appropriate when the CPU budget is known. There is no useful winner without the actual computer and scene load.

Test while the game, slides, video calls, animated overlays and local recording are all active. In View → Stats, distinguish rendering lag from encoding lag and network dropped frames. Those symptoms point to different boundaries; changing the stream key will not repair an overloaded GPU.

Connect one destination without exposing its credential

Under Settings → Stream, select a supported service and connect the intended account when that option fits the workflow, or enter the approved server and stream key. A stream key authorizes publishing. Keep it out of screenshots, tickets, chat and shared scene exports.

For Twitch specifically, continue with the OBS-to-Twitch setup. For YouTube, use the account and event selected in Live Control Room. For a Callaba input, copy the publisher value from the active RTMP Server or SRT Server and follow the protocol-specific guide: RTMP with OBS or SRT sending from OBS.

Record locally before asking a network to prove the scene

Start Recording, operate every scene, play the loudest media, speak, move and trigger the overlays expected in production. Stop normally and watch the file from beginning to end. Check small text, motion, color, lip sync, transitions and every intended audio source. A clean local recording proves the production and encode boundaries without mixing in a network or platform fault.

If local recording is the main job, use the OBS recording settings guide for container, quality mode, audio tracks and storage.

Run a private stream and verify the far end

1. Select a private, unlisted or test destination appropriate to the platform.
2. Open OBS Stats and start streaming with the production scene workload.
3. Confirm the receiver reports an active input and valid media.
4. Watch the real destination preview on another device and listen to it.
5. Switch scenes, play media, speak and leave the test running long enough to expose heat or network drift.
6. Stop through the documented platform and OBS sequence, then confirm the session closes cleanly.

When one OBS program needs monitoring, independent destination controls or several outputs, the OBS streaming workflow explains when to place Callaba between OBS and the destinations. For a single straightforward platform, direct publishing may remain the simpler design.

Troubleshoot the symptom, not every setting at once

Frequently asked questions

Do I need plugins to start using OBS?

No. A first reliable stream needs only the correct built-in sources, audio, encoder and destination. Add a plugin when it solves a defined problem and has been tested against the installed OBS version.

Should OBS use the same settings for every event?

No. Create named profiles for meaningfully different destinations or workloads. Avoid silent last-minute changes to a known-good profile.

Why does OBS work in preview but fail while live?

Preview does not exercise the full encode, network and destination chain. Test the production workload while actually streaming to a private endpoint and, if required, recording at the same time.

Is OBS Studio free?

Yes. OBS Studio is free and open-source software. Download it from the official OBS Project site; a paid relay, CDN, platform or other service may still be part of the wider delivery workflow.