If you stream more than one game, a single overloaded scene list turns into a maze of duplicated sources and mismatched layouts. Scene collections in OBS Studio solve this by giving each game (or each type of show) its own self-contained set of scenes, sources, and audio routing. Get the structure right once and switching from a cozy chat stream to a competitive shooter becomes a two-click job instead of a five-minute panic.
Scenes vs. scene collections vs. profiles
These three OBS concepts get confused constantly, so it helps to separate them. A scene is one layout (webcam + game capture + overlay). A scene collection is a whole bundle of scenes saved together. A profile stores encoder and output settings such as bitrate and resolution. You can pair any profile with any scene collection, which is why they are kept separate.
When to make a new collection
Do not create a collection for every game out of habit. A new collection earns its place when the layout genuinely changes: a vertical mobile game needs a portrait canvas, a two-player couch co-op needs a second camera, a “Just Chatting” show wants a big facecam. If two games share the same layout, keep them in one collection and just swap the capture source.
A folder-style naming system
OBS shows collections in a flat dropdown, so naming is your only organization tool. Use a prefix system so related collections sort together alphabetically.
| Collection name | Canvas | Typical scenes inside |
|---|---|---|
| FPS – Competitive | 1920×1080 | Starting, Game, Clutch Cam, BRB, Ending |
| CHAT – Talking | 1920×1080 | Intro, Big Cam, Screen Share, Outro |
| MOBILE – Portrait | 1080×1920 | Phone Capture, Reaction, BRB |
| COOP – Two Cam | 1920×1080 | Both Cams, Player 1, Player 2, Results |
Scenes every collection should contain
Consistency across collections lowers your mental load. Aim for the same five-scene skeleton in each: Starting Soon, Live/Game, Break (BRB), a full-screen Camera scene for storytelling, and Ending. When every collection follows the same order, your muscle memory (and your Stream Deck buttons) works everywhere.
Nested scenes save hours
Instead of pasting your webcam, alert box, and chat overlay into six scenes, build them once inside a single “Overlay” scene and then drop that scene as a source into the others. Change the overlay once and it updates everywhere. This one trick can cut the time you spend rebuilding layouts by 70 to 80 percent.
Backing up and moving collections
Scene collections live as JSON files. In OBS go to Scene Collection > Export to save one, and Import to load it on another PC. Export after any big change; the files are tiny, usually 20 to 200 KB, so keeping a dated backup folder costs nothing and can save an entire setup from a corrupted config.
Frequently asked questions
Will switching scene collections drop my stream?
No. Switching collections does not stop the stream or recording, but any active source is briefly reloaded, so avoid swapping collections mid-broadcast. Switch scenes within a collection for live changes, and reserve collection swaps for between segments or before you go live.
How many scene collections is too many?
There is no hard cap, but most streamers stay organized with four to eight. Past a dozen the dropdown becomes hard to scan, and it usually means you are duplicating layouts that could share one collection with swappable sources instead.
Common organization mistakes to avoid
The biggest trap is duplicating your entire layout for a game that only needed a different capture source. Every duplicate becomes another place you have to fix a typo, re-align a webcam, or update an overlay. If you find yourself editing the same element in five collections, that element belongs in a nested source instead. A second frequent mistake is forgetting that audio devices are stored per collection: create a fresh collection and your carefully tuned mic filters may not carry over, so copy your audio setup deliberately rather than assuming it follows you. Finally, name collections for the layout, not the game of the week. “FPS – Competitive” survives when you drop one shooter and pick up another, whereas a collection named after a single title becomes dead weight the moment you move on. Treat the collection list like a tidy toolbox: every item has a clear job, nothing is duplicated without reason, and anything shared lives in one editable place.
Bottom line
Treat scene collections like folders: one per distinct layout, a shared five-scene skeleton inside each, a nested overlay source you edit once, and a clear naming prefix so they sort logically. Export your collections regularly, and switching between a portrait mobile game and a full-screen competitive shooter becomes effortless instead of stressful.
