If OBS holds the last image of one gaming VOD before the next clip appears, first check how those files are being played. For local clips in a sequence, try one OBS VLC Video source with an ordered playlist; for separate Media Sources, check what each source does at the end of playback.
Those settings can reduce blank or stale frames, but they do not guarantee a seamless transition on every computer or with every pair of files. Test the actual clips, scenes and audio in your own setup before scheduling a public stream.
Identify how OBS is playing the clips
Start by separating the symptom from its apparent cause. A frozen image in the OBS preview is not automatically proof that viewers are receiving a frozen image. Check the program output and, if possible, make a short private or unlisted test and watch it from another device. A preview may be paused or obscured while the outgoing programme continues, and the reverse can also happen.
Next, identify the source type. If all clips are listed together in one VLC Video source, OBS is handling them as a playlist. If each clip has its own Media Source, the scene or another control may be responsible for changing from one source to the next. A playlist and a set of separate sources are different workflows; advice for one does not necessarily apply to the other.
Look at how the transition is meant to happen. Does the next file start because it follows the previous item in a playlist, because you manually change scenes, or because a Media Source is restarted? Is the issue at the natural end of the file, or after a scene switch and return? Note whether the picture freezes on the final frame, goes black, or disappears. Those distinctions help narrow the test without assuming one universal cause.
If you are building a longer local-file run, it may also help to understand what happens when a file is absent from a sequence. Our guide to keeping a YouTube live playlist running when a video file is missing covers that separate failure case. A missing file is not the same as a source holding its last frame, but checking the file list is a useful first step in either workflow.
Try one VLC Video playlist for ordered local files
When you want several local clips to play one after another, a single VLC Video source is the straightforward OBS workflow to test. OBS documents this source as supporting playlists. Add the gaming VOD files in the order you want them to run, then check the playlist options: shuffle is off by default, so the listed order is preserved, and playlist looping is on by default.
That default loop setting matters. If you want the clips to repeat as a cycle, it may fit the intended broadcast. If the sequence should stop after the final file, inspect the loop setting rather than assuming the playlist will stop. Likewise, check the item order rather than trusting filenames alone: a list can be technically valid but still run a boss fight before its build-up if the files were added in the wrong order.
A playlist centralises playback compared with arranging a separate source for every clip. You maintain one sequence and can inspect it as a whole. That does not mean OBS promises gapless playback between arbitrary files. The clips still need to be readable in your setup, and the source must load the next item; the official documentation establishes playlist support, not a guarantee that every transition will be invisible.
If you already use a playlist in another workflow, the practical distinction is that this recommendation concerns local playback through OBS rather than a YouTube playlist on the channel page. For a comparison of broader approaches to always-on video schedules, see playlist-streaming options for 24/7 YouTube channels. Treat those approaches as context, not as evidence that a specific local transition will be seamless.
Check VLC installation and 64-bit compatibility
The VLC Video source depends on VLC being installed. OBS says the source will not appear unless VLC is installed, so if you cannot find it among the available sources, check that prerequisite before changing unrelated encoder settings. OBS also specifies that a 64-bit OBS installation needs 64-bit VLC. Matching the application architecture is part of getting the source available and usable.
After installation, reopen OBS if needed and verify that the VLC Video source is available. Then add the playlist and play through the end of one clip into the next. Do not treat source availability as proof that every file is suitable: test the actual video and audio files you intend to use.
If VLC is already installed and the source works, there may be no reason to reinstall it just because a transition briefly pauses. First establish whether the pause appears in the outgoing recording, and whether it occurs at the same point on a repeat test. A source configuration can address some end-of-file behaviour; it cannot by itself explain every delay, decode issue or scene change.
For a channel that runs while you sleep, a repeatable test is more useful than a setting copied from someone else's screenshots. If an error appears only on one clip, check that file in the intended sequence and compare it with another file; do not conclude from one observation that every item needs re-encoding. The goal is to isolate whether the issue follows a particular source, file or transition.
Set Media Source end behaviour where relevant
If each clip is its own OBS Media Source, open the settings for the source that is leaving the final frame behind. OBS documents the option Show nothing when playback ends. It is on by default in the documented settings, and OBS describes it as useful for video files so they do not show the last frame indefinitely. Check that this behaviour is enabled where hiding the ended source is what you want.
This setting affects what the Media Source shows after that file reaches its end. It does not mean that a different source will necessarily start at exactly the same moment, nor does it make two independently controlled files a playlist. If your scene continues to show a blank area after the final image is hidden, check what sits behind the source in the scene and how the next clip is triggered.
Also consider Close file when inactive if the symptom happens after switching away from a scene and back. OBS warns that closing a file while inactive can introduce a short period when the source is not showing as it reloads after becoming active. The option is off by default in OBS documentation. If you have enabled it, test whether the scene-return behaviour changes when you use the source without unloading it; do not assume a reload is seamless.
A useful mental model is that end-of-playback behaviour and scene activation are separate points in the chain. One setting can hide a final frame when a clip finishes; another choice can affect whether a source has to reload when a scene becomes active. If you need several clips to play consecutively without manually swapping scenes, test the playlist workflow rather than trying to make independent sources behave like one.
For recurring loops of a single service or video, the restart controls are a related but narrower case. Our guide to OBS Media Source restart options for YouTube video loops explains that kind of setup; a restart loop is not the same thing as a multi-file playlist, and its title should not be read as a promise of frame-perfect transitions.
Test transitions with the actual files
Test privately with the exact gaming clips and the same OBS scene arrangement you plan to use. YouTube recommends testing before an event with audio and movement similar to the real stream, then monitoring stream health and messages during the event. That is more relevant to this problem than changing stream settings based only on a frozen preview. See YouTube's guidance on live encoder settings and testing.
A test should cover the end of one file and the start of the next, not only the opening seconds of each clip. Watch the image through the cut, listen for an audio gap or overlap, and check whether the next item begins in the expected order. If you use scenes, test the same scene changes you expect during the live channel. Include the longest or most unusual files in the sequence if they have different formats or audio arrangements.
Make the test private or unlisted rather than discovering the behaviour in a public broadcast. Then review it from a separate playback device if practical. That gives you a view closer to what a viewer receives and helps distinguish OBS preview behaviour from the outgoing stream. A test is not a guarantee for a later run; it is evidence about the files, settings and machine you tested at that time.
Use a simple checklist:
| Check | What to confirm |
|---|---|
| Source type | One VLC Video playlist, or separate Media Sources, as intended |
| Order | Files appear in the required sequence and shuffle is off if order matters |
| Looping | Playlist looping matches whether the run should repeat |
| End and start | Picture and sound through the boundary between two real clips |
| Scene changes | Behaviour after switching away from and back to a relevant scene |
| Viewer output | Private or unlisted test checked outside the OBS preview |
If you change a setting after the test, repeat the transition. Otherwise you will be relying on a result from a setup that no longer matches the one going live. For a long-running channel, save a note of which files and settings you tested, so a later replacement clip does not quietly become an untested part of the playlist.
Troubleshoot remaining blank or stale frames
If the problem persists, narrow it down in order. First, determine whether the frame is present in the actual output or only in the preview. Next, identify whether the frame is from the old clip, a blank layer, or another source in the scene. Finally, note whether it happens at a file boundary, after a scene switch, or at unrelated moments. These observations are more useful than changing multiple settings at once.
For a VLC playlist, confirm that the next file is present and listed in the intended order. Confirm shuffle and looping settings against the run you want. For separate Media Sources, inspect the end behaviour on the source that reaches the end and consider whether closing files while inactive creates a reload gap on scene return. Change one relevant setting at a time and re-test the same boundary, so you can tell whether the result changed.
Do not assume that YouTube's ingest protocol is the fix for a local OBS source holding a final image. YouTube's HLS instructions describe segmented transport and apply to HLS ingestion; the segment and playlist requirements there do not establish a remedy for a local Media Source's end-of-file display. If you are not deliberately using HLS ingestion, changing HLS settings is not a targeted response to this symptom. The YouTube HLS setup guidance explains that separate workflow.
Similarly, YouTube's encoder recommendations include a two-second keyframe frequency and say not to exceed four seconds, but those are stream-encoding recommendations, not a fix for how OBS displays a file's last frame. Changing keyframes because a local clip appears stale risks confusing two separate stages. Use encoder settings to meet the requirements for your chosen stream setup, and use source tests to investigate local playback transitions.
More technical users may consider concatenating media with tools such as FFmpeg, but that is not a verified drop-in answer for arbitrary file formats and setups. FFmpeg documents a concat protocol and an ffplay example; neither establishes that a particular list of mixed gaming VOD clips will stream without a gap in OBS. If you explore that route, validate the resulting media and full broadcast path before relying on it.
A stable 24/7 broadcast also depends on what happens after local playback, scene composition and connection are considered. Those are separate jobs from eliminating a final image. For the broader question of keeping a channel live while your own computer is off, see what a cloud streaming service can do after you turn off your PC. Keep that decision separate from the OBS transition test: changing where a stream runs does not prove that a set of local files will have seamless boundaries.
If the work of keeping a computer on to play and monitor a prepared file is the specific burden you are trying to remove, StreamNeo can take that computer-off playback task out of the local setup. It does not change the need to check your source files and channel configuration, and the service is for YouTube streams only.
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
How do I play videos back to back in OBS?
For ordered local files, try one VLC Video source with the clips listed in sequence. Check the order, shuffle and loop settings, and test the boundary between clips; playlist support does not guarantee that every transition will be gapless.
How do I stop OBS holding the final frame?
For a Media Source, check Show nothing when playback ends. OBS documents this setting as useful for preventing a video file's last frame from remaining visible indefinitely, but it does not automatically start another source.
Why is VLC Video missing from OBS?
OBS requires VLC to be installed for the VLC Video source to appear, and OBS specifies matching architecture: 64-bit OBS needs 64-bit VLC. Install or check the compatible VLC version, then verify the source is available before testing the playlist.
Should I change YouTube HLS settings to fix the frozen frame?
Not unless you are actually using HLS ingestion and have a separate reason to adjust it. HLS transport settings do not establish a fix for a local OBS source showing a clip's final frame.