Google Drive is a place to store and organise your video files; it does not send a live broadcast directly to YouTube. To loop a Drive video on YouTube Live, make the file available to the computer running OBS, add it as a Media Source, enable Loop, and send OBS’s output to a stream created in YouTube Studio.
For a stream intended to run for hours, use a downloaded or mirrored local copy where possible. A cloud-first file depends on the network and Drive being available during playback; a local copy takes disk space but remains available offline. Test the full path with an unlisted event before you make the channel public.
How Drive files reach OBS
A YouTube Live broadcast needs an encoder: software or hardware that sends an audiovisual feed to YouTube. In this setup, OBS plays the file on your computer and encodes that playback as a live feed. YouTube provides the stream’s server URL and key; OBS uses them to connect. The video may originate in Drive, but the encoder needs access to the actual media file as it plays.
The practical path is therefore Drive to the broadcasting computer, then OBS to YouTube. You can download a file through Drive, or use Google Drive for desktop to access it from your computer. Drive for desktop offers streaming and mirroring modes, but those modes differ in what is stored locally and whether the file can be available offline. We will compare them in the next section.
This is not the same as sharing a Drive link, adding a video to a YouTube playlist, or scheduling a YouTube Premiere. A live encoder continuously sends a signal. If playback pauses, the source disappears, or OBS stops sending, the outgoing live feed is affected even though the original file remains in Drive.
One clip is straightforward to loop with an OBS Media Source. If you want a sequence of bhajans, news segments, or study tracks, OBS also has a VLC Video source for a playlist. OBS notes that VLC must be installed for that source to be available. A playlist adds another dependency, so test the sequence in full before relying on it overnight. See the FFmpeg playlist looping guide for a different approach to repeating several files.
Download or make files available offline
First check that the Google account and computer you will use for broadcasting can access the intended file. If it belongs to somebody else, their sharing settings matter. A Drive file owner can disable downloads for viewers and commenters, so a file that plays in a browser may not be downloadable under your account. Ask the owner for an appropriate copy or access before building the stream around it.
For a one-off test, download the file to a known folder on the broadcasting computer. In Drive’s web interface, use the file’s context menu and choose the download option. Wait for it to finish, then open the downloaded copy locally to confirm that the file is complete and plays. The file picker in OBS will need to point to this local path, not to a page in Drive.
Google Drive for desktop is another route. In its stream-files mode, files are primarily stored in the cloud and accessed through the desktop environment; using a file can require an internet connection. In mirror-files mode, a full copy is stored on the computer as well as in the cloud, making it available offline. Mirroring uses local disk space. Check Google’s current instructions for streaming and mirroring files with Drive for desktop before changing how the Drive folder is handled.
For a long-running broadcast, prefer a completed download or a mirrored copy on the computer running OBS. This is a practical way to reduce dependence on a continuing Drive or network connection during playback; it is not a guarantee that the stream will stay up. A computer can still lose power, an encoder can fail, and the internet connection to YouTube can still be interrupted.
| File access method | What you gain | What to plan for |
|---|---|---|
| Downloaded file | The file is stored locally and can be played without contacting Drive. | You need enough disk space and must replace the local copy if the source changes. |
| Drive for desktop, stream files | Convenient access without keeping every Drive file fully on the computer. | File use depends on an internet connection and Drive availability. |
| Drive for desktop, mirror files | A full local copy is available offline. | Mirroring consumes local disk space; allow room for the video and other system files. |
If the video is large, check available storage before downloading or mirroring it. Do not assume that a file visible in Drive is already present locally. If you use Drive for desktop, confirm the relevant folder’s status in the application and test playback with the internet connection disconnected before the stream day. Treat that as a check of offline availability, not a promise about the rest of your broadcast setup.
Add a file as an OBS Media Source
Open OBS and choose the scene that should carry the loop. In the Sources panel, add a Media Source. Give it a useful name, such as “Main loop”, so you can identify it later. In the source properties, select the local video file you downloaded or mirrored. OBS lists MP4 among its supported video types, though a file’s extension alone does not prove that every codec inside it will play correctly.
Check the canvas after adding it. If the image is cropped, stretched, or smaller than expected, adjust the source transform to fit the frame while preserving the intended picture. Avoid changing the source’s proportions simply to fill the canvas; black bars can be preferable to distorted artwork or text. If your channel has a logo or a background layer, check that it does not cover important parts of the video.
Play the source through a complete check of the opening moments, a representative middle section, and the end. Listen for audio in the OBS mixer and confirm that the video is visible in the preview. A file that plays in a media player may still behave differently as an OBS source, so check the actual scene and output you intend to send. If OBS cannot select or play the file, verify that it is downloaded or mirrored, then check the format and try a locally available copy.
For a series of clips, add a VLC Video source and build its playlist rather than trying to make several independent sources switch in exactly the right order. Enable Loop Playlist if the sequence should repeat. VLC must be installed for OBS’s VLC source to work, so include that in your test. A single Media Source is simpler when the channel repeats one long programme or visual loop.
If the broadcast includes spoken introductions, prayers, or music, set the audio level before going live and listen on the same computer that will run OBS. The church audio-monitoring walkthrough explains a related OBS check for prerecorded material. Use headphones or another monitoring method to catch silence, clipping, or an unexpected desktop sound before viewers do.
Enable Loop
Select the Media Source and open its properties. Enable Loop, then save the source settings. OBS should return to the beginning of the file when playback reaches the end. Confirm this in the preview by letting the file reach its final frames and watching it restart. Do not infer that looping works merely because the source has started playing.
For a VLC Video source with several clips, the corresponding control is Loop Playlist. Confirm that the playlist reaches the last item and returns to the first. If one clip is missing, unavailable, or in a different folder from the others, the transition may not behave as you expect. Keep the files together in a stable location and avoid renaming or moving them after you have set up the source.
Looping the source does not create a permanent YouTube recording or a separate playlist on your channel. OBS repeatedly plays the local material while the encoder sends a live feed. If you stop OBS, lose the source file, or lose the connection to YouTube, the live broadcast can be interrupted even though the loop setting remains enabled.
Connect OBS to YouTube Live
In YouTube Studio, create or select an encoder stream using Create → Go Live. YouTube gives you a server URL and a stream key for the encoder. In OBS, open stream settings, choose the appropriate service configuration, and enter the URL and key. Follow YouTube’s current encoder-stream setup instructions if the Studio labels or workflow have changed.
Keep the stream key private. YouTube describes it as being like a password and address for your stream. Do not post it in a screenshot, send it in a public chat, or include it in a tutorial recording. If it may have been exposed, reset it in YouTube Studio and update OBS to use the replacement. The YouTube guidance on stream keys explains where to manage them.
YouTube says a channel must be verified and must not have had live-streaming restrictions in the previous 90 days to live stream. First-time activation can take up to 24 hours, so check eligibility well before the intended start rather than on the night you plan to go live. If the live option is unavailable, check the channel’s status and YouTube’s current requirements first.
For video settings, use the row that matches your output resolution, frame rate, and codec in YouTube’s encoder settings guidance. YouTube recommends RTMPS, H.264, constant bitrate (CBR), and a two-second keyframe interval, with the interval not exceeding four seconds. For H.264 at 1080p and 30 frames per second, its current guidance lists a recommended video bitrate of 5 Mbps. That figure is for that particular combination, not a universal setting for every stream.
Your internet upload connection must carry the encoded stream steadily. YouTube recommends leaving about 20% headroom over the selected bitrate. Check upload performance from the actual computer and network you will use, and avoid treating a speed test from another device or location as proof of the broadcast connection. If the stream health is poor, reduce resolution or bitrate and test again. The pixelation troubleshooting guide covers a related symptom that can arise when stream settings and available bandwidth do not match.
Test an unlisted event
Before going public, set the test stream’s visibility to Unlisted in YouTube Studio. An unlisted watch page is not a public listing, but anyone with its link may be able to view it, so share it only with people helping you test. Do not use a private stream if you need an ordinary viewer to open the watch page and check playback.
Start OBS and wait for YouTube Studio’s Live Control Room preview. Check that the right scene is being sent, that the picture is moving, and that audio reaches the preview. Then open the watch page on a second device or browser, preferably on a connection different from the encoder’s, and confirm that it plays for a viewer. This catches a problem that the OBS preview alone cannot: the preview can look right locally while the YouTube stream or watch page is not behaving as intended.
Make the test representative of the real broadcast. Include motion, a quiet section, the loudest audio, and a loop transition. Let it run long enough to see the source repeat if the planned programme is short, and check YouTube’s stream-health feedback while it is running. Verify that the beginning and end of the file are not abrupt or silent in a way you did not intend.
Use this rehearsal to check the practical details too: the file is available locally, OBS is using the expected scene, the stream key is current, and nobody needs to keep the broadcasting computer awake or interact with it for playback to continue. A test does not prove that a later long stream will be uninterrupted; it gives you a chance to find obvious access, playback, audio, and bandwidth problems before you announce the link.
Check long-running file access
Before leaving the broadcast unattended, confirm that the local file will remain in place and the computer will stay available. Do not move the video into another folder, rename it, sign out of Drive for desktop, or change account permissions after you have configured OBS without repeating the playback test. If you rely on a cloud-first file, do not assume it will remain available simply because it played once. A network or Drive access problem may affect it later.
A downloaded or mirrored copy is often the more practical choice for a stream that must continue overnight because playback does not need to fetch the video from Drive as it proceeds. Keep the copy on a drive with adequate free space and avoid disconnecting an external drive while OBS is running. This reduces one kind of dependency; it does not protect against power loss, operating-system updates, local disk failure, encoder problems, or a YouTube disconnection.
If you need a broadcast to continue when your own computer is switched off, a local OBS setup is not designed to do that: the computer is the encoder and must remain on and connected. StreamNeo can remove that specific burden when a Drive file is ready as a video to upload: upload it once, connect the YouTube stream, and the broadcast can run without your computer staying on. Keep the distinction clear: it is YouTube-only, and you still need to prepare the right file and stream details.
Decide how you will respond if the stream stops. Know where the Live Control Room preview and stream health are, keep the stream key somewhere private and accessible, and have the source file ready to test again. If you want to compare a local computer with an always-on approach, the overview of cloud options for continuous YouTube Live discusses the broader operating trade-offs. Choose based on who will monitor the channel and what you can maintain, not on an assumption that any arrangement guarantees uninterrupted service.
When you finish a test or a scheduled broadcast, stop it through YouTube Studio’s Live Control Room workflow and stop the encoder as directed. YouTube says streams under 12 hours are automatically archived; do not assume the same archive outcome for a stream that runs 12 hours or longer. If you need a recording, check the current YouTube guidance and verify the result in Studio rather than relying on an assumption about the loop or archive.
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 I stream a video from Google Drive directly to YouTube Live?
No. Drive stores the file; an encoder such as OBS must play it and send a live feed to YouTube. Make the file available to the broadcasting computer, then connect the encoder to a stream created in YouTube Studio.
How do I loop a video on YouTube Live?
Add the video as an OBS Media Source and enable Loop in its properties. For multiple clips, use a VLC Video source and enable Loop Playlist; test the end-to-start transition before going public.
Is a Drive for desktop stream file suitable for a 24/7 loop?
It may work while Drive and the internet connection are available, but cloud-first access depends on them. For a long-running loop, a downloaded or mirrored copy is a practical way to make the source available offline, although it cannot guarantee that the broadcast itself will stay up.
Does YouTube automatically save a long live loop?
YouTube says streams under 12 hours are automatically archived. Its guidance does not establish the same archive outcome for streams of 12 hours or longer, so check the current official information and confirm the recording in YouTube Studio.