OBS and Thunderstream backup: transfer scenes without losing settings

A dictionary without difficult abbreviations

Step by step · 1–4

1. Action

   Schedule a backup before a major change or move, preferably outside of the active LIVE.

   ✓ After this step you will see

   You don't change key settings while transmitting.

2. Action

   Create a folder with a date, e.g. Studio-2026-10-27.

   ✓ After this step you will see

   The copies have clear names.

3. Action

   In OBS, note the name of the active profile and scene collection.

   ✓ After this step you will see

   You know what you are exporting.

4. Action

   In the Profile menu, use active profile export.

   ✓ After this step you will see

   You retain the output and program settings covered by the profile.

Enlarge the screenshot ↗

Step by step · 5–8

5. Action

   In the Scene Collection menu, export the appropriate collection.

   ✓ After this step you will see

   You preserve scenes, sources and their layout.

6. Action

   Copy your used local images, videos, sounds and text files to an organized folder.

   ✓ After this step you will see

   The copy does not depend solely on old disk paths.

7. Action

   Save a list of additional plugins and their versions.

   ✓ After this step you will see

   The new computer will know what's missing.

8. Action

   Protect your copy from public access.

   ✓ After this step you will see

   The export may contain private addresses or other settings.

Enlarge the screenshot ↗

Step by step · 9–12

9. Action

   In Thunderstream, save your own set of configurations or use the available export.

   ✓ After this step you will see

   Panel settings have a separate copy.

10. Action

    Write down the names of the materials you need and check whether their addresses will be available after the move.

    ✓ After this step you will see

    A set is not confused with an archive of all files.

11. Action

    On the second computer, install a compatible version of OBS and the necessary plug-ins from official sources.

    ✓ After this step you will see

    The program can read the sources used.

12. Action

    Import the profile and collection with a distinguishable name.

    ✓ After this step you will see

    You don't immediately overwrite the only working version.

Enlarge the screenshot ↗

Step by step · 13–16

13. Action

    Fix paths to missing files and select the correct microphone and camera.

    ✓ After this step you will see

    Sources use new computer devices.

14. Action

    Check browser sources and resolutions without showing private URLs.

    ✓ After this step you will see

    The overlays work in the correct dimensions.

15. Action

    Record the picture, sound, cuts and scene changes.

    ✓ After this step you will see

    The copy is practically checked.

16. Action

    Keep the old version until you confirm the complete configuration.

    ✓ After this step you will see

    You can go back to the previous layout.

The profile and scene collection are different parts of the copy

The OBS profile stores a group of program and output settings, but does not replace the scene collection. The collection includes scenes, sources and their arrangement, but is not a complete package of all external files. So you do two exports and keep the media separately.

The file used by the source may be on the desktop, in downloads, or on another drive. If you change your computer, the path may no longer exist. First organize the materials in a permanent directory, then recreate the references. Do not remove the originals before checking the new configuration.

A set of settings is not a copy of your entire account

The Thunderstream kit helps you recreate supported tool settings. It should not be considered a transfer of passwords, platform authorizations or all transferred files. After import, check account connections and material availability. Only publish a set after you have audited its contents.

A copy on the same disk protects against misconfiguration, but not against failure of the entire disk. Keep a second, secure copy. After each important addition to the studio, make a new, dated version and keep at least the last working one.

An example you can reproduce

Just exporting your scene collection does not automatically transfer your entire catalog of videos, all your plug-ins and output settings. A full working copy is profile + collection + media + add-on list + separate service configuration. When moving from Windows to Linux, you must additionally check the sources and paths specific to the system.

What do you see on the screen and how to fix it

Fix one thing at a time and try the same thing again. If you change several options at the same time, it will be difficult to determine what solved the problem. Don't delete a working source or entire configuration just because one widget isn't responding.

If you still need help, write down the program name and version, platform, approximate time of trial, expected result, and what actually happened. Attach a dump without passwords, keys and full private links. This description is much more useful than just the "not working" message.

Last attempt before use on LIVE

1. Save the changes using the button assigned to the edited function. If there are separate forms, check each changed part separately.
2. Open the settings again and compare the most important values. Simply moving the slider does not always mean a permanent save.
3. Check the result outside the editor itself: on the target scene, in the recording, or in the reopened configuration.
4. If the function uses the platform, separately acknowledge the new handled event during the active LIVE. Don't expect the appearance test to confirm account authorization.
5. Save the working values ​​and make a copy before the next major change. Next time you start up, start with a quick check.

Frequently asked questions