A scene can be used as a source in other scenes. Keep common visual elements in one clearly named component scene, then verify its order and scale in every parent layout.
Build one reusable overlay scene, place it inside two output scenes, and check which changes should propagate across the show.
In this guide
Before you start
- A duplicate scene collection for the layout experiment.
- Two output scenes that need the same visual elements.
Choose one repeated visual responsibility
Start with something narrow: the same corner logo and social label on a gameplay scene and a talking scene. Leave game capture, camera framing and scene-specific text in their existing layouts. A reusable component is easier to understand when its name describes exactly what it owns.
OBS supports scenes used as sources, including in its documented custom multiview workflow. That lets a parent scene display a composition assembled elsewhere. For a shared overlay, the useful consequence is a single editing location for elements that should change together.
Write down which changes are shared
Call the component something like SHARED — corner identity and the output scenes LIVE — game and LIVE — talk. The names make the relationship visible in the scene list. Avoid putting an output scene inside its own component or creating a chain whose purpose you can no longer explain.
Before moving anything, note the current logo size, padding and source order in each output layout. Decide whether those layouts truly need the same arrangement. If the talking scene needs a large lower third while the game needs a tiny corner mark, two deliberate components may be clearer than many exceptions.
Create and place the shared composition
Assemble the component scene
Create the shared scene and add the repeated visual sources. Arrange them on the intended canvas with empty space where the parent scene must remain visible.
Look for: The component contains only the elements that should be maintained together.
Place the component in both outputs
In each output scene, add a Scene source and choose the shared scene. Position it above the content it should overlay and check its transform.
Look for: Both output scenes display the same component without separate logo and label copies.
Make one reversible shared edit
Change a harmless label in the component, then inspect both parent scenes. Undo the label change after confirming the relationship.
Look for: The update appears in each intended parent and nowhere unexpected.
Inspect the composition from each parent’s point of view
A component that looks correct alone can cover the wrong thing when inserted into a parent. In the gameplay scene, check the score, minimap and subtitles around it. In the talking scene, check faces and name labels. Empty space in the component does not replace those contextual checks.
Also inspect any audio or media accidentally included in the component. A visual-only identity layer should not silently become another route for the microphone or a looping soundtrack. Keep its contents visible and purposeful so another person can understand why the component exists.
Make the maintenance benefit measurable
Rehearse the change you expect to make later, such as updating a social handle or replacing a logo file. Time is less important than completeness: both output scenes should show the update, with no old duplicate left on top. Check the actual saved recording at the delivery size.
If every parent needs a different correction after each edit, the shared boundary is probably too broad. Move scene-specific elements back into their parent or create a second well-named component. Keep the smallest shared arrangement that removes repetitive work while leaving each layout easy to inspect.
Still stuck?
The nested scene hides the game.
Inspect its contents and layer order; an opaque full-canvas source inside the component can cover the parent’s picture.
Sources & references
Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.
- OBS — Power of Projectors ↗Checked 2026-11-04
- OBS — Sources Guide ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗