In OBS’s standard YouTube setup, put the Stream URL in the Server or Server/URL field, and put the Stream Key in the separate Stream Key field. The URL is the destination for the feed; the key is a password-like credential that lets YouTube associate and accept it.
You can find both values for a stream in YouTube Studio’s Live Control Room. Copy the ingestion URL shown there, not the public watch-page address, and keep the key private. OBS labels can differ by version and service, but that basic mapping does not: destination in the server field, key in the key field.
Stream URL and stream key do different jobs
The two values are used together in the standard encoder setup, but they are not interchangeable. The Stream URL tells OBS where to send its outgoing video and audio. The Stream Key identifies or authorises the feed for the selected YouTube stream. YouTube describes stream keys as password-like; treat yours as a credential, not as a public link.
A useful way to remember the fields is to ask two questions. “Where should OBS send this feed?” The answer is the Stream URL, entered as the server destination. “Which YouTube stream should receive it?” The answer is the Stream Key, entered in its dedicated field. If you paste the key into Server, OBS has not been given the destination in the expected field. If you paste the URL into Stream Key, the credential field contains the wrong kind of value.
The URL you need is an ingestion address supplied for streaming software. It is not the link that viewers open to watch the broadcast. The watch-page address is for sharing and viewing; it does not tell an encoder where to send a live feed. YouTube’s live encoder setup instructions show the stream URL and key as distinct pieces of setup information.
This distinction matters whether you are sending a bhajan programme, a local news loop, a study stream or a live camera feed. The content changes, but the standard OBS field mapping does not. An HLS workflow is a protocol-specific exception: YouTube’s HLS guidance notes that its ingestion URL can include the key. Follow the instructions for that selected protocol rather than assuming every setup needs the same separate-field handling. For the usual YouTube preset or RTMP-style arrangement, keep the URL and key separate.
Find the values in Live Control Room
Open YouTube Studio and go to the Live Control Room for the stream you intend to send to. Select the relevant stream or scheduled event, then locate the encoder setup details. YouTube presents the Stream URL and Stream Key there. The exact controls or page arrangement can change, so use the current instructions in YouTube Help on managing live stream settings if your screen differs.
Before copying anything, check that you are looking at the correct channel and the intended stream. A channel with several scheduled events can have multiple entries, and copying values from one while preparing another creates a mismatch. Keep the Live Control Room open while configuring OBS so you can compare the selected stream and the values you copied.
Copy the Stream URL as a whole into a temporary place only if you need it to move between windows; avoid pasting credentials into shared notes or a public document. Then copy the Stream Key separately. If the interface offers a copy control, use it rather than retyping a long value. A missing character, extra space or copied line break can prevent OBS from connecting even though the values look plausible at a glance.
Do not use the browser address bar as a substitute for either value. A URL beginning with the YouTube watch-page route is for viewers, not the encoder. Similarly, the channel name, event title or video ID is not the Stream Key. If you are unsure, return to the encoder setup details in Live Control Room and use the labels there.
If you are preparing an always-on video loop, first make sure the stream destination and the content workflow are understood separately. For example, setting up VLC as a source for an always-on YouTube stream concerns what OBS or another workflow sends as programme content; it does not change which value belongs in Server. Keeping the content source separate from YouTube’s ingest credentials makes troubleshooting easier.
Choose YouTube or a matching custom service in OBS
In OBS, open the stream settings and select YouTube if it is available as a service. Depending on your OBS version and the connection method, the service may offer an account sign-in flow or fields for the server and stream key. If you are using the standard two-field configuration, make sure you can see both the destination field and the separate key field before you paste values.
Some workflows use a custom service instead. Choose that only when the service and protocol settings match the instructions for the YouTube ingest method you are using. A custom service is not a reason to put the key into the URL field or to guess at a server address. Use the exact Stream URL supplied by Live Control Room, and use the matching protocol or preset specified by YouTube for your chosen configuration.
OBS versions and service presets do not always show identical labels. One version may say “Server”; another may say “Server/URL”. A service can also hide or preconfigure some connection details. Read the field labels on your screen and map by function: the field for the server destination takes the Stream URL; the field explicitly for Stream Key takes the key. Do not infer that a field is the key field merely because it contains a long string.
For the standard configuration, avoid mixing a URL from one event with a key from another. If you change the selected YouTube stream in Live Control Room, review both values again in OBS. This is especially useful when you prepare a channel in advance and later reuse an OBS profile. A profile can retain yesterday’s values; it cannot tell you whether those values still correspond to the stream you mean to start.
Put the Stream URL in Server or Server/URL
In OBS’s standard setup, paste the YouTube Stream URL into Server or Server/URL. This is the destination field. Use the ingestion URL copied from the Live Control Room, exactly as supplied, rather than typing an address from memory or using the public watch-page link.
If OBS shows a server and a separate stream key field, keep them separate. Do not append the key to the server address as a workaround, and do not replace the address with the key. The URL and key have distinct roles in this setup. If OBS’s YouTube preset manages the destination automatically, follow the preset’s visible flow instead of forcing a manual custom-server arrangement.
A practical check is to compare the value you are about to paste with the label beside it in YouTube Studio. “Stream URL” belongs in Server. The word “URL” in an OBS label is a clue that it wants a destination address, not the credential. Do not judge by length alone: both values can look like long strings, and visual similarity is not a reliable way to tell them apart.
If you are setting up a loop that needs to run for a long time, keep a note of which OBS profile is tied to which YouTube channel or stream, but do not save the secret in a place accessible to others. Readers considering a machine-based arrangement may find how to stream pre-recorded videos on YouTube 24/7 from a VPS useful for the broader operating choices. That is a separate decision from field mapping: even when the encoder environment changes, the ingest URL and key still need to be handled according to the selected protocol.
Put the Stream Key in its own field
Paste the YouTube Stream Key into OBS’s Stream Key field in the standard configuration. Do not paste it into Server or Server/URL. Treat it like a password: anyone with access to it may be able to send a feed using that key, so share it only with people who need to configure the encoder and can handle it securely.
If OBS masks the value with dots, that is normal. Avoid revealing it on a screen share, in a screenshot, or in a tutorial recording. If you need help diagnosing the setup, describe the field labels and error message rather than sending someone the key. A troubleshooting conversation should not require disclosure of the credential.
YouTube may allow stream key management or selection in Live Control Room. If you use a reusable key, take care not to confuse convenience with safety: anyone who can access the key can potentially use it. If the key is exposed, or you suspect someone else has seen it, reset it in YouTube and replace the saved value in OBS. YouTube’s guidance on stream settings is the place to check the current controls.
An OBS update or profile change can sometimes make a previously entered key appear missing, or leave you uncertain which profile contains it. Do not copy a key from an old message without checking the active stream. First confirm the selected YouTube event, then retrieve its current values and enter them into the relevant OBS fields. If the problem is specifically that the key disappeared after an update, see how to restore a YouTube Stream Key in OBS.
Keep the stream key private
The key is not a viewer-facing address. Do not put it in a video description, public post, shared spreadsheet, support forum or unredacted screenshot. If a colleague needs to configure OBS, pass it through a private channel and remove it from temporary notes afterwards. Limit access to the people responsible for operating the stream.
Check screenshots before sending them to a group chat or posting them for support. OBS may mask the key, but a settings dialog, copied clipboard text or browser panel can expose more than intended. When asking for help, crop or obscure credentials and include only the non-sensitive details needed to identify the issue, such as whether you selected YouTube or a custom service and which field label you see.
If you believe the key has leaked, do not rely on deleting the message alone. Reset or replace the key in YouTube’s Live Control Room, then update OBS and any other encoder that legitimately uses it. Confirm that old copies are no longer being used. A reset can interrupt an encoder still using the former value, so coordinate the change with anyone operating the stream.
For a 24/7 channel, credentials also have an operational aspect. A key should be available to the authorised encoder, but not casually available to every person who can view the channel’s content calendar. If your setup depends on a local computer staying on all night, that is a separate reliability concern from keeping the key safe. A cloud workflow that takes an uploaded video and runs the broadcast without your computer can remove the need to leave a home machine running; StreamNeo addresses that particular always-on operating burden. It does not change the need to use the correct YouTube stream credentials or to protect them.
Test the encoder connection before going live
After entering the values, save the OBS settings and start the encoder output when you are ready to test. Then look at the Live Control Room for the selected stream and confirm that YouTube receives the feed and displays a preview. Seeing OBS report that it is attempting to connect is not by itself proof that the intended YouTube stream is receiving the programme.
Before taking a scheduled event live, check that the preview is the expected content and that the selected event is the one you intended. This catches both credential mismatches and source mistakes. For a music stream, for example, make sure the correct loop is visible or audible in the preview; for a news loop, confirm the current version is being sent. A technical connection can succeed while the wrong scene or file is on air.
If OBS connects but YouTube does not show an incoming feed, check the values in order. Confirm that OBS is pointed at the intended service and protocol; compare the Server/URL field with the Stream URL for the selected stream; compare the Stream Key field with that stream’s key. Check for leading or trailing spaces, stale profiles and accidental use of the watch-page link. If you use HLS, use the HLS-specific URL and key handling rather than assuming the standard two-field behaviour applies.
If the preview appears but the event does not proceed as expected, do not immediately change both fields at once. Check the Live Control Room status and the stream’s scheduled or live state, then make one change at a time. That gives you a clearer record of what fixed the issue. For a more deliberate pre-flight process, testing a 24/7 Indian music YouTube stream before going live offers a broader checklist beyond these two OBS fields.
When the connection is confirmed, record the non-secret parts of the setup: the OBS profile name, intended channel, chosen service and protocol, and where the current values can be retrieved. Do not record the key in a public runbook. If another operator takes over later, they should know how to retrieve the current key securely rather than relying on an old copied value.
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
Which value goes in the OBS Server field?
Put YouTube’s Stream URL in Server or Server/URL. It is the ingestion destination for the encoder, not the public watch-page link. Put the Stream Key in its separate field for the standard setup.
Is the stream key the same as the stream URL?
No. The URL tells OBS where to send the feed, while the key is a password-like credential associated with the stream. Do not swap them or treat the key as a server address.
What if my OBS version has different field names?
Labels vary by OBS version, preset and protocol. Identify the field that accepts the server destination and use it for the Stream URL; use the separate Stream Key field for the key in the standard configuration. If you selected HLS, follow YouTube’s HLS-specific instructions because the URL may include the key.
What should I do if someone sees my stream key?
Reset or replace it in YouTube’s Live Control Room, then update the authorised encoder with the new value. Check any other legitimate encoder that uses the old key and avoid sharing the replacement in screenshots or public notes.