A dedicated OBS Scene Collection keeps the scenes and sources for your YouTube loop separate from your other broadcasts. Put the YouTube connection and output settings in an OBS Profile instead: collections do not store output settings.
Create the collection, add a scene with a looping media source, then run a short test before the planned broadcast. This gives you a setup you can recognise and switch back to without mixing the loop show's layout into a gaming, podcast or recording setup.
What a Scene Collection keeps separate
An OBS Scene Collection is a set of scenes and their sources. You can use separate collections for different productions, then switch collections when you change what you are making. For a dedicated loop stream, that means the scene layout, video source, text and other visual or audio sources can live together apart from your other OBS work.
Collections also contain Global Audio Sources. Bear that in mind if you use global devices: switching collections is not necessarily a way to isolate every audio input. Check the sources shown in OBS after you create the collection, especially if a microphone or desktop audio source should not be part of the loop.
The collection is not where OBS saves the stream destination, video settings or output configuration. Those belong to a Profile. OBS's Scene Collections documentation explicitly distinguishes the two. Keeping that distinction clear is the central part of this setup: the collection organises what is on screen; the Profile organises how OBS sends the broadcast.
For example, you might have a collection called “Evening Bhajans” containing one loop scene, a background video and a small channel mark. A separate “Tutorial Recording” collection can hold a screen capture and microphone layout. You can pair either collection with an appropriate Profile without rebuilding the scenes each time.
This separation also makes changes easier to reason about. If the picture is wrong, look first at the loop collection's scene and sources. If OBS is sending to the wrong YouTube destination or using an unintended output setup, inspect the active Profile rather than expecting the collection to have retained those settings.
Create or select a dedicated collection
In OBS, open the Scene Collection menu and choose the option to create a new collection. The exact menu placement or wording can vary between OBS versions, so look for the collection controls in the application rather than relying on a particular screen position. Give the collection a plain name that will still make sense when you return to OBS later, such as “YouTube Loop — Devotional” or “Local News Loop”.
If you already made a collection for this exact show, select it instead of creating another. Avoid using a general-purpose collection simply because it is currently active. A dedicated name reduces the chance that you will add a source to the wrong production or change a scene that belongs to another broadcast.
After creating or selecting it, look at the Scenes list and Sources list. A new collection may start with an empty workspace or a default scene, depending on your version and prior state. Remove or rename any placeholder scene that could be mistaken for the real loop scene. Before you begin building, confirm the collection name in OBS so that subsequent edits land in the intended place.
A dedicated collection is useful when you expect to switch back and forth between types of work. It is not a backup by itself. If this is a setup you cannot easily reconstruct, preserve a separate copy of your media and make a note of the scene names and source choices. The collection keeps the OBS arrangement organised; it does not protect the video file from being moved or deleted outside OBS.
Build the loop scene
Create a scene with a name that describes what viewers will see, such as “Main Loop”. In that scene, add a Media Source and browse to the video file on the computer running OBS. Use a file location that will remain stable; if you move or rename the file later, OBS may no longer find it at the saved path. Confirm that the preview shows the expected video before adding decoration.
Keep the scene as simple as the programme requires. For a devotional loop, that may be the video and a small channel identifier. A study or ambience stream may need no text at all. Each extra source is another item to position and check, so add overlays only when they serve a clear purpose. The OBS Studio overview guide explains the basic relationship between scenes and sources.
OBS composites sources in their listed order. A source higher in the list can appear over sources beneath it, so if a logo disappears behind the video, move it above the video source. Use the preview to inspect the full frame, including its edges. Check that text is readable against both bright and dark portions of the footage, and make sure nothing important is hidden by an overlay.
Audio deserves the same deliberate check as the picture. Play the source in preview and listen for whether its audio is present, whether it is at a sensible level, and whether an unintended microphone or desktop audio source is also active. A loop image can look right while its audio is silent or doubled. Do not assume that a source's presence in the list proves that the final mix is correct.
Keep source names understandable. “Main video” and “Channel mark” are easier to recognise in a later fault check than several sources with the same default name. If you make a second scene for a holding screen or a break, give it an explicit name too. A scene collection is most useful when you can tell what each part does without having to open every property window.
Enable looping on the media source
For a single local file, open the Media Source properties and enable Loop. This tells OBS to begin the file again when playback reaches its end. The OBS Media Sources documentation lists supported formats, including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM. A format appearing in the list does not remove the need to test your own file in OBS.
After enabling the setting, let playback reach a point where you can observe it, then check the source properties again if necessary. A short preflight need not wait for a very long video to finish, but it should confirm that the correct file is selected, playback begins, and the loop option is enabled. If the file has an audible ending or a visible jump at its boundary, remember that the loop control repeats the file; it does not edit the transition between its end and beginning.
For a playlist rather than one file, OBS offers a VLC Video source with a Loop Playlist control. You can add the playlist entries and enable that option so playback starts again after the list ends. The VLC source requires VLC to be installed; OBS notes that 64-bit OBS requires 64-bit VLC. That dependency matters if you are preparing the scene on a fresh computer or moving the setup to another machine.
| Choice | Fits this workflow | Loop behaviour | Consideration |
|---|---|---|---|
| Media Source | One local video file | Enable Loop to replay at the end | Built into OBS; choose and test the file path |
| VLC Video | A playlist of media | Enable Loop Playlist to restart after the list | VLC must be installed, with matching architecture for 64-bit OBS |
Neither choice is universally better. A single-file programme is simpler with Media Source. A playlist is more suitable when you want multiple entries to cycle as a sequence and are prepared to install VLC. Consider what should happen when a source is hidden during a scene change as well: the source's visibility behaviour can affect whether it continues, pauses or stops, depending on its settings.
If you later replace the loop file, check the source path and properties rather than assuming the new media inherited every intended setting. For a broader workflow on changing material without losing track of the active loop, see how to change videos in a running YouTube loop stream. Keep a note of whether the scene uses one file or a playlist so the next edit is made in the right source type.
Configure YouTube output in a Profile
Create or select an OBS Profile for the YouTube broadcast and configure the stream and output settings there. OBS Profiles save settings such as Stream, Video and Output, while Scene Collections save scene and source arrangements. The OBS Profiles guide describes how profiles and collections can be combined; for instance, a YouTube profile can be paired with a separate collection for a different use.
Before you start a test, verify that the active Profile is the one intended for this channel. Check the stream connection and the output choices you have configured in OBS. The Profile is the place to revisit when those settings need changing; switching to the loop Scene Collection alone should not be treated as changing the destination or output configuration.
This is particularly useful if the same OBS installation serves several jobs. You might keep the same YouTube Profile while switching between a loop show and another collection, or use a distinct Profile when the output configuration genuinely needs to differ. The choice depends on how you organise your work, but the distinction remains: Profile for stream and output settings, collection for scenes and sources.
Do not infer that this OBS setup guarantees YouTube will accept or continue any particular broadcast. Platform eligibility, channel status and current live-stream rules are separate matters. Check the current official YouTube Help information for your account and planned format before scheduling a long broadcast. Test the OBS side too; correct settings are only one part of a functioning stream.
If keeping a computer running OBS for a long loop is itself the part you are trying to avoid, StreamNeo can remove that specific need by taking an uploaded video and running it as a YouTube live stream while your computer is switched off. That is a different workflow from building an OBS collection, so choose it only if an OBS-based local setup is not the requirement.
Run a short test stream
Before the planned broadcast, use a short test to check the complete path from scene to output. OBS's Quick Start Guide recommends testing for a few minutes rather than moving straight into a first stream. Check the current YouTube guidance on testing and streaming from your account as well, since the platform and channel controls are outside the Scene Collection.
Start with the active collection and Profile visible in OBS. Confirm the loop scene is selected, the expected video is playing, and the preview is framed as intended. Listen to the audio. Look for unexpected sources, black margins or an overlay covering important content. If the media is a playlist, confirm that the entries load and that the VLC source appears as expected.
During the test, verify that OBS is using the intended stream connection and that output begins. Where possible, check the resulting live view in the relevant YouTube interface or use an appropriate private test arrangement for your channel. Do not assume that seeing a moving preview in OBS proves that the audience-facing output is correct.
Use a short preflight list rather than relying on memory:
- Correct Scene Collection selected, with the loop scene active.
- Correct Profile active, with the intended stream and output settings.
- Correct local file or playlist loaded, with the appropriate loop option enabled.
- Picture framed properly and overlays legible in the preview.
- Audio present and free of unintended microphone or desktop sources.
- Test output visible through the channel's intended YouTube workflow.
If a check fails, change one relevant setting at a time and repeat the part of the test affected by it. For example, a missing video points first to the source path or media properties; a wrong destination points to the Profile's stream settings. This avoids changing the scene and output configuration together, which can make the cause harder to identify.
A short test is not a promise that a future long broadcast will never encounter a problem. It is a way to catch setup errors while there is time to correct them. If you are assessing a computer-based 24/7 arrangement, consider the practical limits of the device and whether you can monitor it; this guide to running a 24/7 stream on a Chromebook, tablet or low-end laptop covers the different constraints those devices can introduce.
If a stream has stopped unexpectedly before, distinguish the scene setup from the wider cause. A collection can help you keep the intended sources together, but it cannot diagnose every interruption. The guide to why a 24/7 YouTube stream stops after a few hours is a useful next step for troubleshooting beyond scene organisation.
When the test looks and sounds right, save your work and note which Profile and collection form the working pair. That small record is useful when you return after editing another show.
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 Scene Collection save my YouTube stream key or output settings?
No. OBS stores stream, video and output settings in a Profile, while a Scene Collection stores scenes and sources. Select the intended Profile separately when preparing to stream.
Can I loop a playlist without VLC?
The VLC Video source used for playlist looping requires VLC to be installed. For one local video file, use OBS's built-in Media Source and enable Loop instead.
Will enabling Loop remove a visible jump at the end of the video?
No. It makes OBS replay the file after it finishes, but it does not smooth or edit the transition. Check the end and beginning of the media itself during your test.
Does this setup guarantee a continuous 24/7 broadcast?
No. The collection and source settings organise a loop in OBS, but they do not guarantee uninterrupted streaming or YouTube approval. Test the full setup and check current official platform guidance for your channel.