OBS Studio can import a scene collection created in Streamlabs Desktop using its built-in importer. Enable the known-location search, import the detected collection, then select it from the Scene Collection menu to make it active.
The import gives you a starting point for your scene layouts and sources, not a guaranteed copy of every part of your Streamlabs setup. Plan to check media and device sources, and configure output, audio and hotkeys in OBS where needed.
What a scene collection import does
A scene collection is a saved group of scenes and their sources. Scenes define what appears on screen and how it is arranged: for example, a camera, a background image, text and an alert source can be combined into a starting scene, while a second scene might show a holding screen. OBS’s scene collection documentation describes collections as containing scenes and sources, including global audio sources configured in Settings > Audio.
OBS Studio has a native import route for Streamlabs Desktop collections. You do not need to buy an accessory or install a separate importer to use that route. The key action is Scene Collection > Import in OBS. If the collection does not appear at first, enable the known-location search in Settings > Importers and try again.
Importing and activating are separate steps. Import makes the collection available in OBS; selecting it from the Scene Collection menu switches OBS to it. Until you select it, OBS may still be showing the collection that was active before the import.
Treat the result as a transfer of scene structure that needs inspection. Some source references or behaviour may depend on files, devices, settings or features that are not present in OBS in the same form. Streamlabs notes that output configuration, hotkeys and audio settings may need to be set up again. Do not assume that seeing the scenes in the menu means the full stream is ready.
Find the Streamlabs Desktop collection
Start by confirming that the collection you want belongs to Streamlabs Desktop, rather than assuming every setting from the Streamlabs application is part of the collection. The collection is the part you are bringing across: the scenes and their sources. Output settings and other application preferences are a separate matter, covered below.
If you have several collections, make a note of the one you intend to move. Give yourself a way to distinguish it from other collection names when OBS lists detected items. A name such as “Sunday service” is easier to recognise than a generic name such as “Collection 2”, particularly if OBS already contains collections of its own.
You do not need to move files manually as a first step. OBS’s importer can search known locations for Streamlabs Desktop scene collections. The official workflow relies on that detection, so the first thing to check when the item is missing is the importer setting—not a third-party transfer tool.
If you are preparing a channel for a long-running broadcast, keep this work separate from your final live configuration. A scene import does not decide whether your YouTube stream settings, scheduled broadcast or content are appropriate. For a devotional channel, for example, the 24/7 devotional stream setup guide covers broader planning; this page is about moving the scene collection into OBS.
Enable known-location search in OBS Importers
Open OBS Studio and choose Settings. In the Settings window, open Importers and turn on Search known locations for scene collections when importing. This gives OBS permission to look in the places it recognises for Streamlabs Desktop collections when you use the import command.
The setting matters because the import dialogue needs to find the collection before you can choose it. If the option is off, OBS may not automatically list the Streamlabs collection you expect. Turn it on before proceeding, then close or apply Settings as appropriate for the version of OBS you are using.
If your menus differ slightly, take care to identify the Importers section and the setting by its wording rather than guessing at another option. Application interfaces can change, so consult the current Streamlabs import instructions alongside OBS if a label or menu placement appears different. That guide describes the migration using OBS’s scene collection importer.
The search setting does not promise that every collection will be found in every installation. The documented process is detection from known locations; it does not establish every cause of a missing result. If you have enabled the setting and still do not see the collection, reopen the import dialogue and confirm you are looking for the intended collection. Avoid concluding that a separate importer is required.
Import the collection and activate it
With known-location search enabled, use the top menu in OBS Studio and choose Scene Collection > Import. OBS should show collections it detects from supported applications, including Streamlabs Desktop. Select the collection you want and complete the import prompt.
After the import completes, open Scene Collection again and choose the newly imported collection by name. That activation step is easy to overlook: importing adds the collection to OBS, but selecting it tells OBS to use it. Check the scene list and preview so you know you are viewing the intended layout rather than the collection that was active previously.
Do not delete or overwrite your existing OBS collection as part of this process. Keeping the original available gives you a fallback while you compare the imported scene list and test sources. If OBS offers a choice involving names that are similar, pause and read it before confirming; the aim is to add and inspect the Streamlabs collection, not to discard unrelated work.
If the import dialogue contains no Streamlabs collection, return to Settings > Importers and verify that the known-location search is enabled. Then retry Scene Collection > Import. If it remains absent, the official steps do not identify a universal fix for every location or installation issue, so check the current application guidance rather than inventing a file path or changing unrelated settings.
Review scenes, sources and settings
Once the collection is active, move through each scene in the list and inspect its preview. Look for missing-source indicators, blank areas, unexpected crops or media that no longer plays. A scene can exist in the collection even when an image, video, capture device or other dependency is unavailable to the current OBS installation.
Check each source deliberately. Confirm that media files point to locations you can access, and that any camera, microphone or capture device you expect is available and selected. If a source has properties, open them and confirm that the intended device or file is set. The transfer is not evidence that all source dependencies exist on this computer or that the source will behave exactly as it did in Streamlabs Desktop.
Review audio both in the scenes and in Settings > Audio. Scene collections can include global audio sources, but Streamlabs identifies audio settings as something that may require configuration again. Listen to a test recording or monitor the output where appropriate; a source appearing in a mixer is not enough to establish that its level, routing or intended behaviour is correct.
Also review transitions, filters, text and overlays. A source may be present but not render as expected, or a feature used in the original application may need another setup in OBS. Recreate only what you can verify is needed. If the purpose of the move is simply to preserve a camera-and-title layout, do not add optional extensions while still diagnosing basic scene visibility.
Keep scene collections distinct from Profiles. A collection is for scenes and sources; a Profile stores stream, video and output settings. The OBS Profiles documentation explains the separate role of Profiles and their import/export options. Use a collection for the layout and sources, and review or import a Profile separately if you have a suitable configuration file for output-related settings. A Profile does not contain your scene layouts, and a Scene Collection does not store output settings.
| OBS item | What it is for | What to check after migration |
|---|---|---|
| Scene Collection | Scenes and their sources, including configured global audio sources | Scene order, source availability, media paths and visual result |
| Profile | Stream, video and output settings | Service and output configuration, resolution and encoder choices |
| Hotkeys and application preferences | Controls and behaviour configured in the application | Whether your expected shortcuts and preferences are set in OBS |
This distinction helps explain why the imported picture can look right while the broadcast configuration is still incomplete. Check OBS’s service and output settings rather than expecting the scene import to provide them. Likewise, configure hotkeys in OBS if you rely on keyboard actions to switch scenes or mute sources.
A Streamlabs plugin for OBS is a separate feature path for people who want Streamlabs widgets or overlays within OBS. It is not the mechanism required to import a Streamlabs Desktop scene collection. If you are considering it for other reasons, check Streamlabs’ current plugin guide for the current platform and version details before installing it; those details can change.
Test the imported collection before going live
Test the collection locally before using it in a live broadcast. Switch through every scene, wait for animated or timed sources to behave, and check that transitions do what you expect. If a scene is used only occasionally—for example, a “starting soon” card or an intermission screen—test that scene too rather than checking only the main programme view.
Make a short recording or use a private, controlled test where suitable to check picture and sound together. Confirm that the intended microphone or audio source is audible, that desktop or media audio is not unexpectedly overpowering it, and that the image remains composed when sources are active. A preview can reveal a missing file; a recording can reveal an audio problem that is not obvious from the scene list.
For a channel that loops music or video, check that the sources and audio work throughout the relevant content rather than judging only the opening frame. You may also want to review audio normalisation across videos in an FFmpeg playlist if the stream uses a playlist, since a scene import does not level differences between media files.
Finally, confirm the output-related setup in OBS before connecting to a public broadcast. Compare the selected service and stream configuration with your current YouTube requirements, and consult YouTube’s official live streaming help if you need to verify account or live-streaming steps. Do not treat a successful scene preview as proof that YouTube will accept or display a live broadcast as intended.
For a 24/7 channel, consider what happens if the computer or application stops after you have finished testing. OBS running locally depends on that computer staying on and the broadcast being maintained. If keeping a machine on overnight is the specific problem, the power-outage restart guide explains a different operational concern; it does not change how the scene collection is imported.
When your files and channel are ready, compare the operating options and choose the workflow that fits the way you plan to maintain the stream.
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
How do I import scenes from Streamlabs Desktop to OBS Studio?
In OBS, enable Search known locations for scene collections when importing under Settings > Importers. Choose Scene Collection > Import, select the detected Streamlabs Desktop collection, then select that collection in the Scene Collection menu to activate it.
Why did OBS not find my Streamlabs collection?
First verify the known-location search option is enabled, then reopen Scene Collection > Import. The documented workflow uses automatic detection, but it does not specify every reason detection may fail. If the collection remains missing, check the current official guidance for your application version rather than assuming another importer is necessary.
Why did some Streamlabs settings not transfer?
The collection focuses on scenes and sources, while other settings are handled separately. Streamlabs says output configuration, hotkeys and audio settings may need to be set up again in OBS. Profiles are for stream, video and output settings; they do not contain scenes.
Do I need the Streamlabs Plugin for OBS to import a collection?
No. OBS’s native Scene Collection importer is the route for importing a Streamlabs Desktop collection. The plugin is a separate option for using Streamlabs features in OBS, so consider it only if you want those features and have checked its current requirements.