If you want several videos to play in sequence during an OBS YouTube stream, FFmpeg can combine compatible clips into one file, or re-encode clips to make their streams consistent before combining them. If you need to keep separate files and control a playlist, OBS can use its VLC Video Source, which requires VLC to be installed.
Neither route guarantees uninterrupted playback or a smooth live stream. Choose based on how often you change the playlist and whether the clips match, then test the finished media in OBS and check your connection and YouTube's live stream health.
Choose one continuous file or a true playlist
A combined file makes sense when the order is settled and you want OBS to play one prepared asset. You build the sequence before going live, inspect it as a single video, and load it as an OBS Media Source. This reduces the number of playback items you need to manage during a broadcast, but a change to the order means updating the file and checking the revised result.
Keep a true playlist when you may swap, reorder or remove clips without rebuilding a combined video. OBS's VLC Video Source is designed for playlist playback and offers playlist controls; VLC must be installed for the source to work. That is useful for a daily news loop or a study channel that rotates lessons, but it means you should verify the source and playlist behaviour in your own OBS setup before relying on it overnight.
| Approach | Better fit when | Main trade-off |
|---|---|---|
| FFmpeg concat with stream copy | Clips already expose compatible streams and the sequence is stable | Fast preparation without re-encoding, but it does not make differing clips match |
| FFmpeg re-encode, then combine | Input clips differ in properties that need normalising | More preparation and encoding work; the result still needs checking |
| OBS Media Source | You want to play one finished file | The playlist is no longer edited as separate items in OBS |
| OBS VLC Video Source | You need playlist controls over separate files | VLC installation and playlist testing are part of the setup |
These are workflow choices, not promises about stream quality. If you are weighing playback inside OBS against preparing media ahead of time, the OBS and FFmpeg playlist scheduling comparison gives useful context. You do not need FFmpeg simply to play an already suitable single video in OBS.
Check whether the clips are compatible
Before choosing a command, make an inventory of the files. Check each clip's video and audio codecs, time base, duration, frame size, frame rate and audio layout. FFmpeg's ffprobe utility can show stream information; if you are new to reading media details, focus first on whether the files have the same kinds of streams and matching properties rather than trying to optimise every field.
The concat demuxer is a packet-level joining method, not a general-purpose repair tool. The inputs need matching stream structures, including codecs and time bases. If one video is encoded differently, has a different time base, or has an audio stream the others lack, a stream-copy command may fail or produce output with boundary problems. A file extension such as .mp4 alone does not tell you that two clips are compatible.
Duration information matters too. FFmpeg uses durations to place the next file after the previous one; inaccurate duration metadata can affect timestamps and lead to artefacts around transitions. Pay particular attention to the point where one clip ends and the next begins, and check both picture and sound there. A pause, brief jump or audio discontinuity may be present in the prepared file even if each source plays normally on its own.
Create a small test sequence if you have a large collection and are unsure how the clips behave together. Inspect its streams, open it in a player, and watch the joins before preparing the full run. For a church archive or a recurring programme, keeping an untouched copy of each source clip also gives you a way to rebuild the sequence if a correction is needed. You can compare that approach with this guide to streaming archived church services in a continuous schedule.
Concatenate compatible clips with FFmpeg
When the clips expose matching streams, the concat demuxer with stream copy is the straightforward route. Make a plain-text file in the same working folder as your clips. List the media files in playback order, with one file line per clip:
ffconcat version 1.0
file 'clip-01.mp4'
file 'clip-02.mp4'
file 'clip-03.mp4'
Save it as playlist.ffconcat. Use names and paths you control. The -safe 0 option in the command below permits paths that FFmpeg would otherwise reject as unsafe, so omit it if you do not need such paths. Keep the list and the files under your control rather than using that option as a reason to accept unknown file paths.
ffmpeg -f concat -safe 0 -i playlist.ffconcat -c copy combined.mp4
Here, -f concat selects the concat demuxer, -i supplies its list, and -c copy copies the compressed streams instead of decoding and encoding them again. That avoids the additional encode step and its generational quality loss, and is generally quick compared with re-encoding. It also means FFmpeg is not changing the clips to a common format: if the inputs are incompatible, stream copy is not the fix.
The demuxer adjusts timestamps so the first file starts at zero and subsequent files begin after the preceding duration. This is useful for creating a single continuous asset, but does not remove every possible join issue. Play the entire result, or at least review all transitions in a representative test, and confirm that audio remains in sync and the ending and beginning of each clip are acceptable.
The FFmpeg documentation on the concat demuxer explains the input-list method and its requirements. FFmpeg describes stream copy as useful for changing container-level details without re-encoding the compressed streams. For an OBS recording, its separate recording output guide documents remuxing; that feature is not a substitute for combining or normalising arbitrary playlist clips.
Re-encode clips that need consistent streams
If the inventory shows meaningful differences, decide on a common target before joining the videos. That includes a deliberate resolution, frame rate, video and audio format, and audio layout appropriate to the material and the way you intend to stream it. Do not silently stretch a portrait or differently shaped image to fill a frame, and do not expect upscaling a low-resolution source to add detail that was never present.
There are two broad stages: normalise each clip to the same chosen properties and then join compatible outputs, or use FFmpeg's concat filter for a workflow that requires re-encoding. The filter is the documented direction when you need to re-encode, but it is not a universal command that can safely be pasted without knowing the inputs. Stream mapping, timing and audio layout must be handled for the actual files. If you are not comfortable specifying those details, work on copies and ask someone experienced to review the command before processing a long programme.
Re-encoding takes time and uses computing resources. Its output quality and processing time depend on the source, selected settings and machine, so there is no one CRF, preset or bitrate that is right for every playlist. Pick settings for the destination and hardware rather than choosing numbers from a recipe that may assume different source footage. Where the source clips differ greatly, test a representative section first.
After encoding, check that all intended streams are present and that the clips still look and sound right. Watch transitions for black frames, repeated frames, cropped or stretched imagery, and audio that slips out of sync. A normalised file can be easier to manage in OBS, but conversion itself cannot establish that the broadcast will be smooth.
Open the finished file as an OBS Media Source
For a single combined file, add a Media Source to the scene in OBS and select the output. Confirm that the source is visible, that sound reaches the expected mixer channel, and that playback begins and ends as intended. If the scene is part of a longer show, also check what OBS does when the file reaches its end; your intended loop or transition behaviour should not be assumed from a successful first playback.
Keep the file somewhere that will remain available to the OBS machine, and avoid moving or renaming it after configuring the source without updating the path. Run the scene in the same arrangement you plan to use live, including any overlays, other sources and audio monitoring. A media file can play correctly by itself yet behave differently when the full scene is active.
OBS's Media Sources guide describes supported source behaviour and settings. Check the labels in your installed OBS version, since menus and options can change. The important operational check is not simply that the file can be selected: verify the actual scene, sound and transition behaviour with the prepared file.
Use VLC Video when a playlist is preferable
If the playlist must remain a set of separate files, add OBS's VLC Video Source and configure the playlist there. This is often more practical when you update the sequence regularly or want playlist controls, rather than rebuilding a combined file every time a programme changes. Install VLC as required by OBS's source, then confirm OBS recognises it and can play each item in the intended order.
A true playlist shifts some complexity rather than removing it. Check file paths, playback order, whether each item starts correctly, and what happens at the end of the list. Test changes to the list before the live session. If a path points to a disconnected drive or a renamed file, OBS may not play the intended item even though the playlist was correct when you first created it.
Do not assume VLC playback is automatically more reliable than a single file. It depends on the installed software, media paths, input compatibility and the OBS scene. Conversely, do not spend time converting an already compatible file solely because you think OBS needs FFmpeg to play it. Choose the source that fits how often your content changes, then validate it under the conditions you will actually use.
For a devotional channel that repeats the same recorded bhajan programme for days, one inspected file may be simpler to operate. For a local news loop with frequent item changes, separate files in a tested playlist may be easier to maintain. If you are planning a longer-running channel, the practical monitoring checks for a 24/7 study stream are relevant beyond the media source itself. StreamNeo is useful when the specific burden is keeping a prepared video broadcasting after your own computer is switched off, rather than managing a live OBS scene on that computer.
Test the file, connection and YouTube health
Treat the media test and the live test as separate checks. First play the prepared file through the OBS scene and review its picture, sound, joins and end behaviour. Then test the whole live path before relying on it: encoder output, network upload, YouTube's live preview and the stream-health information in Live Control Room. A locally smooth playback test does not exercise the connection carrying the stream to YouTube.
Your encoder's live bitrate must fit the available upload capacity, and the capacity must be dependable, not merely a best result from one speed test. YouTube's streaming tips recommend leaving 20% of upload bandwidth as headroom. Avoid treating that as a guarantee: if other devices share the connection, or upload varies, leave practical room and test at the time and location you intend to broadcast.
YouTube's live encoder guidance covers accepted protocols and video and audio settings, including codec and keyframe recommendations. Confirm current details in YouTube's live encoder settings and in Live Control Room before choosing an encoder configuration. Resolution, frame rate and bitrate should suit both your content and the upload connection. Keep live settings distinct from YouTube's recommendations for uploaded files; the video upload encoding recommendations address a different path.
During the test, look for dropped frames or warnings in OBS and stream-health messages in YouTube, and confirm that the live preview shows the expected picture and sound. If the local file is clean but the YouTube preview buffers or loses quality, investigate upload stability and encoder settings rather than repeatedly converting an unchanged source. If problems occur at the same clip boundary locally and live, inspect that part of the file. These checks help narrow the cause; they do not guarantee uninterrupted service.
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 combine multiple videos into one file with FFmpeg?
If their streams are compatible, put their paths in a text file in playback order and use the concat demuxer with -c copy. If the codecs, time bases or stream layouts differ, stream copy does not normalise them; plan a re-encode or a concat-filter workflow, then inspect the output.
Can OBS play a video playlist?
Yes. OBS provides a VLC Video Source for playlist playback, and VLC must be installed for that source. If you prefer a single asset, combine suitable clips beforehand and play the result as a Media Source.
Why does my YouTube stream buffer when my video plays smoothly locally?
Local playback does not test the upload connection or the complete encoder-to-YouTube path. Check OBS for dropped frames, confirm that your live bitrate fits stable upload capacity with headroom, and read YouTube's stream-health feedback.
Does converting a playlist make a stream smooth?
No conversion or playlist player guarantees smooth live playback. Check clip compatibility, inspect the combined file or playlist in OBS, and test the broadcast path and YouTube preview before relying on it.