A SHOUTcast station can be broadcast on YouTube Live by playing the station on a computer, capturing that audio in an encoder such as OBS, and sending the encoder output to YouTube. You also need a visible video scene, even if that scene is only a still image, logo, or authorised text panel.
The station URL and YouTube's server URL are different things. The station URL is used by a player or audio-routing setup; YouTube receives the finished audio-and-video signal from your encoder using YouTube's server URL and stream key.
Confirm that the SHOUTcast feed plays
Start with the source, before opening YouTube Studio or changing encoder settings. Open the SHOUTcast stream URL in the audio player or browser you intend to use on the production computer. Confirm that the expected station audio is audible and that the player remains connected for more than a brief moment.
Keep the station stream URL in a note, along with any player-specific configuration supplied by the station operator. Some feeds may be delivered through a direct stream URL, while others may need a playlist file or a particular player. That detail belongs to the player or capture workflow, not to YouTube's ingest settings.
Listen for the things that will matter in the broadcast:
- Is the station audio the correct channel rather than a preview or fallback stream?
- Does the player reconnect after a short network interruption?
- Is the volume consistent, or does it alternate between very quiet and very loud programmes?
- Does the stream include announcements, adverts, metadata or silence that you need to account for?
If the feed does not play reliably on the production computer, do not move on to the encoder. YouTube cannot repair a source that is already silent or repeatedly disconnecting. Save a short local test recording if possible, so you can compare the station audio with what OBS later receives.
This workflow is different from sending the SHOUTcast address to YouTube. YouTube's encoder instructions describe connecting an encoder with the server URL and stream key; they do not establish that YouTube accepts a SHOUTcast station URL in the server URL field. Treat the radio feed as an input to your encoder.
Check rights and source details
Before rebroadcasting the station, confirm that the station owner has permission to send its audio to YouTube. The permission needs to cover the music, spoken content, jingles, adverts, artwork and any other material that will appear in the broadcast. A station being publicly playable does not, by itself, answer the question of whether it may be rebroadcast on another platform.
Ask the station operator what the feed contains and who is responsible for its rights. If you operate the station yourself, keep the relevant licences, permissions and programme records together. YouTube may apply its own copyright systems or restrictions, and an encoder configuration does not remove those obligations.
The visual needs its own review. A station logo, presenter photograph, album artwork, sponsor mark or background image may belong to someone else. Use material that you own or have permission to display, and check whether that permission includes a public YouTube broadcast.
You can read YouTube's current copyright and live-stream guidance before publishing. It is the appropriate place to check platform rules, rather than relying on an old tutorial or assuming that an audio-only use is treated differently.
Create an encoder stream in YouTube Studio
Open YouTube Studio and go to the Live Control Room. Choose the encoder workflow, then create a new stream or select an existing stream. YouTube will provide the connection details needed by OBS, including the stream server URL and stream key.
Keep the stream key private. Anyone who obtains it may be able to send a signal to that stream. Do not paste it into a public tutorial, screenshot, shared document or chat message. If you think it has been exposed, reset it in YouTube Studio and update the encoder.
If this is the first time the channel has been enabled for live streaming, YouTube says activation may take up to 24 hours. Check this before scheduling a launch late in the evening. A delay in activation is a YouTube account requirement, not evidence that the station feed or OBS is misconfigured.
At this stage, note the difference between the two addresses you may have in front of you:
| Value | What it does | Where it belongs |
|---|---|---|
| SHOUTcast station URL | Gives a player access to the station audio | The audio player or source workflow on the production computer |
| YouTube server URL | Tells the encoder where to send the finished broadcast signal | OBS streaming settings |
| YouTube stream key | Identifies the YouTube stream receiving the encoder signal | OBS streaming settings, kept private |
Do not replace YouTube's server URL with the station URL. The former is the destination for the encoded broadcast. The latter is the source that your computer must play and capture.
You can follow YouTube's official encoder instructions if the names or positions of controls have changed in Studio. YouTube occasionally changes the Live Control Room layout, so the exact button labels may not match an older screenshot.
Add the station audio to OBS
Install and open OBS Studio on the computer that is playing the station. Use a current version suitable for your operating system, then make one scene for this broadcast. The first task is to get the station audio into an OBS audio source without capturing it twice.
On supported Windows systems, OBS's Application Audio Capture can capture the audio from the player running the station. OBS documents this source for Windows 10 version 2004 or later and Windows 11. Select the application that is actually playing the feed, then check the mixer meter in OBS while the station is audible.
On macOS 13 or later, OBS Studio 30 provides macOS Audio Capture, and the Screen Capture source can also capture audio. The names and permissions can vary by macOS and OBS version, so allow the requested audio or screen access and confirm the meter rather than assuming the source is active. OBS describes these options in its macOS desktop audio capture guide.
Linux users should select the appropriate ALSA or PulseAudio capture source for their desktop or application arrangement. The correct choice depends on how the system exposes the player audio. If application capture is unavailable, use the computer's desktop or output audio capture, then verify that only the intended output is being recorded.
The common routing error is duplicate capture. If the same station player is included in Application Audio Capture and global Desktop Audio, OBS may receive it twice. That can create an echo, comb filtering or a louder-than-expected signal. Disable the unused global source or exclude the player from it, then listen to the OBS monitoring output with headphones.
Watch the mixer while the station plays. A moving meter confirms that OBS is receiving a signal, but it does not prove that the signal is clean. If it reaches the red area, reduce the source or system level. If it never moves, check that the player is not muted, that the correct application is selected, and that the operating system has granted OBS the required permissions.
For a broader explanation of the available sources, see OBS's audio sources documentation. The exact capture option is less important than the result: one copy of the station audio reaches OBS consistently, without echo or clipping.
Build a visual scene
YouTube Live still needs a video signal for this encoder workflow. Create a scene that gives viewers useful context while the station audio plays. A simple arrangement might contain the station logo, station name, current programme information if you can maintain it accurately, and a note telling viewers where the station operates.
OBS can use image, text, browser and media sources. Add a station-owned logo or still image first, then set its position and size in the preview. Keep important text away from the edges, where different screens and player layouts may obscure it. A dark background with light text is usually easier to read than a detailed photograph behind small lettering.
If you use a browser source for a now-playing page, test what happens when the page is unavailable or the song title is missing. A broken browser source should not make the whole scene appear unfinished. For a simpler overnight setup, a stable still image is easier to inspect than a page that needs its own login, script or network connection.
You can add a second scene for maintenance or source failure. For example, one scene can show the normal station artwork and another can show a clear message while you investigate the feed. Do not switch to a blank canvas by accident. Before streaming, confirm that the selected scene contains a visible image or text and that the preview is changing or otherwise visibly present.
If the computer struggles with a complex scene, remove unnecessary animations and browser sources before lowering the audio quality. A modest visual that remains available is more useful than a decorative layout that disappears after a few hours. Readers building a video-based channel may also find the guide to making a 24/7 YouTube stream from pre-recorded videos useful for thinking about scenes, sources and long-running operation.
Enter YouTube's stream details in OBS
In OBS, open Settings and the Stream page. Select the YouTube integration if it is available, or choose the custom service option and enter the YouTube server URL and stream key supplied by Live Control Room. Do not enter the SHOUTcast station URL in either of those destination fields.
YouTube recommends RTMPS for encoder connections. Its current encoder guidance also lists AAC or MP3 audio, 44.1 kHz for stereo audio and 128 Kbps for stereo audio as recommendations. These are YouTube settings guidance, not a promise that every station feed will sound good at those values. The source may already be compressed, and increasing the encoder bitrate cannot restore detail that was removed upstream.
Use the encoder's output settings to match the actual broadcast. If the station is stereo, retain stereo through the capture and encoder path. If it is mono, avoid creating an unnecessarily complicated stereo routing setup. Select the audio device and source deliberately rather than accepting every default source in OBS.
For a longer-running channel, write down the working OBS settings, scene name, YouTube stream selection and station player setup. A written recovery note is useful when the computer restarts or another person has to bring the channel back online. Keep the stream key out of that note if it is stored somewhere that others can access.
This is also the point to decide whether a local computer is the right operating model. OBS can work well when the player, audio capture and encoder are all stable, but it depends on the computer staying awake and connected. If the main problem is leaving a computer running overnight, StreamNeo removes that particular burden by taking an uploaded video and running it as a YouTube broadcast from the cloud; it does not replace the SHOUTcast capture workflow described here.
Test the signal before publishing
Run a representative test before making the broadcast public. Start the station player, open the correct OBS scene, confirm the mixer is moving without clipping, and begin the encoder connection to YouTube. Use the Live Control Room preview to check both the visible scene and the station audio.
Do not rely only on the local OBS preview. The local preview can look correct while the YouTube connection is pointed at the wrong stream, the key is invalid, or the remote signal has a delay or interruption. Watch YouTube's stream health and look for warnings about missing video, unstable connection or audio problems.
Speak through this test in the same order you would use after a restart:
- Open the station player and confirm the expected programme is audible.
- Open OBS and check that the intended scene is selected.
- Confirm that exactly one audio source is active.
- Check that the audio meter moves and does not clip.
- Start the encoder connection.
- Inspect the YouTube preview for the visual and audio.
- Confirm stream health before selecting Go Live in Live Control Room.
If the preview says it is waiting for data, work through the fix order for a stream stuck on Starting Soon or Waiting for Data. If the picture arrives but the sound is missing, return to the OBS mixer and operating-system permissions. If the audio is doubled, remove the duplicate desktop or application capture before testing again.
Check the test from an ordinary viewer account or a separate device when practical. Listen for silence at the start, abrupt level changes, delay, echo and programme audio that is being cut off. A short private or unlisted test can reveal a routing mistake without making the unfinished broadcast the public launch.
If the network connection is unstable, YouTube may report dropped frames or an unhealthy stream even though the source audio continues locally. The guide to YouTube Live dropped frames explains the distinction between source, encoder and network symptoms. Fix the cause before promoting the stream.
Run and end the broadcast cleanly
Once the preview is correct, click Go Live in Live Control Room if the stream has not already been configured to publish automatically. Keep the production computer awake, prevent it from sleeping, and avoid changing the default audio device while the station is running. If the player stops, OBS can continue sending video with silence, so include a check of the station audio in your overnight routine.
Record the working setup: the player used, the selected OBS audio source, the scene name, the YouTube stream selection and the recovery steps. Do not record the private stream key in a document that is shared with the wider team.
When finishing, stop the encoder in OBS and then end the broadcast in Live Control Room. YouTube says streams under 12 hours are automatically archived. Verify the resulting archive before advertising the channel, especially if the station plans to reuse the recording or make it available on demand.
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
Can I paste my SHOUTcast URL into YouTube's server URL field?
No. The SHOUTcast URL identifies the station audio source, while YouTube's server URL is the destination used by the encoder. Play the station through a suitable player or capture workflow, then send the resulting audio-and-video signal from OBS to YouTube.
Does the YouTube broadcast need a visual?
For this encoder workflow, provide a video scene as well as the station audio. A station-owned still image, logo or text scene is sufficient as a practical starting point, provided you have permission to display it.
Why is my OBS audio doubled or echoing?
The station may be captured both by an application or device source and by global Desktop Audio. Disable one route and test again, then confirm that only one mixer channel is receiving the player audio.
What should I do if the first live activation is not available?
YouTube says first-time live-stream activation may take up to 24 hours. Check the channel's Live Control Room status and wait for activation before treating the encoder or SHOUTcast feed as the cause.