Add Existing reuses the original source. Its placements can differ between scenes, while source properties remain shared. Device sources should not be treated as unlimited independent camera connections.
Reuse a camera or capture source across scenes, distinguish placement from shared properties, and test independent visual treatments safely.
In this guide
Before you start
- Two scenes in a duplicate collection.
- One working source you can identify by a descriptive name.
Identify whether you want another placement or another object
Suppose one camera needs to be small during gameplay and large during a conversation. That is usually a placement problem. Creating another connection to the same physical camera adds complexity without explaining which settings should remain common. Name the original camera clearly before adding it elsewhere.
An OBS developer’s documented Add Existing workflow creates a reference to the original capture source. The API also distinguishes sources that can be duplicated from sources that must remain references. A duplicate command should therefore not be read as a guarantee of a fully independent device.
List the change before choosing a copy operation
Write down the intended difference: size, crop, file path, text content, camera setting or filter treatment. A different position in a scene is not the same operation as changing what a source contains. This small distinction prevents a correction in one layout from unexpectedly changing another.
Use a harmless source such as a test label to learn independent duplication. Keep device experiments separate. If two entries have nearly identical names, rename them before troubleshooting; an extra number at the end rarely tells you whether an entry is a shared source or a separately configured object.
Prove the sharing behavior with a reversible edit
Add the existing camera
In the second scene, add the same source type and choose Add Existing, selecting the original named camera.
Look for: The second scene uses the established camera source rather than another unexplained device entry.
Change only its placement
Resize or reposition that scene’s camera placement. Switch back to the first scene and inspect its framing.
Look for: You can confirm which composition changed before touching shared source properties.
Inspect a source-level change
In the duplicate collection, make a reversible source-property or filter change and inspect both scenes. Restore the starting value afterward.
Look for: You see exactly where a shared-source edit propagates instead of discovering it during a broadcast.
Give an independent treatment its own clear boundary
If one scene needs a filter treatment that another must not receive, avoid repeatedly editing the original camera filter between scenes. The OBS developer example wraps the camera in a scene and applies a filter to that scene source. The wrapper becomes the place where that treatment belongs.
Name wrappers by purpose, such as CAMERA — monochrome segment, and keep the unfiltered camera identifiable. Rehearse both views after each filter change. This is easier to maintain than several capture devices all pointing at the same webcam and relying on activation timing to decide which one works.
Trace unexpected changes back to the shared object
When a label, filter or device setting changes in several scenes, inspect the source name and the path by which each scene reaches it. Ask whether the edit was made to a scene placement, a shared source, or a wrapper. That explanation is more useful than repeatedly undoing the visible symptom.
Finish by recording a transition through all affected scenes. Confirm the camera stays available and each composition retains the intended framing and treatment. Keep the result as a small reference layout. It can teach future scene builders the project’s sharing convention without another round of trial and error.
Still stuck?
Changing a filter affects several scenes.
Find the shared source behind those scenes and place an intentionally separate treatment on an appropriate wrapper rather than repeatedly editing the original.
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 developer R1CH — Reusing a capture source ↗Checked 2026-11-04
- OBS — Source API Reference ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗