To send a live source from Restreamer to YouTube, create or select a stream in YouTube Studio, then enter the stream destination details in Restreamer’s Publication Service. Start the publication, confirm that YouTube receives the feed, and end the event in YouTube before stopping Restreamer.
This is a destination configuration task, not a shopping list: you do not need to buy a camera, encoder, or other physical capture gear to follow these steps. You do need a working source in Restreamer, an eligible YouTube channel, and the matching URL and stream key from YouTube.
Prepare a YouTube live stream
Sign in to YouTube Studio and choose Create → Go Live. In Live Control Room, use the Stream tab to create a stream or select an existing one. You can use a scheduled stream if you have already made one, but scheduling is not the same as starting the public broadcast. YouTube’s official stream setup instructions describe the current route to Live Control Room and the stream details you will need.
Find the stream URL and stream key shown for the selected stream. YouTube provides these values; the precise labels can change, but the important point is that the URL and key belong together. Copy both accurately, without adding spaces or substituting a generic RTMP address. If YouTube gives you a choice of server or protocol, use the URL for the protocol you intend to send and that your Restreamer installation supports.
Treat the key like a password. Anyone who has it may be able to send a feed to that destination, so do not put it in a public message, screenshot, or stream overlay. Keep it in a private password manager or another restricted place while you configure the destination. If you think it has been exposed, use Live Control Room to reset it, then update the value in Restreamer as well; the old key will no longer be the one to rely on.
A YouTube stream and a live event are related but distinct parts of the workflow. Restreamer sends video and audio to the stream destination; Live Control Room shows whether YouTube is receiving it and, for a scheduled event, gives you the control to start the public event. Do not assume YouTube automatically starts a scheduled event when an incoming feed arrives.
Before you go further, check that the source you intend to publish is already available in Restreamer. That may be a file-based or other configured source. If you are planning a longer channel, the practical concerns around source continuity and audio are separate from the destination credentials; see our guide to keeping audio between videos on a continuous stream when a playlist is the source.
Open Restreamer Publication Service
Open the Restreamer interface for the instance that holds your active source. Find Publication Service, the area used to send a configured channel to an external streaming destination. Restreamer’s documentation describes publication as the output side of a channel: the source is prepared in Restreamer, then a publication sends that output to a service such as YouTube. The Restreamer publications manual explains the available publication controls and transport choices.
Make sure you are configuring the channel that contains the source you want viewers to see. A destination can be valid while pointing at the wrong channel or an empty source, so verify the source selection before debugging YouTube. If Restreamer’s labels or layout do not match a guide you have open, use the current Publication Service controls in your installed version and confirm the corresponding stream details in Live Control Room rather than copying UI instructions blindly.
This step does not configure a camera, capture card, or physical encoder. Those may matter in a production workflow where they supply the source, but they are not prerequisites for entering YouTube’s destination credentials. Keep the question narrow: can Restreamer publish the intended channel to the selected YouTube stream?
Choose the YouTube destination
In Publication Service, add or select the YouTube destination. The Restreamer YouTube guide describes choosing the YouTube target and entering the valid streaming ID or key before saving. You can consult the datarhei Restreamer YouTube guide if you need the vendor’s explanation of that workflow.
The option may be presented as a YouTube preset rather than a generic RTMP destination. Choose the named YouTube destination when it is available, because a preset can make clear which credential field Restreamer expects. Follow the installed interface’s prompts: a field labelled Streaming ID, Stream key, or similar is not an invitation to paste the whole URL into it.
If your version presents a generic publication instead, use the transport and fields it asks for, taking the endpoint values from YouTube. Restreamer’s general documentation lists RTMP among publication transports, but it does not establish that every version’s YouTube preset offers every protocol. Do not infer capabilities from another installation’s screenshot.
Enter the server URL and stream key
Keep YouTube’s server URL and stream key as a pair. Put the URL in the destination or server field if Restreamer asks for one, and put the key in the key or ID field. Some presets may handle the server address for you and ask only for a streaming ID; in that case, follow the preset’s labels and supply the value it requests. Do not paste the URL into a key field, and do not guess an endpoint from an old tutorial.
YouTube supports RTMP and RTMPS. RTMPS carries RTMP over TLS/SSL, but it works only when the sending software supports it and you use the RTMPS URL supplied in Live Control Room. YouTube’s encoder troubleshooting guidance covers connection checks, including protocol and server details. Restreamer documentation does not confirm that every version’s YouTube destination supports RTMPS, so treat it as conditional: if the installed destination offers the setting and YouTube supplies the matching URL, use that pairing; otherwise use a supported option rather than assuming the protocol can be swapped.
| Choice | What you enter | Practical consideration |
|---|---|---|
| RTMP | The RTMP server URL and matching key from YouTube, where requested | Use the exact endpoint YouTube shows for the selected stream. |
| RTMPS | The RTMPS URL and matching key, if both sides support it | The sending destination must support RTMPS; a normal RTMP URL is not a substitute. |
Enter the key privately and avoid leaving it visible while sharing your screen. If someone else helps with configuration, give them only the access they need and change the key if you later have reason to believe it was exposed. Stream keys are credentials, not descriptive labels.
If you use an RTMPS destination and it times out or fails during connection, check that the server URL is specifically the RTMPS one from Live Control Room and that Restreamer supports that protocol. YouTube’s troubleshooting material also advises checking the protocol and server in the URL; if the service URL requires port 443, use the supplied endpoint as provided. Do not edit ports or encryption settings by guesswork.
Save and check the connection
Save the destination, then start its publication in Restreamer when the source is ready. A saved destination is only configuration; it does not by itself prove that video is being sent. Restreamer’s YouTube guide says bitrate feedback appears in the main window once connected. Look for that indication and check that it changes in a way consistent with an active feed rather than treating a saved form as confirmation.
If no bitrate feedback appears, check the basics in order: the intended channel and source are active, the destination is enabled, the key belongs to the selected YouTube stream, and the URL matches the protocol. Correct a typo from the values in Live Control Room instead of repeatedly trying nearby server addresses. If the key was reset in YouTube, update the stored key in Restreamer before starting again.
Audio deserves its own check. A picture without sound may mean the source or audio configuration is incomplete, not that the YouTube destination is wrong. Restreamer’s wizard documentation notes that some services, including YouTube, require an active audio channel. Check the source’s audio selection and confirm YouTube’s incoming preview includes sound before considering the setup finished.
For a continuing channel, the source and publishing destination need separate attention. A healthy destination cannot fix a file that has ended, an audio track that falls silent, or a playlist that stops advancing. If your source is a computer-based playlist, our article on encoder overload during continuous video playback covers a different failure layer: playback and encoding load, rather than YouTube credentials.
Confirm preview in Live Control Room
Return to the selected stream in YouTube Live Control Room and wait for the incoming feed to appear in its preview. Confirm that the picture is the intended source and that audio is present if your programme uses it. Give the preview time to register; a brief delay is not by itself evidence that the key is wrong. The purpose of this check is to verify what YouTube actually receives, not merely what Restreamer says it is sending.
For a scheduled event, review the title, visibility and timing before going live. When the preview is ready and you intend to begin the public broadcast, click Go live in Live Control Room. The click is a deliberate handoff from preview to the event; receiving a feed does not mean YouTube has automatically started the scheduled broadcast. For a stream that is not scheduled, use the controls YouTube presents for that stream and confirm its live state there.
If the preview does not arrive, check the Restreamer connection indication first, then recheck that the URL and key correspond to the same selected stream. Verify that the publication is running and the source is active. If YouTube reports a protocol or connection problem, compare its selected server URL with Restreamer’s destination and confirm support for that protocol in your installed version.
Once live, look at YouTube’s stream health and your actual playback, not only the preview. A preview can establish that a feed reached YouTube, but it does not guarantee that a long-running programme will remain healthy. Check the stream after any meaningful change to the source, key, or destination. If viewer delay matters for a conversation or a live update, see how to change YouTube Live latency in Studio; latency settings affect the viewing experience, not whether the destination credentials match.
End the stream cleanly
When the event is over, end it in YouTube first, then stop the publication in Restreamer. The datarhei Restreamer YouTube guide specifically advises ending the stream on YouTube first after an event. Its warning is practical: interrupting the Restreamer output while the event is still live may mean YouTube does not save the stream in its DVR archive.
In Live Control Room, use the control to end the live event and confirm the event has ended. Then return to Restreamer and stop the publication. This order makes the end of the YouTube broadcast explicit before its incoming feed disappears. If the event is intended to continue as an always-on channel, do not end the event merely to test the control; use the planned maintenance window or workflow that fits the channel instead.
Afterwards, check the archived broadcast in YouTube Studio if you need a recording. An archive should not be treated as a substitute for deliberately ending the event in the right order. If you discover that the key was shared or copied into a public place, reset it in Live Control Room and replace it in Restreamer before the next publication.
For an always-on channel built around pre-recorded material, the configuration remains about the stream destination, but the operating model can differ from keeping a local computer switched on all night. StreamNeo can remove that specific need to leave your own computer running by taking an uploaded video and sending it as a YouTube live stream; it does not change the need to manage your channel, source choices, or YouTube event controls.
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
Do I need to buy a camera or encoder to configure the YouTube destination?
No. The steps here configure a source already flowing through Restreamer and its output to YouTube. A camera or other capture equipment is only relevant if you need it to create the source in the first place.
Should I enter the YouTube stream URL or the stream key in Restreamer?
Use the exact field requested by the destination. A generic RTMP setup may ask for both the server URL and key, while a YouTube preset may ask for a streaming ID or key and handle the rest; keep the values YouTube supplies together and do not guess a URL.
Why is there no picture or audio in YouTube’s preview?
Confirm that the correct Restreamer channel and source are active, the publication is running, and the URL and key match the selected YouTube stream. For missing audio, check that the source has an active audio channel as well as checking the destination.
Can I stop Restreamer before ending the YouTube event?
End the event in YouTube Live Control Room first, then stop the publication in Restreamer. Restreamer warns that interrupting its output during a live event may prevent YouTube from saving the stream in its DVR archive.