Yes. Wirecast can play a sequence of selected video clips during a YouTube Live broadcast by using a Playlist Shot; the documented workflow builds that playlist from clips or shots you choose, rather than automatically turning a folder into an ordered playlist.
That distinction matters if you expect new files dropped into a folder to join the live rotation by themselves. Treat the folder as a place to organise source files, then add the files you want to the playlist and verify their order and end behaviour before sending it live.
Can Wirecast play a folder automatically?
The practical answer is that Wirecast supports sequential playback through a Playlist Shot, but the Wirecast 15 Windows User Guide documents adding selected clips or shots to that playlist. It does not document choosing a folder and having Wirecast enumerate every file into an ordered playlist. Nor does the documentation reviewed establish that new files added to a folder will be appended automatically.
A folder and a playlist solve different problems. A folder is a filesystem container that helps you keep source media together. A playlist is an explicit sequence of shots that Wirecast can play. Having all your videos in one folder does not, on the evidence in the guide, define which files are included, what order they should run in, or what should happen after the last one.
For example, you might keep a set of devotional recordings together in a folder but want an opening prayer, a group of bhajans, and a closing message to play in a particular order. Build a Playlist Shot from those intended clips and arrange them as a sequence. If someone later places another recording in the source folder, check the playlist and add it deliberately rather than assuming the new recording will appear on air.
Telestream’s Wirecast 15 Windows User Guide describes Playlist Shots as a way to create and broadcast shots containing multiple preselected clips. That is a useful basis for a fixed sequence. It is not evidence of automatic folder scanning. Telestream’s version history mentions media playback changes, including improved watching of network shares for media file updates, but that statement does not confirm folder-to-playlist enumeration or sequencing.
The distinction also helps you choose a workflow. A fixed playlist suits a programme where order matters and you can prepare the set ahead of time. A folder-driven rotation would suit a collection that changes often without an operator editing the sequence, but that behaviour remains unverified in the sources reviewed. If you need it, test the installed version with non-critical media and consult current documentation before relying on it overnight.
Create a Playlist Shot
The Wirecast 15 Windows guide gives a straightforward creation path. In a layer, click the plus sign (+), choose Shots, select New Playlist Shot, and click Add. The resulting Playlist Shot is the item you will populate with the clips or shots intended for sequential playback.
The labels are from the Windows guide, so the exact wording or placement may differ in another release or on macOS. Telestream’s version history lists later releases and playlist or media playback changes. Use the guide as a route through the concept, not as a promise that every button looks identical in your current installation.
Before adding material, make the selection concrete. Decide which source clips belong in this run and whether the playlist should repeat or stop at the end. This is the point to separate a deliberate programme from a miscellaneous file collection. If you are assembling event recordings, the workflow considerations in creating an always-on channel for event recordings can help you think about how individual recordings fit the channel as a whole.
Keep the source files in a location Wirecast can access for the whole session. The available notes do not set out a universal file-location rule, so test your own media paths before going live, especially if the files are on removable storage or a shared location. A playlist can only be useful if each selected source remains available when it is time to play it.
Add clips or shots to the playlist
There are two documented ways to populate the Playlist Shot. One is to drag the desired clips or shots onto the Playlist Shot. The other is to double-click the Playlist Shot to open its Playlist tab, choose Shots > New Shot, and select the clips you want. Both methods add chosen material; neither is an instruction to import every item in a folder automatically.
Think of each playlist entry as a planned step in the broadcast. If a video needs to be represented as a shot before it can be selected, create or select that shot in Wirecast, then add it to the playlist. The guide’s workflow is based on selecting clips or shots, so do not assume that merely copying a file into a media folder changes the playlist.
A useful preparation habit is to name or otherwise identify clips clearly before composing the sequence. Names such as “Opening”, “Morning bhajan”, or “Closing” are easier to inspect than a set of similar filenames. This is an operational suggestion rather than a documented Wirecast requirement, but it reduces the chance of choosing the wrong recording when two files have similar names.
If the source material is large, you may need to prepare it before loading it into the project. For instance, a channel made from long event recordings could benefit from a deliberate file plan; the guide to compressing wedding videos for a YouTube 24/7 playlist stream discusses that separate preparation concern. Compression does not create a playlist, but a manageable collection of ready clips can make selection and review more orderly.
When you add clips, check that the playlist contains the intended items and no accidental extras. The folder may include drafts, duplicate exports, or short test clips that should not be broadcast. Explicit selection is a little more work than hoping for automatic import, but it gives you an opportunity to keep those files out of the live sequence.
Arrange the playback sequence
Once the clips are present, arrange them in the intended order and review the sequence from beginning to end. Leave shuffle disabled where programme order matters. The guide describes shuffle and the previous/next controls, so the operator can change order or move through entries, but those controls are not a substitute for checking the playlist before broadcast.
The end behaviour changes what viewers see after the final item. The documented choices include Loop, which returns playback to the first shot and repeats, and Hold, which keeps the playlist on its last shot. Choose Loop when the sequence should repeat continuously. Choose Hold when it should stop advancing at the final shot rather than begin again.
There is a detail to watch when the last playlist entry is itself a video. The guide says that if you want to hold on the video's last frame, set that clip’s own When Finished behaviour to Hold as well as setting the playlist behaviour to Hold. Setting only the playlist to Hold may not express the full intended behaviour for the clip. Check both levels where a final frame is important.
| Playlist choice | What the guide says it does | When it may fit |
|---|---|---|
| Loop | Returns to the first shot and repeats the sequence | A repeating music or ambience rotation |
| Hold | Stays on the last shot | A programme that should finish on its final item |
| Shuffle | Changes the order of playlist shots | A collection where a fixed order is not required |
| Next / Previous | Moves manually between playlist items | An operator-supervised show with live intervention |
These are playback controls, not folder-management controls. Shuffle changes the order of entries that are already in the playlist; it does not gather new files. Next and Previous allow manual movement while the playlist is live; they do not mean the sequence has been checked for you. For a fixed programme, the safest operational approach is to prepare the list, keep shuffle off, and inspect the order before taking it live.
If this is a recurring channel, note the intended sequence and end setting alongside the source files. That makes it easier for another operator to understand whether the channel should repeat a curated set, stop at a closing item, or accept manual changes. A channel that must restart from a particular first video may need a different operating pattern; the article on restarting a YouTube playlist from the first video in PRISM Live Studio is relevant to that separate question, but it does not change Wirecast’s documented Playlist Shot workflow.
Send the playlist to YouTube Live
A Playlist Shot is sent to the broadcast like another shot. With AutoLive disabled, select the playlist and click Go. With AutoLive enabled, clicking a shot sends it to the Live Broadcast Area. Check which mode you are using before you take the playlist live, because the action that changes the on-air output depends on that setting.
Wirecast supports YouTube as a streaming destination, according to Telestream’s Wirecast product page. That establishes the software’s destination capability, but you still need to configure the YouTube broadcast and the relevant Wirecast output using the current instructions for your setup. Do not infer from playlist creation alone that a broadcast is already connected or transmitting.
Before the hand-off, confirm that the intended YouTube destination is selected, the stream is ready, and the playlist is the shot you mean to send. This is particularly important if the project contains other shots used for titles, cameras, or standby artwork. A quick local review of the first item and the expected next item can expose an accidental selection before viewers see it.
For a channel that is meant to run while you are away, decide how much supervision you can realistically provide. A playlist can repeat a selected sequence, but the documented controls do not remove the need to check the source media, output, and broadcast state. If your channel is based on a set of original recordings, streaming a 24/7 fairy-tale playlist from a Mac mini offers another example of the planning involved in keeping a recorded programme moving; its platform-specific details should not be mistaken for Wirecast instructions.
If the operational problem is that a desktop must stay on and an operator must recover a dropped broadcast, StreamNeo addresses that specific burden by letting you upload a video, connect your YouTube stream key, and run the broadcast without keeping your own computer on. It is YouTube-only, so it is not a replacement for Wirecast when you need its production controls, multiple live inputs, or a manually operated show. Choose the workflow around the job: selected clips in a desktop production setup, or a prepared video intended to run as an always-on channel.
Check the playlist during playback
Once the playlist is live, observe whether the current item advances as expected and whether the sequence is behaving according to the chosen end setting. The previous and next controls are available for manual movement between items. If you use them, treat each press as an on-air change and confirm the resulting shot rather than assuming that the playlist will resume the original plan at a particular point.
The Wirecast 15 guide warns against deleting shots from a playlist while it is running, and it says nested playlists are unsupported. Avoid changing the underlying sequence during playback. If the programme needs a revised item, prepare the change outside the running playlist where practical, then make a controlled transition rather than editing its contents mid-run.
Check for the common failure points before leaving a stream unattended: a missing or moved source file, a wrong first item, shuffle left on, an unsuitable end setting, or an operator who does not know whether AutoLive is enabled. These are checks derived from the documented selection and playback model, not guarantees that every issue will be caught. A short monitored run is a sensible way to see whether the prepared sequence behaves as you expect in your own project.
Do not rely on a network-share update note as proof of unattended folder rotation. Telestream’s version history mentions improved watching of network shares for media file updates, but the sources reviewed do not show that Wirecast turns those updates into newly enumerated playlist entries in a predictable order. If you need newly delivered files to join a sequence, verify that exact behaviour in your installed version before making it part of the channel’s overnight plan.
Choosing between a fixed playlist and a folder workflow
A fixed Playlist Shot is the documented choice when the clips are known in advance. You select the clips, order them, set the playback behaviour, and send that shot live. Its trade-off is maintenance: a new clip or changed sequence requires you to edit the playlist deliberately.
A folder-driven workflow would reduce that editing if it automatically picked up new files, but that is precisely the behaviour not established by the available guide. It would also raise practical questions the fixed workflow makes explicit: should new files go at the end or be sorted by name, should duplicates be included, and should a file arriving mid-broadcast change the sequence immediately? Do not plan a channel around answers you have not tested.
| Need | Documented fixed playlist | Automatic folder update (unverified) |
|---|---|---|
| Select which clips play | You add desired clips or shots | Automatic inclusion is not confirmed |
| Keep a predictable order | Arrange the playlist and leave shuffle off | Sorting and placement behaviour are not established |
| Include later additions | Edit the playlist to add them | Whether additions are detected and sequenced is unresolved |
| Operate without checking changes | The sequence is explicit, but broadcast still needs monitoring | Do not assume unattended updates without a version-specific test |
For a one-time event loop or a carefully sequenced devotional programme, the fixed playlist is usually easier to reason about because you know what is in it. For a station that receives fresh clips continually, test the desired folder behaviour with a small set of clearly named sample files, including one added after playback begins. Confirm not just that a file becomes visible, but that it enters the intended playlist position and behaves correctly at the end of the current item.
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
Can I choose a folder and have Wirecast add every video automatically?
The Wirecast guide reviewed here documents adding selected clips or shots to a Playlist Shot, not automatic folder enumeration. Check the current version’s documentation or test the exact behaviour before depending on it.
Can a Playlist Shot repeat continuously?
The guide describes a Loop behaviour that returns to the first shot and repeats the playlist. Confirm that this is the intended outcome, particularly if the final item is meant to be a closing message rather than the start of another cycle.
What should I set if the final video must stay on its last frame?
The guide says to set the playlist’s end behaviour to Hold and set that video’s own When Finished behaviour to Hold as well. Check both settings in the installed version before sending the sequence live.
Can I change or nest playlists while one is playing?
The guide says nested playlists are unsupported and advises against deleting shots from a playlist while it is running. Prepare and check changes before playback, then avoid altering the active sequence unexpectedly.