A 24/7 YouTube lofi radio stream can be assembled with OBS Studio, VLC and a playlist of media you are authorised to broadcast. Add the playlist as an OBS VLC Video source, enable Loop Playlist, connect OBS to YouTube Live, and check the incoming preview before you go live.
Looping only tells OBS what to do when the playlist reaches its end. It does not keep your computer, power, internet connection, OBS process or YouTube ingest online, so plan for those separately if you want a channel to run unattended.
Check channel access and prepare authorised files
Before installing software, confirm that the channel can stream live. YouTube may require you to enable live streaming and wait for activation; its encoder setup guide says first-time activation may take up to 24 hours. Check the current status in YouTube Studio rather than leaving the activation step until the intended launch.
The playlist is not just a set of audio files. Decide what viewers will see as well: a static cover, a simple animation or a collection of visuals. Prepare media in a folder you can find again, give files clear names, and play them locally before adding them to OBS. Listen for silence, abrupt starts, clipped endings and unintended gaps. Those checks do not prove that a file will behave identically inside OBS, but they can catch basic problems early.
Most importantly, make sure your permission covers the use you intend. Lofi tracks can involve rights in both the sound recording and the underlying musical composition. A download page, attribution line or description such as “copyright free” is not itself proof that you may stream a track on YouTube. Keep the licence or written permission, and check that it covers live broadcast, territories, any archive or replay, and monetisation if relevant. Ask the rights holder whether your channel needs to be allowlisted in Content ID; YouTube says matches to third-party material can interrupt a live stream, including where a channel has permission but has not been allowlisted.
YouTube’s livestream terms put responsibility for the necessary rights on the person providing the live content. That applies to the music and to the visuals, not only to the audio. A track being safe to play locally does not mean it is cleared for a public live broadcast.
Copyright permission and monetisation eligibility are separate questions. YouTube’s channel monetisation policies apply to livestreams and say repetitive or mass-produced content may not be eligible. The policy gives collections of songs from different artists as an example that can fail even where permission exists. If monetisation matters to your plan, read the current policy and think about whether the channel offers original value beyond a repeating music playlist.
Install OBS and VLC with matching architecture
Install OBS Studio and VLC before building the scene. OBS’s Media Sources documentation explains that VLC must be installed for the VLC Video source to appear, and that 64-bit OBS requires 64-bit VLC. Match the architecture rather than assuming that having “VLC” installed is enough.
If you have already installed both and cannot find VLC Video in OBS’s source menu, check VLC’s installation and architecture first. Close and reopen OBS after installing VLC, then inspect the source list again. The point of using VLC Video is that OBS can use VLC’s playlist handling as a source; it is not the same as opening a playlist in the VLC desktop player and assuming OBS will broadcast it.
Keep the media files in a stable location. If you move or rename files after adding them to a playlist, OBS may no longer be able to locate them. A dedicated folder for the stream makes it easier to check what is scheduled and to recover the setup after an update or a restart. For a related local-workstation consideration, see this guide to lowering CPU use in an OBS playlist stream. It is useful to distinguish resource load from connection reliability: reducing CPU use does not repair an internet outage or restart OBS after a crash.
Add a VLC Video source and order the files
In the scene where the stream will run, add a new source and choose VLC Video. Give it a name you will recognise, such as “Lofi playlist”. In its properties, add the authorised files in the order you want them to play. OBS’s VLC source supports a playlist and playback controls, including the option to shuffle; choose a deliberate order if you want transitions or moods to follow a particular arc.
Test the first few transitions before relying on the full list. Check that each file opens, that sound is present, and that the change from one item to the next is acceptable for the channel. A playlist can be valid while still containing a file with a different loudness or an unexpected visual. If the stream uses audio-only music, decide whether the audience should see cover art or a subtle loop rather than a blank or distracting screen.
You can use a static image as the visual layer and keep the playlist as the audio/video source, but make sure the scene order produces the picture you intend. A practical companion is this walkthrough for a static image with continuous audio in OBS. Its subject is different, but the distinction between the visible artwork and the continuing audio source is useful when laying out a simple radio scene.
Enable Loop Playlist and build the scene
In the VLC Video source properties, enable Loop Playlist if you want OBS to return to the beginning after the last item finishes. This controls the playlist’s end behaviour. It does not create new content, reconnect OBS to YouTube, or keep the computer awake. Shuffle is a separate choice: use it only if a changing order suits the station, and verify the result rather than assuming that every track transition will feel coherent.
Build the scene from the viewer’s point of view. Put the artwork or animation in the composition, size it for the canvas, and check that it is not obscured by another source. If you use text, keep it legible at the size a phone viewer will see. The scene preview in OBS is a useful first check, but YouTube’s incoming preview is the more relevant confirmation of what is reaching the platform.
A playlist that repeats is not the same thing as a continuously available broadcast. The distinction matters overnight: the last track can roll back to the first while the computer is still vulnerable to a power cut, a system update, an OBS crash or a lost network connection. OBS’s loop option addresses none of those failure modes. If you want to understand a different local VLC arrangement, this guide discusses running a 24/7 YouTube channel from a PC with VLC.
Plan who will notice an interruption and what they will do. For a stream run from a home or small-business computer, that might mean disabling unattended updates during a scheduled run, checking the machine and connection before leaving it, and arranging for someone to inspect the channel if it drops. These are operating choices, not guarantees. The appropriate setup depends on your computer, operating system, network and tolerance for a break; no single machine or internet specification can be recommended without those details.
If you need the stream to continue with your own computer switched off, a cloud playout approach changes the operating burden: you upload the file once, enter the YouTube key, and the broadcast runs remotely, with monitoring and automatic restart if it drops. StreamNeo addresses the specific problem of a local computer needing to remain on, though it is YouTube-only and does not grant music rights or guarantee platform approval. Compare that approach with running OBS locally in terms of control, ongoing power and internet dependence, monitoring, recovery, and cost.
Check source visibility and playback behaviour
A less obvious check is whether the VLC source continues playing when it is hidden. OBS source visibility is controlled in the Sources list; clicking the eye can hide a source from the scene. In the VLC Video source properties, inspect the option for shutting down the source when it is not visible, and decide whether that behaviour fits your scene. If the playlist is hidden, switched off or placed in a scene that is not active, playback may not behave as you expect depending on the source settings.
This matters when you use scene changes or several scenes. A source that is visible in one scene but not another may stop or restart according to its visibility and shutdown behaviour. Before a long run, test the exact sequence you plan to use: start the playlist, change scenes or hide the source, restore it, and observe whether playback resumes, continues, or starts over. Do not infer the behaviour from the eye icon alone.
Also check that the VLC source is not muted in OBS’s Audio Mixer and that its audio is routed to the stream output. The source can be visible and moving while silent. Watch the mixer when a track plays, then listen to the YouTube preview on another device or through headphones. A meter moving in OBS confirms signal at that point in the chain; it does not confirm that viewers can hear it at a sensible level after YouTube receives the stream.
Enter YouTube’s server URL and stream key
Open YouTube Studio and create or select the live stream in the Live Control Room. YouTube’s encoder workflow provides a server URL and stream key. In OBS, open the stream settings, select the YouTube service or the appropriate current preset, and enter the provided details. Use the current YouTube preset where it is available rather than copying settings from an unrelated tutorial.
Treat the stream key as a password. Do not paste it into a public chat, screenshot, repository or stream overlay. If you think it has been exposed, replace or reset it in YouTube Studio and update OBS with the new key. Keep the key somewhere accessible to the person responsible for operating the channel, but not somewhere viewers can see it.
YouTube supports RTMPS, an encrypted form of RTMP over TLS; its RTMPS setup page explains the option. Follow the current settings shown for your stream rather than changing protocols without a reason. YouTube also documents HLS ingestion, but it has different requirements and higher latency than RTMP; it is not necessary to import HLS-specific settings into a standard OBS setup unless you have a particular reason to use HLS.
If the channel has never streamed before, allow for activation time before planning a launch. Once OBS is connected, start the encoder and wait for YouTube to receive it. The YouTube preview is a checkpoint, not a formality: use it to confirm that the platform is receiving the intended scene and sound before you select the action that makes the broadcast public.
Preview picture and sound before going live
Run a short private or unlisted check before announcing the stream. Confirm that YouTube’s preview shows the expected artwork or animation, and that audio is present at a comfortable level. Check a playlist transition as well as the opening seconds. A test that only confirms the first frame will not show whether a later file is missing or whether one track is much louder than the rest.
Watch OBS’s status and YouTube’s stream dashboard for warnings, dropped frames or ingest problems. If there is a warning, resolve it before treating the setup as ready. Then verify playback on a separate device or browser, since the preview in the production interface is not identical to listening as a viewer. Keep the check proportionate: the objective is to verify your scene, sound, transitions and incoming connection, not to claim that one successful test proves an overnight run will never fail.
Think about the archive separately from the live run. YouTube’s encoder setup guidance says live streams under 12 hours are automatically archived. A continuous 24/7 broadcast exceeds that duration, so do not assume that one uninterrupted day-long stream will produce a complete replay. Check the current Live Control Room behaviour, and if retaining the programme matters, plan separate recordings or shorter broadcasts and confirm the archive settings that apply to your channel.
You can also make a recovery note before the stream starts: where the media folder is, which scene is the intended live scene, where the stream key is managed, and what to check if OBS or the connection stops. Keep a person responsible for monitoring if a break would matter. There is no universal computer, storage product, internet speed or backup-power model for this workflow; requirements vary with your resolution, encoder settings, media, operating system and reliability 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
Does Loop Playlist make an OBS stream 24/7?
No. It makes the VLC playlist repeat when it reaches its end. It does not keep OBS running, restore a broken connection, prevent a power interruption or guarantee that YouTube will continue receiving the broadcast.
Do I need VLC installed to use VLC Video in OBS?
Yes. OBS’s VLC Video source depends on VLC being installed, and the architecture must match: 64-bit OBS requires 64-bit VLC. If the source does not appear, confirm that VLC is installed with the matching architecture and reopen OBS.
Can I use lofi music if I have permission?
Permission needs to cover the sound recording and composition for the uses you intend, including live streaming and any archive or monetisation. Ask the rights holder whether your channel must be allowlisted in Content ID, and remember that permission does not itself guarantee YouTube monetisation eligibility.
Will YouTube archive a full 24/7 stream?
Do not assume so. YouTube states that streams under 12 hours are automatically archived; a continuous 24/7 broadcast is longer than that. Check the current Live Control Room guidance and plan shorter broadcasts or separate recordings if you need a complete replay.