Google Drive stores your video; it does not send that video to YouTube Live in this workflow. Download or otherwise make the file available on the computer running OBS, add it as a looping Media Source, then send OBS’s output to a YouTube stream.
Before depending on the broadcast, check that the local file plays with the intended sound, inspect YouTube’s preview, and watch its stream-health messages. That gives you a chance to catch a missing file, silent audio or unstable connection before viewers are relying on the channel.
Understand Drive’s role in the workflow
Think of the setup as three separate jobs. Google Drive holds the source file and lets you retrieve it, OBS reads and repeats a local media file, and YouTube receives the live output from OBS. The Drive player is not the encoder, and a shared Drive link is not a YouTube stream source in this method.
YouTube describes an encoder as software that converts video into a digital format for streaming. OBS is the encoder in this setup: its scene contains the video and any other sources you choose, and it sends the resulting programme to YouTube. The YouTube encoder workflow uses a stream URL and stream key from Live Control Room.
This distinction helps explain a common point of confusion: “How do I stream a video from Google Drive to YouTube Live?” The practical answer is to move the video from storage into a file OBS can play. You are not asking Drive to broadcast, and you do not need a special Drive-to-YouTube looping feature.
For one prerecorded clip, OBS’s Media Source is a straightforward fit. If you want a sequence of separate files, OBS also documents a VLC Video source with playlist controls; that route requires VLC to be installed and available. For a single repeated devotional recording, study ambience track or local information loop, start with one file and one scene rather than adding software you do not need.
Make the video available as a local file
In Drive, locate the video and download it to the same computer that will run OBS. Google’s Drive download instructions describe downloading a file to a computer. Whether you can do so depends on the owner’s sharing settings and any organisational restrictions. If the download option is unavailable, ask the owner for an authorised copy or access; do not assume a workaround will make a restricted file usable.
Choose a location you can find again, such as a clearly named folder for the channel’s media. Avoid moving or renaming the file after you have selected it in OBS, because the source may then point to a path that no longer exists. If the video is already stored locally, you can use that copy instead of downloading another one.
Before building the scene, open the file in a media player and check its beginning, a representative section and its ending. Confirm that the picture is the version you intended and that the audio is present at a sensible level. A video that plays in a browser from Drive may still fail to play locally if the download is incomplete or the file itself is damaged, so test the actual local copy OBS will use.
Pay attention to the shape of the loop. A clip that ends on a quiet musical phrase may repeat comfortably; one that ends mid-word or cuts sharply to its first frame can make the repetition obvious. OBS repeats the file when playback completes, but that does not guarantee a seamless transition for every recording. Listen across the end and beginning before you put the stream in front of an audience. For a more deliberate file-based looping workflow, the guide to using FFmpeg to loop meditation videos covers a different approach.
Add the file to an OBS scene
Open OBS and create or select a scene for the broadcast. A scene is the collection of visual and audio sources that OBS sends together. In the Sources area, use the add control and choose Media Source. Give it a name that tells you what it is, such as “Main video”, then select the local file you checked earlier.
OBS’s Media Sources documentation describes Media Source playback of local media files and its available controls. Check that the source appears in the preview at the expected size. If the video is smaller than the canvas or has a different aspect ratio, adjust its fit deliberately rather than stretching it until people or text look distorted. A devotional image with a title, for example, should remain readable and keep its proportions.
Check the audio meters while the source is playing. If the clip includes sound, OBS should show activity on the appropriate audio meter. If it is silent, first check the file in a normal player, then check that the Media Source is not muted and that OBS is capturing its audio. Avoid raising levels blindly; listen on the same output device your viewers are likely to hear through and make sure speech, music or ambience is not clipped.
Keep the initial scene simple. A single video source is easier to troubleshoot than a collection of browser overlays, extra audio inputs and several scenes. You can add a logo or text later, but first confirm that the one source plays correctly and fills the intended canvas. If your goal is a Hindi devotional rotation with OBS rather than one repeating file, see the guide to a Hindi devotional music loop with OBS.
Enable Loop for the video
Open the Media Source properties and enable Loop. This tells OBS to start the file again after playback reaches the end. The setting applies to the selected source, so check the correct source if your scene contains more than one video.
Test it rather than relying on the checkbox alone. Seek close to the ending or let the file play through, then watch and listen as it returns to the beginning. Look for a black frame, a pause, an audio click or a sudden change in loudness. The transition depends on the media file, so a visible or audible seam may call for editing the source file rather than changing YouTube settings.
For multiple separate clips, a playlist source is usually more suitable than placing each file as a Media Source and trying to manage transitions manually. OBS documents VLC Video as a playlist-capable source, with a Loop Playlist control; VLC must be installed for this source to be available. A playlist introduces another dependency and more items to check, so use it when you actually need a rotation. If continuous audio across separate videos is the main concern, the article on keeping audio playing between videos discusses that specific problem.
Create a YouTube stream and connect OBS
In YouTube Studio, use Create → Go Live to open Live Control Room and create a stream, or select the scheduled event you intend to use. Follow the encoder setup shown for that stream. YouTube supplies the server URL and stream key; in OBS, select YouTube as the service if that option is available, or enter the URL and key in the stream settings.
Treat the stream key as a password. Do not paste it into a public document, video description or screenshot, and do not share a screenshot of the OBS settings if it exposes the key. If you believe someone else has obtained it, use YouTube’s current controls to replace or reset it before broadcasting. The key connects your encoder to the stream, so using the wrong event’s details can send output somewhere other than the scheduled broadcast you meant to test.
YouTube notes that activating live streaming for the first time may take up to 24 hours. If the channel has never streamed, check eligibility and activation well before a planned event rather than discovering the delay at the start time. For a scheduled stream, use the encoder details associated with that event and confirm that the preview appears on the correct listing.
The outgoing stream also depends on the computer and its internet connection remaining available. OBS must stay open and streaming, the local file must remain accessible, and the connection must sustain the selected output. That is manageable for a staffed broadcast or a test session, but it matters if you expect a channel to run unattended overnight. A cloud option can remove the need to leave your own computer on; StreamNeo removes that specific unattended-computer burden by taking an uploaded video and running the YouTube broadcast without your computer left running.
Set a sensible output and test the preview
Use a stream setting that suits both the video and the upload connection. YouTube’s encoder settings and bitrate guidance recommends RTMPS and publishes different guidance for resolutions and frame rates. For H.264 at 1080p/30 fps, its table lists 5 Mbps minimum and 14 Mbps recommended; for 720p/30 fps, it lists 3 Mbps minimum and 8 Mbps recommended. These are YouTube’s ingestion recommendations, not a promise that your internet connection can sustain a chosen rate.
A higher resolution is not automatically better if the upload fluctuates. Choose an output your connection can maintain steadily, then make a test with sound and movement similar to the actual broadcast. YouTube’s settings guidance also covers CBR, keyframe interval and audio settings; check the current official page when setting these values, as recommendations can change. Do not treat a speed-test result as proof that a connection will remain stable through a long broadcast.
Start streaming from OBS, then wait for the preview in Live Control Room. Check the picture, listen for the expected audio, and read the stream-health status and any messages. If the stream is scheduled, use YouTube’s Go live control when the preview is ready and you intend to begin. Starting OBS and making the event public are distinct actions in this workflow.
A useful test is one that resembles the real programme. Leave the loop running long enough to observe a repeat boundary, check any scene or overlay you plan to use, and listen at normal viewing volume. For a local news loop, verify that text remains legible; for a music or ambience channel, check that the change from the end back to the beginning is acceptable. If the preview is black, confirm that the correct scene is active and the source path still works. If the video appears but the audio meter is inactive, troubleshoot the file and source before going live.
Plan for continuity and a deliberate end
An OBS loop repeats a file; it does not by itself keep a broadcast alive through every interruption. A sleeping computer, closed laptop lid, OBS crash, disconnected network or unavailable file can stop the output. If you are using a laptop, set its power behaviour so it does not sleep during the stream, keep it connected to power, and avoid relying on a lid-closed arrangement you have not tested. Check the channel during the broadcast rather than assuming that a successful start means it will continue unattended.
Decide how you will respond if the picture freezes or YouTube reports a problem. Keep the OBS project and source file easy to reach, know how to restart the encoder, and make sure someone can check the Live Control Room when the stream matters. YouTube’s health messages can help identify ingestion issues, but they do not remove the need to observe the actual broadcast.
When the event is finished, stop streaming in OBS and end the broadcast in Live Control Room as appropriate for the event. YouTube states that streams under 12 hours are automatically archived; do not assume the same outcome for a longer continuous broadcast. If you need a recording, keep the original file and check the archive after the stream rather than treating the live event as the only copy.
There is a practical trade-off between local control and hands-off operation. OBS gives you direct control over scenes and the outgoing programme, but the computer and connection have to remain available. A cloud playout route can be useful when that local requirement is the part you cannot reliably cover; a staffed, short event may be simpler to run from OBS. Check the chosen workflow’s current capabilities and terms before relying on it for a long-running channel.
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
How do I stream a video from Google Drive to YouTube Live?
Download the video, subject to its sharing permissions, to the computer running OBS. Add the local file as a Media Source, enable Loop, connect OBS to the YouTube stream details, then check the Live Control Room preview and stream health.
Can I livestream a prerecorded video?
Yes. In this workflow, OBS plays the prerecorded file and sends its output to YouTube as a live encoder stream. You still need to confirm that you have permission to broadcast the video and its audio, and check YouTube’s current requirements for your channel.
How do I make an OBS video source repeat?
Open the Media Source properties and enable Loop. Test the file’s ending and beginning because the setting repeats playback but does not ensure every clip will have a seamless picture or sound transition.
Can I use a Drive link directly as the OBS source?
This method uses a local media file, not a Drive link or Drive’s browser player. Download an authorised copy and select that file in OBS; if the owner or organisation prevents downloading, ask for access rather than assuming the link can be used as an encoder source.