To connect OBS on Windows to YouTube Live, copy the stream URL and stream key for the intended broadcast from YouTube Studio, then put each in its matching OBS field. The URL tells OBS where to send video; the key is a secret credential that lets YouTube accept it.
The steps are the same in India as elsewhere in the official guidance reviewed here: use the URL displayed in your Live Control Room rather than a server address found online. Prefer the displayed RTMPS URL when your OBS setup supports it, and test the complete path before relying on it for a scheduled broadcast.
Open the intended stream in YouTube Live Control Room
Sign in to the YouTube account that manages the channel. In YouTube Studio, choose Create > Go Live to open Live Control Room. The exact layout can change, but the job is to reach the controls for the broadcast you intend to send, not simply to find any stream key associated with the channel.
Open the Stream area. You can create a stream there or select a scheduled stream that already exists. If you have more than one event planned, check the title, schedule and other identifying details before copying anything. OBS can send a feed using valid connection details, but it cannot tell you whether you have selected the right YouTube event.
YouTube may load settings or a key used previously. That can save time, but do not assume the old details belong to the current event. Confirm the selected stream and the displayed URL before moving to OBS. YouTube’s encoder setup guide describes opening Live Control Room, selecting a stream and connecting an encoder.
If live streaming is unavailable, check channel eligibility before treating the problem as an OBS fault. YouTube’s live-streaming eligibility guidance covers account and channel conditions. Eligibility, service availability and connection quality still matter in India; none changes which fields hold the URL and key.
Find or create the stream and verify its key
In the selected stream’s settings, locate Stream key and Stream URL. The key is not the same thing as the URL. YouTube describes stream keys as being like a stream’s password and address: the key is a credential used when the encoder connects, while the URL is the destination address.
Treat the key as confidential. Do not include it in a screenshot, support post, public document or message to someone who does not manage the channel. Do not paste a real key into an article, tutorial or example. OBS needs the value in its stream-key field, but you do not need to show it to anyone to ask for help with the field layout.
A channel owner or manager can reset a key in Live Control Room. If you think it has been exposed, reset it there and update OBS with the new value before the next broadcast. A reset makes the old value unsuitable for future connections, so remember that other encoders using it will also need updating. YouTube’s stream settings help explains key management and permissions.
Before copying, check that you are looking at the key for the intended stream and not another saved configuration. If you have several channels or events, a simple private note with the event name and a reminder of where to find its settings is safer than storing the secret in a shared checklist. Do not put the key itself in that note unless you have a secure, appropriate way to protect it.
Copy the YouTube server URL and stream key
Copy the Stream URL into a temporary, private working context and copy the Stream key separately. If Live Control Room offers a lock icon beside the URL, use it to display and copy the RTMPS address. Use what YouTube displays for the selected stream; do not construct a URL from a blog post, guess a regional endpoint or substitute a value from another event.
The two values have different jobs and belong in different fields. A useful mental check is: URL equals destination, key equals credential. If you reverse them, OBS will not connect correctly. If a key is visible while you are copying, avoid screen-sharing or recording that screen, and clear any temporary clipboard or notes when you have finished.
There is no India-only server URL in the official instructions reviewed for this article. That does not mean every route or network behaves identically: your internet provider, firewall or connection quality can affect whether data reaches YouTube. It does mean the reliable starting point is the URL shown in your own Live Control Room, not a hard-coded address presented as India-specific.
If a stream is re-created, you switch to another scheduled stream, or you reset the key, copy the current pair again. A URL from one stream and key from another may look like ordinary text, but they do not necessarily form a valid pair. Keep the two values together only in a private working process while configuring the encoder.
Enter the server and key in OBS on Windows
Open OBS on the Windows computer that will send the broadcast. Go to the streaming configuration in the installed version of OBS. Labels and placement can differ between versions, so use the fields by their meaning rather than relying on a screenshot of an older interface.
If OBS offers a YouTube service or preset, select it and follow the prompts. If it asks you to sign in or connect an account, that is a separate route from manually entering the server and key. For manual configuration, choose the custom service option, place the copied YouTube Stream URL in the server field, and put the Stream key in the key field. Do not put both values in one field.
Before you save or start sending, check each field once: the server field should contain the address beginning with the protocol shown by YouTube, and the key field should contain the secret value, not a URL. Avoid reading the key aloud on a shared call or leaving OBS visible during a screen-share. You can confirm the arrangement without exposing the credential.
The OBS interface is software outside YouTube’s controls, and its exact menu names may change. If the labels differ, consult the help for the installed OBS version and look for its streaming service, server and stream-key settings. The essential mapping remains URL to server and key to stream key.
This task is only about connecting OBS. It does not require special equipment or a particular video format. If you are also preparing a continuous recorded programme, the separate guide to looping an MKV file in OBS covers a different part of the workflow: preparing the material OBS sends, rather than authenticating its connection.
Choose RTMP or RTMPS appropriately
RTMP and RTMPS are related transport choices, not two different stream keys. YouTube defines RTMPS as RTMP carried over a TLS/SSL connection and recommends it for streams to YouTube Live. If Live Control Room displays an RTMPS URL and OBS supports it, use that URL and matching configuration.
Do not type a guessed RTMPS address over the one YouTube provides. If OBS has a YouTube RTMPS preset, use it and enter the key when prompted. Otherwise, use the displayed RTMPS URL in the server field of the custom configuration. YouTube’s RTMPS instructions explain the encrypted connection and the URL selection.
A plain RTMP URL may still be available in Live Control Room. Use the actual URL and protocol you choose consistently: do not select RTMPS in one place while pasting an RTMP address, or the reverse. If your version of OBS cannot use the RTMPS address, check whether it can be updated or select an available YouTube-supported configuration rather than making up a port or host.
For a specific SSL error, YouTube says trying port 443 may help when the URL otherwise appears correct. Treat that as a troubleshooting step, not a reason to replace the displayed URL with an address found elsewhere. If you cannot identify the corresponding setting in your version of OBS, consult its current documentation rather than guessing at interface controls.
Check the stream quality before a real broadcast
The URL and key establish the connection, but they do not ensure a stable picture or sound. In OBS, check that the intended scene, source and audio are active. A connection test should use representative movement and audio: a static screen can conceal problems that appear when the full programme runs.
Choose resolution, frame rate and bitrate for the content and for an upload connection that can sustain them reliably. YouTube’s encoder guidance publishes recommended settings, but those figures are reference points, not promises about what a particular home, office or mobile connection in India can hold through a long session. YouTube can transcode incoming video for viewers, but your outgoing connection still needs to deliver a consistent feed.
For example, a quiet devotional image with modest movement may not need the same visual detail as a local news loop with text and camera footage. If you adjust quality settings, make one change at a time and observe the stream health indicator in Live Control Room. The OBS keyframe guide is useful for a related encoder setting, but keyframes do not repair a wrong URL or key.
Run a test early enough to correct configuration issues. If your event is scheduled, starting to send from OBS is not the same as making the event public. Wait for YouTube’s incoming preview and confirm the event’s state in Live Control Room before selecting Go live. At the end, follow the event controls there and stop sending from OBS so that the encoder and YouTube event are both closed as intended.
Test the connection and troubleshoot common failures
Start streaming from OBS when ready to test. Watch its status and then check Live Control Room for an incoming preview and stream-health information. If the event is scheduled, wait for the preview to arrive before choosing Go live. A preview confirms that YouTube is receiving something; review the picture and audio rather than assuming the content is correct from the connection indicator alone.
| What you see | What to check | Next step |
|---|---|---|
| No connection or a rejected feed | The selected stream, displayed URL and current key | Copy the pair again from the intended stream and update the matching OBS fields |
| RTMPS or SSL error | Whether the URL and chosen protocol both use RTMPS | Use the RTMPS URL shown in Live Control Room; if appropriate, check YouTube’s port 443 guidance |
| Connection timeout | The displayed server URL, encoder support and network path | Confirm OBS supports the selected protocol; check local network restrictions or try a reliable connection |
| OBS appears to send, but no preview appears | The event selected in Live Control Room and OBS’s sending status | Check the pair again, allow time for preview, and review stream health |
| Preview appears unstable or poor | Upload consistency, chosen output settings, audio and source activity | Reduce the quality demand if needed, then test again with representative content |
A wrong or stale key is a common configuration possibility. It may be stale because you selected a different stream or reset the key after setting up OBS. Re-copy both values rather than changing one based on memory. If a key was exposed, reset it first and enter the replacement privately.
For an RTMPS SSL error, first confirm that the server field contains the RTMPS URL and that the encoder is configured to use it. YouTube suggests trying port 443 if the URL otherwise looks right. For a timeout, recheck the displayed URL and confirm the installed encoder supports RTMPS; network filtering can also prevent a valid configuration from reaching the service.
If you can send from OBS but no preview appears, verify that Live Control Room is open to the same scheduled stream whose details you entered. A preview can take time to appear. If it remains absent, stop and recheck the URL, key and stream selection rather than repeatedly starting public events.
If the preview is present but unstable, the connection has progressed beyond basic authentication. Check the upload connection and stream-health feedback, then lower output demands or test at a more suitable resolution or frame rate. YouTube’s recommended bitrates are not a guarantee for your connection. For a broader look at the costs and operating trade-offs of a continuous broadcast in India, see what it costs to run a 24/7 YouTube stream; that is a planning question, separate from correcting OBS credentials.
If you are running an always-on channel, a different arrangement may remove the need to keep a Windows machine sending the file overnight. StreamNeo is relevant when the specific problem is leaving that computer on to keep a file-based YouTube stream running; it does not change the need to select the intended YouTube channel and protect its key.
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
Where do I find my YouTube stream key?
In YouTube Studio, choose Create > Go Live, open the intended stream in Live Control Room, and locate its Stream key. Copy the key for that stream and keep it private. If it may have been exposed, reset it and update OBS.
What server URL should I enter in OBS in India?
Use the Stream URL displayed in Live Control Room for your selected stream. The official instructions reviewed here do not identify a separate India-only endpoint, so do not substitute a hard-coded address from an unrelated source. Prefer the displayed RTMPS URL when supported.
Should I use RTMP or RTMPS?
YouTube recommends RTMPS, which encrypts the RTMP connection using TLS/SSL. Use the RTMPS URL YouTube actually displays, and make sure the OBS configuration matches it. If you encounter an SSL error, verify the protocol and consult YouTube’s current guidance before changing settings.
Why is OBS not connecting to YouTube Live?
Check that OBS has the server URL in the server field and the current key in the key field, both from the intended stream. Confirm that the selected protocol matches the URL and that your channel can live stream. Then check OBS status and Live Control Room’s preview and stream-health feedback.