Use OBS Studio to prepare separate scenes for product demonstrations and customer tutorials, then switch between them with OBS controls or hotkeys. YouTube Studio schedules and manages the event; OBS, or another encoder, creates and sends the programme feed.
That distinction matters: scheduling a YouTube event does not make Studio a scene switcher, and changing an OBS scene does not guarantee an uninterrupted broadcast. Plan the segments, rehearse the encoder output, and use Studio to check the incoming preview and manage the event.
Plan the demo and tutorial segments
Decide what viewers should see in each part before building scenes. A product demo might show a physical item on camera, a software window, or both. A tutorial might put instructions or a product interface in the largest area, with the presenter visible only if their explanation benefits from it. Each scene should have one clear purpose, rather than accumulating windows and labels that compete for attention.
Write a simple running order with cues that tell the operator when to switch. For example: introduce the product, show a particular feature, move to a tutorial explaining setup, then return to the product for questions. For a live presentation, these cues can be tied to what the presenter has finished saying rather than fixed durations. A customer question or a demonstration taking longer than expected is a reason to wait, not to let a timer move the picture away mid-explanation.
Choose who will operate OBS. If you are both presenting and switching scenes, rehearse the controls until you can use them without losing your place. If a second person is available, give them a short cue sheet with scene names and transition points. Agree on a fallback cue such as “stay on the current scene” if the presenter needs more time.
Manual operation is usually the more direct fit when a demo can vary in length. An unattended rotation is a different production requirement: it depends on a separate automation method, and the documentation described here does not establish a native YouTube Studio feature for timed scene changes. Check any proposed automation tool’s current compatibility and maintenance, and do not make it the only plan for recovering from a missed or mistimed change.
| Production choice | Manual scene changes | Automated switching |
|---|---|---|
| Who decides when to change | The operator, using the running order or presenter cue | A configured rule or timer |
| Suits | Live demonstrations, questions, and variable segment lengths | Rehearsed sequences with fixed timings |
| What to verify | Scene selection, hotkeys, and cues | Tool compatibility, timing, and a recovery method |
| YouTube Studio’s role | Manages the event, not the encoder’s scene choices | Still manages the event; automation is separate |
The trade-off is control versus reduced hands-on operation. A person can hold a scene while a presenter answers a question; automation can repeat a known sequence but cannot infer that a customer has asked something important. If an operator is required, build that responsibility into the run of show rather than assuming the stream will change scenes by itself.
Create OBS scenes and sources
In OBS, create a scene for each distinct layout. Name them for the action the operator needs to take, such as “Product demo” and “Customer tutorial”, rather than “Scene 1” and “Scene 2”. Clear names help you confirm the selection under pressure and make a cue sheet easier to follow.
A scene is a composition assembled from sources. Depending on the segment, sources can include a display or window capture, a camera, an image, text, and audio inputs. OBS’s guide to scenes and sources explains the building blocks and source types. For a software demo, capture the specific application window where practical, so notifications or unrelated parts of the desktop are less likely to appear. For a physical product, frame the item clearly and check that the camera is pointed at the right area.
In the tutorial scene, make the step being explained easy to read. If a software window is central, check that its important controls remain visible at the output size. A camera inset can help viewers see who is speaking, but it should not cover a button or instruction they need to follow. Use text labels only when they clarify which product or step is on screen.
Keep similar elements in consistent positions between scenes where that helps the viewer follow the change. For instance, a presenter camera can remain in one corner while the main area changes from a product shot to a tutorial window. Consistency is an editorial choice, not a requirement of OBS. Review the composition at the resolution you intend to send and check it on a smaller screen if viewers may watch on a phone.
Check the audio source separately from the visual scene. A microphone can carry the presenter’s explanation while the screen or camera changes; scene changes should not inadvertently mute it or introduce duplicate audio. A dedicated USB microphone may be useful if your narration needs a separate input, but buying equipment does not provide scene rotation. The relevant questions are whether the encoder receives the intended voice, whether playback is clear, and whether other sources are unexpectedly audible.
Use the OBS overlay setup guide if you need a visual label or other on-screen graphic, and keep it subordinate to the product or instruction. If the tutorial uses spoken explanations and viewers need text support, plan captions as a separate accessibility consideration; the guide to showing captions on a recorded lecture stream covers a related viewing need. Neither captions nor overlays replace checking the actual outgoing composition.
Configure scene hotkeys or manual switching
For a host-led event, the simplest control is often to select the next scene in OBS when the cue arrives. The operator can watch the presenter or follow the running order, then click the appropriately named scene. This avoids relying on YouTube Studio to make production decisions it does not make.
You can also assign scene-specific hotkeys in OBS. Choose keys that are easy to recognise and unlikely to be pressed during normal typing or presentation work. Check for conflicts with other applications and avoid placing the important controls where an accidental key press is likely. OBS documents scene hotkeys in its official overview; the exact settings available can change, so consult the current OBS interface and documentation when configuring them.
If a keyboard shortcut is used, rehearse it while the stream is not live. Confirm that each key selects the intended scene, that the change is visible in the output, and that keyboard focus or another application does not interfere. A scene-selection control is an alternative if hotkeys are uncomfortable or a second operator can manage the OBS window.
A hotkey is a command to OBS, not a guarantee that viewers will see a clean change. The encoder must still be running and sending its feed, and the relevant sources must be available. Keep the current scene on air if the next scene has a missing capture, incorrect framing, or muted audio; fix the scene before switching. For a broader checklist on watching a running channel, see how to monitor a 24/7 YouTube Live stream automatically, while remembering that monitoring does not remove the need for a person to judge a live demo cue.
Choose a cut or fade transition
A cut changes from one scene to another immediately. It suits a clear move from one subject to another, such as leaving a product close-up for a tutorial screen. Because the change is immediate, it is easy to understand and does not briefly blend the two layouts.
A fade transitions gradually. It can make a planned change feel less abrupt, especially when moving between a presenter introduction and a different segment. It also means both compositions may be visible during the change. If text, windows, or camera positions overlap in distracting ways, a fade can be less clear than a cut.
Choose one transition for the common scene changes and rehearse it in context. OBS provides Cut and Fade along with other transition options; its transition guidance describes how transitions operate. The right choice depends on the content and layout, not on a claim that one is inherently more professional. A cut is a sensible starting point for a demonstration that needs viewers to see the new screen promptly. A fade is worth testing when a softer visual hand-off better fits the show.
Do not use transitions to conceal an unprepared scene. Check the destination scene’s capture, framing, labels, and audio before the event. If a fade briefly reveals an old window or a misplaced camera box, adjust the scene rather than assuming viewers will not notice. Keep the transition simple enough that the operator can recognise what is happening while also listening to the presenter.
Use Studio Mode to preview changes
OBS Studio Mode gives the operator a preview area and a live output area. You can prepare or select a different scene in preview, inspect it, then take it to the live output when it is ready. OBS explains that this allows scene changes to be prepared in the background rather than showing viewers every adjustment as it is made.
This is useful when the tutorial scene needs a last check before it replaces the product demo. Look for the right application window, readable text, a camera that is not obscuring the lesson, and the expected transition. When satisfied, use the transition control to send the preview to the live output. The encoder remains responsible for producing that output; Studio Mode is an OBS production aid, not a YouTube Studio composition feature.
Without Studio Mode, selecting a scene may change the programme output immediately, depending on the OBS setup. That can be perfectly workable for a rehearsed, simple show, but it leaves less opportunity to inspect a change first. Try both workflows in a private rehearsal and choose the one the operator can manage reliably.
Studio Mode does not validate every part of the broadcast. It cannot confirm that YouTube is receiving the encoder feed, that the event is publicly reachable, or that a remote viewer hears the intended audio. Use it to inspect scene changes, then use YouTube’s Live Control Room preview and a separate playback check as part of the full test.
Schedule and manage the event in YouTube Studio
Use YouTube Studio’s Live Control Room to schedule and manage the event. Scheduling can create an upcoming event page that you can share, and viewers may be able to set reminders. YouTube’s live streaming setup guidance covers scheduling and the event workflow. The scheduled event is not a rotation plan: it does not compose the scenes or decide when OBS changes from demo to tutorial.
Check current channel eligibility in Studio before making a public plan. YouTube’s requirements can change, and account-specific status matters. The current YouTube live streaming eligibility information is the place to check rather than relying on an old checklist or assuming a channel can stream because it has uploaded videos.
In the encoder, connect to the event using the available YouTube integration or the stream URL and key. Treat the key like a password: it allows an encoder to send a feed to the channel, so do not place it in a public scene, screenshot, or shared cue sheet. YouTube’s encoder setup instructions explain the connection flow. For an event on a channel that needs a reusable key, review the steps for creating a reusable YouTube stream key and confirm the current Studio controls before relying on it.
The usual event flow is to start the encoder, wait for the incoming preview in Live Control Room, check picture and sound, and then start the event from Studio when ready. The exact controls can depend on the event setup. Do not assume that the Studio preview is where scenes are switched: it is a way to verify what the encoder is sending before and during the event.
During the broadcast, one person should keep an eye on the incoming feed and event status while the operator handles scene cues, if staffing allows. If you are working alone, keep the run of show short enough that you can monitor the preview and audio without losing track of the presentation. Afterward, end the event in Live Control Room and stop the encoder cleanly. YouTube’s archive behaviour and limits can change, so check its current help before relying on a recording being retained.
Test the complete encoder feed
Rehearse the entire path, not just the scene buttons. YouTube recommends setting up the encoder at least two hours before an event and starting it at least 15 minutes before the scheduled start; these are preparation timings in its live streaming guidance, not a guarantee that everything will work. Allow enough time to fix a capture or audio problem before viewers are waiting.
Run through the sequence from the opening scene to each product demo and tutorial. Confirm that each scene shows the intended sources, transitions appear as expected, and hotkeys or manual controls select the right destination. Speak while switching so you can hear whether narration continues and whether the microphone level remains consistent. Check the encoder’s output and YouTube’s incoming preview, since a scene looking correct inside OBS alone does not establish that the platform is receiving the expected programme.
Check the event from a viewer’s perspective as well. YouTube recommends checking stream quality and verifying access from channel and watch pages, including on mobile devices. Confirm that the scheduled page leads viewers to the right event and that the important parts of a software demonstration remain readable on a phone-sized display. If the stream is private or unlisted for a rehearsal, use the appropriate access settings and do not share it more widely than intended.
Prepare a fallback for a scene that fails. The operator can remain on a working scene while the presenter explains the delay, or return to a simple introduction layout while the source is corrected. This is a production contingency, not an assurance that the broadcast will be uninterrupted. Scene switching and monitoring can help you respond, but the connection, encoder, source devices, and platform all remain part of the live path.
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 YouTube Studio rotate between my demo and tutorial scenes?
No. YouTube Studio schedules and manages the event, while OBS or another encoder composes and sends the programme feed. Use the encoder’s scene controls for the changes viewers see.
Can I switch scenes without a second operator?
Yes. You can select scenes manually in OBS or use configured hotkeys, and Studio Mode lets you inspect a change before taking it live. Rehearse the workflow so operating the controls does not distract you from presenting or monitoring the event.
Should I use a cut or a fade?
A cut makes the change immediate, which can suit a move to a demonstration screen. A fade is gradual and may suit a softer hand-off, but test whether the two layouts blend clearly. Choose the one that makes the content easiest to follow.
Does a successful OBS scene change mean the stream cannot drop?
No. A scene change controls the encoder’s composition; it does not guarantee that the encoder remains connected or that YouTube receives an uninterrupted feed. Check the Live Control Room preview and have a practical response ready if a source or connection fails.