Google Drive stores your sermon video; OBS plays and loops it; YouTube receives the live output. To repeat one sermon, make the file accessible on the computer, add it to OBS as a Media Source, enable Loop, and connect OBS to the stream created in YouTube Studio.
For several sermons, use OBS’s VLC Video source to arrange clips in order and enable Loop Playlist. Do not rely on a Drive file being available just because it appears in your online account: prepare local access and test playback before the service.
How Drive, OBS and YouTube fit together
Think of the workflow as three separate jobs. Drive is where the video is stored and shared. The computer running OBS needs to be able to read that video. OBS then decodes and plays the file, repeats it if you configure a loop, and sends the resulting programme to YouTube Live.
This distinction matters because adding a Google Drive link to your plans is not the same as adding a playable file to OBS. OBS’s Media Source is designed to play a media file, and its Loop setting controls what happens at the end of playback. Drive does not set OBS’s loop behaviour. The OBS Media Sources guide documents the available source options and their properties.
The basic route is:
- Decide how the streaming computer will access the sermon video: download it, mirror it with Drive for desktop, or use a streamed Drive file that has been made available offline.
- Add the file to an OBS scene as a Media Source, or build an ordered list with VLC Video.
- Check the picture, audio and repeat behaviour in OBS.
- Create or open the YouTube Live event, enter its connection details in OBS, and confirm the preview before starting the broadcast.
Your computer and internet connection are part of this chain when OBS is the encoder. That makes the setup different from an arrangement where the computer can be switched off. If the computer must remain in use during a long-running service, plan for its power, network connection and updates; this church OBS update guide covers one interruption to consider.
Make the Drive video available to the computer
First find out where the file actually resides and what access mode the computer is using. Google Drive for desktop can stream or mirror files in My Drive. Streaming saves local disk space, but files that are only online require internet access, and Drive for desktop must be running for streamed files to be available. Mirroring keeps a local copy and allows offline access, at the cost of using storage on the computer. Google’s Drive for desktop instructions explain these modes and their requirements.
For a service where a file must play at a known time, arrange access before the service rather than relying on a fresh online fetch at the moment you need it. In streaming mode, use Drive for desktop’s offline-availability option for the sermon, then check that it is accessible. Alternatively, download a permitted copy into a clearly named local folder. With mirroring, verify that the file has finished syncing before you add it to OBS.
These choices have different practical costs. Streaming can be useful when local disk space is tight, but the Drive application, account access and internet connection remain relevant to online-only files. Mirroring or downloading uses storage, but gives you a file on the machine to select and inspect. Neither label removes the need to test the file in the actual playback setup.
| Access choice | Useful when | What to check before service |
|---|---|---|
| Stream from Drive | You want to reduce local storage use | Drive for desktop is running, the account is connected, and the file is available; online-only files depend on internet access. |
| Make streamed file available offline | You want to keep Drive’s streaming setup but prepare this file | Confirm the offline option has completed and that the file remains accessible through Drive for desktop. |
| Mirror My Drive or download a copy | You prefer a local file for OBS playback | Confirm the file is present, complete and has enough local storage behind it. |
Google says Shared Drives can only be streamed in Drive for desktop, so do not assume that a Shared Drive can be mirrored in the same way as My Drive. If your church stores sermons in a Shared Drive, check the current access method and test the specific file on the streaming computer. The Google guidance on streaming and mirroring is the place to confirm current behaviour.
Permissions can also affect preparation. A viewer or commenter may not be allowed to download a file if its owner has disabled downloads. Ask the owner or an administrator to provide an approved way to access the video rather than trying to work around the setting. Google’s download help page describes the relevant sharing limitation. If you do not control the file, resolve permission and access before building the OBS scene.
Add one sermon as an OBS Media Source
Open OBS and select the scene that will be used for the YouTube programme. In the Sources area, choose the add control and select Media Source. Give the source a useful name, such as “Sunday sermon”, so that it is recognisable if you later add an intro, a camera or other material to the scene.
In the source properties, choose the local file you prepared. If you are using Drive for desktop, select the file through the location exposed on this computer; if you downloaded it, browse to that copy. The exact path and dialog wording can vary by operating system and setup, so check the location rather than assuming it is the same on every machine.
OBS lists common built-in video formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM. A listed extension does not guarantee that every file will behave identically on every computer: the codec, file condition and installed playback components can matter. Google also cautions that Drive’s listed video formats do not all work on all devices. If OBS shows a black screen or no sound, test the file outside the scene and consider making a playback-ready copy in a format your system can handle.
Once added, inspect the preview. Check that the picture fills the intended canvas, that the sermon is not cropped unexpectedly and that the audio meter responds when speech is present. If the source is hidden behind another item or placed outside the canvas, it may be loaded correctly but not visible in the programme. A simple scene with the sermon as its only visual source makes the first test easier to interpret.
Enable looping for a single sermon
Open the Media Source properties and turn on Loop. OBS describes this option as specifying whether the file plays again after playback has completed. That is the setting that repeats one sermon; neither Drive’s storage mode nor YouTube’s event settings determine whether OBS starts the file again.
After changing the property, let the video run to its end and watch what happens. A file that reaches the end and stops usually points to the source’s loop setting or to the source no longer being available. Do not assume that seeing the first few seconds is enough: the end of the file is where the repeat behaviour is confirmed.
Consider what viewers will see at the boundary. A sermon that restarts immediately may return to its opening title, prayer or greeting. If you want an ordered service sequence, or a pause between talks, one looping file may not be the right structure. You can prepare a single edited programme file, or use an ordered playlist and test how the transition from the final item to the first item appears. Be clear about what the congregation and online viewers should expect rather than treating “loop” as an invisible setting.
If the video includes audio, monitor it through the end and the restart. Listen for a cut-off word, a sudden jump in volume or silence where you expected speech. A visual preview will not tell you whether the output audio is muted, routed unexpectedly or too loud. Make adjustments in OBS, then repeat the boundary check.
Build an ordered playlist with VLC Video
For several sermon files, add a VLC Video source instead of stacking separate Media Sources and managing each transition by hand. OBS’s source lets you add playlist items in the order you want them played. Choose each prepared file, arrange the list deliberately, leave shuffle off when order matters, and verify Loop Playlist in the source properties.
The VLC source depends on VLC being installed. OBS notes that the VLC installation architecture must match OBS: for example, 64-bit OBS requires 64-bit VLC. If VLC Video does not appear in the add-source menu, check that VLC is installed and that the architectures match before troubleshooting the playlist itself.
A useful order might be an opening notice, the sermon, and a closing prayer. The last item will lead back to the first when Loop Playlist is enabled, so decide whether that repeated opening is appropriate. If viewers join at different times, they may see any point in the cycle; avoid relying on a spoken announcement that only makes sense once at the start.
The default shown in OBS’s documentation is not a substitute for checking your own source. Open the playlist properties and verify both the item order and Loop Playlist. Confirm shuffle is off if the order is part of the service. Then play through the final item and observe whether the first item begins again as expected.
For planning a longer rotation, the playlist length guide offers a separate discussion of how a sequence affects a continuous channel. Its advice does not replace checking this particular OBS playlist: your files, transitions and intended order still need a local test.
Connect OBS to the YouTube Live event
Create or schedule the stream in YouTube Studio’s Live Control Room. YouTube’s encoder setup instructions describe the process and the details you need to connect an encoder. In OBS, open the stream settings and provide the server URL and stream key shown for that event, following the current instructions in YouTube Studio.
Treat the stream key as private. Anyone who has it may be able to send a broadcast to the associated event, so do not paste it into public notes or screenshots. If the key has been exposed, use YouTube Studio’s available controls to replace or reset it before relying on it again.
Start the encoder output from OBS and check the YouTube preview. The preview is a useful confirmation that OBS is sending the scene you intended, but it is not a substitute for watching the local source and checking the audio. For a scheduled event, YouTube’s workflow may require you to wait for the encoder preview and then select Go live in Live Control Room. Do not assume that connecting OBS alone has made the event public; confirm the event state in Studio.
If the goal is to keep the broadcast running without the computer, a desktop OBS workflow is not the same as uploading a file once and letting it play elsewhere. Here OBS is the software doing playback and encoding on the computer you configured. For other approaches to continuous output, compare the practical trade-offs in this OBS and FFmpeg overview; the right choice depends on whether you need a local production setup or a hands-off file loop.
Test playback and file availability before going live
Run a rehearsal using the same computer, Drive account, scene and network you plan to use. Open the file in OBS after a restart of the computer if practical, since that checks whether your chosen access path still works when you return to it. If you are using Drive streaming, verify that Drive for desktop is signed in and open. If you use a downloaded or mirrored file, confirm OBS points to the intended copy rather than an older file with the same name.
Test the entire loop boundary, not just the beginning. For one sermon, let playback reach the end and verify it starts again. For a playlist, watch the last clip finish and the first clip begin. Listen at the same time, because a video can loop correctly while its sound is missing, muted or unexpectedly interrupted. If a complete rehearsal is not practical, at minimum test the transitions that determine whether the loop is configured correctly and schedule a fuller check before the service.
Check what happens if the file becomes unavailable. For example, temporarily disconnecting from the internet is only an informative test if your Drive access mode makes that relevant and you can safely restore it before the event. An online-only file may stop being readable when the connection or Drive access is lost. Do not make an assumption based on a file appearing in the Drive interface: open and play it from the configured OBS source.
Google documents a maximum playback resolution of 1920 x 1080 for video played in Drive. That figure describes Drive playback, not a universal OBS or YouTube Live ceiling. Keep the distinction clear if you preview a file in Drive: it does not set the output resolution of your OBS scene. Google also notes that internet speed and quality can affect Drive playback, another reason to prepare the file and test the actual route you will use.
Write down the scene name, file location, access mode and YouTube event for whoever will operate the service. A small handover note can prevent someone from moving or renaming a file after OBS has been configured. If the church rotates volunteers, include where the stream key is managed without putting the key itself into a shared document. When the file and channel are ready, the next step is to choose how you want the broadcast operated.
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 loop a Google Drive video directly in OBS?
OBS loops a media source; Drive stores or exposes the file. Make the video accessible to the computer, add it as a Media Source, and enable Loop in OBS. An online-only file is not guaranteed to remain available or play reliably without the required connection and Drive access.
Do I need to download the sermon from Google Drive?
Not necessarily. You can use Drive for desktop, but streamed files that are online-only need internet access and the app running; you can also make a streamed file available offline. A downloaded or mirrored local copy uses disk space but gives you a file to inspect directly, subject to the owner’s download permissions.
How do I loop several sermons in a set order?
Use OBS’s VLC Video source, add the files in the intended order, leave shuffle off and check Loop Playlist. VLC must be installed, with its architecture matching OBS. Play through the last item during a rehearsal to verify the transition back to the beginning.
Why does OBS show a black screen or stop at the end?
Check that the selected file is present and playable from the computer, then verify the Media Source path and its Loop setting. For a playlist, check the VLC installation, item list and Loop Playlist property. File format, permissions and an online-only Drive access path can all affect whether playback continues as expected.