If you want the same webcam to look different in different OBS scenes, add it once to a reusable base scene, then add that scene to each destination scene and apply the treatment to each nested instance. This keeps one camera capture while allowing, for example, a neutral look in one scene and a keyed or cropped look in another.
If you are sending video to another application, configure OBS Virtual Camera separately from the scene setup. Choose Program, Preview, Scene or Source according to what that application should receive, and check that the application supports webcam video input before relying on it.
Set up a reusable webcam base scene
Start by making a scene whose job is to hold the shared camera feed. Give it a name you will recognise, such as “Camera base”. Add your webcam there as a Video Capture Source, select the device OBS should use, and set the framing you want to keep across looks. OBS treats webcams as video capture sources; see its guide to sources for the source model and device types.
Keep this base scene simple. It can contain the camera and any adjustments that genuinely belong in every version, such as a common framing or colour balance. Do not put a filter here if one destination needs that filter and another must not: a filter attached directly to a shared source affects that source wherever it is used. For a clean base, begin with only the adjustments you want to be universal.
Think of the base scene as the camera feed before individual scene styling. Suppose you host a devotional stream and use one scene with a close camera view and another with a wider layout and a decorative frame. The camera itself can be captured once. The framing, mask or colour treatment that distinguishes the final looks belongs on the relevant nested scene instance, not on the shared camera source.
You can preview the base scene on its own before building the rest. Check that the camera is the intended device, that it is not obstructed, and that the framing leaves room for the overlays you plan to use. A filter cannot fix a wrong device selection or an unsuitable shot. This small check also makes later comparisons easier because you know what the unmodified feed looks like.
OBS lets you open Filters by right-clicking the relevant source or scene, and its overview explains that filters can be added to both. The distinction matters: a source filter changes the camera source, while a scene filter can supply a treatment to a reusable scene as it appears in a destination. The OBS Studio overview describes the available filter approach and examples, including Color Correction, Chroma Key, Crop/Pad and Image Mask/Blend.
Add the existing scene to destination scenes
Create each destination scene for its actual purpose: perhaps “Talking”, “Questions” and “Break”. In each one, add the existing “Camera base” scene as a Scene source. Choose the existing scene from OBS’s source list rather than creating another Video Capture Source for the same physical camera. The destination scene can then arrange the camera feed alongside titles, graphics or other content.
This is a nested scene: a scene is being used as a source inside another scene. The base scene holds the shared camera capture; the destination scene controls how that content fits into a particular layout. OBS’s source-and-scene model makes that composition possible, and the OBS forum discussion of per-scene camera filters describes this nested-scene method for separate treatments.
Repeat the addition of the existing base scene in each destination that needs the camera. Keep names descriptive. “Camera – neutral” and “Camera – keyed” are more useful than “Scene 2” and “Scene 3” when you return to the collection later. If two scenes have similar names, include the intended look or use, so you can recognise which instance to select before changing its filters.
After adding the scene source, position and size it in that destination layout. This is where you can make one camera placement smaller for a corner view, while another destination gives it more room. If a transform is not the filter you mean to vary, do not assume that changing the nested scene’s effects also changes all layout properties. Check the destination preview and adjust the item in context.
The nested scene should be visible in the destination’s source list. If the camera does not appear, check that the base scene itself is not empty or hidden, and make sure the Scene source is enabled. Work from the destination preview rather than adding devices repeatedly; a missing camera image is a troubleshooting question about the existing source or its visibility, not a reason to add the webcam again by default.
Apply a different filter to each nested instance
Select the camera base scene source inside the destination scene and open its Filters. Add the effect that belongs to that version of the image. For a soft colour change, try Color Correction; for a coloured background you intend to remove, try Chroma Key; for a shaped edge or frame, consider Image Mask/Blend. Crop/Pad can remove unwanted areas of the frame. Which filter is appropriate depends on the result you want and the material in the shot.
Now repeat that process in the other destination scene, selecting its own nested instance before changing filters. Give that instance a different treatment. One can remain neutral, while the other has a crop or mask. Because the filter is attached to the scene instance rather than the shared camera source, the two destination scenes can show different looks without making a second capture of the same camera.
Test by switching between the destination scenes and comparing them. If changing one instance unexpectedly changes both, check that you selected the nested scene item rather than the webcam source inside the base scene. Confirm the filter appears on the selected scene instance’s Filters panel. The key is not merely that the same camera appears in both scenes, but that each treatment is attached at the level where it should vary.
Keep a practical record of the choices if your scene collection is complex. A short note such as “Talking: neutral; Questions: crop and mask” can prevent accidental edits during a live session. For a visual change that should apply everywhere, edit the base source; for a change that belongs to one layout, edit its nested scene instance. That simple rule is often enough to locate the right control later.
Filters are not interchangeable in their effects. A chroma key depends on the background and lighting; a mask depends on the image asset and how it aligns with the source; a crop removes parts of the image rather than smoothing them. Preview each treatment at the size it will actually occupy, and check edges, hair and movement where relevant. A result that looks acceptable in a large preview may reveal rough edges when reduced in a corner of the layout.
Avoid creating duplicate webcam sources
Adding the physical webcam as a newly created capture source in every scene is usually the wrong first move. It can leave you with multiple device entries to identify and maintain, and source-level filter changes will not provide the per-scene behaviour you intended. Elgato’s scene collection guidance recommends one source per webcam and reusing the existing source where needed. That is consistent with the base-scene method: capture once, compose in multiple scenes.
There is a difference between reusing a source and duplicating it. When you add the existing scene to a destination, you are reusing the established camera feed in another composition. When you add a fresh Video Capture Source and point it at the same camera, you are creating another source entry for that device. For different scene-level effects, the first arrangement is the clearer native workflow.
| Approach | Where the different look lives | What to keep in mind |
|---|---|---|
| Reusable base scene with nested instances | On each nested scene instance | Uses OBS’s scene and filter model; suitable when treatments vary by destination scene |
| Separate newly created webcam sources | On each source | Avoid as the default: it creates separate source entries for the same device and can complicate management |
| Source-clone plugin | On cloned source entries | Consider only when you specifically need separate source-level filters; check current plugin and OBS compatibility |
A plugin can be relevant for a narrower requirement: separate filters must belong to separate cloned webcam sources rather than to scene instances. Elgato’s documentation discusses a source-cloning plugin for that case. A plugin is an additional dependency, so check its current listing, maintenance and compatibility with your OBS release before making it part of a show you rely on. Plugin availability and interface details can change.
For most users seeking different looks in different scenes, start with the nested scene method because it avoids that dependency and directly expresses the intended composition. If your workflow genuinely depends on source-level filters being separate, test a clone-based setup in a copy of the scene collection before using it on air. Do not change a working scene collection immediately before a scheduled stream without a preview test.
If your broader OBS workflow includes always-on visuals, the waveform visualizer setup for an OBS podcast stream is another example of adding presentation elements to a scene. For a channel built from longer recordings, the guide to verifying a large video upload before an OBS YouTube stream addresses a different part of preparation: checking media before it becomes part of the programme.
Choose an OBS Virtual Camera output mode
Once the scene looks are set up, decide what an external app should receive. Start OBS Virtual Camera and select its output mode for the job. Virtual Camera is not the same as merely adding the webcam source to a scene: it sends an OBS image to a supported destination application, and the selected mode determines which OBS image is presented. The OBS Virtual Camera guide documents the available modes.
| Mode | Output to expect | When it fits |
|---|---|---|
| Program | OBS’s regular programme output | You want the final live composition, including the active scene and its visible layout |
| Preview | The Studio Mode preview | You intentionally want the preview scene rather than the current programme |
| Scene | The selected scene | You want a particular scene as the camera output, independent of the regular programme selection |
| Source | The selected source | You want one source directly, rather than a complete scene composition |
Program is generally the straightforward choice when the other app should see what your audience sees as the current OBS output. Preview only makes sense if you use Studio Mode and specifically intend the destination to see the preview side. Do not select it casually before a call: the scene you are preparing may differ from what you meant to send.
Scene and Source are more fixed choices. With Scene, select the scene you want Virtual Camera to output; with Source, select the individual source. They are useful when the destination should keep receiving a particular scene or source rather than follow the standard programme output. They are not identical modes, so check the selected item and verify the result in the destination app.
The correct mode depends on the task. For a video call where you want overlays and scene changes, Program may match your intention. For a call where only a clean camera image should be present, a selected Source may be more suitable if that is what your OBS setup supports. If you need a particular composition that is not the live programme, a selected Scene can be more direct. Test instead of assuming the names mean the same thing.
Select the virtual camera in the destination app
OBS setup and destination-app selection are separate steps. First start Virtual Camera in OBS with the intended output mode. Then, in the other application, open its camera or video settings and choose OBS Virtual Camera as the camera input if the app lists and supports it. Apps differ: do not assume that a browser, meeting app or chat client accepts a virtual webcam just because OBS is running.
Check the destination preview before joining a call or starting a recording. Confirm that the image is moving, the intended scene is visible, and any overlays or filters are present or absent as expected. If the destination shows a black frame or the wrong scene, check the OBS Virtual Camera state and output selection, then confirm the app has selected the OBS device rather than the physical webcam. Revisit the app’s own current help if its camera controls are unclear.
A useful test is to switch between two destination scenes in OBS while watching the app’s preview. If Program is selected, the app should follow the regular programme output; if a fixed Scene or Source mode is chosen, it should stay tied to that selected item. This makes the distinction concrete before an audience or caller is waiting. Repeat the check after changing modes or reopening either application.
The order matters when you are troubleshooting. If OBS’s own preview shows the desired treatment but the destination app does not, inspect which Virtual Camera mode is active and which camera the app selected. If the treatment is already wrong in the destination scene preview, return to the nested instance’s Filters panel. Changing the destination app’s camera setting cannot correct an effect attached to the wrong OBS item.
For a scheduled programme, consider whether OBS needs to remain open and actively outputting for the destination you have in mind. This workflow is for sending OBS video to an app that accepts webcam input; it is not a way to send a camera image into every service or to make OBS’s Virtual Camera output an always-on YouTube broadcast by itself. If your channel depends on a computer staying online, see the practical guide to keeping an FFmpeg YouTube stream running with systemd for a distinct, server-based workflow.
Check the setup before relying on it
Do a short rehearsal with the exact scenes and destination app you plan to use. Switch scenes, watch the destination preview, and check the filter result at the size viewers or callers will see. If you use Studio Mode, test the Preview mode deliberately rather than discovering its behaviour during a live hand-off. Keep the first version of the scene collection intact until the revised setup has worked as intended.
When a filter is missing, identify the selected item before adding anything. The Filters window can belong to the physical webcam source, a nested scene instance or another source entirely. Look at the item name in the destination scene’s source list. If you want one look to remain unique to that destination, apply it to its nested scene instance. If you want an adjustment shared in every use, apply it to the base source only after confirming that shared behaviour is intended.
For a camera that appears unavailable, first check the base scene’s capture source and visibility, then check whether another application or device state is preventing the camera from appearing in OBS. Avoid “solving” a camera problem by creating a second source pointing at the same device unless you have a specific, tested reason. The source-reuse approach keeps the project easier to understand when you return to it.
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 I use the same webcam with different filters in two OBS scenes?
Yes. Add the webcam once in a base scene, place that scene in both destination scenes, and apply filters to each nested scene instance. Keep filters on the shared webcam source only when you want their effect to appear everywhere that source is used.
Why does changing a filter in one scene change the other scene too?
You may have opened Filters on the shared webcam source rather than on the nested scene instance. Select the scene source inside the destination scene and apply the treatment there; then confirm each destination has its own instance selected.
Which OBS Virtual Camera mode should I use for a video call?
Use the mode that matches the image the supported destination app should receive. Program follows the regular OBS output, Preview exposes Studio Mode’s preview, and Scene or Source sends a selected item; test the app preview before joining.
Do all destination apps accept OBS Virtual Camera?
No. An app must support webcam video input and recognise the OBS Virtual Camera device. Check the app’s current camera settings or help, then verify the output in its preview rather than assuming support.