OBS Studio builds the video and audio programme you send to YouTube Live. For a reliable first broadcast, install OBS from the official project, use its Auto-Configuration Wizard as a starting point, assemble and check your scene, connect it to a YouTube encoder stream, then verify the incoming preview before you go live.
A successful connection in OBS is not the same as a ready broadcast. Test with the actual sources and sound you plan to use, check YouTube’s stream health, and keep an eye on both audio and video while the event is running.
Install OBS from the official project
Download OBS Studio from the official OBS Project download page and choose the installer for your operating system. Avoid download mirrors or links in old tutorials: the official project page is the straightforward place to get the current release. Follow the installer prompts, then open OBS and allow it the permissions your operating system requests for screen, camera, or microphone capture.
On first launch, OBS may offer to run its Auto-Configuration Wizard. If it does not, you can start it from Tools → Auto-Configuration Wizard. Do not worry if the interface looks busy at first. The main areas you will use are the preview, the Scenes dock, the Sources dock, the Audio Mixer, and the controls for starting and stopping a stream.
You do not need to buy a dedicated camera, microphone, capture card, or hardware encoder just to begin. A laptop camera and built-in microphone may be enough for a simple talking-head broadcast, while a devotional channel might use a still image and an audio source. Add equipment only where it improves the programme you are actually making.
OBS has to compose your scene and encode it on the computer that is running it. Its system requirements and performance notes are useful to check, but compatible hardware alone does not promise a smooth stream. Output resolution, frame rate, scene complexity, selected encoder, and other activity on the computer all matter. If you are planning an overnight broadcast from an older laptop, try a representative test before relying on it; this guide to keeping a stream running on an old Windows PC covers the separate question of long-running computer use.
Run the Auto-Configuration Wizard
The wizard asks how you intend to use OBS and considers the computer and network conditions it can assess. Choose the option for streaming, then follow its prompts. Treat the suggested settings as an initial configuration, not a verdict that your computer or internet connection can carry the whole event.
The output choice is a trade-off. Higher resolution can show more detail, and a higher frame rate can make fast movement look smoother, but either can increase the work for the encoder and the demands on the upload connection. For a speaker, aarti, lofi image, or news loop with little movement, a modest starting configuration may be more practical than aiming for the largest numbers available. For fast gameplay or sport, motion may make a higher frame rate useful, if the computer and connection handle it.
Do not copy settings just because another creator reports that they work. A household connection may be shared with other devices, and the upload available to your computer can vary. YouTube advises leaving 20% of upload bandwidth as room in its live streaming tips; that is headroom, not an additional bitrate to spend. If others in the home are uploading files or making video calls, the connection available to OBS may be less steady.
If you want to adjust output after the wizard, make one change at a time and retest. Lowering resolution or frame rate can reduce both encoding work and the required bitrate, though it changes the look of the broadcast. The wizard gives you a place to start; a test with your real scene tells you whether that choice is workable.
Create a scene and add sources
A scene is the arrangement OBS sends as your programme. OBS opens with a blank scene. In the Scenes dock, select or rename a scene for the job, then use the plus button in the Sources dock to add what belongs in it. The source options depend on what you are capturing and your operating system: common examples include a display or window, a game capture on Windows, a camera, an image, or text.
For a simple presentation, you might use a window capture for your slides and a small camera view. For a music or devotional stream, the scene might contain a background image and an audio source. These are starting examples, not required layouts. Check that you have permission to broadcast any music, footage, or images you include; a technically working scene does not answer rights or YouTube policy questions.
Look at the OBS preview as you arrange the sources. The order in the Sources dock matters: an item higher in the stack can cover items below it. If a camera disappears behind a background, move it above the background. Select a source to adjust its size and position, and check that text, logos, or other important content are not clipped at the edge of the frame.
Keep the first scene simple enough to diagnose. Every extra source is another possible point of failure or distraction. A browser page might change unexpectedly, a window can be minimised, and a camera can be disconnected. If the scene is intended to run unattended for a time, consider what viewers will see if a changing source stops updating.
Before connecting to YouTube, check what appears in the preview when you switch between scenes and sources. Confirm that the intended display or window is being captured, rather than a private message or the wrong monitor. For more context on choosing between a computer-based setup and other approaches for a long-running radio stream, see this overview of free software for a 24/7 YouTube radio stream.
Check microphone and desktop audio
The Audio Mixer shows the audio channels OBS is receiving. Speak into the microphone you intend to use and play the sound that should reach viewers. Watch the meters for movement. If they remain still, OBS may be listening to a different device, or the source may not be active.
OBS commonly starts with desktop audio and microphone input configured, but defaults are not proof that the right devices were selected. If a meter does not respond as expected, open Settings → Audio and check the device choices. Select the microphone you are actually using, and confirm whether desktop audio should be included. If the programme is meant to be music only, an unwanted open microphone can introduce room noise; if it is a talk, a muted microphone can make the broadcast appear normal while leaving viewers with no speech.
Meters show that sound is reaching OBS, not that the final mix is pleasant or correctly balanced. Make a short recording or a private/unlisted test and listen back on headphones or another device. Check for speech that is too quiet, music masking a speaker, clipping or crackling, and audio arriving noticeably ahead of or behind the picture. Adjust one source at a time and listen again.
For a live event, decide in advance what should happen when you are not speaking. You may want low background music, silence, or the programme’s normal audio. Check that choice in the test rather than relying on the meter alone. If you are troubleshooting a channel that relies on a steady prerecorded feed, this guide to why a YouTube stream may not start from OBS on an India network may help separate a local audio or scene issue from a connection problem.
Set up an encoder stream in YouTube Studio
Open YouTube Studio and go to Go Live to create or select an encoder stream in Live Control Room. An encoder stream is the route for software such as OBS to send its video and audio to YouTube. Follow the current YouTube interface to prepare the event and locate the stream connection details. YouTube’s instructions for creating a live stream with an encoder explain this flow.
YouTube provides a stream URL and a stream key. The URL is the destination; the key identifies the stream connection. Treat the key like a password. Do not put it in a scene, show it in a screen recording, post it in a chat, or send it to someone who does not need access. If you think it has been exposed, reset it in Live Control Room and update OBS with the replacement.
Use the URL and key shown for the stream you are preparing, rather than copying an address from a video or an unrelated setup guide. YouTube recommends RTMPS where the encoder supports it. The Live Control Room and the current OBS choices should guide which server address and preset to use; do not assume that an old tutorial’s menu labels or server details still match your screen.
Before moving on, check that you have selected the intended event in YouTube Studio. A stream sent to a different scheduled event may not appear where your viewers expect it. If you are unsure, pause and verify the event title and visibility settings before sending a feed.
Enter the URL and stream key in OBS
In OBS, open Settings → Stream. If YouTube is available as a service preset, select it and enter the stream key in the field provided. If OBS asks for a server, use the URL shown by YouTube’s Live Control Room. The exact controls can vary between software versions, so follow the labels you see rather than a screenshot from an older release.
Copy the key carefully, taking care not to include extra spaces. Do not read it aloud during a stream or leave it visible while sharing your screen. If you use a key again for a later broadcast, first confirm that it still belongs to the intended stream and has not been reset. YouTube documents how to view and reset a stream key.
If the OBS connection does not work, check the destination URL and key before changing several output settings. Confirm that you are looking at the right event in Live Control Room, then copy the current details again if needed. Also check whether your network blocks or interrupts the connection. Make one correction, try the connection again, and note any message shown by OBS or YouTube; changing many settings at once makes the cause harder to identify.
Preview, test, and go live
Start by sending a test feed from OBS, not by announcing the event to viewers. Once OBS begins transmitting, wait for the incoming preview to appear in Live Control Room. Inspect the picture and listen to the sound if the interface offers a preview. A moving OBS status indicator by itself does not confirm that YouTube has received the programme correctly.
Use a representative test, not just a static opening frame. Speak at normal volume, play the intended music or desktop sound, switch any scenes you plan to use, and include the kind of movement the event will contain. Check the picture crop, source order, text, and audio mix. Review YouTube’s stream-health messages and resolve warnings that you can identify before you invite viewers. YouTube’s encoder settings and recommendations describe the available settings and its guidance for stream health.
Bitrate is the amount of video data sent each second, and the suitable rate depends on codec, resolution, and frame rate. YouTube’s current H.264 recommendations include the examples below. They are reference points, not a promise that a particular setting will work on your connection or a reason to choose the highest value. The same YouTube table gives different recommendations for other codecs.
| H.264 example from YouTube’s recommended-bitrate table | Recommended video bitrate |
|---|---|
| 720p at 30 fps | 8 Mbps |
| 720p at 60 fps | 8 Mbps |
| 1080p at 30 fps | 14 Mbps |
| 1080p at 60 fps | 17 Mbps |
Check YouTube’s current bitrate and encoder settings page before choosing settings, because its guidance may change. Use an upload speed test and leave room for changes in a shared connection. If health warnings point to an unstable feed, test a lower output resolution or frame rate, reduce other activity on the network, or simplify the scene. A setting that looks sharper in the preview is not useful if the connection cannot sustain it.
When the preview and health checks look acceptable, click Go live in Live Control Room to make the event live. Keep OBS and Live Control Room available during the broadcast. Watch for audio meters that stop moving, a frozen or missing source, and health messages from YouTube. A healthy test does not remove the need to monitor the actual event; conditions can change after it begins.
If your aim is a fixed video running continuously rather than a programme you compose and operate in OBS, the workflow is different: your own computer does not need to stay on when the file and channel are ready in StreamNeo. For a manual OBS broadcast, keep control of the scene and monitor it for as long as you are sending the feed.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I use OBS to stream on YouTube?
Install OBS, prepare a scene and audio, then create or select an encoder stream in YouTube Studio. Enter YouTube’s stream URL and key in OBS, send a test feed, check the preview and stream health, and only then click Go live.
Where do I put my YouTube stream key in OBS?
Open Settings → Stream and select YouTube or the server option shown by your OBS version. Paste the key from the correct YouTube Live Control Room event, keep it private, and reset it in YouTube if you believe it has been exposed.
What bitrate should I use for YouTube Live?
It depends on the codec, resolution, frame rate, and the upload connection available to your computer. Use YouTube’s current encoder table as a reference, choose a rate your connection can sustain with headroom, and test the actual scene before going live.
Do I need a webcam or microphone to stream?
No. OBS can send a scene made from other sources, such as a screen, image, or text, and you can leave out camera or microphone inputs if the programme does not need them. If you do use audio or a camera, test what viewers will receive rather than assuming the selected source is working.