A 24/7 OBS stream can appear to stop for two different reasons: the local media source has ended or changed, or OBS is still playing while the connection to YouTube is dropping frames. Check which of those is happening before changing files, codecs or hardware.
The usual causes are an unchecked loop setting, a playlist that has finished, source visibility behaviour during a scene change, or a connection problem between OBS and YouTube. You should also keep a local recording, because YouTube says streams longer than 12 hours may not be captured as an archive.
First establish what actually stopped
Look at OBS before looking at the YouTube page. If the video has stopped, frozen or gone blank in the OBS preview, start with the source and its playback settings. If the preview continues normally but YouTube reports dropped frames or a disconnection, the media may still be playing locally.
This distinction matters because the remedies are unrelated. A file that reaches its final frame needs a loop or playlist setting. A stream that is losing data on the way to YouTube needs an investigation of the connection or bitrate. Changing the media source will not repair an unstable route to YouTube, and changing the bitrate will not make a finished file start again.
Use a simple observation test during the next incident:
| What you observe | Inspect first | Next check |
|---|---|---|
| The video stops at the same point each time | Media Source or playlist settings | Check Loop or Loop Playlist |
| Playback changes after a scene switch | Source visibility behaviour | Keep the source visible while testing |
| OBS preview or recording freezes or goes blank | Local source and file path | Confirm the source type and file availability |
| OBS continues playing but YouTube reports dropped frames | Connection to YouTube ingest | Review OBS stream-connection guidance |
| The live broadcast existed but its archive is incomplete or absent | YouTube archive limits | Keep a separate local recording |
If you can reproduce the problem, note the approximate time, the scene that was active, whether the OBS preview changed, and what YouTube Studio reported. Those details are more useful than assuming that every interruption is an OBS playback failure.
Identify the source type before changing settings
OBS has different source types for a single local file and for a playlist. A Media Source is intended for local media files. A VLC Video Source provides playlist functionality and depends on VLC being installed. The controls you need for one source type do not automatically apply to the other.
Open the Sources panel and identify the source that is producing the video. Then open its properties rather than creating another source immediately. For a Media Source, confirm that the selected file still exists at the path shown in OBS. A file moved to another folder, renamed, disconnected from an external drive or unavailable after a restart can look like a playback failure.
For a VLC Video Source, confirm that VLC is installed and that each item in the playlist points to a file that is still available. OBS documents the relevant source types and their requirements in its media sources documentation. A playlist can therefore fail for a different reason from a single Media Source, even when both appear in the same scene.
Do not treat the source type as a minor detail. If you are checking the Media Source's Loop box while the scene actually uses VLC Video Source, you are inspecting the wrong control. Write down the source name and type before troubleshooting so that a later scene edit does not leave you testing a different item.
If you are building a devotional or bhajan channel from several prepared files, a playlist may be convenient. If you are repeating one long ambience video, a single Media Source has fewer moving parts. Neither choice removes the need to test the exact scene that will be live.
Check the end-of-file and playlist controls
A Media Source can reach the end of its file and stop unless Loop is enabled. In the Media Source properties, check the Loop setting and then test the source by allowing it to reach the end. A short test file makes this easier than waiting for a several-hour programme to finish.
Also check Show nothing when playback ends. That control affects what OBS displays after the media completes. It does not make the file repeat. A source can therefore be configured to hide at the end while still having Loop disabled, or it can be configured to loop while remaining visible between repetitions.
For a VLC Video Source, inspect Loop Playlist rather than assuming that the Media Source setting controls it. If the playlist reaches its last item without that option enabled, playback can stop even though the files themselves are valid. Check the order of the items as well, because a playlist may appear to stop when the actual issue is that it has reached its final entry.
A useful controlled test is to make a playlist containing two short, known-good files. Watch the handover from the first file to the second, then watch the point at which the second item should return to the first. If the first handover works but the playlist does not repeat, the problem is likely in the repeat setting. If an individual item fails during the test, inspect its path and availability separately.
Avoid adding a second copy of the same source as a workaround before you understand the setting. Duplicating sources can make scene visibility and audio routing harder to follow. First make one source behave correctly, then save the scene collection and test it after restarting OBS.
For a broader comparison of ways to repeat pre-recorded material, see this guide to how to loop a video on YouTube Live. The important point here is narrower: OBS must be instructed to repeat the local media, and a single-file loop is not the same control as a VLC playlist loop.
Review source visibility and scene changes
A source can behave differently when it becomes hidden. This commonly appears when you change scenes, use a transition, or switch to a temporary holding scene. The source may stop, pause, restart or resume when it becomes visible again, depending on its configured visibility behaviour.
Start by keeping the video source visible in one test scene. Do not change scenes while testing the file's loop. If playback remains continuous in that scene but changes when you switch away and back, the source visibility setting or scene arrangement deserves attention.
Then inspect the VLC Video Source visibility behaviour and choose the behaviour that matches your intended broadcast. A source that should continue from its current position needs different behaviour from a source that should restart whenever it appears. For a 24/7 channel, an unexpected restart can be mistaken for a stopped video, especially if the opening seconds are visually quiet.
Check whether the same source appears in more than one scene. A source can be present in a scene but hidden, or a scene can contain a different copy with a similar name. Rename sources clearly, such as Main playlist and Emergency holding video, and check the eye icon in the Sources panel before going live.
Scene changes are also a reason to keep the first test simple. Use one scene, one video source and the intended audio source. Once the media has passed its end-of-file test, add the other scenes one at a time. This helps identify whether the interruption begins with a scene switch rather than with the media itself.
If you run an OBS-based worship broadcast, the 24/7 worship stream setup guide is useful for thinking through the complete scene arrangement. For this particular fault, however, stay focused on what happens when the source becomes visible or hidden.
Separate dropped frames from ended media
OBS uses dropped frames to describe a streaming connection problem, not proof that a local video file has reached its end. OBS's stream-connection guidance attributes dropped frames to an unstable connection or a bitrate that the connection cannot sustain. Its stream connection troubleshooting guide is the right place to follow that path.
The practical test is to compare three views: the OBS preview, an OBS recording if one is running, and YouTube's stream-health information. If the local preview and recording continue but YouTube shows dropped frames, investigate delivery. If the local preview itself has stopped, return to the source, playlist and visibility checks.
A connection problem can make the YouTube picture appear frozen or intermittent while OBS continues to advance through the file. When the connection recovers, YouTube may receive later frames, which can make the incident look like a media jump. That is different from the local file ending at the same point every time.
Look for a repeatable pattern. A stop at the exact end of a file points towards Loop or Loop Playlist. A problem that appears during network congestion, after a disconnection notice or alongside rising dropped frames points towards delivery. If both occur, fix them separately rather than treating one as evidence of the other.
Do not infer a codec, operating-system or hardware-decoding cause from dropped frames alone. The available evidence does not establish one universal cause for 24/7 playback stops. Record the relevant OBS log and the source type if you need further help, because the operating system, OBS version and exact symptom can change the diagnosis.
Compare OBS with YouTube's preview
YouTube's preview is useful, but it is not a substitute for checking local playback. It shows what has reached YouTube, while OBS shows what the local scene is currently producing. A difference between them helps locate the break in the chain.
If OBS is blank and YouTube is also blank, begin with the local source. If OBS is playing and YouTube is behind, frozen or reporting dropped frames, begin with the connection and ingest path. If YouTube is playing but the OBS preview appears unchanged, confirm that you are watching the active scene and not a different preview or source.
During a controlled test, keep the YouTube Studio page open long enough to compare its status with the local preview. Note whether the issue is described as dropped frames, a disconnection or a different stream-health warning. Do not use a successful preview at one moment as proof that the whole night will be captured correctly.
YouTube also has separate behaviour for archives and DVR on long broadcasts. A live preview can look correct while the later archive is incomplete. That is why the preview comparison answers the question of delivery now, but not the question of whether you have a dependable recording for the whole programme.
If you are using a pre-recorded library rather than a single programme, the guide to building a linear TV channel from your video library can help with the wider programming model. For the immediate fault, use the preview only as one piece of evidence alongside OBS and the stream-health indicators.
Keep a local recording backup
A 24/7 broadcast should have a recording that does not depend on YouTube's archive. YouTube says that streams under 12 hours can be automatically archived, while a stream exceeding 12 hours may not be captured at all. It also says DVR capabilities may be limited or unavailable for streams longer than 12 hours. Check the current YouTube archive live streams guidance and DVR guidance before relying on either feature.
In OBS, use local recording alongside the live output when the computer has enough storage and processing capacity for both tasks. Choose a recording location that remains mounted after a restart and has room for the intended duration. An external drive can be useful for storing media and recordings, but it will not correct an incorrect loop setting, a hidden source or a connection failure.
Test the backup before the first overnight broadcast. Start a short stream and recording, stop both cleanly, then open the recording from beginning to end. Check that the picture and audio are present and that the file is written to the location you expect. A recording option that has never been opened is not yet a tested backup.
Separate the source library from the recording destination where practical. If the source files and the recording are written to the same unreliable or nearly full drive, one storage problem can affect both playback and the backup. Keep copies of important source files and confirm that the paths used in OBS remain available after the computer restarts.
For a more resilient local loop that must survive a reboot, you may also want to read about running FFmpeg as a systemd service. That is a different operating model from OBS, not a fix for the settings above, but the same principle applies: test recovery and keep a separate copy of the output.
If the main pain is leaving a computer running overnight, StreamNeo removes that particular local-computer task by letting you upload the prepared video, connect the YouTube channel and leave the broadcast running without keeping your own computer switched on. You still need to check the source material, channel permissions and the current YouTube requirements yourself.
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
Why does OBS stop when one video finishes?
A Media Source can stop when the file reaches its final frame if Loop is not enabled. Open the source properties, confirm the file path and enable Loop if the intended behaviour is continuous repetition. If the source is a VLC Video Source, check Loop Playlist instead.
Why does YouTube freeze while OBS keeps playing?
That usually points first to delivery rather than the local media source. Compare the OBS preview or recording with YouTube's stream-health information and investigate dropped frames, disconnections or a bitrate the connection cannot sustain. Dropped frames do not by themselves show that the file has ended.
Can changing scenes restart my video?
Yes, source visibility behaviour can affect playback when a source is hidden and later shown. Test the source in one scene without switching, then inspect its visibility behaviour and the scene copies. Choose a setting that matches whether the video should continue, pause, resume or restart when it becomes visible.
Is the YouTube archive enough for a 24/7 broadcast?
No. YouTube says streams exceeding 12 hours may not be captured at all, and DVR capabilities may be limited or unavailable for very long streams. Keep and test a local recording backup instead of treating the archive as your only copy.