Google Drive stores your Hindi music files; it does not send them to YouTube as a live broadcast. To keep a channel live, make the tracks available to a playback source, send that playback through an encoder such as OBS, then confirm the preview and start the broadcast in YouTube Live Control Room.
The practical path is therefore Drive storage → files available on the computer running playback → a looping file or playlist in OBS → YouTube’s live ingest and start workflow. Each part has a separate job, and you should test the whole chain before you announce a continuous station.
Understand storage versus live playout
A file in Drive is a stored file, not a broadcast. YouTube receives a live feed from an encoder: software that plays the media and sends its audio, and optionally video, to YouTube. If the computer or hosted playback setup stops supplying that feed, a Drive folder on its own cannot keep the channel live.
For a straightforward local setup, use a computer that can access the music files and run OBS for the duration you intend to broadcast. The files may have originated in Drive, but the playback step described here is for local files accessible to OBS. This guide does not assume that a shared Drive link can be pasted into OBS and played indefinitely. Confirm the current Google Drive desktop options for your operating system and make sure the chosen files are actually available to the playback computer before relying on them.
The complete workflow has two control points. OBS starts sending the feed; YouTube’s Live Control Room lets you check that it has arrived and start the public broadcast. A loop setting handles repeated playback, not the encoder connection or YouTube’s start action. For a broader introduction to the latter, see how to start a YouTube live stream.
Clear the music before building the station
Resolve music rights before you schedule a public stream. For every track, check that you have permission for public YouTube livestreaming, the intended territories, and the length or manner of use. A purchase, a download, a credit line, or a label such as “royalty-free” does not by itself establish that those rights cover a continuous live broadcast.
YouTube says it scans live streams for matches to third-party content. Depending on the match and rights holder, the stream may show a placeholder, receive a warning, be interrupted or terminated, or result in a strike. If you have licensed third-party music, ask the owner whether your channel needs to be allowlisted in Content ID. A licence alone may not prevent an interruption when the channel has not been allowlisted.
YouTube for Artists advises creators to verify the account and enable live streaming ahead of the planned broadcast, and to coordinate with a label or distributor before using copyright-protected music. Check YouTube’s live-stream copyright guidance and the YouTube for Artists guide to going live for current instructions. If the repertoire includes other people’s recordings, the separate question of reuse and monetisation also matters; see YouTube reused content policy for 24/7 live streams.
Keep a simple record of each track, its source, the permissions you hold, and any rights-holder response about Content ID. It will not substitute for permission, but it gives you something concrete to check when a claim or interruption occurs. If you cannot establish the rights for a track, leave it out until you can.
Make Drive files available to playback
OBS’s documented media sources work with local media. The bridge from Drive is to make the files available to the computer that will play them, then select those files from that computer in OBS. Do not treat a Drive URL as a verified, continuous playback source: the workflow here does not establish that OBS or VLC can play arbitrary Drive links, nor that a browser preview will remain available for a long-running stream.
Check Google’s current Drive documentation for the desktop app and your operating system before choosing how to access files. In particular, verify that the music is available offline or otherwise remains accessible without an interactive sign-in, and that the files you intend to use have completed any download or sync operation. The exact controls and behaviour can change, so avoid relying on a click path copied from an older guide. A file that is visible in a folder but still needs to download is not a reliable source for a stream that must keep playing.
Once available, organise the tracks in a dedicated folder and use clear filenames. For a devotional channel, you might group a morning bhajan sequence separately from an evening sequence, rather than placing every track in an unpredictable order. Keep an independent copy of the source files if they matter to you; a playback setup is not a substitute for a backup. Before going live, open several intended tracks from the playback computer and confirm that they play through to the end.
The number of files, file size, and available storage depend on your collection and computer. There is no single safe capacity figure to assume here. Check the free space and the access status of the actual files you plan to use, especially if the computer may restart or lose network access during a long session.
Connect OBS to YouTube with a URL and key
Enable live streaming for your YouTube channel and complete any account verification YouTube requires well before launch. YouTube for Artists recommends doing this at least 24 hours before the planned live stream, so do not leave channel readiness until the evening you intend to start. Check YouTube’s current account and live-stream requirements directly, since eligibility and interface details can change.
In YouTube Studio, create or configure a live stream using the encoder workflow. YouTube provides a stream URL and a stream key for the encoder. In OBS, open the stream settings and enter the connection details in the corresponding fields, following YouTube’s current encoder setup instructions. The URL tells the encoder where to send the feed; the key identifies the stream configuration. Treat the key like a password: do not publish it, include it in a screenshot, or send it in a public chat. If it is exposed, reset it in YouTube Studio.
The precise labels and screen layout in Studio or OBS may change. Follow the current on-screen instructions rather than assuming every account has an identical interface. If the stream key is missing or the live setup is not visible, resolve that before building the playlist; these stream-key troubleshooting steps focus on the YouTube side of the connection.
Do not confuse an encoder connected to YouTube with a broadcast already started for viewers. First the encoder sends a feed, then you check that YouTube receives it, and then you start the broadcast from Live Control Room. Keep the stream key private throughout that process.
Use OBS Media Source for one local file
For a single track or a long continuous recording, add an OBS Media Source and select a local file that you have confirmed is available. OBS documents support for common audio formats, including MP3, AAC, OGG and WAV, and offers a file-loop setting. Consult the current OBS Media Sources documentation if the controls differ from what you see.
A Media Source can be a useful first test because it keeps the playback chain simple: one source, one file, and a loop option. Enable the loop setting if you want the same file to repeat. Then listen to the audio in OBS, check that the source is not muted, and confirm that the level is sensible rather than clipping. These checks are about the feed you are sending; YouTube’s preview is still needed to verify what arrives at the other end.
For a station made from several bhajans, a single continuous audio file may avoid gaps between separate tracks, but it gives you less control over order and individual track changes. A file loop repeats the same recording, so it is not equivalent to a song library or playlist. Use a track only when you have the rights for its repeated use and its duration suits the channel.
Test what happens when the source reaches the end. Confirm that OBS begins again at the expected point and that the YouTube feed continues. A preview that looks healthy at the start cannot tell you whether a file will remain readable or whether a loop transition will behave as intended hours later.
Loop a file or VLC playlist
If you want to rotate through several local tracks, OBS can use its VLC Video source to play a playlist and repeat the playlist. This source depends on VLC being installed on the computer. Add the source, select or assemble the intended files in the playlist, and enable the playlist loop control. OBS’s source documentation explains the available controls; check it alongside the version of OBS you are running.
Choose the order deliberately. An ordered playlist makes a predictable sequence, which suits a themed devotional programme or a planned progression from softer to more energetic tracks. A shuffled order can make repeated listening feel less predictable, but it makes each transition harder to anticipate during testing. Start with ordered playback if you want to verify every file and transition, then decide whether shuffle serves your channel.
The VLC playlist source and a single Media Source solve different problems. A single file is simpler to test and repeats the same recording. A playlist offers variety and a chosen sequence, but each file becomes another item to check for access, format, rights, and audible transitions. Make sure the final item loops back to the intended first item, and listen for unexpected silence or a large change in level at track boundaries.
| Playback approach | Useful when | Check before going live |
|---|---|---|
| OBS Media Source with one local file | You want a simple repeated recording | The file is available, the loop works, and the repeated content is cleared for use |
| OBS VLC Video source with a playlist | You want several tracks in a chosen rotation | VLC is installed, every item plays, playlist order is right, and loop behaviour is tested |
| Local playback through OBS on a computer | You already have a computer that can remain in operation | Files stay accessible, the encoder remains active, and you can respond if the feed stops |
| Hosted encoder arrangement | You do not want your own computer to run playback continuously | Confirm its file access, reconnect behaviour, terms, and whether it meets your operational needs |
A hosted encoder is a category, not a guarantee that Drive integration or any particular operating behaviour exists. Verify a provider’s own documentation and terms before placing files or relying on it. If the tiring part of a local workflow is keeping a computer available and restarting a dropped feed, StreamNeo can remove that particular task by turning an uploaded file into a YouTube live stream that continues with your computer switched off; you still need to prepare suitable content and complete YouTube’s own live workflow.
Preview in Live Control Room, then start
Before the public launch, run a test with the actual files and playlist you intend to use. Start the encoder in OBS so it sends the feed to YouTube, then open the stream in Live Control Room and wait for the incoming preview. Check that the sound is present and recognisable, not just that a connection indicator has changed. YouTube’s encoder setup guide describes the connection and preview process; use the current Studio instructions for the final start action.
When the preview is ready and you have checked the title, visibility, and other stream details, start the broadcast in Live Control Room. Starting OBS alone does not make the stream public. This distinction is easy to miss when you are testing: the encoder can be sending a signal while the YouTube broadcast has not yet been started. Likewise, stopping OBS interrupts the source even if the Studio page remains open.
Check playlist transitions, not only the first minute. Make sure the next track begins, confirm that the last item returns to the start when looping is enabled, and listen for a silence, clipping, or a sudden level change. Test the feed after a source ends and after you stop and restart the encoder. A short rehearsal helps you find local file-access issues before viewers encounter them, but it cannot guarantee that the stream will never drop.
Keep the stream key private and have a simple response plan. Know where the playlist files live, how to restart the encoder, and how to confirm the new preview in Live Control Room. If the stream disappears, check both the local playback source and the YouTube connection rather than repeatedly changing unrelated settings.
Plan for a 24-hour operation and replay
A continuous broadcast has to keep supplying media to YouTube. With a local setup, that means the computer, source files, OBS, and network connection all need to remain available; a loop setting does not look after those conditions. You should test the setup for the kind of run you actually intend, and decide who will check it if the feed stops. There is no need to buy a particular computer or encoder solely on the basis of this guide; first check whether equipment you already have can run the tested workflow.
YouTube’s archive guidance says streams shorter than 12 hours can be automatically archived, while streams longer than 12 hours may not be captured at all. That is not a promise that every shorter stream will produce a complete replay. If viewers need to revisit the programme, keep local recordings or plan separate broadcasts, and check YouTube’s current archive and DVR guidance before setting expectations. A continuous 24/7 channel and a reliable complete replay are different requirements.
For a channel that needs uninterrupted presentation, plan how to respond to an encoder stop, a file becoming unavailable, or an internet interruption. Consider whether a person can monitor the stream and whether a restart should be manual. If complete archives matter more than one uninterrupted live session, shorter planned broadcasts plus separate local recordings may suit you better. The trade-off is more start and stop work, but you are not relying on a single very long stream to become a complete archive.
Before launch, write down the recovery sequence in plain terms: verify the files are accessible, check OBS playback and connection, confirm a new preview, then start the broadcast in Studio. Keep a local copy of content you need to preserve. Do not promise a particular level of availability or replay outcome based only on a successful test.
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 broadcast directly to YouTube?
No. Drive stores files; an encoder such as OBS must play media and send a live feed to YouTube. Make the files available to the playback setup, connect the encoder, and start the broadcast through Live Control Room.
Can I use one Hindi song on repeat?
OBS Media Source can loop a local file, but repeating a song does not establish that you have the rights to use it. Confirm permission for the intended livestream and ask the rights holder about Content ID allowlisting where relevant. Test the loop and transition before launch.
Will a 24-hour live stream always be archived?
No. YouTube says streams longer than 12 hours may not be captured at all, and shorter streams are not guaranteed complete archives. Keep a local recording or consider planned shorter broadcasts if replay matters, and check YouTube’s current guidance.
Do I need VLC for every OBS playlist?
You need VLC installed to use OBS’s VLC Video source for a playlist. A single local recording can instead be played with OBS Media Source and its loop setting. Choose the source that matches the playback you have tested.