OBS Studio, short for Open Broadcaster Software Studio, is a free and open-source application for live streaming and screen recording that combines cameras, game capture, windows, images and audio into a single composited video output. In live streaming, it is the most widely used broadcasting tool among independent creators, and many commercial streaming apps are built on its code.
OBS Studio runs on Windows, macOS and Linux and is released under the GNU General Public License. It sends its output to platforms such as Twitch, YouTube and Kick, records to local files or feeds other software through a virtual camera. Its appeal lies in professional control at no cost: the creator decides every layout, encoder setting and audio filter.
How OBS Studio composes a broadcast
OBS Studio organizes a broadcast into scenes and sources. A source is one input, such as a webcam, a game, a browser page or a microphone, and a scene is a saved arrangement of sources with positions, sizes and layering. During a stream the creator switches between scenes, for example from a starting screen to gameplay to a break screen.
Every frame is rendered on the graphics card, scaled to the output resolution and passed to an encoder. Audio from all sources runs through the audio mixer, where each track has its own volume, monitoring and filters such as noise suppression, a noise gate or a compressor. The encoded audio and video are then sent to a streaming server, written to a file, or both.
The following table summarizes the building blocks that appear in almost every OBS Studio setup.
| Element | Function | Typical example |
|---|---|---|
| Source | A single video or audio input | Webcam, game capture, microphone |
| Scene | A saved layout of sources | Gameplay, just chatting, intermission |
| Filter | Processing applied to a source | Chroma key, noise suppression |
| Transition | Effect between scenes | Cut, fade, stinger animation |
| Audio mixer | Level control for every audio track | Separate game and voice levels |
| Studio Mode | Preview a scene before it goes live | Prepare changes off-air |
Encoding and output settings
The quality of an OBS Studio stream depends mainly on the encoder, bitrate, resolution and frame rate. OBS supports software encoding with x264 and hardware encoders from NVIDIA, AMD, Intel and Apple, with H.264, HEVC and AV1 available depending on the hardware and destination platform.
| Parameter | Typical value | What it affects |
|---|---|---|
| Encoder | Hardware NVENC, AMF, Quick Sync or x264 | CPU or GPU load and efficiency |
| Rate control | CBR for streaming, CQP or CRF for recording | Bitrate stability versus constant quality |
| Video bitrate | 3,000 to 6,000 kbps for 720p or 1080p streams | Sharpness and upload demand |
| Keyframe interval | 2 seconds | Platform compatibility |
| Output resolution | 1280×720 to 1920×1080 | Detail and bitrate efficiency |
| Frame rate | 30 or 60 fps | Motion smoothness |
A practical rule is to stream with constant bitrate (CBR), which ingest servers expect, and to record locally with a quality-based mode at a much higher bitrate. Recording to MKV or hybrid MP4 protects the file if the application or computer crashes, whereas a classic MP4 can become unreadable when writing is interrupted.
OBS Studio compared with other streaming software
OBS Studio competes with tools that trade some control for convenience. Streamlabs Desktop, for example, is built on OBS code but adds integrated alerts, themes and paid features, while hardware switchers and professional suites target studio production.
| Tool | Cost model | Strength | Trade-off |
|---|---|---|---|
| OBS Studio | Free, open source | Full control, plugin ecosystem | Manual setup and learning curve |
| Streamlabs Desktop | Free with paid tier | Built-in alerts and themes | Higher resource use, upsells |
| Professional production suites | Paid license | Multi-camera and broadcast features | Cost and hardware demands |
| Browser studios | Subscription | Easy guests and multistreaming | Less control, cloud dependency |
Because OBS Studio does not include alerts or chat widgets natively, creators add them as browser sources that load pages from alert and overlay services. This modular approach keeps the core application lean while letting each creator choose their own services.
Plugins, protocols and integrations
OBS Studio is extensible through plugins and scripting in Lua and Python. The obs-websocket interface, included in recent versions, lets external devices and apps control scenes, sources and recording, which is how stream decks and automation tools integrate.
- RTMP and RTMPS remain the standard way to send a stream to most platforms.
- SRT offers better resilience on unstable networks, which helps IRL streaming and remote contributors.
- WHIP, based on WebRTC, supports very low-latency delivery to compatible services.
- Multistreaming plugins send one broadcast to several platforms when upload bandwidth allows it.
Plugins should be installed only from trusted sources and checked after each OBS update, since an outdated plugin is a common cause of crashes at startup.
Common problems and how to fix them
Most OBS Studio problems fall into three categories: network limits, encoding overload and rendering lag. The statistics window distinguishes them, which is the first place to look before changing settings.
| Symptom | Likely cause | Fix |
|---|---|---|
| Dropped frames | Upload too slow or unstable | Lower bitrate or use wired connection |
| Skipped frames from encoding | Encoder overloaded | Use hardware encoder or faster preset |
| Frames missed due to rendering lag | GPU fully used by the game | Cap game frame rate, simplify scenes |
| Audio out of sync | Device latency differences | Set sync offset on the audio source |
| Black game capture | Wrong capture mode or permissions | Use window or display capture, run as needed |
A test recording of a few minutes before every important broadcast catches most issues, because it uses the same encoder settings without any audience watching.
A plain-language summary
OBS Studio is a free program that works like a small television control room on a computer. It takes the webcam, the game or screen, the microphone and any pictures, and arranges them into one picture.
That picture is then sent live to sites such as Twitch or YouTube, or saved as a video file. The creator can switch between prepared layouts with one click. It costs nothing and gives full control, which is why so many streamers start with it.
An example from practice
A secondary school teacher runs a weekly live coding lesson for students at home. In OBS Studio she builds three scenes: a full-screen code editor with her webcam in a corner, a whiteboard camera view and a break screen with a countdown.
She streams at 1280×720, 30 fps and 3,000 kbps using the hardware encoder, because her laptop’s processor also has to run the development tools. A noise suppression filter removes fan noise, and she records a local MKV copy at higher quality at the same time.
After the lesson she converts the recording to MP4 and uploads it for students who missed the session. The same setup is reused every week with no software cost, and students report that the clear separation between code and whiteboard views makes the lessons easier to follow.