For one local podcast episode that should repeat, use OBS Media Source and enable Loop. For several episodes that should play in sequence and repeat, use VLC Video and enable Loop Playlist.
These are choices about playback inside OBS, not ways to start a YouTube broadcast. You still need to connect OBS to YouTube Live, and you should test source playback separately from the stream’s health and quality.
Playback source and live destination are different jobs
An OBS source decides what media plays in a scene. Media Source is designed for a file; VLC Video provides a playlist interface for several media items. OBS displays that source as part of your scene, alongside any artwork, captions or other elements you have added.
The destination is a separate part of the setup. OBS sends the finished programme to YouTube through an encoder connection using the stream URL and stream key supplied in YouTube’s Live Control Room. Adding a source, pressing Loop or loading a playlist does not create that connection or publish a live stream by itself.
Keeping these jobs separate makes troubleshooting more useful. If the episode does not repeat, inspect the source and its playback settings. If OBS shows the scene correctly but YouTube does not receive it, inspect the connection and stream health. If viewers hear or see a poor-quality broadcast, look at the encoding and upload conditions rather than assuming the source type is at fault.
The choice also does not determine whether your material is suitable for monetisation or whether you hold the rights to it. You remain responsible for having the necessary rights to the audio and video. YouTube’s monetisation policy discusses repetitive or mass-produced content as an inauthentic-content concern; that is a policy question, not a technical verdict on either OBS loop control.
Choose Media Source for one repeating episode
When the job is to play one episode file and start it again when it finishes, Media Source is the direct fit. Add a Media Source to the scene, select the local file, and enable Loop. OBS documents Loop as off by default, so check the setting rather than assuming a file will repeat automatically.
Media Source supports a range of common audio and video formats, including MP4, MOV, MKV, WebM, MP3, AAC, OGG and WAV. That list is not a substitute for a rehearsal with your actual file: container, codec, operating system and OBS version can all matter to whether a particular file plays as expected. If the source stays blank or has no sound, test the file in OBS before you build the rest of the show around it.
For a simple programme, this keeps the playback arrangement legible. You have one source to check, one file to replace when you prepare a new episode, and a visible Loop control. If the episode includes a video track, the source can supply it to the scene; if it is audio-only, you can design the scene around a still image or other visual material.
Think through what should happen if you hide the source or switch scenes. OBS documents controls such as restarting playback when a source becomes active and closing the file when it is inactive. Those choices affect playback lifecycle; they do not change the YouTube destination. Rehearse any scene-switching pattern you expect to use, especially if you want an episode to continue through a transition rather than start again.
If you need a queue of different episodes, Media Source is not a playlist manager. You could arrange a more involved scene or change files manually, but that creates extra operational steps and does not provide the same documented playlist controls as VLC Video. For a planned sequence, use the tool that presents the sequence directly instead of relying on a workaround.
Set up VLC Video for a multi-episode playlist
Use VLC Video when you want OBS to play a sequence of media items, such as several podcast episodes, and then return to the beginning. In the scene, add a VLC Video source and populate its playlist with the files in the order you want. The source uses VLC libraries for extended media support and requires VLC to be installed on the computer running OBS.
Before adding every episode, make a small test playlist with representative files. Confirm the order, check that both audio and video behave as expected, and look at the transition between items. A playlist that works with one file does not prove that every file in a larger folder will decode or have consistent sound levels. If the show depends on a particular sequence, keep an independent note of that order so you can compare it with the source after changes.
VLC Video also has visibility behaviour. OBS documents options for continuing, pausing or stopping playback while the source is not visible; the documented default is to stop when not visible and restart when visible. This setting is about whether the source is visible in the current OBS scene, not whether the OBS application window is on screen. If a scene change hides the source, the chosen behaviour can affect what the audience hears after you return.
Playlist editing during a live broadcast deserves its own rehearsal. The available documentation describes playlist playback but does not establish that every edit made during an active broadcast preserves uninterrupted playback. Do not assume a live update is seamless. Test the precise change you intend to make on a private or unlisted stream, or make playlist changes before going live if you cannot tolerate uncertainty.
For a more structured episode queue, see the guide to building an automated podcast episode queue. It addresses the scheduling side of preparing multiple episodes; it does not remove the need to check how your chosen OBS source handles the files and transitions.
Check Loop and Loop Playlist behaviour
The two controls sound similar but apply at different levels. Media Source’s Loop repeats the selected file after it reaches the end. VLC Video’s Loop Playlist repeats the playlist after the sequence has run through. In the documented VLC Video settings, Loop Playlist is on by default; check the actual source settings before relying on that default.
| Playback job | OBS source | Control to check | What repeats |
|---|---|---|---|
| One episode, again and again | Media Source | Loop | The selected file after it ends |
| Several episodes in a set sequence | VLC Video | Loop Playlist | The playlist after its final item |
| Several episodes, but no repeat | VLC Video | Turn off Loop Playlist if that is the intended behaviour | Nothing after the final item |
A loop setting does not repair a file that cannot play, add a missing audio track or guarantee that the transition between two episodes will sound smooth. It also does not tell YouTube to reconnect if OBS loses its encoder connection. Treat it as a narrow playback instruction and verify the result by watching at least one complete boundary: the end of a file and the beginning of the next pass or next episode.
For a podcast with spoken introductions or music at the end, that boundary is worth listening to rather than checking only the picture. A file can technically repeat while still creating an awkward pause, clipped ending or abrupt return to the opening. If a playlist is meant to feel like a continuous station, check the transitions among representative files, not only the first one.
If OBS stops a playlist after a scene change, the cause may be source visibility behaviour rather than Loop Playlist. The troubleshooting guide on OBS stopping a podcast playlist during a YouTube Live stream is relevant when playback changes as scenes or visibility change. Use it alongside the source settings, not as evidence that all playlists behave identically.
Install VLC and match the OBS bitness
Media Source does not state a VLC dependency. VLC Video does: VLC must be installed for the source to use its libraries. OBS’s documentation makes the architecture requirement explicit: 64-bit OBS requires 64-bit VLC. Installing a different architecture can leave OBS unable to use the VLC components, even though VLC itself appears installed on the computer.
Check which OBS build you are running, then install the matching VLC build from the official VLC download page. If you update or reinstall either application, verify the pairing again rather than assuming the previous setup still applies. This is a compatibility check, not a claim that one source will play more reliably than the other on every computer.
After installation, restart OBS if needed and add or reopen the VLC Video source. Confirm that the playlist appears and that a file plays in the preview with sound. If it does not, check the architecture pairing, file path and file playback before altering YouTube settings. Avoid changing several parts of the setup at once; otherwise, you will not know which change addressed the problem.
Keep media files in a location that remains available to the computer running OBS. A playlist that points to files on a removable drive or a temporary folder can fail if that location is unavailable. For a computer that must stay on overnight, check that power settings, updates and local storage arrangements will not interrupt access. Those operating details sit outside the choice between the two sources, but they affect whether OBS can keep using the media you selected.
Connect the encoder to YouTube Live
Once playback works locally, configure the separate YouTube connection. In YouTube’s Live Control Room, obtain the stream URL and stream key for the broadcast, then enter them in OBS’s streaming settings. Follow YouTube’s current encoder setup instructions, since the controls and requirements can change.
Treat the stream key as a credential: do not show it in a screen recording or share it with people who do not need access. If you suspect it has been exposed, use the Live Control Room controls to manage it. The exact steps depend on YouTube’s current interface, so use its official guidance rather than an old screenshot.
Before a public broadcast, test the connection with the same sort of audio and video you expect to send. YouTube recommends monitoring stream health and messages during the event. A successful OBS preview only establishes that the scene renders on your computer; it does not by itself prove that YouTube is receiving a usable stream.
This distinction matters for an always-on channel. The source can continue playing while the encoder connection has a problem, and a healthy connection cannot make a broken local file play. If the computer must remain involved in the operation, plan for power, network interruptions, OBS updates and human monitoring. Do not infer continuity from a loop checkbox.
StreamNeo is relevant when the pain is keeping your own computer out of the overnight playback job: it turns an uploaded video into a YouTube-only 24/7 live stream after you upload the file and provide your stream key. That addresses a different operating arrangement from configuring OBS sources, so decide whether you need local scene production or simply a file that keeps playing to YouTube.
Test playback and stream quality separately
A useful rehearsal has two passes. First, test the source inside OBS: start the file or playlist, listen for sound, watch the image, and confirm the intended loop or playlist restart. Then test the whole encoder path on a private or unlisted stream, watching YouTube’s received preview and stream-health messages. A successful first pass does not substitute for the second.
For playback, include the details that often reveal a fault: the opening seconds, an episode ending, the transition to the next playlist item and a scene switch that hides or reveals the source. Check the source’s visibility behaviour against the programme you intend to run. If you are testing a playlist edit during a stream, treat that as a separate scenario and rehearse it privately because the documentation does not guarantee how live edits behave.
For transmission, use YouTube’s encoder settings page for the codec, resolution and frame rate you plan to send. YouTube’s current guidance recommends a two-second keyframe interval and says not to exceed four seconds; use the page’s settings table for the applicable format rather than copying a preset from a different setup. The recommended interval is an encoder setting, not a measure of how well Media Source or VLC Video handles a file.
Also consider whether your available upload bitrate can support the selected video settings. A demanding resolution or frame rate can be a poor fit for a constrained or variable connection, regardless of whether the source is a single file or a playlist. The practical comparison of constant and variable bitrate for streaming can help you understand that encoder decision; it should not be read as a source-selection rule.
Test with representative programme material rather than a short silent placeholder. Spoken audio, music, artwork and motion put different demands on the viewer experience. Listen at a sensible monitoring level and check YouTube’s received stream, because sound that is clear in the OBS preview may still be affected by the encoder path or the connection.
YouTube says streams under twelve hours are automatically archived. That is a platform fact, not a guarantee about streams longer than that, nor a promise that an archive will resolve a continuity problem. If you plan a long-running channel, check the current official guidance and decide how you will handle recording, interruptions and a restart rather than treating a local loop as an archive plan.
Make the choice around the show you run
If the schedule is one episode repeating until you replace it, use Media Source, enable Loop and rehearse its behaviour through the scene changes your show uses. It avoids adding VLC as a dependency solely to repeat one local file.
If the schedule is a sequence of episodes, use VLC Video, install the matching VLC build and confirm Loop Playlist and visibility behaviour. Make playlist edits before broadcast where possible, or test the exact live-edit workflow privately. The playlist feature makes a sequence easier to represent, but does not establish how any change will behave during an active stream.
If neither source matches the real job, reconsider the production shape before tuning encoder settings. For instance, a channel that needs scheduled episode changes may need a queueing workflow, while a channel that needs graphics and live scene changes may need OBS to remain part of the production. The guide to streaming software with virtual backgrounds is relevant if your programme includes camera composition as well as prerecorded material.
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 Media Source play more than one episode?
Media Source is documented around a selected media file, while VLC Video provides playlist support. For a sequence you want OBS to play as a playlist, VLC Video is the clearer fit. Test the files and order before relying on the sequence live.
Does turning on Loop start a YouTube Live broadcast?
No. Loop controls playback of a file inside OBS; it does not connect OBS to YouTube or publish a broadcast. You still need the stream URL and key from YouTube’s Live Control Room and a working encoder connection.
Does VLC Video require the same architecture as OBS?
Yes. OBS’s documentation says 64-bit OBS requires 64-bit VLC. Check the OBS build and install the matching VLC architecture, then confirm that the source can play your files.
Is looping podcast content automatically ineligible for monetisation?
The OBS playback setting alone does not answer a monetisation question. YouTube’s policy discusses repetitive or mass-produced material in relation to inauthentic content and viewer value. Review the current policy and consider the substance and rights of your own programme.