An OBS playlist that stops between videos can have a source problem or a stream problem. First check whether OBS is still showing and sending a scene; only then change the playlist, file or encoder settings.
If OBS continues to display the scene but the next video does not start, investigate the source and its files. If OBS output is missing or YouTube reports health errors at the same time, follow the encoder and connection path instead.
Check OBS output and YouTube stream health separately
The most useful first step is to observe the same transition in two places. Keep OBS visible on the computer and open the YouTube Live Control Room in another window or on another device. Note the approximate time when the current video reaches its end.
In OBS, look at the preview and the output indicator. Is the scene still present? Is the source visible? Does the audio meter continue to move? If the last frame remains on screen while OBS continues sending a picture, the outgoing stream may be healthy even though the playlist has stopped advancing.
YouTube may show a different symptom. Its stream health area can display status messages and errors with timestamps. Compare those times with the moment the video stopped. YouTube's live metrics guidance explains where to inspect stream health and status information in Live Control Room.
Use this simple distinction:
| What you observe | Where to begin | What it suggests |
|---|---|---|
| OBS preview continues, but the same video or last frame remains | Source and playlist checks | The media source may not be advancing |
| OBS preview goes blank or the scene disappears | OBS scene and source visibility | The source or scene may be changing state |
| OBS shows the scene, but YouTube reports dropped or unhealthy input | Encoder and network checks | The outgoing feed may be degraded |
| OBS and YouTube both remain healthy, but one file is skipped or stops | File and playlist checks | A particular entry deserves isolation |
Do not treat the first visible freeze as proof of a network failure. A local source can stop while OBS continues to send its final frame. Conversely, a stream can lose health while the local preview appears normal, so the YouTube status evidence matters too.
For a 24/7 channel, write down the source name, the video that was playing, the time, and what each application showed. A short record is more useful than repeatedly changing settings and losing the original symptom. This is particularly important for devotional replays, sleep music and local information loops, where the same transition may take hours to occur again.
Identify the OBS source type
OBS does not use the same source for one repeating file and a collection of files. An OBS Media Source is intended for an individual local media file and includes a Loop control for repeating that file. It is not, by itself, a multi-item playlist manager.
For multiple local items, OBS documents VLC Video Source as the playlist-oriented source. It can create a list from several files and includes a Loop Playlist control. This distinction is easy to miss when a scene has been copied from an older project or assembled from several different tutorials.
Open the Sources panel and select the item that should be playing. Check its source type and properties rather than relying on the name shown in the scene. A source called “night playlist” may still be a single Media Source, while a source called “video loop” may be a VLC Video Source.
| Option | Best fit | Important control or dependency | Main caveat |
|---|---|---|---|
| OBS Media Source | One local audio or video file | Loop repeats that file |
It is not a multi-file playlist source |
| OBS VLC Video Source | Several local playlist items | Loop Playlist; VLC must be installed |
Visibility behaviour can stop or restart playback when hidden |
VLC Video Source appears only when VLC is installed. OBS also states that 64-bit OBS requires 64-bit VLC. If the source type is missing, greyed out or behaves differently after an installation change, check that VLC is installed and that its architecture matches OBS before rebuilding the scene. The OBS Media Sources guide documents these source requirements and controls.
Do not switch source types simply because a transition looked poor once. First identify what you are using, then test the relevant controls. Replacing a source can also remove its crop, transform, audio settings and scene placement, creating a second problem that hides the first one.
If your wider project is a low-cost computer-based channel, the explanation in how to set up OBS for a 24/7 fireplace stream on a low-end PC may help you review the overall source layout without assuming that a more powerful computer is the answer.
Check playlist entries and media files
Once you have confirmed that the source is intended to handle a playlist, inspect the entries themselves. Look at the order, spelling and location of every file. A file that was moved, renamed or stored on a drive that is not currently mounted can make a playlist behave differently from the one you tested.
Start with a short local test list containing two or three files. Put the suspected entry in the middle rather than at the end. If playback stops after the same preceding file, remove that entry and test the remaining list. If the list advances when the entry is removed, test that file on its own in OBS and in VLC.
This does not establish that the file format is always the cause. It is an isolation method. The official OBS guidance identifies the playlist source and its controls, but it does not provide one universal file-validation procedure for every transition fault. Treat the result as evidence about your particular file and system, not as a general rule.
Check the following without changing several things at once:
- Does each playlist entry point to a file that still exists?
- Does the filename contain a changed extension, spelling or folder path?
- Does the suspect video open and play through in VLC outside OBS?
- Does it play through in OBS when used as the only item?
- Does the stop occur before the same item, during that item, or after it ends?
- Are the audio and video tracks present in the file you expected to use?
If an item fails alone, replace or re-encode that item using a workflow you understand, then test it again before adding it to the long playlist. Keep the original file so you can compare the result. Avoid deleting an item from the production list while the channel is live unless you have a separate tested scene ready.
File organisation matters for unattended streams. Keep the playlist and media library in stable folders, use clear filenames, and avoid relying on removable storage for the only copy of a live programme. An external drive may help you manage a larger library, but it is not a fix for a transition fault by itself. A file that is unavailable at runtime remains unavailable regardless of where the playlist is displayed.
For a recorded-video channel, this guide to making a YouTube live stream from recorded videos on a low budget gives useful context for organising the source material before it reaches OBS.
Review playlist and visibility settings
If the source is VLC Video Source, check whether Loop Playlist is enabled when the list should return to its first item after the final entry. This control concerns what happens at the end of the complete list. It does not by itself explain a stop between two particular files.
That difference matters. Enabling Loop Playlist may solve a list that reaches its final item and then remains there, but it cannot prove why an intermediate transition fails. If the stop happens before the last entry, return to the file-isolation test rather than assuming the loop control is the answer.
Next, check how the source behaves when it is not visible. OBS documents VLC Video Source with a visibility behaviour that defaults to stopping when hidden and restarting when visible. A scene change, source toggle or transition can therefore alter playback even when the playlist itself is intact.
Look at the eye icon in the Sources panel and at the scenes that contain the source. Confirm that the intended source is visible in the scene being sent to YouTube. Also check whether another scene contains a second copy of the source, because changing scenes can make it appear that a playlist stopped when OBS actually switched to a different source instance.
Choose the visibility behaviour that matches your production workflow. If the source should continue playing while another scene is briefly shown, a stop-when-hidden behaviour may not suit that design. If it should restart each time a scene appears, retaining that behaviour may be deliberate. The right choice depends on whether your channel uses one permanent scene, scheduled interstitials or several scenes for adverts, notices and programme blocks.
The OBS Sources guide is useful here because it explains source visibility, ordering and scene placement. Use it to confirm which source is actually in the active scene rather than changing the playlist repeatedly.
For a channel that needs to recover after the computer or power supply fails, this guide to restarting an ambient stream after a power cut covers a separate recovery problem. Automatic restart does not repair a source that stops at a file boundary, so keep those two issues distinct.
Test transitions in OBS preview
Before returning to an overnight broadcast, test the exact transition in OBS preview. Use a short list and remain present for the boundaries that have caused trouble. A local preview test lets you inspect the source without adding YouTube ingest, public visibility or network conditions to the diagnosis.
Keep the test controlled. Use the same source type, scene and visibility arrangement as the live setup. Do not test a new source in a different scene and then assume it represents the production scene. If the source is expected to remain visible, leave the eye icon enabled and avoid switching scenes during the boundary.
Watch both picture and sound. A video can change picture while its audio has stopped, or the source can be hidden while a different audio source continues. Note whether the final frame holds, the source disappears, the next item begins, or the playlist returns to the first item.
If a short list works, repeat it with the original entries one at a time. Add the longer library only after the small test is consistent. This takes longer than changing every setting, but it gives you a useful answer about where the behaviour changes.
You can also make a temporary test scene with only the playlist source. That removes browser sources, animated overlays and other scene elements from the picture. If the isolated source transitions correctly but the production scene does not, compare visibility, scene changes and system load instead of rebuilding the playlist.
Do not infer gapless playback from a successful preview. The documented controls allow a source to loop or move through entries, but they do not guarantee a seamless boundary for every file and every computer. A brief visual or audio change may be a property of the files, decoding, scene design or the system running OBS.
YouTube recommends previewing and monitoring a live stream before relying on it for an ongoing channel. Its live streaming tips for computer provide the platform-side guidance. Use the OBS preview to test the source, then use an unlisted or otherwise controlled broadcast when you need to check the complete path.
Check YouTube Live Control Room health
If OBS output remains present but YouTube reports a problem, move to the outgoing stream path. In Live Control Room, inspect the stream health and status messages around the exact time of the failure. Save the wording or take a note before changing the encoder.
YouTube's troubleshooting guidance points creators towards the encoder picture and sound, encoder errors, CPU load and outbound internet strength. The useful question is not whether the computer is old or new. It is whether the evidence shows a rendering, encoding or connection problem at the same time as the playlist symptom.
Check the encoder side for:
- a missing or frozen preview output;
- encoder warnings or error messages;
- unusual CPU or GPU load;
- audio that has stopped reaching the output;
- a connection that has weakened or dropped;
- changes that were made shortly before the incident.
If YouTube reports timestamped health errors while OBS is also showing a degraded output, investigate this path before editing the playlist. Check the outgoing connection, confirm the stream key and destination are still correct, and review the encoder's current load. Make one change at a time so the next observation remains meaningful.
OBS's encoding performance troubleshooting guide discusses rendering and encoding bottlenecks. Only apply performance remedies when the symptoms support them. Simplifying scenes, reducing output resolution or reducing frame rate can be reasonable tests when OBS is overloaded, but they are not established general cures for a playlist that stops between videos.
Similarly, buying a faster computer, GPU or capture device is not the first response to a source that fails at one file boundary while stream health remains normal. Hardware becomes relevant when the evidence shows sustained rendering or encoding pressure, not merely because the playlist contains several files.
Apply the fix indicated by the evidence
At this point, choose the smallest change that matches the evidence.
If OBS continues sending a healthy scene and one entry causes the stop, isolate or replace that entry. If the source is a single Media Source but you need several files, create a properly configured VLC Video Source and confirm that VLC and OBS have compatible architectures. If the list reaches its end and stays there, review Loop Playlist.
If the source disappears during a scene change, review source visibility and confirm which scene is live. If the local test works but the complete scene overloads OBS, simplify the scene or reduce the expensive elements while watching performance indicators. If YouTube health degrades at the same moment, follow the encoder and outbound connection checks rather than treating the event as a playlist fault.
After making a change, run the short test again. Then run the original list in the real scene. Finally, observe a controlled live test long enough to cover the boundary that failed previously. Do not describe the result as guaranteed uninterrupted playback; describe exactly what was tested and under what conditions.
For people who run an always-on channel from a home computer, the local approach has a practical limit. OBS must remain open, the media files must remain available, the computer must stay powered, and the connection must continue working. If the recurring problem is not the playlist itself but keeping a computer running through the night, StreamNeo removes that particular operating burden by letting you upload the video, connect the YouTube stream and leave the broadcast running without keeping your own computer switched on.
That is a different operating model, not a repair to an OBS source. It is also YouTube-only, so decide first whether you need OBS's scene controls or simply need a prepared video to keep playing. For other channel planning questions, this guide to scheduling videos on a YouTube live stream using OBS may help you separate scheduling from playlist playback.
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 on the last frame between playlist videos?
There is no single setting that explains every transition failure. First check whether OBS is still sending a scene and whether YouTube reports a health problem; then inspect the source type, playlist entry and file that precedes the stop.
Is OBS Media Source suitable for a multi-file playlist?
Media Source is intended for an individual local file and has a Loop option for repeating that file. OBS documents VLC Video Source for multiple local playlist items, provided VLC is installed and matches the OBS architecture.
Will enabling Loop Playlist fix every stopped transition?
No. Loop Playlist controls what happens after the complete list ends. It does not establish why playback stopped between two entries, so test the preceding and following files separately if the failure occurs in the middle.
Should I upgrade my computer when an OBS playlist stops?
Only consider a hardware change when OBS or YouTube evidence shows rendering, encoding or connection pressure. A playlist source that stops at one file boundary while stream health remains normal calls for source, visibility and file checks first.