What does a small tournament broadcast actually need?
A small tournament broadcast needs four things: a clean picture of the match, voices explaining it, a few graphics that tell viewers who is playing, and somewhere to send it all. Everything meets on one computer we will call the production PC -- the machine that runs OBS Studio, mixes sound and pushes the stream out.
- The game feed. Either a spectator seat in the match (many competitive games let an extra player join a custom lobby as an observer) or the video output of a player's machine through a capture card.
- Casters. One or two people with headsets or microphones, ideally sitting in a quieter corner than the players.
- Graphics. Team names, the score, the bracket and a few holding screens for breaks.
- A destination. A live channel with a player your audience can open in a browser.
Before you announce anything, read the game publisher's rules for community events and broadcasts. Publishers set their own terms for tournaments and for showing their game, and they differ from title to title.
Getting the match picture into OBS
The simplest reliable feed is an observer client: a spare copy of the game, logged in as a spectator, running on the production PC itself. On Windows, OBS's Game Capture source grabs that game directly, and its documentation calls it the most efficient way to capture a game. It offers three modes -- Capture any fullscreen application, Capture specific window and Capture foreground window with hotkey -- the last one helps when you change games between rounds.
If your game has no spectator mode, run a capture card from a player's or observer's computer and add it in OBS as a Video Capture Device, the same source type used for webcams. On macOS, Game Capture does not exist; OBS points Mac users to macOS Screen Capture or Display Capture instead.
A fullscreen game stops drawing when someone alt-tabs out of it, so the feed freezes in OBS. Whoever runs the observer seat should stay in the game while it is on air.
Building your scenes before match day
Build a small set of scenes the evening before, so on the day you only switch between them. A scene in OBS is one complete screen layout; a source is one thing inside it, such as the game, a webcam or a picture. Here is a running order that covers most community events:
| Scene | What is in it | When it is on air |
|---|---|---|
| Starting soon | Logo, event name, start time, quiet music | Before the first match |
| Casters | Webcam of the casters, team names | Previews and post-match talk |
| Match | Game feed full screen, scoreboard strip, small caster camera | During play |
| Bracket | The bracket page, next match | Between matches |
| Break | Holding image, sponsor thank-yous | Pauses and technical trouble |
- Click + under Scenes and create each scene from the table, named as you will say it out loud.
- In the Match scene, add your game feed, select it and use Edit -> Transform -> Fit to Screen so it fills the frame.
- Add the caster webcam as a Video Capture Device, then in Edit Transform set Bounding Box Type to Maximum size only and park it in a corner that hides no part of the game's own interface (minimap, timers, health bars).
- Add a Text source for the score. OBS can read its text from a file, so keep a plain text file with the score in it and edit that file between rounds; the overlay updates without touching the scene.
- For the Bracket scene, add a Browser source with the address of your bracket page, set Width and Height to your canvas size, and tick Refresh browser source when scene becomes active so it shows the latest results every time you cut to it.
- Press each scene in turn. You should see every layout complete, with nothing cropped and no black boxes.
Will the casters be heard over the game?
They will if you set the levels in the Audio Mixer before the doors open. OBS's own guidance is to keep speech in the upper part of the yellow zone of the meter, gameplay sound toward the lower end of yellow, and music and alerts in the green. The Peak marker shows the loudest moment of the last 20 seconds, which is how you catch a caster who shouts every time someone scores.
- Give each caster microphone its own source, so one can be muted without silencing the other.
- Add a Compressor filter to the game audio with ducking turned on and the casters as the trigger: the game drops a little whenever someone speaks and comes back when they stop.
- Use the monitor button (set up under Edit -> Advanced Audio Properties) so the person running OBS hears the mix through headphones, not the hall speakers.
Keep the venue's speakers and the players' headsets away from the caster microphones. Players hearing the casters, or casters hearing the room, is how a stream ends up with echoes and spoiled strategy.
Switching live without mistakes
Turn on Studio Mode and you get two screens: the right one is what viewers see, and the left one is the next scene you are preparing. You change the score, reposition a camera or load the bracket on the left, then press Transition to send it live. Viewers cannot tell Studio Mode is on; they only see clean cuts.
Set a short Fade as your default transition and keep Cut for instant replays or emergencies. You can add both as Quick Transitions and bind hotkeys to them, so the producer never has to hunt for a button while a round is ending.
If players in the same room can see the stream, they could watch it to spy on opponents. OBS can hold the stream back by a set number of seconds as an extra precaution, but remember that the viewers' feed already runs behind the live game, so the venue screens should show the observer client, not the stream.
Sending it to a page your community can open
With a live video channel, OBS sends the finished picture over RTMP -- the standard way an encoder hands video to a streaming server -- and viewers get an HLS link and an embeddable player with no ads that plays on phones, tablets, computers and smart TVs. Nobody needs an app to watch.
| Your event | Plan that fits | Why |
|---|---|---|
| Rehearsal the week before | Free | One channel for up to 10 viewers at a time: enough to check picture, sound and the player with your crew |
| One match on air at a time | Pro | One channel at up to 1080p and 5 Mbps, 1,000 viewers at once, traffic not counted |
| Two matches in parallel, or a backup feed | Platinum | Two channels at 5 Mbps each, and each viewer is served by whichever of five CDN cities is closest |
Bitrate -- how much data per second the stream uses -- is limited by your venue's upload, not just the plan. Measure the line where the production PC will sit, using our guide to upload speed for live streaming, and if OBS starts skipping frames mid-event, our dropped-frames guide helps you find out why.
Want a tournament home page with the schedule, rules and the player in one place? Put the embed on a site on our web hosting under a name from our domain search, and every event after this one has the same address.
After the final: replays and the next event
Live broadcasts are not saved into your channel's video library, so press Start Recording in OBS alongside Start Streaming and keep a copy on the production PC. Afterwards, upload the grand final and the closest matches to the library -- 50 GB on Pro, 200 GB on Platinum -- and the 24/7 TV station plays them between live events, so the channel keeps showing your tournament when nobody is broadcasting.
When this setup is not enough
A single production PC with one observer seat suits a club night, a school league or a weekend LAN. It is the wrong tool for a large event that shows several player cameras, instant replays from multiple angles and many matches at once; those need a dedicated crew and more machines. A channel takes up to 1080p, so a 4K or high-frame-rate showcase is beyond it, and an audience of more than 1,000 at the same moment is beyond the plans above.