Google Drive can hold your podcast files, but it is not itself a YouTube Live source. To broadcast episodes, make the media available to the computer running OBS, use OBS to play and encode it, then connect OBS to YouTube Live through Live Control Room.
That distinction matters when you are setting up an overnight or always-on channel. A folder or an arbitrary Drive share link is not documented as a native YouTube playlist or as a direct OBS media source; the practical workflow is Drive for storage, OBS for playback and encoding, and YouTube Live as the destination.
Understand the Drive-to-OBS-to-YouTube workflow
Think of the setup as three separate jobs. Drive stores and organises your episode files. OBS opens those files as media in a scene and turns the scene into a live encoder feed. YouTube receives that feed and presents it as a live broadcast.
This means the files must be available to the computer that is running OBS. If a file appears in Drive on your phone, or you can open a share link in a browser, that alone does not mean OBS can play it. The documented OBS workflow uses media available to OBS rather than treating a Drive folder as an input device.
A useful way to picture the chain is a folder of MP4 episodes made available on the OBS computer, a VLC Video source in an OBS scene containing those episodes in the intended order, and a YouTube broadcast connected with the stream URL and key shown in Live Control Room. OBS plays the programme; YouTube does not reach back into Drive to choose the next file.
The practical guide to video content management can help you think about naming, organising and maintaining a collection before you put it into a playlist. For a live broadcast, organisation helps, but it does not replace checking that every episode actually opens in OBS.
Before configuring anything, confirm that you have permission for the planned broadcast of each episode and any music, clips, images or other material in it. Uploading a file to Drive and adding it to a playlist do not grant streaming permission. Check rights for the use you intend; this is a practical check, not a conclusion about your legal position.
Make podcast media available to the OBS computer
Start by locating the files you want OBS to play. They may already be stored on the computer, or you may use a Drive setup that makes them available there. The important point is that OBS needs access to the actual media file. Do not assume that sharing a folder or copying its web address into a source field will work.
If you use Drive desktop syncing, check how the files are represented on your particular computer and account. A file that is online-only may not behave like a locally available file when OBS tries to open it, and the details can depend on your operating system and Drive settings. Verify the arrangement on your machine rather than relying on a universal instruction about Drive sync.
A safe preparation routine is to choose one episode, make it available to the OBS computer, and open it from OBS before preparing a long playlist. If OBS cannot open it, first check whether the file is downloaded or otherwise accessible, whether its path has changed, and whether the media format is supported. For a larger collection, use consistent filenames and keep track of where the accessible copies live.
Be cautious about moving or renaming files after building a playlist. A playlist entry refers to a file location; if the location changes, OBS may no longer find it. Before a long broadcast, revisit the source settings and check that all intended entries still point to accessible files. This is particularly useful when the files are synchronised from Drive, since changes in availability may not be obvious from the folder view alone.
For a channel with many episodes, a simple folder structure can reduce mistakes: separate ready-to-stream files from drafts, and use filenames that make the intended order apparent. This does not create a YouTube playlist automatically. It gives you a clearer set of media to add inside OBS, where you choose the actual playback order.
Choose an OBS Media Source or VLC playlist
OBS offers two relevant ways to play podcast media. A Media Source is suitable when you need one file in a scene, while a VLC Video source is designed to use VLC to play a playlist. OBS documents audio support for MP3, AAC, OGG and WAV, and video support for MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM. A container appearing in the list does not guarantee that every codec variant inside it will play correctly, so test the actual episodes in your installed software.
| What you need | OBS source to consider | What to check |
|---|---|---|
| One episode in a scene | Media Source | Confirm the file opens and the audio reaches the intended output. |
| A sequence of episodes | VLC Video | VLC must be installed; check playlist entries and transitions. |
| Repeat a playlist | VLC Video playlist controls | Confirm loop is enabled and the last-to-first transition works. |
| Rotate episodes unpredictably | VLC Video playlist controls | Check shuffle behaviour and decide whether that suits the channel. |
For a single file, add a Media Source to the scene and point it to the media available on the OBS computer. Inspect the source in the preview and listen to the programme audio. If the source is silent or displays no video, do not assume YouTube will fix it; troubleshoot the file and OBS scene first.
For multiple episodes, add a VLC Video source and build its playlist from the files you have prepared. OBS documentation notes that VLC must be installed for this source type. That dependency is worth checking before you plan a continuous channel around the playlist: the source should appear and play correctly in the OBS installation you will use.
OBS’s Media Sources documentation describes the supported source types and their controls. Use it alongside the controls in your installed OBS version, since the actual scene and source configuration still needs to be checked locally. For a channel that displays episode titles, an OBS playlist overlay guide may help you plan what viewers see, but an overlay does not replace verifying the source playlist.
Configure playback for the intended episodes
Decide how the channel should behave before adding the playlist. A podcast archive intended to run in sequence usually needs a predictable order. A discovery-style station may benefit from shuffle. A short selection that should repeat needs looping; a one-off programme may be meant to stop at the end. These are editorial choices, not settings that Drive or YouTube infer from the folder.
OBS’s VLC Video documentation lists loop playlist as on by default and shuffle as off by default. Treat those as documented defaults, not proof of how your particular source is configured. Open the source properties and check the options yourself. A scene may have been copied from an earlier setup, or someone may have changed a control without changing the files.
If order matters, add episodes in the intended sequence and inspect the list from top to bottom. If the list is shuffled, verify that the resulting behaviour is acceptable for the programme. For example, a channel that alternates a short introduction and a longer discussion may not work well with a random sequence. If you are using a playlist for a devotional or study channel, consider whether a transition between episodes needs a spoken introduction or a pause rather than an immediate jump.
Then decide what should happen when playback reaches the end. Looping returns to the beginning of the playlist; it does not necessarily create a seamless programme. The final seconds of one file and opening seconds of the next may contain silence, abrupt edits or differing loudness. Listen through the transition in OBS and adjust the media or playlist if it is distracting.
Test every file at least far enough to establish that it opens and that its audio and video behave as expected. Do not infer compatibility from the filename extension alone. OBS’s listed formats describe support at the source level, but codec variations and file-specific problems can still prevent clean playback. Make a note of any episode that needs conversion or replacement rather than discovering it during a public stream.
A useful overnight check is to start the playlist in OBS and observe a transition, then confirm that the loop or stop behaviour matches your plan. The guide to preventing audio and video drift in an FFmpeg YouTube loop stream addresses a different playback method, but it is relevant if you later use an FFmpeg loop and need to investigate timing drift. For this OBS workflow, begin with the source controls and the files themselves.
Create or schedule the YouTube stream
Once playback works locally, create or manage the broadcast in YouTube Live Control Room. If you have not streamed before, check whether live streaming is enabled for your channel. YouTube Help says first-time enablement may take up to 24 hours, so do not leave this step until just before a planned launch.
In Live Control Room, create or select the broadcast and use the encoder setup shown for it. The relevant connection information includes a stream URL and a stream key. Keep the key private: it is the credential OBS uses to send the feed to your channel. If you believe it has been exposed, use YouTube’s available controls to replace or reset it rather than continuing to use a public key.
The YouTube Help encoder setup instructions explain how to create a live stream with an encoder. Follow the current Live Control Room screen for the broadcast you are creating; the selected stream determines the connection details and status you should see.
Set the broadcast details deliberately. Choose an accurate title and description, audience setting and visibility for the intended programme. Scheduling gives you time to prepare the event listing, but it does not start OBS playback or confirm that the encoder is connected. Make sure the source is ready on the OBS computer and the broadcast is selected before you expect viewers to see the programme.
If you are using YouTube for a channel aimed at viewers in India, a local start time and a clear programme description can help people understand what is on. Once live, inspect whether viewers can find and watch the stream using the guide to checking whether a 24/7 YouTube stream is reaching viewers in India. That is an audience check after setup, not a substitute for confirming the encoder and playback first.
Connect OBS using YouTube’s encoder setup
In OBS, open the stream settings and enter the connection information for the broadcast using YouTube’s encoder setup. The stream URL and key are supplied for the YouTube stream in Live Control Room. Check that you have selected the right broadcast and copied the current details accurately; an old key or details from another event can send you into avoidable troubleshooting.
Use the ingest protocol and settings presented for the stream you created. For a basic encoder setup, there is no need to add a different protocol simply because you are streaming a playlist. YouTube also documents HLS as an ingestion option, but it has extra requirements, including TS segments and a rolling playlist with no more than five outstanding segments. YouTube notes that HLS has higher latency than RTMP because it sends segments rather than a continuous stream. Unless you have a reason to select HLS and can meet its requirements, use the setup shown for your chosen stream.
You can review YouTube’s HLS stream setup guidance if HLS is the protocol you intend to use. Do not copy settings from an unrelated example in place of the values shown for your stream in Live Control Room. Protocol and ingest configuration affect how OBS delivers the programme; they do not change where the files are stored or how the playlist is built.
Before connecting, check the OBS scene that will be sent as programme output. It should contain the intended Media Source or VLC Video source and any necessary audio sources. Confirm that the right scene is selected, especially if your OBS profile has several scenes for different programmes. A successful encoder connection can still broadcast the wrong scene, a blank canvas or silence.
When OBS is ready, start the stream from the encoder and watch the YouTube preview and status in Live Control Room. Follow the control-room prompts before making the broadcast public. If the preview is not right, pause and correct the local scene or encoder settings rather than assuming that viewers will see a different result once the event is live.
Test playback and stream continuity
A local OBS preview and a YouTube preview answer different questions. The OBS preview helps you check the selected scene and media playback. The YouTube preview and status help confirm what is arriving through the encoder. Check both before announcing a long-running broadcast.
Use a short, repeatable test checklist. Confirm the intended video is visible, programme audio is audible, the playlist advances as expected, and the end-of-list behaviour is correct. If the plan is to loop, watch the transition from the last episode back to the first. If the plan is a scheduled event, confirm that the YouTube broadcast is the correct one and that its status reflects the encoder feed you expect.
For a stream that is meant to run overnight, consider what can interrupt it. The OBS computer must remain able to play the media, the files must stay accessible, and OBS must remain open with the correct scene and encoder connection. A Drive sync change, a computer restart or an accidental scene switch can matter even if the playlist worked during a short daytime check. Set up the computer and file access for the conditions in which you will actually run the broadcast.
If a file goes missing, repair the file access or playlist entry in OBS. If the local preview works but YouTube receives no programme, inspect the encoder connection and the stream status. If YouTube shows video but no sound, check OBS audio routing and the source’s audio settings. Isolating the failure by stage is more useful than changing Drive, OBS and YouTube settings at once.
After the stream begins, monitor it long enough to see a representative transition and confirm that the broadcast remains as intended. There is no setting that makes a playlist immune to every file, computer or connection problem. A deliberate test gives you a chance to catch the issues you can see before viewers depend on the channel.
If keeping a computer on and checking that it stays available is the part of this setup you want to avoid, StreamNeo can take the uploaded video and run it as a YouTube live stream without leaving your own computer on. It is relevant when your programme is a file-based broadcast and the ongoing playback computer is the specific operational burden; the Drive-to-OBS workflow remains useful when you want OBS to control a multi-file playlist locally.
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 paste a Google Drive folder link into YouTube Live?
No. The workflow described here uses Drive for storage, OBS to play media available to the OBS computer, and YouTube Live to receive OBS’s encoder output. The sources do not establish a Drive folder as a native YouTube Live playlist or arbitrary Drive share links as direct OBS media sources.
Do I need VLC to play several podcast episodes in OBS?
OBS’s VLC Video source requires VLC and supports playlist controls such as loop and shuffle. For one file, Media Source may be more suitable. Test the actual episodes in the OBS installation you plan to use, including audio and transitions.
Will a Drive file that is online-only play in OBS?
Do not assume it will. The media must be available to the computer running OBS, and the behaviour of Drive syncing depends on your account and system configuration. Test a real episode from OBS before building a long playlist around it.
How long does YouTube live-stream enablement take?
YouTube Help says enabling live streaming for the first time may take up to 24 hours. Check your channel and Live Control Room well before a planned broadcast, and follow the current official instructions if your status differs.