To make an OBS channel recoverable, back up three separate things: the active Profile, the Scene Collection, and every local media file that a playlist source uses. They serve different purposes, so exporting settings alone is not a complete backup.
Before you resume an always-on schedule after a computer failure or move, restore those pieces and check that the files resolve, the playlist behaves as intended, and a short test stream works. A saved backup is useful only if you can identify and restore its parts.
What an OBS backup needs to preserve
Think of the setup as three layers. The Profile holds stream, video and output settings. The Scene Collection holds the scenes and sources that make up the programme. The media files are the actual videos or audio referenced by those sources. Keep a copy of each layer.
| Backup component | What it preserves | What it does not replace |
|---|---|---|
| Profile export | Stream, video and output settings | Scene layout and source media |
| Scene Collection | Scenes, sources and Global Audio Sources | Output settings and the referenced media files |
| Playlist media copy | The local video and audio content | The OBS source configuration or Profile |
OBS documents Profiles and Scene Collections as separate components. A Profile export is not a full setup export, and a Scene Collection does not stand in for output settings. The playlist source configuration is also separate from the files it points to. Keeping those distinctions clear avoids the common mistake of finding a valid JSON backup but no usable programme footage.
Start by listing the active Profile, the Scene Collection you actually use, and each playlist source in that collection. If you keep test scenes, alternate collections or old media on the same computer, do not assume they belong in the live backup. Record what the live channel needs, and note anything you intentionally exclude.
If you use OBS to replay events continuously, the distinction between playback and delivery method may also matter; the OBS and FFmpeg comparison for a nonstop replay stream can help you keep that broader choice separate from this backup task. This guide focuses on preserving an OBS setup rather than choosing an encoder.
Export the active Profile
In OBS, use the Profile menu’s Import/Export option to export the Profile settings as a JSON file. Menu wording can change between versions, so check the controls in your installed version rather than relying on a screenshot from another release. Give the export a clear name and put it with the rest of the dated backup, not in a folder that might be wiped during a reinstall.
First confirm which Profile is active. A channel may have one Profile for its normal live output and another used for recording, testing or a different resolution. Exporting the wrong one can preserve valid settings that are simply not the settings your live schedule needs. Include the Profile name in your backup notes, then compare the exported file name to that note.
OBS’s Profiles documentation explains what Profile settings preserve and notes that Profiles do not store scenes. Profiles contain stream, video and output settings; keep the export as one piece of recovery, not as proof that the whole broadcast is backed up. The profile may include account-related configuration, but after restoring, check the current account and connection state rather than assuming they work unchanged.
Treat the export as sensitive operational information. Store it somewhere you can reach after a computer failure, but do not post it publicly or attach it to a support request without checking its contents and the recipient. Keep the file in its original form; if you want a human-readable note, write one separately rather than editing the exported JSON.
A Profile export can be made again after a deliberate change to output resolution, encoder, audio or stream settings. Keep the latest working export clearly marked, and retain an earlier known-good copy if you need to compare after an accidental edit. Do not label a new file “final” unless you have noted which OBS Profile it came from and whether it was tested.
If a stream key changes or the account connection needs attention, that is a separate recovery check. The article on what happens when a YouTube stream key changes covers that failure mode; a Profile backup does not remove the need to verify the current YouTube connection.
Back up the Scene Collection separately
Select the Scene Collection used by the channel and use OBS’s Scene Collection controls to export it. The exact menu path can vary by OBS version, so consult the collection controls in the installed application. Keep this exported collection alongside the Profile export, but name it so nobody mistakes one for the other.
A Scene Collection captures scenes and sources, including Global Audio Sources. It does not preserve the output configuration from a Profile. The official OBS Scene Collections guide describes this separation. For recovery, write down the collection name and the role it serves, such as “overnight bhajan loop” or “local news standby”, rather than relying on a vague label such as “Collection 2”.
If the channel has multiple collections, export the live one and any alternative you would genuinely need to resume service. Do not export every old experiment without a reason: extra files make it easier to import the wrong collection during a hurried recovery. A short inventory note can say which collection is production, which is backup, and which is obsolete.
The collection records source configuration, not a guarantee that the source’s files are present at the same paths on another machine. It is possible to restore the collection and see missing-media warnings, or a source that points to a location that does not exist on the replacement computer. That is why the next step is to back up actual media and record locations.
Copy playlist media and note file paths
For each playlist source, identify every video or audio file it uses and copy those files into the backup. A playlist entry is not the same thing as a copy of the media: the source setup can survive while the content has been moved, deleted or left on a drive that failed. OBS’s Media Sources guide describes media-source behaviour, including VLC Video Source playlist options. If your setup uses that source, check whether VLC is installed on the machine where you intend to restore it.
Make an inventory with the displayed source name, file name, current path and, where useful, the intended order or loop behaviour. For example, a “Morning Aarti” source might reference a set of files under a local D:\ChannelMedia\Morning folder. The path is a note about the current machine, not a portable promise. On a replacement computer the drive letter, folder or operating system may differ.
If your playlist uses files in several folders, preserve the folder structure or make a clear map from old locations to new ones. Do not rename files casually after exporting the collection: a source that points to the previous filename may no longer find the renamed copy. If a rename is necessary, plan to relink the source and test it before returning to the live schedule.
Check that the copy is complete by comparing the inventory against the playlist entries, rather than looking only at the folder name. Include audio beds, interstitials and any still-image or media source the live scene depends on. Avoid relying on a shortcut to media on a separate disk; copy the underlying files into the backup destination.
OBS warns that media referenced within a Scene Collection is not made portable just because OBS is run in Portable Mode. Its Portable Mode documentation notes that files used in the collection, such as images and media, are not portable. If you move a portable setup, the collection’s JSON may need manual path edits or a common path that exists on each device. Portable Mode is not a substitute for a media copy.
Store and label the backup
Keep the Profile export, Scene Collection export, media copy and a brief inventory together in a clearly named folder. Include the channel or project name and a date in the folder label; in the inventory, note the OBS version and operating system used when you made the export if you know them. This is a practical label, not a claim that a particular file format or directory will work everywhere.
Use a destination that is separate from the computer whose failure you are planning for. An external USB drive is one optional physical place for a copy, and another separate location may help if that drive is lost; choose a method you can actually access and maintain. Keep any sensitive account or stream information private. Do not assume a file sync folder is a backup unless you have confirmed the exported files and media are present there.
A useful inventory can be plain text or a small table. Record the active Profile, live Scene Collection, media folder names, the sources that rely on VLC, and any path changes needed on a replacement machine. Include a note such as “test the stream key and account before broadcast” rather than placing secrets into an unprotected note.
Before considering the backup ready, open the destination and confirm that the exports are present and the copied media files can be seen. If removable storage is involved, eject it properly and store it away from the broadcast machine. A backup that remains plugged into the only computer is less useful if that computer or disk is damaged.
Restore on the same or replacement machine
On the recovery machine, install OBS and VLC if your sources require it, then import the Profile and Scene Collection as separate steps. Select the intended Profile and collection explicitly. The Profile controls output-related settings; the collection restores scenes and sources. Do not infer that one import has brought in the other.
Then copy the media files to the planned location. If you restored to a different drive or operating system, inspect each source’s file path in OBS and relink it where needed. A familiar folder name does not prove that the path is the same. Check for missing-file indicators and open sources individually if the programme depends on a particular playlist or audio bed.
Restoring a Profile does not guarantee that the account connection, stream key, paths or broadcast will work. Sign in or reconnect through the current OBS workflow as needed, confirm YouTube Studio is set up for the intended live stream, and verify the destination before you send a signal. For a separate preflight of the key, see how to test a YouTube RTMP stream key before a 24/7 broadcast.
Keep your old machine or the prior media copy unchanged until the replacement has passed its checks. That gives you a way to compare source names and paths if the restored collection behaves differently. If you have been using a local machine for a continuous broadcast, the guide to streaming a 24/7 playlist from Airtel broadband is relevant to the separate question of a home connection; it does not replace this restore checklist.
Verify sources and test a short stream
Before restarting the full schedule, confirm the active Profile and Scene Collection in OBS. Inspect the live scene, check that each playlist source points to existing files, and make sure the expected playback order, loop or shuffle behaviour is selected. Listen for audio and watch for black frames, frozen video or an unexpected transition. These checks catch problems that an export alone cannot reveal.
If a source uses VLC Video Source, verify VLC is available and the playlist opens. Check more than the first item: a list can begin correctly but fail later because one entry points to a missing file. If music or long-form ambience is part of the channel, let playback run long enough to observe a transition and confirm the audio remains present. The right duration depends on the playlist and what needs checking; there is no universal short test that proves every file will work indefinitely.
OBS’s Quick Start Guide recommends testing settings for a few minutes before a first stream or recording. Apply the same idea after a restore: make a controlled test before returning to a long-running output. Confirm the preview, audio meters and output settings, then check the receiving side in YouTube Studio. A local preview is not proof that the live destination is correct.
Use a private or otherwise controlled test arrangement appropriate to your channel and current YouTube workflow. Check the live status and playback from a separate viewer device if practical, then stop the test and review whether the intended scene and playlist appeared. Do not treat a successful test as a guarantee of uninterrupted service; it is a way to discover errors before they affect the regular schedule.
If the files resolve but YouTube reports an encoder or bitrate problem, troubleshoot that separately rather than changing paths blindly. The encoder settings checklist for a low-bitrate warning addresses that distinct issue. Once the restored setup has passed the source, playback and destination checks, resume the normal schedule and keep the backup folder intact for the next change.
For a channel where the local computer itself is the recurring point of failure, moving from a machine-based workflow to a hosted file-to-live workflow can remove the need to keep that computer switched on. StreamNeo turns an uploaded video into a YouTube live stream, so the specific burden of leaving your own computer running for that file-based broadcast is removed; you still need to prepare the media and verify the channel before going live.
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
Does exporting an OBS Profile back up my scenes?
No. A Profile contains stream, video and output settings, while scenes and sources belong to a separate Scene Collection. Export both when you need to preserve the full OBS configuration, then copy the media files those sources reference.
Does OBS Portable Mode include my playlist videos?
No. Portable Mode does not package media files used within a Scene Collection. Keep a separate copy of the files and check or edit paths if the setup moves to a different machine or folder structure.
What should I check first after restoring OBS?
Confirm the intended Profile and Scene Collection are loaded, then check the media paths and playlist playback. Verify audio and video, the current account or stream connection, and the receiving side in YouTube Studio before resuming the normal schedule.
How can I tell whether a backup is recovery-ready?
Restore it on the same or a replacement machine and test the important sources rather than relying on the presence of exported files. A useful backup has the Profile, Scene Collection, referenced media and path notes together, and it has passed a controlled playback and stream check.