You can move an OBS playlist stream to another PC without rebuilding its scenes and sources: export the scene collection, then import it on the destination. Export the profile separately if you need its output settings, and copy the referenced playlist media files yourself; neither export packages those files.
The part that most often needs attention is not the scene layout but the connection between each file-backed source and its media path. Plan the move as three separate jobs—configuration, media, and destination checks—and verify playback before you switch the live channel over.
Export the scene collection
On the original PC, note which scene collection is active before exporting. In OBS, scene collections are managed separately from profiles; use the Scene Collection menu to export the collection you actually use. If you have more than one collection, check the names carefully rather than assuming the first or currently visible one is the right one.
A scene collection contains your scenes and sources, including global audio sources. That is the structure you want to preserve: scene names, source arrangement, and the relationships between them. The OBS Project’s Scene Collections guide explains the export and import controls.
Before exporting, open the scenes that matter to your broadcast and make a simple inventory of file-backed sources. Include playlist videos, standalone media sources, images, logos, and any local overlays. This is not a substitute for the collection export; it is a reminder of what the export does not carry. A written list is useful if your collection has several scenes that reuse different assets.
If you use a playlist to keep a radio, devotional, or ambience stream running, note how that playlist is implemented. It could be an OBS Media Source with a playlist, or a VLC Video source. The distinction matters on the destination because a VLC-based source has an additional software dependency, while either kind can depend on media files stored outside the collection.
The collection itself is not a backup of every component of the broadcast. For example, a scene might retain a source entry whose file path points to a video on a drive connected only to the old computer. The imported scene can appear in OBS while that source still cannot find its media. Treat export as preserving scene configuration, not as making all the inputs portable.
Export the profile separately if needed
A profile is a separate export from a scene collection. Export the active profile too if you want to retain its streaming, video, and output settings. OBS documents profiles as containing settings such as Stream, Video, and Output; its Profiles guide describes the profile export and import controls.
Do not expect a profile import to restore scenes. Likewise, importing a scene collection does not restore the output configuration held in a profile. They answer different questions: the collection describes what OBS composes, while the profile describes relevant output behaviour. If you only bring one across, you may preserve one part of your setup and still need to configure the other on the new PC.
Before exporting the profile, record any details you will need to confirm later, especially the selected output mode and the intended stream destination. Do not put a stream key in a general migration checklist or share it alongside exported files; treat it as a credential and enter it only in the appropriate OBS account or stream settings. If you need a reminder of how output choices affect a YouTube broadcast, the OBS setup guide for a 4K 60fps YouTube loop is a separate reference, not a substitute for checking your own channel and connection.
A profile export is most useful when the destination PC should behave like the original for encoding and output. If you are deliberately changing resolution, frame rate, or output mode as part of the move, you may prefer to import the profile and then adjust it, rather than assuming every old setting remains appropriate. Check the resulting configuration on the new machine before a public broadcast.
Copy playlist media files
Copy the playlist files and any other assets referenced by your sources as a separate transfer. OBS’s portable-mode guidance is explicit that files used within a scene collection, including images and media, are not made portable by the configuration move. An export does not include your video folder, audio tracks, images, or overlays.
Make a folder inventory from the old PC and compare it against the playlist entries and the sources you noted earlier. Check that the copied files are complete and readable on the destination, and keep the filenames intact unless you intend to update source references. If a playlist points to several files, moving only the playlist definition or only some of its media leaves the stream incomplete.
A removable SSD or USB drive can be a convenient way to carry the exported configuration and media, but it is optional transfer storage, not an OBS requirement. You can use another transfer method if it preserves the files. The important part is that the destination has the actual media, in a location that OBS can reach, and that you do not accidentally leave the only working copy behind on the old PC.
If you are using VLC Video as the playlist source, install VLC on the destination as well. OBS notes that its VLC Video source requires VLC and that 64-bit OBS requires 64-bit VLC; see the official Media Sources guide. A playlist entry can be correct while playback still fails because this dependency is absent or mismatched.
For a long-running channel, the source files are part of the broadcast setup, not disposable transfer clutter. Check that every playlist item expected to run is present, and consider keeping a separate backup of the original media until the destination has been verified. If you are building a recorded-class channel, the workflow for a 24/7 playlist of recorded classes on YouTube Live may help you think through the playlist content, while the file copy itself remains your responsibility.
Import the collection and profile on the new PC
Install and open OBS on the destination PC, then import the scene collection using the Scene Collections controls. Import the profile separately using the Profile controls if you exported it. After importing, select the intended collection and profile so you are not testing a default or unrelated configuration by mistake.
Importing a collection made on a different operating system may cause OBS to adjust it for the destination operating system, according to the Scene Collections documentation. That does not mean it has found or transferred the media. Open the key scenes and inspect the sources after import; a visible source name is not proof that the source’s referenced file is available.
Review plugin-dependent scenes and filters separately. A collection may include a source or filter that relies on a plugin, but the plugin itself should be treated as another destination requirement. Install a compatible version where needed and consult that plugin’s documentation for any settings migration. OBS’s Plugins Guide covers plugin installation locations, but there is no single documented procedure that transfers every third-party plugin’s settings.
This staged import makes it easier to isolate problems. First confirm that the expected scenes and sources appear; then check that the right profile is active; then deal with file paths, plugins, and playback. If you change several things at once, it becomes harder to tell whether a missing picture comes from the imported collection, an unavailable file, or a plugin that is not installed.
Preserve or update media paths
Once the media is copied, choose between preserving the original directory structure and updating source paths. Preserving the structure can be convenient if you can reproduce the same path on the destination PC. Updating paths is more practical when the files will live somewhere different, but you must correct the affected sources or paths in the collection.
OBS’s portable-mode documentation describes these path choices for relocating a configuration: use a generic path common to devices, or manually modify collection paths after moving. It also makes clear that portable mode is about where OBS keeps its configuration, not about bundling media. The documentation states that media and images used within a scene collection are not portable even when portable mode is used.
| Path approach | When it fits | What you need to check |
|---|---|---|
| Recreate the same folder structure | You can place the copied assets at the same usable path on the new PC | The destination drive and folder names match what the source expects |
| Update paths on the destination | You are storing media in a different location | Every source and playlist reference points to the new location |
Do not assume that a drive letter or home-folder path will mean the same thing on both computers. A file stored on one computer’s desktop, for instance, may not exist under that same location for a different user account on the destination. Choose a stable media folder deliberately, then either reproduce the expected structure or edit the sources to point to it.
Portable mode can make OBS configuration placement easier to move in supported environments, but it does not remove this media-path decision. OBS states that portable mode is not supported on macOS or Linux. If you are considering it, read the current official guidance and keep the media files as a distinct transfer either way.
A useful way to track the work is to keep a short path checklist: source name, old file location, destination file location, and whether the reference has been checked. This is especially helpful when several scenes reuse a logo or background track, since correcting one source does not necessarily correct a separate source entry elsewhere.
Check missing sources and output settings
After import and path work, open each scene used by the stream and check for missing-media indicators, blank previews, or unexpected source behaviour. Inspect the playlist items rather than only the first item. A source can show its name in the source list while still pointing at a file that is unavailable or that does not play correctly on the new PC.
Then verify the output settings in the active profile. Check that the intended YouTube destination is selected, that the stream credential is current and kept private, and that the output choices are the ones you mean to use on this PC. A profile import restores profile settings, not permission to stream or a guarantee that the channel is ready; confirm current account and YouTube requirements through official guidance before relying on it.
Check plugins and filters that affect audio or video as well. A missing plugin can leave a scene different from the original even when all the media files are present. If you use a VLC playlist source, confirm VLC is installed with the architecture matching OBS. For audio-focused channels, review the stream’s playback and levels in context; the advice for fixing desynced audio in a 24/7 YouTube music stream can help identify a separate sync issue, but first establish that the correct source files are loading.
Keep the old PC and its working configuration available until the destination has passed its checks. This gives you a way to compare source properties or recover a forgotten asset without rebuilding the scene. It is a practical fallback, not a reason to leave two PCs trying to broadcast the same channel at once.
Test the playlist before going live
Run the playlist in OBS on the destination before making it the live machine. Watch enough of the sequence to confirm that items load in order, transitions behave as expected, and audio is present. Check at least one source from each group you depend on, such as playlist video, standalone image, background audio, and any overlay. A still preview is not a meaningful test of a playlist that must advance through multiple files.
If you can, perform a private or otherwise non-public test appropriate to your YouTube setup, and verify the result from the viewer side as well as in OBS. Check that the picture and sound reach YouTube, not just the local preview. YouTube’s current live streaming help is the place to check platform requirements and controls; the exact options available can depend on your channel and current YouTube interface.
Once the test passes, write down which collection and profile are active and where the media folder lives. That small handover note is useful if you need to restart OBS later or move the setup again. If you have chosen to keep the stream running from a PC, remember that the migration only verifies this new machine’s setup; it does not protect a channel from every later interruption. For a playlist that stops at its end, see the specific considerations in keeping an OBS radio stream going after a playlist ends.
If the job of keeping a dedicated computer available and checking it through the night is the problem you are trying to avoid, StreamNeo can run an uploaded video as a YouTube live stream without leaving your own PC on; it is a separate workflow from transferring an OBS scene collection, and it is YouTube-only.
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 scene collection include my playlist videos?
No. The collection preserves scenes and sources, but the referenced media files remain separate dependencies. Copy the playlist videos and other local assets to the new PC, then make sure the source paths resolve.
Do I need to export a profile as well as a scene collection?
Export the profile if you need its output-related settings on the destination. It is separate from the collection: a profile does not restore scenes, and a scene collection does not contain profile output settings.
Should I keep the same media folder path?
Either reproduce a path that works for the imported sources or update the affected paths on the destination. Keeping the same folder structure can reduce edits, while changing it means checking each source that points to the old location.
Does OBS portable mode make the playlist portable?
No. Portable mode concerns OBS configuration placement, not the media files referenced by the collection. Follow OBS’s current documentation for supported operating systems and still copy and verify the media separately.