RTMP is a protocol an encoder can use to send a live feed to YouTube. In Live Control Room, copy the stream URL into the encoder’s server or URL field, then copy the stream key into its separate key field.
The URL identifies YouTube’s ingestion address for that stream; the key identifies the stream you are authorised to send. They are different values, and entering them in the wrong fields will not be fixed by choosing RTMP or RTMPS alone.
What RTMP means for a YouTube stream
RTMP stands for Real-Time Messaging Protocol. For a YouTube live broadcast, think of it as the method by which an encoder sends video and audio to YouTube’s receiving service. The encoder is the sending end; YouTube’s Live Control Room is where you prepare and manage the destination.
The term can sound as though it names one particular URL, but RTMP is the protocol, not the credential. YouTube supplies a stream URL and a stream key for the stream you create. Your encoder uses both, in the relevant fields, to send the feed to the intended YouTube broadcast.
You may encounter RTMP in a software encoder, a hardware encoder, or a YouTube preset within an encoder. A preset can populate settings for you, but it does not remove the need to verify which stream details are selected. If you are setting up a scheduled devotional channel, for instance, check that the encoder is pointed at the scheduled broadcast you intend to start, not an older stream.
YouTube’s encoder setup instructions describe copying the stream URL and stream key into their corresponding encoder settings. Your particular encoder may use labels such as “Server”, “URL”, “RTMP server”, or “Stream key”. Labels vary; the separate purposes do not.
RTMP URL and stream key have separate jobs
The stream URL tells the encoder where to send the feed. The key tells YouTube which stream the feed belongs to and serves as a credential. In practical terms, treat the URL as the destination address and the key as the secret that authorises the connection.
| Value | What it does | Typical encoder field | Handling |
|---|---|---|---|
| Stream URL | Identifies the YouTube ingestion address | Server, URL, or RTMP server | Copy from the intended stream’s settings |
| Stream key | Identifies and authorises the stream | Stream key or key | Keep private; do not publish or send casually |
Do not paste the key into the URL field simply because an encoder labels that field “RTMP URL”. Likewise, do not place the URL in the key field. If your encoder presents one combined connection field rather than separate fields, consult that encoder’s instructions: some workflows require the address and stream name or key to be composed in a particular way. Do not guess a format from another application.
Google’s LiveStreams API documentation exposes ingestion information for a particular live-stream resource, including addresses and stream name details. That is why an example URL found in a forum or old guide should not be treated as your universal address. Use what YouTube shows for the stream you are configuring.
Find the stream details in Live Control Room
Open YouTube Studio and go to Live Control Room. Create a new stream or open the scheduled stream you intend to use, then locate its stream settings. YouTube’s labels may change, but look for the values called “Stream URL” and “Stream key”. The details shown for the selected broadcast are the ones to copy into the encoder.
Before copying anything, check the stream title and schedule. If you maintain several loops—perhaps a local news bulletin by day and a music stream overnight—an old key or URL from another broadcast can point your encoder at the wrong setup. Re-open the intended stream in Live Control Room rather than relying on notes that have been sitting beside the encoder for months.
YouTube may let you reuse a stream key, but that convenience does not make it harmless to share. For a first setup, the safest practical approach is to copy the displayed values afresh and verify each encoder field. YouTube’s live stream settings help explains the stream URL and key settings as part of managing a live stream.
Keep the Live Control Room tab available while configuring. When the encoder starts sending, the control room can show a preview or connection state. The stream is not necessarily public just because the encoder has begun sending: for a scheduled broadcast, follow the on-screen steps in YouTube, including starting the broadcast when prompted.
Copy the URL into the encoder server field
In the encoder, find the field named “Server”, “URL”, “RTMP server”, or something similar. Paste the YouTube stream URL there. If the encoder offers a YouTube preset, choose it only if the resulting settings still let you verify the correct stream destination and key. A preset is a shortcut, not evidence that the values match the broadcast currently open in Live Control Room.
Check for accidental whitespace before or after the pasted value. Avoid adding punctuation, a key, or an extra path unless YouTube or your encoder explicitly tells you to. The server field is for the address YouTube provides, while the key field remains separate in the ordinary two-field workflow.
Some encoder interfaces have options for a primary and backup address, or ask for a stream name as well as a server. YouTube’s API describes primary and backup ingestion addresses, but those are configuration options for supported workflows, not a requirement for every creator. If the software asks for an additional value, use its documentation and the data shown for your stream rather than improvising a combined address.
Now check the selected protocol and destination. If you have copied a regular RTMP URL, use the matching RTMP option. If you have chosen RTMPS, use the RTMPS URL and an encoder that supports it. A URL alone does not ensure that every other encoder setting—such as video format, audio, network access, or stream state—is correct.
If a test feed does not appear, revisit the destination before changing unrelated settings. Confirm that the encoder is sending to the intended URL, then check the key independently. For broader reliability work after connection details are correct, see why a 24/7 stream may keep buffering and how to keep video quality consistent across a 24/7 playlist.
Enter the stream key separately
Copy the key from the same stream settings page and paste it into the encoder’s “Stream key” field. If the key is hidden, use YouTube’s reveal control before copying. Avoid typing it from memory: a missed character can prevent the encoder from authenticating, while a stale key may belong to a different setup.
If the encoder has a “Use authentication” or similar toggle, do not assume it replaces YouTube’s stream key field. Follow the encoder’s YouTube-specific instructions. Some products label the key field differently or bundle a preset with a key entry step, but you should still be able to identify which setting contains the credential.
After saving, compare the first and last few characters of the key with the value you copied, if the interface permits. Do not take a screenshot that exposes the full key for a public help request. If you share a troubleshooting image, obscure the key and any other credential first.
Send the stream from the encoder and check Live Control Room for an incoming preview. If YouTube does not show the expected preview, pause and verify that the URL and key were copied from the intended stream and placed in their matching fields. Changing bitrate or resolution before checking that distinction can send you down the wrong troubleshooting path.
For a continuous prerecorded channel, encoder configuration is only one part of keeping the broadcast available. If your chosen local workflow can stop when a process exits, the guide on restarting a YouTube live stream after FFmpeg exits covers that separate problem. For an uploaded video that you want to send without leaving your computer running, StreamNeo removes the need to keep a local encoder machine powered on for the broadcast.
Choose and use the RTMPS URL
RTMPS is RTMP carried through SSL/TLS encryption. YouTube provides an RTMPS URL as an option for a protected connection; it is not the same text as the ordinary RTMP URL, and it does not replace the stream key. In Live Control Room, use the lock icon in the Stream URL area to reveal the RTMPS URL, then copy that value to the encoder’s server or URL field.
Check that your encoder supports RTMPS before selecting it. Some encoders may offer a protocol selector or choose a method based on the URL. In either case, make the encoder’s protocol and the copied address agree. Do not paste the RTMPS address into software configured to make a plain RTMP connection and expect the security negotiation to work automatically.
Google’s RTMPS ingestion technical guide describes the protocol requirements, including a YouTube ingestion server and path, port 443, and SNI hostname indication. Most creators do not need to configure those implementation details by hand if their encoder handles RTMPS correctly, but the points help explain common failures. A TLS error or timeout can indicate an incompatibility or a mismatch in how the encoder connects, not a bad stream key alone.
When troubleshooting an SSL certificate error, confirm you copied the RTMPS rather than the plain RTMP address, and check the encoder’s RTMPS support. If the encoder exposes advanced network options, use its documentation to confirm it connects over TLS to the proper hostname and port. Do not alter these values by guesswork; YouTube’s interface and technical guidance are the reference for the current endpoint.
A regular RTMP connection may suit an encoder that does not support RTMPS, while RTMPS is the appropriate selection when you want the encrypted method and your encoder supports it. Neither choice guarantees a working stream regardless of the encoder’s other configuration. The format, network path, key, broadcast state, and compatibility still matter.
Keep stream credentials secure
Treat the stream key like a password for sending to your channel. Do not put it in a public spreadsheet, paste it into a forum post, include it in an unredacted screenshot, or share it in a group chat simply to show someone the setup. A person who has the key may be able to send a feed to the associated stream, so limit access to people who need to configure or operate it.
Store it in a private password manager or another access-controlled place if you need to retain it. If several people help run the channel, agree who is responsible for changing or replacing a key and updating the encoder. A key change without updating the encoder can interrupt the feed; leaving an exposed key unchanged can create a different risk. If you believe a key has been exposed, check YouTube’s current controls for changing or resetting it, then update the encoder with the new value.
The URL is generally less sensitive than the key, but do not assume a screenshot containing both is safe to publish. Redact the key completely before asking for help. When sharing logs, remove credentials and check that the software has not printed a full connection string that includes them.
Keep a simple private note with the stream title, the encoder profile name, and whether the profile uses RTMP or RTMPS. Avoid saving the key in a plain shared document. This small bit of organisation helps when a night operator takes over without turning a working credential into a publicly accessible one.
Before you go live: verify the pairing
A quick check is more useful than repeated trial and error. Confirm that the selected stream is the one you mean to broadcast, the URL belongs to that stream, the key is in its own field, and the protocol setting matches the address. Then confirm that the encoder is sending and that YouTube’s preview or live workflow shows the expected incoming feed.
If the preview is absent, change one thing at a time. Re-copy the URL first, then independently re-copy the key. Check whether the encoder is set for RTMP or RTMPS as intended, and look for an error message that distinguishes authentication from connection failure. An SSL error points towards protocol or TLS handling; a wrong-stream result calls for checking the selected stream and paired credentials.
For a scheduled stream, follow the Live Control Room prompt to start the public broadcast once the preview is ready. Starting the encoder and starting the YouTube broadcast are related but distinct steps. Keep the control room’s current instructions in view because the available workflow can vary with the stream setup.
If you operate an unattended channel, test the exact profile you intend to leave running before relying on it overnight. That test should include the content source and the encoder’s own continuity behaviour, not just whether the URL and key were accepted once. For example, an online-class recording turned into a broadcast has different source-file needs from an ambient loop; the guide to recording online classes for YouTube covers that upstream task.
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
What is an RTMP URL?
It is the server address an encoder uses to send a live feed to YouTube over RTMP. Copy the value YouTube displays for the stream you are setting up and place it in the encoder’s server or URL field.
Where do I enter the YouTube stream key?
Enter it in the encoder’s separate “Stream key” field, not in the server or URL field. If your encoder uses a combined field or a special YouTube preset, follow that product’s instructions and confirm how it expects the values to be supplied.
How do I get the YouTube RTMPS URL?
Open the stream settings in Live Control Room and use the lock icon in the Stream URL area to reveal the RTMPS URL. Copy it into the encoder’s server or URL field and check that the encoder supports RTMPS.
Does RTMPS guarantee that my stream will work?
No. RTMPS describes an encrypted transport, but a working broadcast also depends on the correct stream URL and key, encoder configuration, network connection, and the stream’s state in YouTube. Check the current YouTube guidance and your encoder’s documentation if the connection fails.