You can play a radio station’s website player on the computer running your stream and capture its desktop or application audio in OBS. The exact steps depend on your operating system and OBS version, so confirm that the meter moves, listen to the outgoing mix, and test with an unlisted YouTube stream before going public.
The important condition comes before the technical setup: a player that anyone can hear online does not prove that you may retransmit the station’s programming. You need permission that covers YouTube livestreaming, and YouTube may still detect, interrupt or terminate a stream containing third-party content.
Check rebroadcast permission before opening OBS
Listening to a station through its website is normally a listener activity. Sending that same programming to your YouTube audience is a separate use. The player’s public availability, a “play” button, or the absence of a download option does not establish permission to rebroadcast it.
Ask the station for written permission before you build the stream around its audio. Your request should describe the intended use clearly: a live retransmission on your YouTube channel, the countries in which it will be available, whether the stream will run continuously, and whether YouTube will keep an archive or replay. The station may control some rights itself but not every right in every recording, broadcast or territory.
YouTube’s livestream terms and conditions place responsibility for the necessary rights on the person providing the live content. That includes relevant music licensing rights from artists, record labels, publishers and other rights participants. A station’s agreement with its own listeners or website visitors may not cover your channel.
Ask the station whether it can also have your channel allowlisted. YouTube explains that even a licensee can encounter an interruption when the rights holder has not allowlisted the channel. Permission is therefore necessary, but it is not a promise that automated systems will recognise the permission without further action.
Keep the permission email, agreement or licence details somewhere you can find them. Note the channel name, the permitted territory, the start and end dates if any, whether an archive is allowed, and the person or organisation granting the permission. If the answer is vague, ask a follow-up question rather than treating silence as approval.
Do not use the station’s audio while you wait for a reply. You can test OBS with audio you are entitled to use, or with a short local recording made for testing, but do not publish the station feed merely because the technical capture works.
Play the station website player on the streaming computer
Once the rights question is settled, use the computer that will actually send the YouTube stream. Open the station’s official website in a stable browser session, load the player, and start playback. Do not assume that hearing the station on your phone proves that the streaming computer is receiving the same audio path.
Before adding a capture source, check the simple things. Confirm that the browser tab is not muted, the player itself is not paused, and the computer’s output device is the one you expect. If the station requires a login, keep that session active and understand what happens if the player asks for a consent, location or age confirmation again overnight.
If you capture all desktop output, every sound routed through that output can enter OBS. That may include browser alerts, operating-system sounds, notification chimes, a video call, or another tab. Close unrelated tabs and disable notifications for the test. For a long-running channel, a dedicated browser profile can make it easier to keep the station player separate from everyday browsing.
There is a practical choice here. Capturing the full desktop is often easier to understand because you hear exactly what the computer sends to its output. Isolating only the browser or application is tidier because unrelated sounds stay out of the stream, but it may require a supported application-capture route or additional audio configuration.
| Approach | What reaches OBS | Main benefit | Main risk |
|---|---|---|---|
| Capture all desktop output | Audio from the selected computer output | Simple and broad | Notifications and unrelated applications can be broadcast |
| Capture one application | Audio from the selected browser or application, where supported | Keeps other desktop sounds out | Availability and steps vary by operating system and OBS version |
| Capture a selected device | An input or output device added as an OBS source | Gives direct control over a device | Duplicate configuration can create echo |
| Older macOS routing setup | Audio passed through an additional routing arrangement | Can support setups not covered by native capture | More configuration and another point to troubleshoot |
This is an audio-capture decision, not a rights decision. Every row still requires permission to retransmit the programme. If you also want a visual loop, keep the audio source and video source conceptually separate so that you can identify which part failed.
Choose desktop or application audio capture in OBS
OBS’s Quick Start Guide explains that desktop audio and microphone input may be captured by default, while devices can also be selected manually. The labels and available sources can vary, so read what your own OBS installation presents instead of following a button name from an older tutorial.
Start with a scene for the stream. In the Audio Mixer, look for the desktop audio source or add the relevant audio source to the scene. If your version supports application-level capture, choose the browser or application playing the station. If it does not, use the desktop output route or consult current guidance for your operating system.
On macOS 13 Ventura and later with OBS 30 or later, OBS documents a macOS Audio Capture source that can capture all desktop audio or a single application. Older macOS arrangements may need additional audio-routing software. That is why a Windows guide, an older Mac guide and a current Mac guide may show different procedures while all describe valid setups for their own conditions.
On Windows and macOS, OBS documents selected input and output device capture in its Audio Sources guide. The guide also warns about capturing the same device through more than one path. If a device is already enabled as a global source and you add it directly to the scene, disable one of those configurations before testing.
The duplicate-source problem is easy to miss. You may hear the station twice with a slight delay, producing an echo or hollow sound. Look for two mixer channels responding to the same station, or mute one source briefly while listening. Keep one deliberate route and label it clearly, such as “Station browser audio”.
Linux users should not assume that the macOS or Windows method applies unchanged. The available audio systems, desktop environment and OBS package can alter the route. Use current OBS and distribution guidance for the specific setup, then verify the result in your own test stream.
If you are building a broader 24/7 channel rather than retransmitting a live website player, a recorded file may be easier to control. For example, a 24/7 YouTube lofi stream with a playlist bot uses prepared media rather than depending on a browser session remaining logged in and audible.
Verify the OBS meters and listen to the mix
Start the station player, then watch the OBS Audio Mixer. A moving meter shows that OBS is receiving audio, but it does not by itself prove that viewers will hear the right source. Check that the source is not muted, that its fader is raised, and that the selected device is the one actually playing the station.
Listen to the mix through the monitoring arrangement you normally use. You are checking for silence, clipping, echo, a second delayed copy, abrupt browser sounds and a level that makes speech or music difficult to hear. A pair of monitoring headphones can help during the test, but no particular equipment is required.
Use the monitoring controls carefully. If you hear the stream locally and also hear the same output through a separate monitoring path, a loop can form. Keep the arrangement simple: one source into OBS, one deliberate monitoring route, and no microphone unless you specifically need it. If you add a microphone for announcements, test its balance separately and mute it when it is not required.
The station may insert adverts, news bulletins, presenter links or other programmes without warning. These changes are part of the feed you are retransmitting and may have their own rights conditions. Do not treat a quiet period in the player as evidence that the overnight stream will remain quiet or unchanged.
For a channel intended to run overnight, test the browser’s behaviour as well as the audio. Check whether the player stops after inactivity, loses playback when the computer locks, asks for a sign-in again, or changes output after a system update. These are operational issues, but they can turn a working afternoon test into silence later.
If your wider workflow is based on recorded video, compare it with the guidance on looping pre-recorded meditation videos on YouTube Live. The lesson is not that recorded content is always preferable; it is that a prepared file removes some browser and live-feed dependencies.
Test with an unlisted YouTube stream
Do not make the first full test public. Create an unlisted livestream and send the same OBS scene and audio route that you intend to use for the public broadcast. An unlisted test can reveal a capture problem, a bad mix, a broken player session or a rights notice before viewers are directed to it.
In YouTube Studio, confirm that the stream is unlisted and that you understand who can access the test link. Start OBS, connect the stream, and wait long enough to check more than the first few seconds. Watch the OBS meter, listen locally, and inspect the YouTube preview. YouTube’s live streaming tips recommend testing and continuously monitoring audio and video quality.
Check the YouTube side for a clear audio signal and a stable preview. A meter moving in OBS while the YouTube preview is silent means the problem is between OBS and YouTube, or in the selected monitoring and source configuration. Conversely, a preview with audio does not confirm that you have permission to use the station’s programming.
Watch for copyright notices during the test. YouTube says that live streams are scanned for matches to third-party content, including another copyrighted live broadcast. Its copyright guidance for live streams explains that a response can include a warning, a placeholder image, interruption or termination.
A clean short test is not a permanent clearance. The station’s programme may change later, an automated match may occur after more material has played, or a rights holder may apply a different policy. Keep the unlisted test as a technical check, not as proof that the public broadcast is authorised.
If YouTube displays a rights notice, stop and investigate before publishing. Check your written permission, ask the station about allowlisting, and read the current notice in YouTube Studio. Do not simply start another public stream and hope that the result changes.
Check the YouTube preview before going public
When the unlisted test is technically sound and the rights position is documented, inspect the final YouTube preview immediately before changing visibility. Confirm that the correct channel is selected, the intended title and description are present, and the preview is showing the same audio source you tested.
Listen for the points that a local OBS check can miss. YouTube may receive a different level from the one you hear through local monitoring. There may be a delay, a missing channel, a low voice level, or an unintended source that was not audible on the streaming computer. If possible, use a separate device or browser to check the viewer experience without feeding its sound back into the streaming computer.
Keep the preview open during the first public launch. YouTube recommends continuous monitoring of live audio and video quality, and the preview can show a change that is not obvious in OBS. If the stream is intended to run overnight, arrange a way to check it periodically rather than assuming that a successful launch means the player and capture will remain healthy.
If you plan to keep a public archive, confirm that your permission covers the replay as well as the live transmission. Live and on-demand uses can have different terms. If the station only authorised a live relay, do not leave an automatic archive available unless the rights holder has agreed to it.
YouTube’s Creator Music is not a general live-radio workaround. YouTube’s current guidance describes Creator Music usage for long-form videos rather than live streams, and its rights-holder guidance says paid licences were deprecated from 10 August 2026. Check the current terms and availability in YouTube Studio instead of relying on a music licence intended for another format.
If the main difficulty is keeping a local streaming computer awake, StreamNeo can remove that specific computer-running requirement by taking an uploaded video and running it as a YouTube livestream after you provide the stream key. It does not turn a station website player into licensed material, so rights clearance still comes first.
Troubleshoot capture and rights issues
The OBS meter does not move. Check that the station is playing on the same computer, that the browser or output device is not muted, and that the selected source matches the active device. Test a known permitted sound briefly to distinguish a station-player problem from an OBS configuration problem.
The meter moves but YouTube is silent. Confirm that the correct OBS scene is live and that the source is not muted in the active scene. Check the YouTube preview, not only local monitoring. A source can be audible to you through the computer while a different scene or output is being sent to YouTube.
The audio has an echo. Look for the same device configured as both a global audio source and a scene-level device source. OBS warns that duplicate capture can produce echo. Remove or disable one route, then test again with headphones or another controlled monitoring method.
Unrelated sounds are reaching the stream. You are probably capturing all desktop output. Close unrelated applications, disable notifications, or move to application-level capture if your operating system and OBS version support it. If application capture is unavailable, use a deliberately isolated desktop session and test the result.
The station player stops. Check browser sleep behaviour, login expiry, consent prompts and the computer’s power settings. A player that works for ten minutes may still stop when the computer locks or the browser changes focus. Do not disable security controls blindly; first identify what caused playback to stop.
YouTube shows a copyright warning. Treat it as a rights and platform issue, not merely an OBS error. YouTube may identify third-party audio during the live broadcast, and the result can progress from a warning to a placeholder, interruption or termination. Stop the stream if necessary, review the station’s permission, and ask the rights holder about allowlisting.
You have permission but the stream is still interrupted. Permission does not necessarily make YouTube’s automated detection aware of your channel. Ask the relevant rights owner whether your channel can be allowlisted, keep the documentation, and follow the current YouTube and rights-holder instructions. Do not tell viewers that a licence guarantees uninterrupted delivery.
You are considering “free” music instead. A label such as “free” is not enough to establish permission. YouTube’s guidance on finding safe music points to public-domain material or material used with permission from the copyright owner, while noting that claims can still arise. Check the exact licence and whether it covers live YouTube use.
For a channel that must restart after a connection failure, the technical recovery problem is separate from the audio rights problem. You can review how to make a 24/7 YouTube stream restart automatically after disconnecting, but an automatic restart should never be used to bypass a copyright notice or a permission restriction.
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
Does listening to the station online mean I can rebroadcast it?
No. Public access to a website player shows that the station has made listening available, not that it has granted you permission to retransmit the programming on YouTube. Ask the station and relevant rights holders for permission covering the live broadcast, territory and any archive.
Will YouTube flag radio audio during a livestream?
It may. YouTube scans live streams for matches to third-party content, and it may warn, show a placeholder, interrupt or terminate a stream. Even licensed audio may need the rights holder to allowlist your channel.
Should I capture all desktop audio or only the browser?
Capture all desktop audio when simplicity matters and you can isolate the computer from unrelated sounds. Capture only the browser or application when your operating system and OBS version support it and you want to reduce the chance of notifications entering the stream. Test either route in an unlisted stream before choosing it for public use.
Why does the station sound correct in OBS but not on YouTube?
Local monitoring and the YouTube preview test different parts of the path. Check the active OBS scene, source mute state, selected device and YouTube preview, then listen from a separate viewer device if possible. Also check for duplicate sources, because echo or cancellation can make the final result different from what you expect.