You can make an always-on YouTube stream from videos stored in Google Drive by making those files accessible on the computer running OBS, then sending an OBS playlist to YouTube Live. OBS does not provide a documented direct Google Drive playlist connection, so treat Drive as the place you organise or synchronise files, not as the playback source.
For one repeating video, use OBS Media Source and enable Loop. For several videos in sequence, use the VLC Video source and enable Loop Playlist. In both cases, test the files, sound and YouTube preview before you rely on a long broadcast; looping is a playback setting, not a guarantee that a stream will remain uninterrupted.
Make Drive files available to the streaming computer
Start by deciding where the actual video files will be read during the broadcast. OBS's documented media sources work with media files and playlists; they do not establish a Drive-native playlist feature. Put the files on the streaming computer in a location that remains accessible for the whole session. If you use Drive synchronisation, wait for the files to be available locally and check that they open before setting up OBS.
A cloud-only placeholder is not the same as a ready-to-play video. If a file is still downloading, the computer is offline, or a synchronised folder changes location, the source may fail when OBS tries to read it. Keep the files in a stable folder and avoid renaming, moving or replacing them after configuring the source. A useful check is to open each video in a desktop player from the exact folder you plan to use.
Make a simple inventory before building the playlist: filenames, intended order, approximate durations and any audio that needs checking. Use clear filenames such as aarti-morning.mp4 rather than several copies called final. If your sequence has multiple parts, numbering filenames can help you confirm the order when selecting them in OBS. Keep a separate copy of the source files if losing or changing the Drive copy would disrupt your channel.
For a home setup, consider what happens if the streaming computer restarts or loses access to its files. A locally available copy can avoid depending on a live download during playback, but it cannot prevent a power cut, operating-system update or network failure. Think through the computer's sleep and restart behaviour before leaving it unattended. This is particularly relevant if you are estimating whether a home computer can remain on, as discussed in running a 24/7 fireplace stream from a home PC in India.
Do not assume a change to a Drive folder will update an OBS playlist already in use. If you add a new file or change the order, reopen the OBS source settings, confirm the playlist contents and run a test. This makes your workflow repeatable: organise in Drive, prepare and verify accessible media, then explicitly update and test the OBS source.
Choose Media Source or VLC Video in OBS
Choose the source based on what you need to repeat. A Media Source is the simpler choice for one file that should play again from the beginning. VLC Video is intended for a playlist of items, so it is useful when you want several recordings to play sequentially and repeat as a group. The OBS Project explains the difference in its Media Sources documentation.
| What you want to play | OBS source | Useful when | Check before going live |
|---|---|---|---|
| One video over and over | Media Source | A single recording is the whole programme | Confirm the file path and Loop setting |
| Several videos in a set order | VLC Video | Episodes or clips should play one after another | Confirm VLC is installed, the file order and Loop Playlist |
To add a source, select the scene where the programme will appear, use the Sources panel to add the relevant media source, and point it to the prepared file or files. Names for controls can shift between software versions, so use the current OBS interface and documentation rather than relying on an old screenshot. Keep the scene straightforward: one main video source and the audio it provides are usually easier to inspect than a complicated stack of overlapping sources.
The VLC Video source depends on VLC libraries; OBS notes that VLC must be installed for this source to appear. If you cannot find VLC Video in the source menu, check the OBS documentation and your VLC installation rather than trying to force a Drive URL into another source. For only one video, Media Source avoids the playlist-specific setup.
If you are creating ambience with a changing visual, this choice may be one piece of a wider scene arrangement; see how to make a 24/7 rain stream with a changing background for that distinct use case. Do not add visual layers simply because OBS permits them: first make sure the underlying video and audio play reliably.
Enable looping for one file or a playlist
For a single video, open the Media Source properties and enable its Loop option. Confirm that the source points at the intended local file. If the video stops after one pass in a test, check the source's loop control and restart playback from the beginning; do not infer that YouTube will repeat it automatically.
For several videos, add them to a VLC Video source in the order you want them to play, then enable Loop Playlist. Check every selected entry. A playlist can contain a missing file, duplicate item or unintended clip even when its first video plays correctly. Review the sequence in the source settings and watch across at least one transition during your test.
A loop setting tells the source what to do at the end of media. It does not ensure a seamless transition, continuous encoder output or stable connection to YouTube. A black frame or a short audio break may come from the recordings themselves, their differing formats, or how the source changes between items. If the channel depends on uninterrupted sound, test transitions with headphones and adjust the source material rather than assuming the loop setting removes every gap. For sleep or ambience programming, preventing audio gaps in a looping sleep-sounds stream is a relevant separate concern.
Use a deliberate order. For example, a study channel might put a welcome slate first, then three lecture recordings, then a short break card before the sequence repeats. If that break card contains no audio, make sure the silence is intentional. A devotional channel may prefer continuous music, so check the end and beginning of each track for a pause or abrupt volume change. These checks are about the content files and transitions, not a promise of a perfectly gapless output.
When you edit the playlist later, save the change and run it again in OBS. A test of the old sequence does not validate the new one. Also avoid removing or moving source files while OBS is running; if a source loses its path, it may stop being usable until you select the media again.
Connect OBS to YouTube Live
Before configuring OBS, check that the channel can go live. YouTube's current help page says the channel must be verified and have had no live-streaming restrictions during the previous 90 days; review YouTube's live-streaming eligibility guidance in case requirements or the interface have changed.
In YouTube Studio, open the Live Control Room and create or schedule an encoder stream. YouTube provides a stream URL and a stream key for the encoder. In OBS, open the stream settings, choose the appropriate service or custom server configuration, and enter the URL and key in their corresponding fields. Follow the current instructions in YouTube's guide to creating a live stream with an encoder, since controls and available choices may change.
Treat the stream key like a password. It authorises an encoder to send video to the associated stream, so do not show it in a screen recording, share it in a public message or paste it into a public document. If you think it has been exposed, use YouTube Studio's current controls to reset or replace it and update OBS with the new key.
YouTube recommends RTMPS and publishes encoder guidance. Set the protocol and output options in OBS to match the current YouTube instructions, your available upload capacity and the quality of your source files. A higher output setting is not automatically better if the connection cannot sustain it. Avoid copying a bitrate or resolution from an old tutorial without checking the current documentation and testing the actual connection.
When the files, scene and connection are ready, start the encoder output and wait for the stream to appear in the Live Control Room preview. Follow YouTube's controls for starting the public broadcast. Keep in mind that sending a feed from OBS and making the event available to viewers are related but distinct steps in the Live Control Room workflow.
Preview picture and sound before viewers arrive
Use the OBS preview to check that the right scene is selected, the video is framed correctly and the source is moving. Then check YouTube's Live Control Room preview as well. A picture visible inside OBS only confirms what OBS is composing locally; the Control Room preview checks that YouTube is receiving the feed. YouTube's encoder setup and stream guidance describes the settings and preview workflow; consult the current version when preparing a stream.
Listen to the stream from a separate device if possible. Check the beginning, a transition and a point later in the sequence. This can reveal muted source audio, duplicated sound from another OBS source, clipping, an unexpectedly quiet recording or a pause between playlist items. Keep the monitoring device's volume at a sensible level and avoid judging audio only from the meters: meters show signal, not whether the content sounds right.
Check the picture at the format viewers will see. If a video is portrait, letterboxed or a different aspect ratio from the scene, decide whether that presentation is acceptable before going live. Do not stretch the picture simply to fill the canvas if that distorts text or faces. If the channel's materials have mixed orientations, changing video orientation for a live stream may help you plan the scene deliberately.
Run a private or otherwise limited test where the available YouTube options allow, or rehearse with a short session before a longer one. Verify that the file starts, the playlist advances, the loop returns to the intended beginning, and the output stays visible in the Control Room. You are testing a chain of dependencies: accessible media, OBS source behaviour, computer performance, internet connection and YouTube ingestion. A test cannot guarantee later continuity, but it can expose configuration errors while they are easy to fix.
Also review rights before broadcasting. YouTube says live streams are scanned for matches to third-party content, and a detected match can lead to a placeholder, interruption or termination. Having a file in Drive does not establish that you have the rights to stream it. Even licensed material may require the rights owner to allowlist your channel for Content ID. Read YouTube's guidance on copyright issues with live streams and check the status of any permissions directly with the rights owner.
Keep the live output under observation
An always-on broadcast depends on more than the playlist setting. The computer must remain powered and awake, the files must remain accessible, OBS must continue sending output, and the network must sustain the connection. A home PC can be a reasonable way to test or run a channel if you can monitor those dependencies, but do not treat a successful start as proof that the stream will survive every overnight change or interruption.
While live, check the YouTube preview and watch page periodically. Confirm that the current video is still moving, sound is present and the stream has not been interrupted or ended. If you cannot watch continuously, arrange a practical check-in routine and decide what you will do if the feed drops: reconnect OBS, inspect the source path, check the network, or restart the event in Studio as appropriate. Monitoring can help you notice trouble; it cannot prevent every failure.
For creators who do not want a personal computer to remain involved in an ongoing broadcast, StreamNeo removes the need to keep that computer switched on after the video and YouTube stream details are prepared: it runs an uploaded video as a YouTube live stream and monitors and restarts the broadcast if it drops. It is YouTube-only, so it is not a general output tool. Whichever workflow you choose, keep your source files and stream key organised and check the live result.
Think separately about the replay. YouTube says streams under 12 hours are automatically archived; do not assume a longer continuous stream will produce one complete replay. If a replay matters, review YouTube's current archive guidance and plan shorter sessions or another recording approach rather than relying on an unverified assumption. For a sequence built from recorded talks, streaming Hindi podcast episodes on YouTube 24/7 offers a related programming example, but the same need to check the live output still applies.
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 OBS play a playlist directly from Google Drive?
The OBS documentation describes media files and playlists, not a direct Google Drive playlist integration. Make the files accessible to the streaming computer, then select them as media in OBS. Check the paths and play the exact files before going live.
Should I use Media Source or VLC Video?
Use Media Source when you want one file to repeat, and VLC Video when several files should play in sequence and the sequence should loop. VLC Video requires VLC to be installed for the source to appear in OBS. In either case, verify that the media files remain accessible locally.
Does enabling Loop Playlist make the stream uninterrupted?
No. It controls what the source does when playback reaches the end of its playlist. The computer, files, OBS, network and YouTube connection can still fail, and transitions in the media can still have gaps. Preview the feed and monitor it while live.
Will YouTube keep a full replay of an always-on stream?
YouTube states that streams under 12 hours are automatically archived. Do not assume that a longer continuous broadcast will result in one complete replay. Check YouTube's current archive information and plan for replay needs separately.