“Playlist” in vMix can mean a sequence of production inputs or a sequence of media files inside one input. Choose the right one first: a script can change what vMix sends to your live output, but YouTube Live is configured separately and neither kind of vMix playlist is a YouTube channel playlist.
Use PlayList when separate vMix inputs need to follow one another, often with transitions between them. Use a List input when a set of files should play through one input. vMix scripting can automate actions in a workflow, but its built-in PlayList is not a clock-based 24/7 schedule.
Two meanings of playlist in vMix
The distinction is about what the sequence contains. vMix PlayList arranges inputs that already exist in the production: for example, a camera input, a title-and-video composition, then another video input. Moving through the sequence changes which input is taken to output, using the configured transition behaviour.
A vMix List is itself an input. It holds media items, such as video or audio files, and plays them through that one input. The live production sees the List input; it does not treat every file within the list as a separate production input. The vMix Video List documentation describes this media-playback model.
Neither feature is a YouTube channel playlist. A YouTube playlist organises videos on YouTube; it does not tell vMix which input to take live. Here, vMix is the production system, its output is the video and audio sent to the stream, and YouTube Live is the destination receiving that output.
| If you want to… | Use… | The sequence changes… |
|---|---|---|
| Move among cameras, graphics, or distinct video inputs | PlayList | Production inputs |
| Play several files through one media source | List input | Media within one input |
| Start a different programme at a particular time of day | A separately planned scheduling workflow | Not the basic built-in PlayList alone |
This naming ambiguity matters when you search for a “playlist switch” script. A command that acts on an input is not necessarily the same as controlling media playback inside a List. Decide what should change on screen before you build automation.
Choose PlayList for switching production inputs
Choose PlayList when each part of the programme has a reason to be its own input. A local news loop might have an opening slate, a presenter camera, a weather graphic, and a recorded community notice. A devotional channel might use separate inputs for a title card, a bhajan video, and a still image with background audio. That separation makes per-segment transitions and manual intervention easier to reason about.
Add the available inputs to the PlayList in the order you want them used. Review the available options, including looping, beginning from the selected item, clearing overlays, and manual mode. Previous and Next move through the items using the transition set for the item. The precise controls and presentation can vary by vMix version, so check the guide and the controls in your installed release rather than assuming a tutorial matches your screen.
A PlayList is useful for sequential switching, not a full programme clock. It can carry the production from one input to the next, but it does not by itself express a weekly timetable such as “news at 8 am, music at 9 am, repeat tomorrow”. vMix states in its scheduling support article that it does not support time-of-day scheduling. If that is the requirement, plan a separate scheduling method and test how it starts, recovers, and hands over to the live output.
Keep the input design modest. If a sequence is only a set of files, turning each file into a separate input may add unnecessary setup and make the operator manage more items. If one segment needs its own graphic layers, camera choice, or distinct transition, a separate input is often clearer than hiding those production choices inside a file list.
Choose List for sequential media files
Use a List input when your sequence is fundamentally a queue of files. It can play the next media item automatically and can loop, depending on its configuration. This is a good fit for a set of recorded talks, instrumental tracks, or short information videos that should run as one source in the wider production.
The practical distinction is resource and control. vMix notes that a List can avoid loading all videos at once, which may be useful when the sequence contains multiple files. In return, files inside the List are not independent production inputs for the purpose of switching among cameras or overlay layouts. If you need a transition between one full-screen input and another, use the production-input model rather than expecting a file queue to behave as a scene list.
A List can also sit inside a standard PlayList. For example, a production could take a holding graphic, then take a List input that plays a run of recorded clips, then return to a camera input. This combines media-level auto-next behaviour inside the List with input-level sequencing in PlayList. Keep the nesting easy to understand: an operator who has to recover playback at night should be able to tell whether the current item is a file in the List or the active input in the production.
Before loading a long set, confirm that the media plays correctly and in the intended order. Check file paths, audio levels, aspect ratio, and whether the final item loops or stops as intended. For a 24/7 channel, a technically valid sequence is not necessarily a useful programme: viewers may encounter it at any point, so make the transitions between its end and beginning deliberate. For broader planning around recorded content, see how to run a 24/7 stream of recorded coding tutorials.
Set up the YouTube Live destination separately
A script that changes vMix inputs changes the production output. It does not create a YouTube playlist, select a YouTube event, or configure the destination for you. Configure the YouTube Live destination independently, then verify that the intended vMix output is being sent to it.
vMix documents a workflow for streaming to YouTube Live and a separate guide for creating a YouTube Live stream and streaming from vMix. Depending on the route and current interfaces, you may sign in through vMix or select a stream/event and provide the required stream credentials or key. Follow the current official instructions for the account and stream you are using; do not treat an old saved key or a successful local preview as proof that YouTube is receiving the intended programme.
The key operational check is the boundary between production and destination. First confirm vMix is taking the expected input to its output. Then confirm the YouTube event is configured for that output and is actually receiving the stream. This separation helps diagnose a black picture: the cause may be the selected vMix input, the outgoing stream configuration, or the YouTube event, and changing a playlist will not fix a destination configuration problem.
If your goal is a persistent channel rather than a one-off event, decide how the destination is started and monitored as well as how content changes. An older computer and local setup may be workable, but consider the operational burden and recovery steps; our guide to the cost of a 24/7 stream on an old Chromebook helps frame that trade-off. A stream can be live while the wrong input is showing, so destination status alone is not a content check.
Plan the switching workflow
Begin with a written sequence, not a script. List each item, its type (production input or media file), what viewers should see, whether it needs an operator decision, and how it should hand over to the next item. A small table kept beside the vMix project is often enough. Include the recovery state too: if vMix is restarted, should it begin at a holding card, a particular input, or the first item?
Then choose the mechanism. vMix documents scripting in Settings > Scripting for its 4K and Pro editions; confirm current edition requirements and interface details against your installation. The official Scripting and Automation documentation explains creating a named script. To launch it, create a Shortcut using ScriptStart and enter the script name. A shortcut gives you a controllable start point, rather than requiring the script to begin as an unexplained side effect.
For a straightforward sequence, Web Scripting can run function lines in order and insert Sleep delays between them. Its function syntax follows the Web API without the URL portion. This can be useful when you want a deliberate pause between actions, but timing is not a substitute for checking whether the preceding media actually finished. A fixed wait can drift from the content if a clip is changed or playback stalls.
Do not copy a guessed command such as PlaylistNext into a script and assume it is valid. vMix's API documentation says callable functions are those available in the Shortcuts function dropdown under Settings > Shortcuts > Add. Inspect that list in the installed release, identify the functions that perform the intended action, and test them there first. The exact playlist control names are not established by the general documentation for every installation, so a ready-to-run command cannot safely be assumed here. The Web Scripting guide and Developer API documentation are starting points, but your own function list is the authority for what your version exposes.
Keep scripts readable and narrow. Name each script for its purpose, such as “advance programme inputs”, and use comments or a separate note to record the expected order. Avoid building a long sequence of opaque waits if a simple manual mode or the List input's own auto-next behaviour already meets the need. A script should solve a repeated control task, not make a basic playlist harder to inspect.
If you are planning a file-driven channel rather than a production with cameras and overlays, consider the broader playback trade-offs before committing to a software arrangement. This guide to FFmpeg playlists and YouTube Live covers a different workflow; it is useful context, not a claim that vMix PlayList and an FFmpeg playlist are interchangeable.
Test transitions and playback
Test off-air before relying on automation. Verify each input manually, take it to output, and confirm its audio and picture. Then run the PlayList or List behaviour on its own. If a transition should fade between inputs, confirm that the actual transition is applied; if the item should simply cut, check that it does not unexpectedly inherit another transition. A sequence that looks correct in the input preview can still behave differently once taken to output.
Test the complete script from its normal launch point. Confirm the ScriptStart shortcut references the intended script name, that each function is available in the installed Shortcuts list, and that delays leave enough time for the intended action. Watch several handovers, including the last item returning to the first when looping is enabled. If you use overlays, check whether they clear or remain according to the PlayList option you selected.
Test interruptions deliberately. Stop or pause playback, reopen the project if that is part of your real recovery process, and confirm what an operator needs to do to resume. Test with representative media rather than placeholder clips: file duration, audio presence, and codec behaviour can affect what the viewer hears and sees. Keep a simple manual fallback, such as a known holding input and a written next action, rather than relying on an untested script when something goes wrong.
For a channel intended to run overnight, test longer than a single transition and observe the whole path that matters: media playback, input changes, vMix output, and the YouTube event. A short local test can establish that a command works, but it cannot prove a setup will recover from every interruption or run indefinitely. Record what you actually checked and what still requires an operator, so expectations remain realistic.
Check the live output
Once destination and switching have been tested separately, check them together. Start the YouTube Live event using the current official process and verify that the viewer-facing stream shows the input you expect. Watch a transition from the stream's perspective, not only from vMix's multiview or preview. Confirm the audio continues across the change and that the stream does not remain on a slate after the script has advanced elsewhere.
When troubleshooting, change one layer at a time. If vMix output is wrong, inspect the active input, PlayList state, List playback, and script action. If vMix output is correct but YouTube shows something else or no stream, inspect the destination and event configuration. This basic split avoids repeatedly rewriting a working script to compensate for a separate streaming problem.
Remember that “automatic” describes only the actions you have configured and tested. A sequential PlayList is not a time-of-day scheduler; a List's loop is not a programme timetable; and a live destination does not verify the content is appropriate. vMix's scheduling guidance is particularly relevant if you need a channel to change programmes by the clock. For a 24/7 workflow with a prepared file and the need to keep a computer switched off, StreamNeo removes the repeated local playback and restart burden by turning an uploaded video into a YouTube live stream; it remains separate from vMix's production-input playlist controls.
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
Does a vMix PlayList change a YouTube channel playlist?
No. A vMix PlayList sequences production inputs in vMix; a YouTube playlist organises videos on YouTube. The script affects the vMix output sent to the configured live destination.
Should I use PlayList or List for a series of videos?
Use a List input when the items are media files to play through one input, with its media playback and loop behaviour. Use PlayList when the items need to be separate production inputs with input-level switching or transitions. You can combine a List inside a PlayList when both kinds of sequencing are useful.
Can vMix scripts schedule a different programme by time of day?
The basic PlayList and scripting workflow described here is for sequential actions, not clock-based programme scheduling. vMix says it does not support time-of-day scheduling, so plan and verify another scheduling approach if that is essential.
Why not include a ready-made playlist script command?
The callable functions depend on the list exposed in your installed vMix Shortcuts interface, and the exact playlist control function names should be confirmed there. Check Settings > Shortcuts > Add, test the action in your release, and only then use it in a script.