To launch OBS with a saved setup for YouTube looping, select the Profile that holds your stream and output settings, and the Scene Collection that holds the loop scene and its sources. OBS documents launch switches for choosing those items and optionally starting a scene or stream, but the example here is illustrative: paths and launch behaviour vary by installation, so test yours before relying on it overnight.
A Profile and a Scene Collection are separate pieces of configuration. Keeping that distinction clear makes it easier to reuse a channel’s output settings with different scenes, or to use the same loop scene with a different output configuration. It also helps you diagnose a launch that opens OBS but does not show the file, play audio, or connect to YouTube.
Separate Profiles from Scene Collections
Think of a Profile as the settings for sending a signal, and a Scene Collection as the contents of the picture and sound being sent. The Profile holds most stream, video and output settings. OBS’s Profile documentation includes Stream settings, including a Connected Account, Video settings such as Base (Canvas) Resolution, and Output settings. It explicitly distinguishes Profiles from scenes; for the latter, use Scene Collections. See the OBS guide to Profiles when you want to confirm which settings belong there.
A Scene Collection holds scenes and sources, as well as Global Audio Sources. A scene might be called “Loop” and contain a Media Source pointing to a local bhajan video, a logo image and an audio mixer configuration. The collection does not store output settings. OBS documents the division in its Scene Collections guide.
This division matters at launch. Selecting only a Profile may leave OBS with a different scene collection than you expected; selecting only a collection may leave it using a different stream configuration. If a familiar scene appears but YouTube does not receive the intended output, inspect the Profile. If the stream connects but the expected visuals are absent, inspect the collection and the media paths.
Before automating, open OBS normally and note which Profile and collection are selected. Set up each deliberately rather than using whichever configuration happens to be active. A profile can be duplicated and exported for backup, according to the OBS Profile documentation. Keep a known working copy before changing output settings for a new channel or format.
For a broader account of taking a video file to a live broadcast, see how to stream a pre-recorded video as a YouTube Live stream. The launch switches only select OBS configuration and actions; they do not prepare the underlying video or establish that a continuous broadcast meets YouTube’s current requirements.
Choose names for the saved setup
Choose names that tell you what the configuration is for without relying on memory. For example, a Profile might be YouTube Loop, while its Scene Collection might be Loop Scenes, with the scene itself named Loop. These are example labels, not special OBS keywords. The launch arguments need to match the names you actually saved in OBS.
Avoid nearly identical names such as “YouTube Loop”, “YouTube Loop 2” and “YouTube Loop New” if you may later create shortcuts or scheduled tasks. A clear naming pattern helps you see at a glance whether a selected collection belongs to a devotional music channel, a local news loop or a study ambience stream. If you do keep alternatives, identify their purpose in the name and verify which one is selected before launch.
Spaces in names are allowed, but when you pass a name as a command-line argument, put it in quotes. Without appropriate quoting, a command interpreter can treat the words as separate arguments. Use the names as shown in the OBS interface, including spaces and punctuation, and do not assume a scene name is interchangeable with a collection name.
There is a practical reason to settle names before building a shortcut. Renaming a Profile, collection or scene later means checking the launch arguments and any automation that refers to it. Keep a short note with the exact names and the purpose of each. That is more reliable than trying to work out which similarly named setup a shortcut was meant to select after a restart.
Use the documented OBS switches
OBS Project lists launch parameters for automation on its Launch Parameters page. The relevant switches are --profile to choose a Profile, --collection to choose a Scene Collection, --scene to select a scene, and --startstreaming to request that OBS start streaming. Names containing spaces should be quoted as argument values.
The following is an illustrative Windows-style pattern, not a tested universal command:
obs64.exe --profile "YouTube Loop" --collection "Loop Scenes" --scene "Loop" --startstreaming
Read it as a sequence of intentions: launch the OBS executable, choose the Profile named YouTube Loop, load Loop Scenes, select Loop, and request streaming. The executable may have a different name or location on your computer. This example has not been verified against your installation, OBS version, account, scene contents or operating system, so do not treat it as copy-and-paste proof that an unattended stream will work.
You can omit --scene if the selected collection already opens with the intended scene, but being explicit can make the intended choice easier to audit. You can also omit --startstreaming while you are still checking configuration. Starting OBS and selecting a scene is a different action from starting a broadcast; adding the streaming switch changes the consequences of a launch, particularly if it is triggered by a scheduled task while you are away.
A flag cannot repair a missing or invalid setting. The Profile must already contain the destination and output settings you intend to use, and the Scene Collection must contain a usable scene and media source. OBS documents the switches, not a guarantee that they will match every installation or that the resulting YouTube broadcast will stay connected. For settings that affect picture and delivery, the 24/7 OBS settings guide for YouTube in India is a separate place to review the trade-offs.
Prepare the loop scene before launch
Put the loop media into the Scene Collection you plan to select. For one local video, add a Media Source and enable its Loop option. OBS’s Media Sources guide says looping is Off by default, so a file that plays once and then stops may simply have that option disabled. Confirm the source points to the intended file and that the file is available at the same path when OBS is launched by automation.
A playlist is a different input shape. OBS’s VLC Video source can play a playlist and has a Loop Playlist option, which the OBS documentation lists as On by default. It requires VLC to be installed, and 64-bit OBS requires 64-bit VLC. If you use a playlist, check the installed VLC build and inspect the source in the scene rather than assuming the single-file Media Source instructions apply.
| Loop approach | Suitable when | What to check |
|---|---|---|
| Media Source | You want to repeat one local file | Enable Loop and check the file path |
| VLC Video | You want a playlist or list of files | Install matching VLC, check playlist entries and Loop Playlist |
The table describes OBS source behaviour, not a recommendation about what content to broadcast. Use media you have permission to stream, and check YouTube’s current rules for continuous or repeated content. The research supporting this setup guide does not establish YouTube’s current eligibility, duration limits or treatment of repeated material. A successful OBS launch is not evidence of policy compliance.
For a devotional channel, for example, the scene might pair one permitted local recording with a static title card and a restrained audio level. A local news loop may use a playlist of clips instead. In either case, inspect the source properties and playback before enabling a launch action that starts streaming. If you are working specifically with devotional music, the guide to making a 24/7 devotional music live stream covers content and channel considerations beyond these OBS switches.
Adapt the example to the executable path
The string obs64.exe is an example executable name, not a promise about where OBS is installed or what its executable is called on your machine. Installation choices, operating system and architecture affect the path. Locate the executable through the installation you actually use, and keep its path distinct from the arguments that select the Profile and collection.
If the path contains spaces, the executable path needs quoting in the way required by the shell or shortcut field, while the names after --profile, --collection and --scene also need their own quotes when they contain spaces. These are separate quoting jobs. A command can fail to select a saved Profile if the shell splits its name, even when OBS itself starts successfully.
Do not paste a Windows path into a macOS command, or assume a shortcut example applies to a terminal, scheduled task or launcher. Use the OBS launch documentation for the platform-specific form and check the actual executable location. The documented switch names are useful, but their surrounding syntax depends on how that platform launches an application.
Portable mode is not required merely to choose a saved Profile and collection. OBS describes portable mode as loading configuration from beside the application, but notes that media files in scene collections are not made portable by this. Moving the application or configuration therefore does not necessarily move or relink your video, images or other assets. The OBS portable mode page also says portable mode is unsupported on macOS and Linux. Do not use it as a shortcut around broken media paths.
Pass arguments on Windows or macOS
On Windows, a shortcut can launch OBS with arguments appended after the executable in the shortcut’s Target field. Make a copy of an existing shortcut first, then edit the copy so you can return to a normal launch easily. The OBS Launch Parameters page gives the Windows shortcut approach; use the actual executable path in your Target field and add the switches after it. Preserve the quoting that the field requires for the path and the names.
After editing, open the shortcut’s properties again and read the Target from beginning to end. Check that the executable path is still a single path, that each quoted name follows its intended switch, and that there are no stray quote marks. Launch without --startstreaming first if you need to validate the selected Profile, collection and scene without immediately attempting a broadcast.
For macOS, OBS documents passing launch arguments with open -a "OBS" --args followed by the switches. The OBS application is addressed differently from a Windows executable path, and a shell command or Automator action has its own quoting rules. If you use an Automator Run Shell Script action, test the exact script in your own account rather than assuming a Windows shortcut’s syntax carries over.
The launch documentation also notes that --version is unavailable on Windows. Do not use that flag as a Windows version check. More generally, avoid inferring that a switch has a particular effect merely because another platform’s command accepts it; consult the documented launch parameters and check OBS’s visible state after launch.
Launching with --startstreaming can be useful when you deliberately want an unattended action, but it also removes a manual pause in which you could notice the wrong scene, a silent media source or an unexpected account. Make a first run interactive. Add automatic streaming only after checking the exact configuration, and keep a way to stop or disable the shortcut if the result is not what you intended.
Set the working directory for automated launches
A scheduled or automated launch has a little more context than a command typed into a terminal. On Windows, OBS’s launch guidance says to set the scheduled task’s Start in field to the folder containing obs64.exe. This working directory can matter when an automated process starts the program outside the usual shortcut context. Use the folder that actually contains your executable rather than copying a path from another computer.
Treat Start in as a separate setting from the Target or command. The Target says what program and arguments to launch; the working directory says where the process starts from. Confirm both. Also consider which Windows account runs the task: files, mounted drives and user-specific configuration available in your normal session may not be available to another account or a background task.
Media paths deserve particular attention. A source that points to a file on a removable drive, a disconnected network location or a user-specific folder can appear correctly configured in OBS but fail when the task runs under different conditions. A working directory does not make an absent file available. Test with the account and launch method that will actually be used, and inspect the media source after launch.
On macOS, the documented open -a form is the platform-specific way to pass arguments. If an Automator action is used, its shell environment and working context may differ from an interactive session. Keep paths explicit, avoid relying on an assumed current folder, and run a supervised test before adding the action to login or other automation. This is a portability precaution, not a claim that a particular script will work unchanged in every macOS release.
Automation also changes the cost of a mistake. A shortcut started by a person is easy to notice; a scheduled action may launch at a time when nobody is looking. Leave a manual check or alerting process appropriate to your situation, and do not treat an automatic start as a substitute for checking the broadcast. If avoiding a computer running overnight is the main concern, StreamNeo removes that specific requirement by letting you upload the video once and run the YouTube broadcast without keeping your own computer switched on; it does not remove the need to verify the channel and content.
Test the selected scene before streaming
Run the launch in stages. First use the arguments that select the Profile and collection, and, if useful, the intended scene. Leave out --startstreaming while verifying that OBS opens the expected configuration. Check the visible Profile and collection, preview the scene, and confirm that the file plays from its beginning or resumes as intended. Listen to the audio rather than relying only on moving video in the preview.
Then inspect the source and mixer. Confirm the video is not a black frame, that the loop behaves as intended at the end of the file, and that audio is audible without clipping or unwanted silence. If a playlist is involved, confirm that the next item appears and that it can continue when the first ends. A loop icon or checked option is not a substitute for watching a complete transition at least once.
Only after those checks should you test the stream path. Start the broadcast manually and confirm the status in OBS and on YouTube. The OBS disconnect diagnosis guide can help when a stream connects but later drops; a launch command cannot diagnose network interruptions or keep a remote broadcast uninterrupted. Do not assume that a successful start means a reliable overnight run.
Finally, test the actual automated method under supervision. A scheduled task, shortcut or Automator action can behave differently from a command entered in a terminal. Check whether it starts one OBS instance or opens an existing one, whether the expected Profile and collection are selected, and whether the media file remains available. Repeat the test after changing names, file locations, the OBS installation or the launching account.
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 a Profile contain my scenes?
No. OBS Profiles contain most stream, video and output settings, while Scene Collections contain scenes and sources, including Global Audio Sources. Select both when you need a particular output setup and a particular set of visuals and media.
Do I need --scene if I use --collection?
Not always. If the selected collection already opens on the scene you want, you may not need to specify it; adding --scene makes the intended scene explicit. Confirm the scene name and what OBS selects on your installation before automating.
Why did the launch open OBS but not start the stream?
The executable may have opened even though an argument was malformed, a saved name did not match, or the selected configuration was not ready. Check the Target or script, the Profile and collection names, and the OBS stream status. The documented flags do not guarantee that a YouTube broadcast connects or remains live.
Does a successful loop prove YouTube allows it?
No. OBS’s media and launch documentation explains how to select a source and repeat it, not YouTube’s current rules for continuous or repeated content. Check the current YouTube Help requirements for your channel and content, and confirm your live status independently before relying on a broadcast.