To show product demos in sequence on YouTube Live with OBS, create a scene for each demo and switch between those scenes with hotkeys or Studio Mode. If every demo runs in a separate application window, OBS’s Automatic Scene Switcher can react to the active window, but that is not the same as a timed rotation.
The right method depends on who or what decides when the next demo appears. For a planned presentation, an operator can advance at the right moment; for a window-led demonstration, OBS can react when you focus a configured window. Test the whole path from scene to YouTube preview before treating it as ready for a long broadcast.
Build one scene for each product demo
A scene is a layout of sources that OBS sends to the programme output. Make one scene for each distinct product demo, then give it a name that tells you what a viewer will see: “Demo — kettle controls” is more useful than “Scene 3”. Clear names matter when you are switching by keyboard or checking the preview during a broadcast.
Start with the sequence you actually intend to present. If you have three products, you might prepare an opening scene, one scene per product, and a closing or holding scene. The opening and holding scenes are optional, but they give you somewhere deliberate to go while you introduce the stream, answer a question, or recover from a demo that is not ready. Do not add scenes simply to imitate a playlist: each should have a purpose.
The scene-per-demo approach separates the layout and sources for one product from those for another. A browser-based product can have a browser source in its scene, while a desktop application demo can use an application or display capture. That makes it easier to adjust one demo without accidentally changing the layout of another. OBS’s source guide describes the different source types available, including browser, image, audio and capture sources.
Before building, decide what stays consistent. You may want the same logo, lower-third, background or microphone audio in every scene. Add those elements consistently and check their position and visibility in each scene. A source that exists in one scene does not automatically appear in another; if it needs to be present throughout, include it in each relevant scene or use an appropriate shared-source arrangement in OBS.
Keep a simple scene map beside you while setting up. List each scene, the product or purpose it covers, and the source it depends on. This catches a common rehearsal problem: the scene name is right, but the wrong application or media file is in it. For a broader prerecorded presentation workflow, the guide to streaming recorded cricket commentary around the clock offers related planning context, though a live product demo needs its own scene and switching choices.
Add the capture or media sources
For an application demo, add the appropriate capture source and select the application or window you intend to show. For a web page, use a browser source or capture the browser window, depending on whether you need a controlled page inside OBS or the actual browser interface. For product footage, an image, or a prerecorded clip, add the corresponding media source. OBS’s source guide is a useful reference when choosing among these inputs.
Check each source while its scene is selected. Confirm that the product is framed properly, any important controls are readable, and no private desktop content, notifications or unrelated windows are visible. If you are capturing a whole display, remember that anything appearing on that display may enter the broadcast. A window capture can limit what is shown, but its behaviour depends on the application and capture method; rehearse on the computer you will use live.
Audio deserves its own check. A product demo may need microphone narration, the application’s sound, or both. Watch the OBS audio meters while speaking and operating the demo, then listen to the output rather than assuming a visible meter means the mix is suitable. If viewers will hear prerecorded material, verify that it is present and clear in the stream output; the troubleshooting guide on pre-recorded video with no sound on a YouTube stream covers a related failure mode.
If you use prerecorded clips as part of a demo, set up and test their playback behaviour separately from scene switching. A scene change changes which layout is live; it does not, by itself, define a reliable timed programme of clips and transitions. Check whether a media source starts, stops or continues in the way you expect when you leave and return to its scene. The FFmpeg concat demuxer and playlist comparison is relevant if your real requirement is assembling continuous prerecorded video rather than switching among live OBS layouts.
Give sources descriptive names as well as scenes. When a source needs attention during rehearsal, “Browser — product setup page” is easier to identify than “Browser Source 2”. Avoid changing source settings while the stream is live unless necessary: changing capture targets or resizing a source can create a visible interruption or expose the wrong content.
Switch scenes with hotkeys
For a host-led product presentation, hotkeys give you direct control over when each demo appears. In OBS settings, assign a distinct keyboard shortcut to each scene, then practise the sequence without streaming. OBS documents scene hotkeys in its Studio overview. Choose combinations that are unlikely to be pressed accidentally while typing or using the product.
A useful test is to rehearse the spoken hand-off and the key press together. For example, finish the current explanation, say that you are moving to the next product, then switch to its scene. Check that the scene changed and that the expected source is visible before continuing. This is less distracting than discovering mid-sentence that a shortcut was assigned to the wrong scene.
Hotkeys work well when a person is deciding the pace: a presenter can spend longer on a feature that needs explanation, pause for questions, or skip a demo that is not behaving. Their trade-off is that someone must be available and attentive to operate them. If the broadcast is meant to run unattended, an operator-led method does not solve that requirement; do not mistake a collection of scene hotkeys for a scheduled sequence.
Use a keyboard you can operate comfortably, but you do not need a special scene controller. A spare keyboard can be convenient if it reduces the chance of typing into a product window, but it adds another device to test and is not a prerequisite. Whatever you use, verify that the shortcut still works when the relevant application has focus, since your workflow may involve switching between OBS and a demo window.
Write down the key-to-scene mapping near the operating position. Keep it concise: the scene name and its shortcut are enough. This is particularly useful if another person takes over the stream or if you return to the setup after a break. Rehearsing the mapping is more dependable than relying on memory during a live demonstration.
Preview the next scene with Studio Mode
Studio Mode is useful when you want to prepare a scene before putting it on air. OBS presents a preview scene separately from the live scene, and you use a transition to move the prepared scene to the live output. The OBS overview explains Studio Mode and the available transition controls.
The practical difference is that selecting or editing the next scene in the preview does not immediately replace what viewers see. You can check framing, source visibility and the transition, then commit when you are ready. That small pause helps when the next product window is still loading or when you need to confirm that the correct clip has been selected.
Rehearse the exact transition you will use. A cut is direct; a different transition may make the change more noticeable or take longer to complete. Do not assume a preview of the scene is proof that every source is behaving correctly on the live output. Confirm the result after transitioning, including the audio mix and any source that should remain present across scenes.
Studio Mode adds a deliberate operator step. It is a good fit for a presenter who wants to review each scene before switching, but it does not create a timed rotation. If your goal is to display demos in a fixed order without anyone at the controls, you need to establish a separate, verified playback or automation method rather than treating Studio Mode as a scheduler.
Use Automatic Scene Switcher for matching windows
OBS’s built-in Automatic Scene Switcher addresses a different problem: associating scenes with application windows and changing scenes when the relevant window becomes active. In the documented OBS example for OBS 31.1 and later, you create scenes for the relevant windows, configure the switcher from the Tools menu and activate it. Focusing a configured window then triggers the associated scene. See the OBS League of Legends capture guide for that window-based example.
This can suit a product presentation where every demo lives in a distinct application window and you deliberately focus each one as you move through the presentation. It can reduce the need to press a scene hotkey at the same time as changing windows. The behaviour is still tied to window focus: an accidental click into another configured window may change the scene, and an unconfigured window may not produce the transition you expect.
Do not describe this as timed scene rotation. The cited OBS guide demonstrates switching in response to the active window; it does not establish that the built-in feature advances scenes at set intervals or cycles through demos unattended. Window-triggered switching and scheduled playback have different triggers and different failure modes. If an unattended schedule is essential, verify a current, maintained tool that explicitly supports that behaviour and test it separately before relying on it.
| Method | What triggers the change | Useful when | Main trade-off |
|---|---|---|---|
| Scene hotkey | The operator presses a shortcut | You decide the pace while speaking | Someone must press the right key at the right time |
| Studio Mode | The operator transitions a prepared preview scene | You want to check the next scene before it goes live | It is an operator-controlled transition, not a schedule |
| Automatic Scene Switcher | A configured application window becomes active | Each demo has its own window and you intentionally focus it | Window focus, not elapsed time, determines the change |
Try only one switching method at first. If you use window switching and hotkeys together, identify which one takes precedence in practice and test for accidental changes. Keep a fallback hotkey available if that suits your setup, but rehearse it before broadcast so it does not become another source of uncertainty.
Test the sequence and YouTube output
Test from the start of the programme to its final scene, not just by clicking each scene once. Check that each product appears in the intended order, the capture stays on the right window, transitions look acceptable and audio remains intelligible. Repeat the sequence after reopening OBS if the setup will need to survive a restart; a saved scene collection is only useful if its sources reconnect as expected.
For a window-triggered setup, test by focusing every configured window in turn, then visit an unrelated window and observe what happens. Confirm that switching occurs only in the circumstances you expect. For hotkeys, practise the entire presentation using the actual keyboard and applications. For Studio Mode, rehearse preparing the next scene and transitioning it while checking that the current live scene remains correct until the transition.
Then test the encoder connection to YouTube. YouTube’s encoder instructions explain that the stream URL and stream key are entered into the encoder settings. Treat the key as private, and confirm that OBS is sending the intended scene and audio to the correct scheduled or created stream. Wait for the Live Control Room preview and check it before going live.
YouTube recommends setting up the encoder in advance, checking the preview and monitoring audio and video during the broadcast in its live streaming tips. An unlisted test stream is a practical way to inspect what reaches YouTube without presenting the rehearsal as a public product demo. Check the preview on the same kind of device your viewers are likely to use if possible; small product details that look clear on a desktop monitor may be difficult to read on a phone.
During a real broadcast, keep an eye on both the programme and the YouTube preview. Look for a frozen capture, missing application audio, an unexpected scene change or a product window that has moved or closed. If a scene fails, use a known holding scene or return to a safe layout while you correct it. Avoid making promises about uninterrupted operation: test and monitoring help you notice problems, but no scene-switching method removes the need to watch the output.
If your central difficulty is keeping a prerecorded visual live while your own computer is off, StreamNeo removes the need to leave OBS running on that computer by turning an uploaded video into a YouTube live stream. That addresses a fixed-file broadcast rather than the operator-led scene changes described here, so choose it only if it matches the programme you intend to 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
Can OBS automatically switch between product demos at set intervals?
The built-in Automatic Scene Switcher example covered here switches in response to a configured application window becoming active. The cited documentation does not establish timed rotation, so do not rely on it as a scheduled carousel. Verify a separate current tool if interval-based sequencing is essential.
What is the simplest way to switch during a narrated demo?
Assign a distinct hotkey to each demo scene and rehearse the order with the product windows open. If you want to inspect the next scene before it appears, use Studio Mode and transition when ready. Both approaches leave the timing under your control.
Will changing scenes change the audio too?
It can, depending on which audio sources are included and how they are configured in the scenes. Check the OBS meters and listen to a test output while moving through every scene; do not assume that visible video means the intended microphone or application sound is reaching viewers.
Should I test on YouTube before making the stream public?
Yes. Connect OBS to the intended YouTube stream, inspect the Live Control Room preview, and rehearse the scene changes in an unlisted test when appropriate. YouTube’s guidance supports checking the preview and monitoring the stream, but a test does not guarantee that a later live broadcast will have no problems.