Google Drive stores your bhajan files; it does not send them to YouTube as a live broadcast. For a local setup, make the files available on a computer, play them in OBS using VLC Video source and Loop Playlist, then connect OBS to YouTube Live with the stream URL and key.
This workflow depends on the computer, files and internet connection remaining usable, so test it before treating it as an always-on channel. If you do not want a computer running continuously, YouTube’s encoder guidance also points to a cloud tool for prerecorded 24/7 streams; compare the practical trade-offs before choosing.
Install compatible OBS and VLC versions
OBS is the encoder in this workflow: it combines the bhajan programme and sends it to YouTube. The VLC Video source is an OBS source type that uses VLC’s media playback components to play files and playlists. Installing VLC separately matters; OBS may not show that source if it cannot find a compatible VLC installation.
Install a current OBS Studio release and VLC from their official sites. Match the architecture: a 64-bit OBS installation needs a compatible 64-bit VLC installation, and a 32-bit OBS installation needs compatible 32-bit VLC. If you installed VLC first and OBS still does not show VLC Video, check whether the applications have matching architecture, then restart OBS after correcting the installation. A mismatch is a common reason the source appears to be missing.
Use official download pages rather than bundled installers from third-party sites. OBS and VLC change over time, so follow their current installation guidance instead of relying on an old tutorial’s screenshots. You can first open OBS and confirm that it starts normally; then check the Sources panel’s add menu for VLC Video. If it is absent, resolve the installation mismatch before preparing the whole playlist.
OBS and VLC can play local media, but neither removes the need to keep the computer powered, connected and monitored. A local setup makes sense when you already have a machine and want direct control over the programme. For the separate question of local encoding load, see the discussion of hardware for a 24/7 YouTube playlist; that article’s 4K use case is not a requirement for a bhajan stream.
Prepare local bhajan media
Create a dedicated folder for the recordings and any still image or other visuals used in OBS. Use filenames you can recognise in a playlist, such as the song or programme name followed by a sequence number. Play each file on the same computer that will run OBS. A file visible in Drive is not necessarily ready for uninterrupted playback if it still depends on an online connection.
Install and sign in to Google Drive for desktop. Google documents two ways to access My Drive files: streaming and mirroring. Mirroring keeps files both in Drive and on the computer, which uses local disk space but makes them available offline by default. For a local playlist expected to run through a connection interruption, mirroring is often the simpler choice if the computer has enough space.
Streaming files use less local disk space because files are primarily kept in the cloud. Google says streamed-file access depends on Drive for desktop running; files are online-only unless you make them available offline. If you choose streaming mode, explicitly mark the source files or folder available offline and test playback with the machine in the state you intend to use for the broadcast. Google’s guide to streaming and mirroring Drive files explains those modes and their availability implications.
An external SSD can be a practical place for a local copy if the computer’s internal storage is limited. It is optional; choose storage based on the size of your library and keep a second copy of important source files if losing the only copy would disrupt the channel. Do not rename or move files after building the OBS playlist without checking the source paths again. OBS may no longer find media at the old locations.
Check that the sound level is comfortable and reasonably consistent from one recording to the next. If some songs are much louder than others, adjust the source files or OBS audio levels and listen to the transitions. A devotional sequence can sound abrupt even when every file plays correctly. The playlist is a programme, not merely a folder of audio.
Before using a recording, establish that you have the rights needed for the planned live use. A bhajan’s traditional subject does not by itself establish that a particular recording, performance, arrangement, lyrics or accompanying image is cleared. YouTube says live creators are responsible for the rights in their content, including music rights; review its live-streaming terms and seek permission or licensing as appropriate. YouTube also scans live streams for third-party matches, and a match can lead to interruption or termination. Do not assume a past upload, devotional purpose or credit line is permission to rebroadcast.
Add an OBS VLC Video source
Open OBS and create a scene for the live programme. In Sources, choose the add control and select VLC Video. Give the source a clear name, such as “Bhajan playlist”, so it is easy to identify later. If VLC Video is absent, return to the compatible installation check rather than substituting a different source and assuming it has the same playlist controls.
In the source properties, add media files to the playlist using the file browser. Select the local or offline-ready copies you prepared, not an online-only Drive preview link. Arrange them in the order you want the programme to play. If the source properties offer shuffle, leave it off when the intended order matters; use a deliberate sequence rather than relying on an accidental order.
Fit the visual output to the OBS canvas. For audio-only bhajans, you might use a static devotional image that you have permission to show, or a simple visual identifying the channel. Check that it fills the canvas without stretching important content and that no desktop windows or personal notifications can appear. Keep the scene uncluttered and inspect it in the OBS preview before sending it live.
If you are comparing ways to create a playlist on YouTube itself, note that a YouTube playlist is not the same thing as an encoder playlist of local files. This local method plays media in OBS; YouTube receives OBS’s programme feed. The guide to creating a YouTube playlist from videos on your channel covers a different feature that can help organise published videos, not replace the OBS source.
Load the playlist and enable Loop Playlist
In the VLC Video source properties, confirm that every intended file appears in the playlist and that the order is right. Enable Loop Playlist. This tells the source to return to the start of its list when playback reaches the end. It does not keep a broadcast alive by itself: OBS must remain running, the files must remain accessible, and the connection to YouTube must keep working.
Save the scene and source settings, then test a short sequence before adding the stream key. Watch the OBS preview and listen as one file ends and another begins. Confirm that the first item returns after the last if you have tested the full sequence. If an item is missing, check its path and local availability. If playback stops at the end, re-open source properties and verify that Loop Playlist is selected.
Avoid making an untested late change to the file names, folder location or VLC installation. If you need to update the programme, pause and test the changed list in OBS before using it on the live channel. For more detail on how playlist repetition can fail in a different service’s workflow, see troubleshooting a playlist that will not repeat on YouTube; its product-specific steps do not replace the VLC Video source setting here.
A continuous loop also needs human checks. Leave OBS open during a longer test, check that the audio continues after transitions, and confirm that the computer does not sleep or restart unexpectedly. No playlist setting can prevent a power cut, a device fault, a file access problem or a dropped network connection.
Create or schedule a YouTube broadcast
First check that live streaming is enabled for your YouTube channel. YouTube Help says a channel must be verified and have no live-streaming restrictions within the previous 90 days; its guidance also sets a minimum age of 16. First-time live streaming activation can take up to 24 hours, so do this well before the planned broadcast. Check the current YouTube live-streaming requirements because platform rules can change.
In YouTube Studio, open Live Control Room and create a stream or schedule one. Choose the visibility and details that fit your launch plan. An unlisted test can help you check the feed without presenting it as a public programme, but ensure you use the intended stream configuration when you are ready to publish. YouTube’s instructions for streaming with an encoder walk through creating the event and connecting an encoder.
YouTube provides a stream URL and stream key for the encoder connection. Treat the key as a credential: keep it private, do not paste it into screenshots or public messages, and reset it through YouTube if it is exposed. The URL tells OBS where to send the feed; the key identifies which YouTube stream configuration should receive it. VLC alone does not create the broadcast or send anything to YouTube.
Consider archive needs before choosing a continuous stream. YouTube’s encoder instructions say streams under 12 hours are automatically archived. A 24/7 broadcast is longer than that, so do not plan on one complete archive of the entire continuous programme. If separate replays matter, consider scheduled sessions and consult the current YouTube guidance before launch.
Connect OBS to YouTube Live
In OBS, open Settings and find the Stream section. Choose YouTube as the service if that option is available, then enter the stream key from the correct Live Control Room event. If OBS asks for a server or stream URL rather than handling the service choice for you, use the URL YouTube provides. Keep these details aligned with the broadcast you intend to test or publish.
Apply the settings and return to the main OBS window. Confirm the bhajan scene is selected, the VLC source is visible, and the audio meter responds during playback. Start the stream from OBS only when the YouTube event is ready to receive it. YouTube should show an incoming feed and preview in Live Control Room; allow time to check that it is the right scene and that sound is present before making it public.
Choose the output settings with your internet upload capacity in mind. YouTube recommends leaving headroom rather than using all available upload bandwidth, and the appropriate encoder settings depend on the selected output and connection. Do not copy a bitrate from an unrelated tutorial as a guarantee of stability. Check YouTube’s current encoder guidance and test from the actual internet connection and machine you plan to use.
If your primary need is to keep the computer switched off, a local OBS setup may not suit that constraint. YouTube’s encoder documentation lists Gyre as a cloud-based tool for 24/7 prerecorded-video streaming. That listing is not an endorsement or a comparison of current prices or guarantees; verify whether a service can access your files and meets your requirements. StreamNeo can remove the specific burden of leaving this local computer on by taking an uploaded video and running the YouTube broadcast from the cloud, while you still need to prepare the media, connect the channel and check the live result.
Test looping and stream output
Test before announcing the channel as continuous. In OBS, watch the preview, listen to the programme and confirm that the VLC source continues across file changes. In Live Control Room, check the incoming preview and stream health. Also open the watch page on another device, where possible, to confirm that viewers hear and see the expected output rather than relying only on the encoder’s local preview.
For a useful test, let playback cross several transitions and, if practical, the end of the list back to its first item. Check for silence, unintended gaps, an incorrect image, unexpectedly high or low volume, and a stopped source. This is a practical check, not proof that the setup will never fail. Repeat the test after changing the playlist, file locations, output settings, or network arrangement.
Plan who will notice a problem and what they will check. A local continuous stream depends on power, the computer staying awake, OBS remaining open, the files being readable and internet upload continuing. If the channel matters overnight, arrange a way to check it and a simple recovery routine: inspect the source, restart playback or OBS if needed, and verify the YouTube preview again. Keep the stream key private while doing so.
If the broadcast drops, diagnose the chain rather than repeatedly pressing Start. Check whether the local file is still playing, whether OBS has an output error, whether the computer has slept, and whether the internet connection is available. Then confirm Live Control Room’s status. Test the repaired setup before leaving it unattended. A loop option handles list repetition; it does not replace device, media and connection checks.
Choose the workflow that fits your operating constraints
The local OBS route gives you direct control over the scene and sequence, and it can use files already available from Drive. Its cost in effort is the need to keep the machine on, maintain local access to the media, protect the connection details and monitor the feed. A cloud route removes the requirement for your own computer to run the encoder continuously, but you must examine file access, service terms, controls and recovery behaviour yourself.
| Consideration | Local computer with OBS and VLC | Cloud prerecorded-video workflow |
|---|---|---|
| Source access | Drive-synced or offline files on the computer | Confirm how the chosen service accepts or retrieves files |
| What must keep running | Computer, OBS, media access and internet connection | The chosen service and its connection to the YouTube event |
| Playlist control | Set and test the VLC Video playlist in OBS | Check the specific service’s playlist and repeat controls |
| Main practical burden | Power, sleep settings, file paths and network checks | Service setup, credentials, current terms and monitoring |
| Best fit | You want local control and can leave a machine running | You do not want your own computer to run the broadcast |
There is no universal best choice. If you already have a suitable machine and want to observe the whole playback chain directly, local OBS may be easier to understand. If leaving a computer on is the part that makes the plan impractical, investigate a cloud workflow and confirm its current capabilities rather than assuming all services handle Drive files in the same way.
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 Google Drive itself stream my bhajans to YouTube?
No. Drive stores or synchronises the files, but an encoder must play them and send a live feed to YouTube. In this workflow, OBS is the encoder and VLC Video is the playlist source.
Why can’t I see VLC Video in OBS?
Check that VLC is installed and that its architecture matches OBS, such as 64-bit VLC with 64-bit OBS. Restart OBS after installing the compatible version, then check the Sources add menu again.
Will Loop Playlist guarantee a 24/7 broadcast?
No. It repeats the VLC source’s playlist, but the computer, OBS, media access and internet connection still need to work. Test the transitions and loop, then monitor the stream and have a way to respond if it stops.
Will YouTube save the entire 24/7 stream as one replay?
Do not rely on that. YouTube’s encoder instructions say streams under 12 hours are automatically archived, so a continuous broadcast longer than that should not be planned as one complete archive. Check current YouTube guidance and consider separate scheduled sessions if replays are important.