If you already run a station through a cloud radio playout service, you can bring its public listening stream into an encoder such as OBS, add a visual, and send the resulting video feed to YouTube Live. The playout service supplies the station audio; unless it documents a direct YouTube destination, you still need an encoder to create and deliver the YouTube broadcast.
Before connecting anything, check that the music, speech and other material in the station feed are cleared for YouTube livestreaming and for any archive. Then rehearse the complete route, from the listening URL to YouTube’s preview, before you announce a public start time.
Confirm the station stream and rebroadcast rights
First decide exactly which audio you intend to broadcast. If you want YouTube viewers to hear the same programme as people using your station’s player, find the public listening URL in the playout service’s dashboard or documentation. Check that it plays outside your account and that it carries the expected programme, not a private preview, a silent standby feed or a dashboard-only source.
A listening link is not automatically a licence to rebroadcast. The rights you have for an internet radio station may not cover YouTube Live or a recording that remains available afterwards. YouTube’s livestream terms and conditions place responsibility on the streamer to have the necessary rights for content on Google services, including relevant music rights. Ask the rights holders or your licensing adviser whether your particular agreements cover the intended territory, live use and any video-on-demand archive.
Pay particular attention if your station uses commercial recordings. YouTube scans live streams for third-party content. Its guidance says a match can lead to a placeholder and warning, and continuing to broadcast the matched material can result in interruption or termination. A licence does not necessarily stop an automated interruption: YouTube says a licensed content owner may need to add your channel to its Content ID allowlist. Resolve that with the rights owner before relying on a commercial-music feed.
Check spoken material and visuals too. A presenter’s intro may include a recording, a guest’s contribution or material that the station is not entitled to republish. A station logo, album artwork, background photograph or video loop also needs to be suitable for the YouTube use you have in mind. Keep a simple record of what you checked, who confirmed it and whether the permission includes an archive.
If you plan to leave the recording available, check those archive rights separately rather than treating them as part of the live permission. YouTube says streams under 12 hours are automatically archived, and Content ID claims can be made after a stream ends if it is archived. The current YouTube Help guidance on live-stream archives is worth checking before you set up a long broadcast. For a related distinction between audio and video requirements, see whether a radio station can stream to YouTube Live without video.
Choose an encoder workflow
There are two useful starting points. In a relay workflow, the programme already exists in the cloud station: OBS receives its listening stream, combines it with a visual, and sends the composition to YouTube. In a live-origin workflow, a presenter speaks or performs into a local microphone, mixer or computer audio input and the encoder sends that input to YouTube. Some broadcasts combine both, for example by taking the station feed and adding a locally hosted introduction.
| Workflow | Audio begins at | What the encoder does | Practical consideration |
|---|---|---|---|
| Relay the station | The cloud service’s public listening URL | Receives the programme, adds a visual and sends it to YouTube | Confirm the listening link remains available and carries the right feed |
| Present or perform live | A microphone, mixer or selected computer audio input | Captures the live input, adds a visual and sends it to YouTube | Someone must manage the local input and watch for unwanted sounds |
| Use a documented direct destination | The service’s own supported YouTube output, if it offers one | Follows that service’s documented connection and visual options | Do not assume the route exists or that it behaves like OBS |
The OBS relay route is documented in Radio.co’s guide to broadcasting a radio station on YouTube. Its example uses a station listening link as a VLC media source in OBS, then sends the scene to YouTube. That is evidence for that particular workflow, not a promise that every cloud radio provider exposes the same URL, or that all links work in the same OBS source type.
Some providers document other ways to originate or route audio. Read the service’s current instructions and distinguish a live audio input to its radio station from a direct video encoder destination to YouTube. A browser playout tool that queues tracks for a station, for instance, should not be treated as a YouTube encoder unless the vendor explicitly documents that output. If you prefer a managed, video-file-based route rather than relaying a live station feed, compare the approach with options for scheduling video changes in YouTube loop services.
OBS is a practical choice when you need to combine a live station feed and visuals yourself, but it means a local computer and encoder session are part of the broadcast path. That computer must stay on, connected and configured while it is sending. If your aim is to operate a stream while your computer is off, a separate cloud video-streaming workflow may fit better; StreamNeo addresses the specific burden of keeping a local computer running for an uploaded video-to-YouTube broadcast, but it is YouTube-only and is not a bridge for a cloud radio listening URL.
Add the listening stream as an audio source
In OBS, create a scene for the YouTube broadcast, then add the station’s listening stream as an audio or media source. Radio.co’s example uses a VLC media source. Your provider may instead give you a different format or recommend a particular player, so use its current listener-link instructions and the source type that can open that URL. If the stream requires credentials, do not expose them in a public scene, on screen or in a tutorial recording.
Give the source a clear name such as “Station programme”. This makes it easier to identify the right feed if the scene later includes a microphone or an alert sound. Start the source and listen through OBS monitoring or another safe test path. Confirm that it is the intended station output and that it continues beyond the first few seconds; some player links can open a web page rather than the audio stream itself.
If the service offers several outputs, choose the one intended for listeners rather than an internal studio return unless its documentation says otherwise. A monitor or preview output might contain talkback, an unbalanced mix or silence when nobody is logged in. Compare what you hear in the service’s public player with what reaches OBS. The goal is to notice a wrong source or a stalled player before YouTube viewers do.
You can add a microphone as a separate source when the programme calls for live introductions or announcements. It is not required just to relay a station URL. If you capture system audio instead, remember that it can include computer alerts, browser sounds or unrelated media as well as the station. Radio.co’s live broadcasting guidance discusses source choices and monitoring levels; keep unnecessary applications and notification sounds out of the capture path.
Before relying on the route, let the source play through a rehearsal long enough to check that OBS still receives audio and that the feed does not unexpectedly switch to a different programme. Do not assume that a stable public player proves the encoder is receiving it: listen to the audio in the scene that you will actually send.
Add an appropriate visual
YouTube Live is a video broadcast, so give viewers a deliberate visual rather than leaving a blank scene. A station logo on a suitable background, a programme slate, a webcam shot or a simple studio view can all work, depending on the station’s format and permissions. For a static image, check that it is legible on a phone and does not promise a programme or presenter who is not actually on air.
In OBS, add the image or capture source to the same scene as the audio source, then arrange the canvas so that the visual fills the intended frame. Inspect the preview at the size viewers are likely to see it. A small logo can disappear on mobile, while text close to the edge can be cut off in some displays. If you show current track information, make sure it updates accurately; stale song text is more confusing than a clean station slate.
A simple slate can set expectations: station name, programme name and a concise note that the audio is live or continuous, if that is accurate. Avoid adding artwork just because it is available in the playout dashboard. Rights to play a recording do not by themselves establish rights to show its cover image. Similarly, a webcam or studio capture can reveal private screens, phone numbers or other material that should not be public.
You can keep the visual straightforward. The setup problem is to deliver a valid, intentional video picture alongside the audio, not to build a complex television production. If the channel is a continuous loop, the discussion of a playlist versus an OBS loop for a 24/7 meditation stream may help you think through how a visual behaves over time, though a radio relay has its own audio-source requirements.
Connect the encoder to YouTube Live
In YouTube Studio, choose Create and then Go Live. Use the Stream tab when you are preparing an immediate broadcast, or Manage to schedule one. A scheduled event can provide a watch page to share ahead of time; verify the event’s visibility and details before you promote it. If you need a rehearsal without a public audience, review how to make a private YouTube Live stream and confirm the privacy state in Studio rather than relying on a scene name or an OBS label.
YouTube’s encoder setup instructions explain how to find the stream settings in Live Control Room. Copy the stream server URL and stream key shown there into OBS’s stream settings. Treat the key like a password: anyone with it may be able to send a feed to your event. Do not paste it into a public document or show it in a screen capture, and regenerate it if it is exposed.
If OBS offers a YouTube service preset, use it to reduce manual entry. For transport, prefer YouTube’s RTMPS option where the encoder supports it. YouTube describes RTMPS as its encrypted ingest option; use the exact server URL supplied in the stream settings rather than substituting a guessed address. Its RTMPS guidance notes that port 443 may help in some connection cases. If the connection times out, check that the encoder supports RTMPS; if an SSL error appears, verify that the URL and protocol match the settings YouTube provided.
Start sending from OBS and inspect YouTube’s preview before making the stream public. For a scheduled event, YouTube may show the incoming feed first, after which you use Go live in Live Control Room to start the public broadcast. Make sure the right event is open: a correct OBS connection to the wrong scheduled stream is still the wrong broadcast. Confirm title, description, thumbnail or slate, visibility and start timing in Studio.
Do not assume a cloud radio playout service offers a direct YouTube connection merely because it can broadcast a station to listeners. If its current documentation explicitly describes a direct YouTube destination, compare that route’s setup and visual controls with the OBS relay path, then test it. Otherwise, treat the station service as the source and the encoder as the separate YouTube delivery step.
Test levels and playback before going public
A rehearsal should follow the whole route: station output, OBS scene, YouTube ingest and viewer playback. Check that speech and music are audible, the video is present, and the feed is not a dashboard preview or an unintended studio return. Monitor OBS’s audio meters while listening; meters moving without a useful listening check will not tell you whether the source sounds distorted, too quiet or simply wrong.
Set levels with headroom rather than pushing every source to its limit. If the station feed is already mixed, avoid applying extra gain without a reason. If a microphone is added, check it separately and make sure it does not mask the station programme or produce feedback. Listen on headphones or speakers at a sensible level, and check YouTube’s preview as well as the local OBS monitor: the encoder may be sending a different scene or source than the one you are listening to locally.
For a private rehearsal, verify visibility before you start and tell anyone assisting which event to open. Confirm the visual is legible, the audio and video stay together, and the YouTube preview is receiving the intended content. A short test can reveal a missing source or a key copied into the wrong field; a longer rehearsal is useful when you need confidence that the listening stream stays connected. Do not present a test as proof that the public broadcast will never drop.
Check for sounds that are easy to overlook: desktop notifications, browser tabs, operating-system alerts and a microphone left open in the room. If system audio is part of the scene, close or mute unrelated applications and silence notifications. If you use a station listening URL, system sounds should not normally be needed at all, which can make that source route simpler to audit.
Only promote the public event when the rights check, scene, connection and preview all agree. If the preview is silent, pause and identify whether the problem is the station URL, the OBS source, the selected scene or the YouTube connection. If the audio is right but the picture is missing, correct the scene before proceeding. The point of the checklist is not to guarantee a flawless show; it is to catch avoidable setup mistakes while you can still fix them privately.
Monitor the broadcast
Once live, keep an eye on both OBS and YouTube Live Control Room. Watch for an audio meter that stops moving, a disconnected indicator, a frozen visual or a warning in Studio. If you have a second person available, assign one person to programme duties and another to watch the encoder and YouTube status, rather than asking a presenter to manage every screen while speaking.
A cloud playout source and a local encoder are separate links in the route. If viewers report silence, check whether the station’s public player is still playing, then whether OBS receives it, and then whether YouTube shows incoming audio. This sequence helps narrow the fault without changing several settings at once. Keep the listening URL, scene and event details to hand, but protect the stream key.
If the stream disconnects, check the actual status before restarting blindly. Confirm the network, OBS connection and YouTube event, then restore the intended scene and verify the preview. A backup server URL is useful only if YouTube supplies one for the event and your encoder setup uses it as documented. The guide to YouTube primary and backup ingest URLs explains why these fields are not interchangeable guesses.
At the end, stop sending from the encoder and end the event in YouTube as appropriate. Confirm that the archive is allowed to remain available and check it after processing. YouTube says streams under 12 hours are automatically archived; post-stream Content ID claims may still arise when an archive is made. If the recording should not be public, review its visibility and remove or restrict it according to your rights and channel needs.
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 connect OBS to my radio stream?
Add the station’s public listening URL as an audio or media source in an OBS scene, using the source type your provider documents. Add a suitable visual, then connect OBS to the YouTube server URL and stream key shown in Live Control Room. Rehearse the complete path and confirm the YouTube preview before going public.
Can I use a cloud radio service’s direct YouTube connection?
Only if that service’s current documentation explicitly offers a direct YouTube destination. Many cloud playout services provide a station listening stream or tools for sending audio to a radio station, which is not the same as a video encoder connection to YouTube. When no direct route is documented, use an encoder such as OBS as the bridge.
Can I play copyrighted music on a YouTube livestream?
Do not assume your station licence covers YouTube Live or an archived recording. Confirm the necessary YouTube-specific rights with the relevant rights holders, and ask whether your channel needs to be allowlisted in Content ID. YouTube may interrupt a live stream that continues to carry matched third-party content.
Do I need a microphone to relay a station feed?
No. If the purpose is to rebroadcast the station’s existing programme, the listening stream can supply the audio. Add a microphone only if you have a live presenter or another intended local input, and check that it does not introduce room noise, feedback or unwanted audio into the scene.