A 24/7 YouTube synthwave radio channel needs two things in place before you build an OBS scene: permission to use every track, and a YouTube channel that can go live. OBS can send a broadcast, but it does not grant music rights or prevent Content ID action.
The reliable order is to clear the music and allowlisting, verify live access, prepare the broadcast and scene, test privately, then launch with a recovery plan. Treat a 24/7 schedule as an operating goal, not a guarantee that one broadcast will run without interruption.
Clear music rights and Content ID allowlisting
Start with the catalogue, not the visuals. For every track, identify who controls the relevant rights and get permission for the uses you intend: a live YouTube broadcast, the territories where it will be available, and any replay or archived version. Keep written records that identify the track, rights holder, permitted uses, any attribution requirements, and the term of permission.
A file being downloadable, labelled “royalty-free”, or supplied with a creator pack is not enough to establish that it can be used in a continuous YouTube live stream. Read the actual licence and ask the rights holder or distributor whether continuous livestreaming and archiving are covered. If you plan to monetise, verify that use too rather than assuming a general licence includes it.
There is a separate operational step: ask each relevant rights owner or distributor to add your channel to its YouTube Content ID allowlist, and confirm that this has been done before broadcasting. YouTube scans live streams for matches to third-party content. Its copyright guidance for live streams says a licensed stream can still be interrupted if the channel is not allowlisted. A licence and allowlisting address different problems; neither is a promise that a stream cannot be interrupted.
Keep evidence of both permission and the allowlisting request or confirmation. If a track is claimed or a stream is interrupted, you will need to establish which track and rights owner are involved. A playlist assembled from several artists, labels or distributors may require separate clearance for each catalogue. Do not assume that one artist’s permission or one distributor’s process covers material controlled by another party.
Decide deliberately whether to keep an archive. YouTube says Content ID claims on an archived live stream may be made after the stream ends. Confirm that replay use is covered and check the resulting video in YouTube Studio after the broadcast. You can read more about the separate playback and continuity issues in this guide to running a prerecorded OBS livestream continuously.
If the rights holder cannot confirm that your channel is allowlisted, do not use that track in the live playlist while waiting. Substitute music whose permission and platform use you can verify. This is a practical risk decision, not a guarantee that another track will never receive a claim.
Verify YouTube live-stream access
Before spending time on OBS, check that your channel is able to stream. YouTube’s live-streaming access requirements say the channel must be verified and have no live-stream restriction during the preceding 90 days; the current help page also states that streamers must be at least 16. Check the current official page and the status shown for your channel, since access can depend on account conditions.
YouTube for Artists advises enabling live streaming at least 24 hours before the first planned broadcast. If this is a new channel or the first time you have streamed, do not schedule the public launch for the same evening you turn the feature on. Enable it early, then return to Studio and confirm the option to create a live stream is available.
YouTube offers horizontal and vertical live experiences, with differences in discovery and features. Horizontal is a straightforward starting format for a persistent radio visual that people may leave running on a television or desktop. Vertical can be worth considering if mobile discovery matters; YouTube for Artists describes vertical live streams appearing in the Shorts feed, while the general live-streaming format comparison explains that the experiences differ. Features can change, so verify what Studio currently offers before designing around a particular discovery route.
For an initial channel, choose one format and make the test match the eventual public stream. If you want both orientations, check whether dual streaming is available to your channel and what it means for the scene layout. A square album image with small text may look fine in a horizontal preview and become unreadable in a vertical crop.
Create the YouTube broadcast and stream
You need a YouTube broadcast for viewers to watch and an encoder feed from OBS to supply its video and audio. Prepare the broadcast in YouTube Studio’s Live Control Room, or use the YouTube connection workflow available in OBS. Interface labels change over time, so follow the current prompts rather than relying on an old screenshot. The OBS Project’s community-maintained YouTube setup guide can help explain the encoder workflow, but its exact controls may not match your installed version.
Set the title, description, audience setting, category and thumbnail with the actual stream in mind. Say clearly that this is a continuous synthwave music stream, and avoid implying that music is original or licensed unless you have verified that description. If you plan to run a private rehearsal, create a separate private or unlisted broadcast so that the test does not become the public launch by mistake.
In Studio, confirm that the chosen broadcast is the one OBS will connect to. If you create several tests, name them plainly, such as “audio test” and “launch rehearsal”, and check the selected event before starting the encoder. A correct OBS scene connected to the wrong broadcast can still produce the wrong result.
Choose intentionally whether the live broadcast is archived. Archive availability and retention are not something to build a plan around without checking current Studio behaviour and rules. If you do enable archiving, confirm replay rights for every track and review the result after the stream. If you do not need a replay, consider turning the archive option off where Studio permits it.
Build the OBS scene and audio source
A radio scene can be simple: a still image or subtle licensed animation, your channel name, and optionally a restrained “now playing” label. These are production choices, not YouTube requirements. Make sure you have rights to the artwork and animation as well as the music. If you have a loop with a visible seam or black frame, test the full cycle before going live; this guide to looping short clips without black frames covers a related visual problem.
Add the visual source in OBS and size it to fill the canvas without stretching. Then add the music as a media source, playlist source or other supported playback method appropriate to your setup. Test what happens at the end of a track and at the end of the playlist. The source should either advance or loop in the intended order rather than stop silently, repeat a single track unexpectedly, or leave an empty scene.
Set audio levels so that the music is audible but not clipping. Listen on headphones and on another device if practical; the OBS meter alone will not tell you whether the source sounds balanced to a listener. Watch for abrupt changes in loudness between tracks, long gaps, and duplicate capture paths that make the music louder or produce echo. For a focused treatment of levels, see how to stop audio clipping in a continuous YouTube stream.
If you use desktop audio capture, close notification-heavy apps and silence operating-system alerts. A private test can reveal a notification sound or a desktop source you did not intend to broadcast. If possible, prefer a clearly identified music source over capturing the entire desktop audio mix. Give each source a useful name in OBS so that another operator can see what is being sent.
Keep the scene legible at the intended viewing size. Large, high-contrast channel branding is more useful than tiny track text that cannot be read on a phone. Avoid changing the scene frequently just to make it look active; for a radio stream, a stable visual can be part of the format. Use your private rehearsal to check for cropping, black borders, unintended overlays and any artwork that has not been cleared.
Configure the encoder and stream key
In OBS, connect to YouTube using the available account integration or enter the stream key supplied by the matching YouTube broadcast. A stream key is access information for sending a feed to your channel: do not share it in screenshots, chat or public documents. If it may have been exposed, replace it in Studio and update OBS before the next broadcast.
Select an encoder and video settings that the computer and connection can sustain. YouTube’s current encoder recommendations are the place to check supported settings and any current limits; do not assume a setting from an older tutorial is still appropriate. For a static radio visual, a consistent modest output can be more useful than a higher-resolution setting that causes dropped frames or overloads the computer. Make the choice based on the machine, available upload connection and the needs of your artwork.
Set the audio output to a format supported by YouTube’s current guidance, then watch OBS’s status indicators during the rehearsal. If you see dropped frames, encoder overload or unstable connection warnings, reduce the load or resolve the network problem before opening the stream to viewers. A stream that appears to be sending is not necessarily clean: the Live Control Room preview and a separate listener check help catch problems at the destination.
Do not build your plan around a single broadcast having no maximum runtime, or around an archive being retained for a particular period. The official guidance cited here does not establish a universal uninterrupted runtime or a retention promise. Check the current YouTube Studio information before deciding whether your operating design depends on one long broadcast or on planned restarts.
Run a private test before launch
Make the rehearsal private or unlisted, not public. YouTube for Artists recommends an unlisted test, and Google’s live-streaming preparation checklist recommends testing the complete setup. Use the same computer, OBS scene, audio source, network path and broadcast workflow that you expect to use at launch.
Check the picture in Live Control Room and listen from another device. Confirm that the correct broadcast is selected, the audio is present, the image is stable, and the title and thumbnail are correct. Let the playlist play through a transition, not just the first few seconds. Listen for silence, clipping, uneven track levels, abrupt gaps and an unintended repeated track.
Check practical failure points while the test is still private. Let a track or playlist reach its end if possible, confirm loop behaviour, and verify that the audio does not stop when OBS loses focus. Look for notifications, mouse movement or other desktop elements. If you use a visual loop, watch it long enough to see its transition and confirm that no unlicensed artwork appears in an alternate scene.
Write down what you tested and what still needs attention. A short checklist might record the broadcast selected, audio source, loop order, OBS status, preview quality, rights confirmation and archive choice. Do not treat a green indicator or a successful test as proof of music permission: the rights and allowlisting work remains separate from technical readiness.
If the private stream receives a copyright interruption or claim, stop and investigate before making it public. Identify the track and rights holder, then confirm the licence and allowlisting status. Replacing a track may resolve the practical issue, but do not assume that a successful private test establishes what will happen in a later broadcast.
Launch, monitor and recover from interruption
Before launch, make one final check that the public broadcast has the intended title and visibility, the correct stream is selected, OBS is sending the expected scene, and the music rights and allowlisting records are in hand. Start the encoder and watch Live Control Room until YouTube shows the incoming stream as expected. Then check the public viewing experience on another device if practical.
A 24/7 label describes the intended schedule; it is not a promise that YouTube, OBS, the computer or the internet connection will stay live. Decide who will notice an interruption and how they will respond. Keep access to the channel and OBS machine available to someone who can check whether the encoder stopped, the network failed, the playlist ended or YouTube interrupted the broadcast.
Use a simple recovery sequence: check Live Control Room for the current state and any notices; check OBS for encoder or connection errors; check that the audio source is still playing; then restart the encoder or create a new broadcast only after confirming which event should be live. Avoid repeatedly clicking start without checking the state, since that can leave you uncertain about which broadcast viewers should open.
For a machine that must remain running, disable automatic sleep and plan around updates, power loss and network changes. If you operate OBS on a remote computer, the machine and stream must remain active after your remote session ends; this guide on keeping an OBS stream running after closing Remote Desktop addresses that specific operational concern. It is a separate hosting decision, not a substitute for checking the stream itself.
Schedule human checks of the playlist, audio meters, network and broadcast status. Keep a note of the time and nature of each failure and the action taken. That record helps distinguish a recurring playlist problem from an encoder or connection fault, and gives you a practical basis for changing the setup. Do not advertise a recovery time or continuity guarantee you cannot control.
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 stream music 24/7 on YouTube?
Clear the rights for every track and intended use, have the rights holders allowlist your channel through Content ID, enable YouTube live access, and set up the playlist, OBS scene and broadcast. Run a private or unlisted rehearsal before launch, then monitor the feed and have a restart procedure. A continuous schedule is an operating plan, not a guarantee of uninterrupted service.
Can I use copyrighted music in a YouTube live stream?
You can only use music when you have the necessary permission for the relevant broadcast and any replay use. YouTube scans live streams for third-party material, and its guidance says to ask the rights holder to add your channel to its Content ID allowlist when you have licensed material. A licence does not itself prevent interruption.
Will YouTube Content ID interrupt my live stream?
It can. YouTube says live streams are scanned for matches, and continued detection can lead to interruption or termination; an unallowlisted channel may be interrupted even when the streamer has a licence. Confirm allowlisting with each relevant rights holder, keep permission records and check Studio notices if a problem occurs.
Should I archive a 24/7 synthwave stream?
Choose based on replay rights and whether viewers need an archive, then check the current archive controls in Studio. YouTube notes that Content ID claims on archived live streams may occur after the stream ends. Review any archived result rather than assuming the live broadcast’s status settles the replay question.