For a product demo that repeats in OBS, use a Media Source with Loop enabled for one clip, or a VLC Video source with Loop Playlist for several clips. To make changes between OBS scenes smoother, choose a scene transition such as Fade and set its duration.
Those controls handle different things. A scene transition affects the change from one OBS scene to another; it does not repair a visible cut between the last frame and first frame of a file that restarts. Check that media boundary separately, then test the whole sequence in preview before you take it live.
Choose scenes or a playlist for the demo sequence
Start by deciding what the viewer should see change, and when. If your demo has distinct states — an opening title, a close-up of a feature, a price or specification card, and a closing shot — you can arrange them as separate OBS scenes. Each scene is a composition of sources, so it might contain a video, a logo, a lower third, or a background. A scene change is useful when the layout or presentation state changes, not merely because another file begins playing.
If the whole demo is a set of clips that should play in order in one unchanged layout, a playlist source may be simpler. The choice affects your control: separate scenes make it easier to set up a particular layout or transition for each segment, while one playlist keeps the sequence together. Neither choice automatically makes the files’ edit points invisible.
For a small shop, for example, one scene might show a product rotating on a plain background, another might show its controls close up, and a third could hold a detail card. If you instead have several short shots that all sit inside the same framed layout, keep the layout in one scene and decide whether a playlist is the right playback control. Avoid creating scenes for every tiny edit unless you need that level of control; more scene changes mean more transitions to review.
OBS Studio’s overview guide explains scenes, transitions and Studio Mode. In Studio Mode, you can prepare a different scene while the current one remains on air, then transition when you are ready. That is useful for a live presenter or operator who needs to inspect the next state. It is less important for a fully prerecorded sequence that must run unattended, but it remains a way to verify a scene before putting it on the programme output.
Keep the viewer’s purpose in mind. A product demo should make the object and its use easy to follow. A transition that looks smooth but obscures a button, label or change in state is not an improvement. Choose scene boundaries around meaningful changes in the presentation, and decide whether each shot needs its own scene or belongs in a continuous clip.
Loop one clip with Media Source
For a single local video that should repeat, add a Media Source to the scene and select the file. OBS documents common media formats such as MP4, MOV, MKV, AVI and WebM; whether a particular file plays correctly still depends on its encoding and your OBS setup. Its Media Sources documentation describes the available controls, including Loop.
Enable Loop when the source should restart after playback ends. The control tells OBS to replay the file; it does not align the end and beginning for you. If the final image shows the product from the side and the opening image jumps to a front view, viewers may notice the jump each time the clip restarts. You will need to choose or edit the footage to address that point.
A single source is straightforward when one finished demo has the desired order, timing and audio. It also keeps the loop behaviour with the file, rather than asking you to build separate scene changes for each shot. If you want a clean product hold between demonstrations, include it in the edit. Do not assume that a transition setting elsewhere in OBS will create that hold.
Before adding the file, give it a clear name and keep track of which version is final. If you later replace a clip with a revised export, confirm that the source points to the intended file. Play it through once in OBS and check that picture and sound start as expected. A file can appear fine in an editor but behave differently when loaded into the streaming scene, so the source itself needs a check.
OBS treats a Media Source as a video input, distinct from devices such as a webcam or capture card; see its sources guide. For prerecorded product footage, you generally do not need a capture card just to load a local file. Add one only if your production also needs an external camera or other device.
Loop several clips with VLC Video
For multiple files that should play as a sequence, use a VLC Video source and add the files to its playlist. OBS documents a Loop Playlist option for repeating that list. VLC must be installed, and OBS notes that 64-bit OBS needs 64-bit VLC. Check the documented requirements on the OBS Media Sources page before building your scene around this source.
A playlist is practical when you want the same layout around a series of independent clips: for instance, product angles, a short feature demonstration, and a closing card. Put them in the intended order, then play through the list rather than assuming the order in the source panel is the order viewers will see. A playlist repeats the sequence, but the handoff between clips and the handoff from the last clip back to the first are still media edits to inspect.
One consideration is source visibility. OBS documents that VLC Video playback can stop when the source is hidden. If your playlist is on a scene that you switch away from and later return to, test the actual behaviour you want rather than expecting it to continue in the background. A source that restarts on reappearance might be right for an introduction, but not for a sequence you expected to pick up midway through.
| Playback choice | Suits | Check before using |
|---|---|---|
| Media Source with Loop | One finished file repeating | Whether the file’s end-to-start point looks and sounds acceptable |
| VLC Video with Loop Playlist | A set of files repeating in order | VLC installation and matching 64-bit or 32-bit setup, plus playlist and visibility behaviour |
| Separate OBS scenes | Different layouts or presentation states | Whether each scene change is necessary and how its transition looks |
This table is about control and testing, not a ranking. If your clips have different aspect ratios or framing, make sure the scene layout handles each one consistently. A product that shifts position or size at every playlist item can look like an accidental jump even if each file’s own endpoint is clean.
If the clips belong in a fixed order, write it down before adding them. A simple sequence such as “wide view, controls, use, closing card” makes it easier to spot a missing or misplaced item during testing. For more on a different playlist-based streaming workflow, the article on keeping a radio playlist livestream running from a VPS offers relevant context, though a VLC Video source has its own OBS-specific playback behaviour.
Set a scene transition and duration
OBS includes built-in Cut and Fade scene transitions, and you can set a duration for a transition such as Fade. A Cut changes immediately. A Fade blends between the outgoing and incoming scenes over the selected duration. Choose according to the footage: a cut can keep a demonstration crisp when the composition is similar, while a fade can soften a deliberate change from a close-up to a title card.
There is no single duration that suits every product demo. A longer fade may make a layout change less abrupt, but can also leave the product and the next scene visible together for longer than you want. A short fade may read almost like a cut. Preview the actual content at normal viewing size and choose the duration by what remains legible, not by trying to make every change look decorative.
This setting applies when OBS transitions between scenes. If one Media Source loops inside a scene, the scene has not changed at the media boundary. Likewise, placing multiple clips in a VLC playlist does not turn each file handoff into an OBS scene transition. That is the key distinction when diagnosing a jump: first establish whether the visible change coincides with a scene switch or with a file restarting.
Studio Mode helps when you are manually choosing the next scene. You can prepare the next composition and check its crop or overlays before transitioning it to the live output. If the show is fully automated and no operator will be selecting scenes, design and test the sequence in advance; Studio Mode does not make a loop boundary seamless by itself.
For a different kind of always-on OBS workflow, see how RadioDJ and OBS work together for a YouTube radio station. It is relevant if you are considering playlist-style programming, but do not conflate an audio-radio workflow with a product-video sequence. The right playback source depends on whether your demos are one file, a list of files, or distinct scenes with different layouts.
Inspect the last-to-first frame boundary
A loop restarts playback; it does not promise a seamless edit. Check the last frame and audio of the file against the first frame and audio. If the product changes angle, the camera moves, the background brightness jumps, or the sound cuts to a different room tone, the seam may be visible or audible every time the file repeats.
Look at the boundary as a viewer would. Play the end, note the composition and motion, then play the opening immediately afterwards. Repeat that handoff several times. A still frame at each end can be helpful, but moving footage matters too: a slow camera pan that ends on one side and restarts from the other can produce a jump even if the product appears in both frames.
Audio deserves the same attention. A music bed that stops abruptly and begins at a different level can call attention to the loop more than the picture does. Listen at the volume intended for the stream, using headphones or speakers that reveal a click or sudden change. If speech is present, avoid a loop that cuts a word or restarts with an unnatural fragment.
If the boundary is poor, the most reliable remedy is in the media: select a clip with compatible endpoints, edit the footage so the final and opening moments lead into one another, or build a deliberate pause or closing-and-opening structure. A dissolve can be authored into the video if it suits the shot, but it needs to be part of the media edit or playback arrangement. A scene fade cannot fix the last-to-first cut inside a looping file.
Do not try to hide every seam with extra OBS scenes unless the scene genuinely changes. You may make the sequence harder to operate while leaving the file’s own restart untouched. Keep a note of the timecode or moment where the discontinuity occurs, revise the media if needed, and recheck the new export in OBS. This distinction is useful when a demo has polished scene transitions but still seems to “jump” every few minutes: the problem may be the clip’s own boundary.
A 24/7 loop has no natural stopping point for the audience, so a small discontinuity will repeat rather than disappear after one playback. If the content is an informational loop, consider whether the order itself helps viewers who arrive partway through. For example, a brief title or product identifier near the start can make the sequence understandable to someone who did not see the previous cycle, but it does not substitute for a clean edit.
Test the full sequence in preview
After setting up sources, test the sequence in OBS before broadcasting. Start at the beginning, follow every clip or scene in order, and stay through the final-to-first handoff. Check picture framing, overlays, volume changes, transitions and timing. A transition that looked acceptable on a still thumbnail may obscure small product details during motion.
If you operate scenes manually, rehearse the order and use Studio Mode to inspect the next scene before putting it live. If the playlist should continue while hidden, switch away and return during the test to observe whether it pauses or restarts. Test the actual switching pattern you plan to use, since visibility behaviour can change what viewers see when you bring the source back.
When you are preparing a YouTube live stream, use YouTube’s encoder guidance to test representative audio and motion, and preview in Live Control Room before starting. YouTube recommends monitoring stream health and audio/video during the event in its live streaming tips. Its encoder settings guidance covers resolution, frame rate, bitrate, CBR and keyframe interval; choose settings for the resolution you are sending and a stable upload connection rather than treating one table row as universal.
A local OBS preview checks the composition and playback, but does not show the entire YouTube ingest path. If the channel or connection is new to live streaming, check YouTube’s current eligibility and getting-started guidance, then conduct a private or otherwise appropriate test using the intended stream configuration. Keep your stream key private: it is a credential for sending the encoder feed to your channel.
For an always-on channel, a loop also needs to survive when your own computer is not being watched. If OBS is running locally, the machine, power and internet connection are all part of that plan; see the discussion of a nonstop church YouTube stream’s format and bitrate choices when checking media and connection trade-offs. StreamNeo removes the specific burden of leaving your computer running for an uploaded-file YouTube loop: you upload the video and provide your stream key, then the broadcast runs without your computer on. It is YouTube-only, so it is not a replacement for an OBS scene workflow when you need to switch live layouts or combine cameras and sources.
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 loop a video in OBS?
Add the local file as a Media Source and enable Loop. Then play it through, including the restart, because Loop restarts playback but does not guarantee that the ending and beginning match.
How do I repeat a playlist in OBS?
Add a VLC Video source, make a playlist of the files in the intended order, and enable Loop Playlist. OBS requires VLC to be installed and notes that its bitness should match OBS; test what happens when the source is hidden and shown again.
How do I make a smooth transition between OBS scenes?
Choose a scene transition such as Fade and set its duration in OBS, then preview the change with the actual scenes. The right effect and duration depend on the footage and how much overlap still keeps the product readable.
Will a scene fade hide the cut when a looping clip restarts?
No. The fade handles a change between OBS scenes, not the last-to-first edit inside a media file that loops in one scene. Inspect the file boundary and adjust the footage or its edit if the restart is visibly or audibly abrupt.