If a video or other media source stops playing in OBS, that does not by itself show that OBS stopped sending the stream or that YouTube ended the broadcast. First identify which layer stopped; then adjust the control for that layer.
For a finite local video intended to repeat, enable Loop in the OBS Media Source properties. Use Restart playback when source becomes active when you need playback to begin again after a source is hidden or reactivated. These source settings affect playback, not YouTube’s auto-stop behaviour or the availability of the stream output.
Identify what actually stopped
There are three separate things to check: playback of a source within OBS, OBS’s streaming output, and the YouTube live event. They can fail independently. A video can reach its end while OBS continues transmitting a scene; OBS can lose its connection while the file keeps playing; and YouTube can end an event based on its broadcast controls even if the source itself behaved normally.
Start by looking at OBS’s streaming status. If it still indicates that streaming is active, but the picture is blank, frozen or no longer changing, inspect the scene and media source. If OBS reports a disconnection or shows a reconnect attempt, investigate output and network state instead. Then check the Live Control Room: does the event still show that it is receiving data, is it waiting for the encoder, or does it say the event has ended?
Do not infer the cause solely from a black preview or a media source’s status. A source can finish playback and leave a blank area in the composed scene, while other scene elements continue to show. Conversely, a scene preview in OBS does not prove that YouTube is receiving it. OBS’s overview of its controls describes Automatic Reconnect as an output-related control, while YouTube documents broadcast controls separately in its live stream settings.
Write down what each application reports before changing anything. Note which scene is active, whether the source is visible, whether OBS says it is streaming, and what the Live Control Room reports. If a scheduled event is involved, also confirm whether it has been taken live; an encoder preview and a published live event are not necessarily the same state.
Check the media source’s playback properties
For a local file added as an OBS Media Source, open that source’s properties and confirm the file path and the relevant playback options. If the source points to a file that was moved, renamed or stored on a disconnected drive, playback can fail because OBS cannot access the expected media. Looping cannot fix a missing or unreadable file, so first make sure the selected file is available and plays correctly.
The Show nothing when playback ends property is easy to misread. It controls what OBS displays for that source after the media reaches its end. It does not tell YouTube to end the broadcast. If the option is enabled, the source can disappear from the composition when playback completes; if it is disabled, the last frame may remain visible. Either result concerns the source’s display, not the live event’s start or stop state.
Likewise, Close file when inactive is about the media file’s handling when its source is hidden or not active. Closing it can mean OBS needs to load it again when the source returns, which may introduce a delay. If the file is on a slow or removable drive, test that return path instead of assuming it will be instant.
OBS distinguishes a Media Source from a VLC Video source, which has playlist-oriented controls. If your scene uses VLC Video, check that source’s playlist and visibility behaviour rather than looking for every Media Source property in the same place. OBS notes that VLC Video requires VLC to be installed, and that 64-bit OBS requires 64-bit VLC. For a scene built around a list of clips, the guide to looping an OBS playlist for a continuous stream may help you distinguish playlist settings from a single file’s playback settings.
Enable Loop for finite media that should repeat
If the source is a finite local video and you expect it to play again each time it reaches the end, enable Loop in the Media Source properties. This is the direct setting for repeating that file. It does not extend the file, restore a source OBS cannot read, or control whether the encoder remains connected.
Consider the viewing experience as well as the setting. A short video with an abrupt cut from its final frame back to the opening frame will repeat as configured, but viewers may notice the transition. A longer devotional recording, an ambience scene or a recorded lesson may loop more naturally, depending on its ending and beginning. Preview the transition in OBS and make sure overlays, captions or scene elements do not make the restart look like an unintended interruption.
Loop is not a general answer for every kind of source. It applies to finite media that has an end; it cannot make a remote feed available when its provider is offline or repair a missing local file. For multiple files, use the playlist features of the source type you have chosen and test the transition between items. A playlist that completes, pauses or changes visibility according to its own settings is a different case from one Media Source reaching the end of one file.
If you run an archive of talks or songs, consider how repeated material will appear to viewers and whether the sequence makes sense from any point of entry. The practical question is not only whether playback continues, but whether the resulting scene is still the programme you meant to broadcast. A guide to streaming a Hindi podcast archive on YouTube Live can offer useful context for planning an archive-based schedule, though its subject does not change the OBS controls described here.
Use restart playback when a source becomes active
Restart playback when source becomes active addresses a different situation from Loop. It tells OBS to start the media again when the source becomes active in the scene. This can be useful when a source is hidden, a scene is switched away from and later returned to, or a source is otherwise made visible again. It is not a command to keep replaying a file continuously while the source remains active.
Think through the intended scene behaviour before enabling it. Suppose a channel alternates between a host scene and a recorded devotional segment. If you want the segment to start at its opening whenever that scene returns, restarting on activation may be appropriate. If you want the segment to resume where it left off, that restart behaviour may be undesirable. If the recording should keep repeating while the scene stays live, Loop is the relevant setting; in some cases you may use both settings, but they solve distinct playback needs.
Visibility matters. A source hidden behind another scene element or moved off the active scene may be treated differently from a source that remains visible. Combine restart behaviour with Close file when inactive only after testing the actual transitions: closing an inactive file and restarting it on return may produce a fresh start, but the file still needs to load successfully. For remote media, activation cannot make an unavailable remote resource come back online.
If the source is meant to be a single announcement or a timed clip, restarting it every time the scene reappears could replay it unexpectedly. If it is a background loop, failing to restart on return could leave you at an unwanted point or without playback, depending on the other settings. Choose based on the behaviour you want when the scene changes, then observe a complete hide-and-return cycle.
Inspect OBS output and encoder state
When OBS indicates that its streaming output disconnected, source properties are not the fix. Check whether the stream is still active in OBS, whether a reconnect attempt is in progress, and whether the event is receiving data in YouTube’s Live Control Room. OBS’s Automatically Reconnect setting concerns an output connection interruption. It cannot restart a video file that has ended or make an offline remote source available.
A reconnect option is a recovery measure, not proof that a stream will stay online. Test it during a controlled session and watch what both OBS and YouTube report. If your stream depends on a computer, network connection or encoder workflow, the wider planning considerations in options for a 24/7 YouTube stream are separate from a source-level playback fix; they do not establish why a particular OBS output disconnected.
Also check the encoder workflow for a scheduled event. YouTube’s instructions for creating a live stream with an encoder describe connecting the encoder and managing the event. Depending on the workflow, the event may need a Go live action after the preview appears. If OBS is sending data but the event has not been started in the Live Control Room, changing Loop will not publish it.
If you use an encoder failover arrangement, test that workflow as its own procedure. YouTube recommends testing and monitoring stream health, including failover where it applies, in its live streaming tips. A backup encoder addresses a broader continuity question; it is not a specific cure for a local file ending or a scene source becoming unavailable.
Check YouTube Live Control Room auto-stop
YouTube’s auto-stop setting is a broadcast control, not a property of an OBS media source. YouTube explains that when the relevant encoder settings are enabled, you can start or stop streaming from the encoder. Inspect the auto-start and auto-stop selections in the Live Control Room for the event you are using. Do not assume they are off or on based on a different event.
In particular, reused stream settings can carry selections forward. If you duplicate or reuse an event, check its current settings rather than relying on what you remember selecting previously. YouTube’s documentation identifies auto-stop as a setting that lets the encoder stop the stream when enabled. That does not mean every source reaching the end causes YouTube to stop; it means the broadcast behaviour is governed separately and must be diagnosed from the event’s settings and status.
Turning auto-stop off is not a universal recommendation. The right choice depends on how you operate the event and how you want the encoder and broadcast to behave. If the event stopped, verify the current setting and consult YouTube’s official instructions for that workflow. Do not use a playback property as a substitute for checking the event itself.
For a small business loop or local news programme, a useful operating note can record the event type, the intended auto-stop behaviour and who is responsible for ending the broadcast. That is a simple way to avoid treating a reused event’s configuration as if it were a source-level setting. The OBS scene and the Live Control Room event should be checked independently whenever the outcome is unexpected.
Test playback and broadcast separately
Make a controlled test before relying on a changed setting overnight. Start with a short, known-good local file and a scene that contains it. Observe what happens when the file reaches its end, first with the intended Loop configuration. Confirm whether the source starts again, what the transition looks like, and whether the rest of the scene remains visible. This tests the media behaviour without making assumptions about YouTube’s broadcast controls.
Then test activation behaviour. Hide the source or switch to another scene, return to the original scene, and observe whether playback resumes, restarts or remains absent. If you have enabled Close file when inactive, allow for the file to load and check whether the first visible frame is acceptable. Repeat with the actual source type you use; a VLC Video playlist and a single Media Source do not have identical controls.
Finally, test the encoder-to-event workflow separately. Confirm OBS reports an active output and that the Live Control Room shows the event receiving data. If the event is scheduled, follow the applicable go-live steps. End or stop the test using the controls you intend to use in normal operation, and note what each application reports. Do not conclude that Loop keeps the broadcast online merely because the test file repeated successfully.
Keep a short troubleshooting record: source type and file, relevant playback properties, OBS output status, event status in YouTube, and auto-stop selection. That makes it easier to tell whether a later incident is a playback issue, a disconnected encoder, or an event-control issue. For channels that run long recordings, test after any change to the file path, scene collection, OBS version or event setup rather than assuming last week’s result still applies.
If the source is a remote stream rather than a local file, focus on whether that upstream source is available and whether OBS can decode it. Loop does not apply in the same way to a source with no finite file end. If you rely on a particular scheduled programme, keep a fallback scene or alternate content ready as an editorial choice, but recognise that a fallback scene is not a guarantee that OBS output or the YouTube event will remain active.
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
Does Loop stop YouTube from ending my broadcast?
No. Loop controls whether a finite media file plays again in OBS after it reaches the end. YouTube’s broadcast behaviour is controlled separately, so check the Live Control Room and the encoder workflow if the event ends.
Should I enable both Loop and Restart playback when source becomes active?
Use Loop if the file should repeat while the source is playing. Use restart-on-activation if playback should begin again when the source becomes active after being hidden or switched away from. Enable both only if both behaviours match your programme, then test a full scene transition.
Why does my stream stay live with a blank or frozen picture?
OBS may still be sending output while a media source has ended, gone blank or become unavailable. Check the OBS streaming status and the source properties, then verify that YouTube is still receiving data; a source display problem is not automatically a broadcast stop.
What if OBS says it is streaming but YouTube says the event ended?
Treat that as an event-control or workflow question rather than a Loop setting. Inspect the Live Control Room status, the event’s auto-stop selection and whether a scheduled event was taken live, then follow YouTube’s current official instructions.