OBS scenes organise the visual layouts in your broadcast; they do not, by themselves, keep a channel live around the clock. For a prerecorded programme, build scenes around the distinct parts viewers will see, add the relevant media and overlays, then save and test the configuration before you go live.
This guide focuses on that scene-and-source workflow. It does not assume OBS will advance scenes on a timer or manage a continuous broadcast without an operator or another playback arrangement. Check current YouTube guidance for platform-specific live settings before broadcasting.
Plan scenes around prerecorded segments
Start with the programme, not with a collection of effects. Write down the visual parts of a typical run: perhaps an opening slate, a main bhajan or talk, an intermission card, and an ending slate. Give each part a scene only if its layout or media needs to differ. A scene is a layout; its sources supply the video, text, images, and other visible or audible elements.
For example, a devotional channel might use an opening scene with a channel name and a short welcome, a main scene containing a prerecorded performance with a small logo, and an intermission scene with a still image and quiet background audio. A local news loop might instead need a title card, one scene per format with a consistent lower-third graphic, and a closing notice. The point is to make it clear what belongs on screen at each point, not to create a separate scene for every clip or every line of text.
Sketch the source layers for each layout before building it. Note which item is full-frame video, which is a title or logo, and whether any image should remain visible when a video ends. This makes it easier to spot conflicts such as a title being hidden behind a full-screen source or an ending card not being present in the scene where you expect it.
Also decide how scene changes will happen. If a person will move from the opening to the main segment, OBS can be operated manually, including with a scene-switch hotkey. A saved scene collection is not a timed rundown, however. If you need unattended switching between prerecorded files, plan and test that playback workflow separately rather than assuming the scenes themselves provide it. The guide to restarting a media playlist in OBS covers a related playback concern.
Create and name scenes in OBS
In OBS, use the Scenes dock to add a scene, then select it and add sources in the Sources dock. Create the small set of layouts from your plan. Names such as Opening, Main programme, Intermission, and Ending are easier to operate than Scene 1 or New Scene 4, especially when you return to the project after a break.
Keep names short enough to read in the dock, but specific enough to distinguish layouts that look similar. If you have a separate version for a weekday and a weekend programme, include the distinction in the scene or collection name rather than relying on memory. Avoid duplicating scenes just to change one title if you can use a clear, maintainable source arrangement instead.
OBS allows sources to be used in scenes, and you can organise those layers according to what the viewer should see. A logo that appears throughout may be added to each relevant scene. A source in one scene should not be assumed to appear in another; inspect each layout in the preview. The OBS sources guide explains scenes and sources, including the way source order controls what appears above other items.
There is a practical trade-off between reuse and clarity. Reusing the same image or media source in multiple scenes can reduce repetitive setup, but it can also make it less obvious which source settings affect which segment. For a simple channel, explicit scene layouts are often easier to inspect than a highly nested or complicated set of sources. If the collection grows large, keep a separate scene collection for this programme rather than mixing it into an unrelated production setup.
Add prerecorded media as a source
For a single local prerecorded file, add a Media Source to the scene that should show it and choose the file. This is the direct approach when the scene represents one video segment. OBS lists video formats including MP4, TS, MOV, FLV, MKV, AVI, GIF, and WebM, and audio formats including MP3, AAC, OGG, and WAV in its Media Sources documentation. Confirm the file plays and that its framing fits the scene before relying on it in a broadcast.
The Media Source settings let you choose behaviours such as looping, restarting when the source becomes active, hiding after playback ends, and closing the file while inactive. Choose based on the segment’s role. A short opening clip may need to restart when its scene becomes active; an ending slate may need to remain visible rather than disappear with the video. A looping source can repeat its file, but that setting should not be confused with automatic movement through a multi-part programme or with keeping the whole live broadcast connected.
For several files that should form a playlist, OBS offers a VLC Video source with playlist and loop or shuffle controls. The VLC source only appears when VLC is installed, and OBS documentation specifies that its architecture must match OBS: for example, 64-bit OBS requires 64-bit VLC. A playlist can be useful when the scene’s job is to present a series of media items, but verify the actual order and end behaviour in a test. It does not replace checking that your stream remains live or that YouTube receives the intended output.
| Need | Suitable OBS source or setting | What to verify |
|---|---|---|
| One local video in a scene | Media Source | File selection, framing, audio, and end behaviour |
| One file to repeat | Media Source with looping enabled | It repeats as intended and does not obscure the planned next step |
| Several files in a playlist | VLC Video source | VLC is installed with an architecture matching OBS; order and loop or shuffle behaviour are correct |
| A visible still card after a clip | Image source or another retained layer | The card is above the background and remains visible in the scene |
If your file has not been prepared for the intended output size, address that before building many scenes. The HandBrake settings guide for 1080p stream video can help you think through file preparation, while this article remains focused on how the prepared media is arranged in OBS.
Layer titles and graphics with source order
OBS draws sources in a stack. Sources higher in the list appear over sources lower in the list, so a full-screen video belongs beneath a logo, title, or lower-third that should remain visible. If a title vanishes after you add the video, inspect the source order before rebuilding the scene. Select and move the source in the list until the preview shows the intended layers.
A typical main scene might have a background image or video at the bottom, the prerecorded segment above it, then a small logo and a title at the top. The actual order depends on the design: a full-screen video may cover a background entirely, while a transparent logo image should sit above it. Text and image sources are separate objects, so you can reposition or hide them without editing the video file.
Check the edges and safe areas in the preview. Text that looks centred on your monitor may be cropped or too close to the edge of the output. Keep titles readable against the picture behind them, and avoid stacking several opaque graphics over the part of the footage viewers need to see. If the programme uses several formats, use a consistent logo and title position so that viewers do not have to reorient at every change.
For an intermission, consider whether the intended scene should contain a still graphic, a low-level audio source, or both. A muted or hidden source can be confusing when you return to a collection later, so name sources clearly and remove obsolete layers. A scene with only the essential items is easier to test and less likely to reveal an old title or an unexpected source.
Save the scene collection and profile
OBS separates scene layouts from stream and output settings. A Scene Collection stores scenes and sources, while a Profile stores stream, video, and output settings. They are different pieces of the setup and should be saved and selected deliberately. The OBS Scene Collections guide and Profiles guide describe what each saves.
Use a descriptive collection name for the programme, such as Morning devotional, and a profile name that tells you which output configuration belongs with it. If you use OBS for other purposes, keeping the programme in its own collection reduces accidental changes to unrelated scenes. Remember that switching a Profile does not bring along the scenes; switch to the matching Scene Collection as well.
After saving, close and reopen or deliberately switch away and back, then inspect the scenes and settings you expect to use. This is a simple way to catch an unsaved change or a mismatch between collection and profile. Check media paths too: a scene can retain its layout while a source no longer points to an accessible file if you moved or renamed it. Store the source files in a stable location and confirm OBS can still open each one.
If a collection becomes sluggish or hard to manage, simplify it. OBS’s encoding performance troubleshooting guidance advises reducing unnecessary complexity and resource-heavy elements when performance is poor. That may mean removing unused sources, avoiding excessive filters, or using fewer demanding browser sources. This is not a promise that a simpler scene will solve every performance issue; it is a sensible first check when preview or output is struggling.
Preview transitions and playback
Before a broadcast, move through each planned scene and look at the preview. Confirm that the opening appears as designed, the main video fills the intended area, the intermission card is readable, and the ending scene has the right final image. Switch between scenes the way you expect to operate them during the programme, rather than only checking each one in isolation.
If you will advance manually, assign and test a scene-switch hotkey that is easy to use without confusing it with another shortcut. OBS supports hotkeys for switching to a specific scene. If you use Studio Mode, practise the preview-and-transition action so that you understand which scene is currently on the output and which is staged for the next change. Neither feature should be treated as an automatic schedule of scene changes.
Play the media from the start and observe the whole behaviour that matters: image, crop, audio, and what happens at the end. For a playlist, check the sequence and any loop or shuffle choice. For a source set to restart on activation, switch away and return during a test to see whether its behaviour matches your plan. Do not infer an unattended 24/7 playback system from a successful scene change; scenes organise the output, while continuous playback and broadcast operation require their own tested arrangements.
Listen through headphones or speakers and watch the audio meters while the file plays. A video can appear correctly in the preview while its audio is missing, too loud, or coming from the wrong source. Check that the intermission audio does not overlap unintentionally with the programme, and that a source you expect to be silent is actually silent. For further context on operating a long-running setup, see the guide to monitoring and troubleshooting a YouTube live stream.
Check the output before broadcasting
Preview is not the same as checking the output that will be sent. Review OBS’s stream and output settings, confirm the intended profile is selected, and make a short test recording or test stream. Watch or listen to the resulting output, not only the OBS canvas. The OBS Quick Start Guide recommends testing for a few minutes before a first stream; use a test long enough to check the transitions and media behaviour that matter to your programme.
Look for practical faults: a title outside the visible area, black frames when a scene changes, a source that shows an old file, silent audio, or an ending slate that disappears too early. If the output stutters, simplify the scenes and check whether expensive filters or browser sources are contributing. If you need to adjust the media or settings, make the change, save it, and repeat the relevant test rather than assuming the fix worked.
For platform-specific settings, scheduling, channel eligibility, and ingest details, consult current YouTube Help rather than relying on a remembered menu path. This setup guide does not establish those YouTube requirements. A correct OBS scene collection cannot guarantee that a stream is accepted, remains connected, or meets every channel-specific condition.
If you need the programme to run while your computer is switched off, scene design in OBS alone does not provide that. StreamNeo can remove the need to leave your own computer running for the broadcast by taking an uploaded video and stream key for a YouTube-only stream; decide separately whether that arrangement suits the way your content is prepared and operated. Your OBS scenes still need to be organised and checked for the output you intend to produce.
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
Do OBS scenes keep a prerecorded channel live 24/7?
No. Scenes are visual layouts, not a guarantee of continuous playback or a connected broadcast. You need a separate, tested way to operate the playback and maintain the live stream.
Should I use Media Source or VLC Video?
Use Media Source for a single local file in a scene. VLC Video is useful when you want a playlist, but it requires VLC installed with an architecture matching OBS and you should test its ordering and playback behaviour.
What is the difference between a Scene Collection and a Profile?
A Scene Collection saves scenes and sources. A Profile saves stream, video, and output settings, so select the matching pair when you return to this programme.
How can I confirm the setup before going live?
Preview every scene, play the media through the points where it changes or ends, watch the audio meters, and make a short test recording or stream. Review the resulting output and correct any visible, audio, or playback issue before broadcasting.