Opening OBS when you sign in to Windows does not, by itself, start a YouTube broadcast. To play a playlist, configure the right OBS media source, then choose separately whether to go live manually or use OBS’s automatic-start option.
The steps below apply to Windows users in India, but the documented workflow is general: the research does not establish a separate India-specific rule for this setup. Treat automatic go-live as a deliberate choice, not a side effect of adding OBS to startup.
Add OBS to Windows startup
First install OBS from an official source, such as the OBS Project website or its linked release channels. Avoid third-party download sites. The OBS Windows installation guide describes the available installation routes and requirements.
To open OBS when your Windows user account signs in, press Windows + R, enter shell:startup, and press Enter. This opens the Startup folder for the current user. Add a shortcut to OBS there; do not move the application itself into the folder. The next time that user signs in, Windows should launch the shortcut.
You can also check Settings > Apps > Startup or Task Manager > Startup apps. If OBS appears in the list, enable it there instead. The exact labels vary between Windows versions, so the folder method is a useful alternative when you cannot find the toggle.
Microsoft also documents shell:common startup, which opens the shared Startup folder for all users of the PC. Use that only if OBS should launch for every account on the machine and you have permission to change the shared folder. Windows startup is tied to a user sign-in; it is not the same as running a stream independently when nobody has signed in. See Microsoft’s guide to configuring startup applications for the Windows-side options.
A normal OBS shortcut is enough if your requirement is simply “open OBS after I log in”. Do not add a streaming command yet. On a shared or unattended PC, check which account signs in, whether Windows asks for a password, and whether the machine is set to sleep. Launching OBS does not resolve those separate power and sign-in conditions.
Configure the playlist as an OBS media source
Choose the source based on what you want to play. If the playlist is one video that should repeat, add a Media Source, select the file and enable Loop in its properties. This is the simpler route because it does not depend on the separate VLC playlist source.
For several local video files in a queue, add VLC Video as a source and build its playlist from the files. OBS provides loop and shuffle controls for this source. VLC must also be installed, and for 64-bit OBS the matching 64-bit VLC installation is needed. If the VLC source is missing from OBS, check the VLC installation and architecture before rebuilding the scene. OBS explains the available media source options.
Keep the video files in a stable folder, rather than a temporary downloads location that you might clear later. Use descriptive filenames and check the queue order in OBS. If you move or rename a file after setting up the source, OBS may no longer find it. Test what happens at the end of the final playlist item: confirm whether playback loops or stops, and whether the transition between files looks and sounds as intended.
In your scene, make sure the media source is visible and positioned as expected. Check that its audio is not muted in OBS and that the mixer shows a signal during playback. A source can be present in the scene but hidden behind another source, pointed at a missing file, or silent because its audio has been disabled. Test the same scene you intend to use on YouTube, not an unrelated preview scene.
For a longer walkthrough of playback gaps and scene behaviour, see this guide to avoiding a black screen between sermon videos. The practical point is to test the hand-off between files, not just confirm that the first one plays.
Choose manual or automatic stream start
There are two separate decisions: should OBS open at sign-in, and should YouTube begin broadcasting when OBS sends a signal? You can have OBS open automatically while still starting each broadcast yourself. That is a safer default while you are configuring a scene, checking the stream key or learning the workflow.
For manual start, open OBS, check the preview and audio, then start streaming from OBS when you are ready. In YouTube Studio, select the intended live stream and verify that the incoming picture and sound are right before you make the broadcast public or start it through the relevant controls. The exact YouTube flow depends on how the stream was created and the current Studio interface.
Automatic start can reduce steps when the channel is deliberately unattended, but it also makes mistakes easier to publish. A wrong scene, an outdated playlist, an accidental desktop capture or a test signal can go out without the usual final check. If a computer reboots overnight and signs in, automation may act on the configuration that is present at that moment, not the one you intended to use.
| Workflow | What happens at sign-in | Broadcast control | Best suited to |
|---|---|---|---|
| OBS startup only | OBS opens | You start the stream manually | Setup, testing, or a person checking the programme first |
| OBS plus automatic start | OBS opens and the launch option can tell it to start streaming | YouTube’s encoder auto-start settings also affect whether the broadcast begins | A tested, intentional unattended workflow |
The table describes the distinction, not a guarantee that every sign-in will produce a live broadcast. YouTube’s settings, stream selection, account eligibility and OBS configuration all matter. For a separate perspective on a computer-based workflow versus cloud playout for long-running programming, read Control Room versus cloud playout for a 24/7 lecture stream.
Understand the --startstreaming launch parameter
OBS supports launch parameters that change what happens when the programme opens. The parameter --startstreaming tells OBS to begin streaming on launch. It is not the same as the Windows Startup folder, and a regular OBS shortcut does not need it when you only want the application to open.
To add it, edit the OBS shortcut’s Target field and append the parameter after the quoted path to obs64.exe, with a space between the closing quote and the parameter. Do not remove the existing path or its quotes. A shortcut may also specify a profile, scene collection or scene, and OBS documents additional options such as --profile, --collection, --scene and --minimize-to-tray in its launch parameters documentation.
For automated or scheduled launches, OBS advises setting the shortcut’s Start in field to the folder containing obs64.exe. This is a consequential detail: a shortcut can appear to open but use an unexpected profile or fail to locate files if its working directory and paths are wrong. Confirm the shortcut’s target, working directory, profile and scene collection before enabling automatic streaming.
There is no need to use --startstreaming merely to make OBS open at sign-in. Add it only if your intended behaviour is for OBS to try to begin streaming as it launches, and only after the full workflow has been tested. Starting OBS and starting a public YouTube broadcast are related steps, but they are not interchangeable.
Confirm YouTube auto-start settings
An encoder stream needs to be associated with the intended YouTube Live stream. YouTube’s setup process uses a stream key in the encoder, so check that OBS has the correct key and that the selected stream in YouTube Studio is the one you mean to run. A valid key does not prove that the right programme, title or audience setting is selected.
YouTube also has an auto-start setting for encoder streams. When enabled, an incoming encoder signal can trigger the broadcast start; when it is not enabled, sending a signal does not necessarily make the broadcast live automatically. Check the current control-room settings and YouTube’s encoder streaming instructions before relying on automatic behaviour. The interface and available controls can change.
YouTube’s published eligibility guidance says a channel must be verified and have no live-streaming restrictions in the preceding 90 days to use live streaming. Those are general YouTube requirements, not a special rule for India or for OBS startup. Review the current YouTube live-streaming eligibility guidance for your channel rather than assuming that a configured encoder means the account is ready.
If you are not certain what happens when the signal arrives, leave auto-start off and use a manual start while testing. With --startstreaming enabled, OBS may send a signal as it opens; YouTube’s separate setting influences whether that signal starts the broadcast. Verify the behaviour with a private or otherwise appropriate test arrangement before using the setup for a public programme.
Test the full workflow and check content rights
Test the sequence from a Windows sign-in, not just by pressing Play in OBS. Sign out or restart when it is safe to do so, sign back in to the intended account and observe what opens. Check that OBS uses the expected profile and scene collection, the correct scene appears, every playlist file loads, and audio is present. Then verify the selected YouTube stream and whether it remains stopped or starts, according to the choice you made.
OBS recommends testing settings and streaming for a few minutes before a real broadcast; its quick-start guide covers the initial checks. During your test, watch YouTube Studio as well as the OBS preview. Look for the incoming signal, picture and sound, and confirm whether the broadcast state matches your intention. A working local preview alone does not confirm what YouTube is receiving.
Test a restart and a return from any power-saving state you expect to use. If Windows installs updates or loses power, you may need to sign in again; startup shortcuts do not bypass that requirement. Review Windows sleep settings and avoid depending on an unattended session until you know how the PC behaves after a restart. For a sustained stream, upload stability also matters; this JioFiber checklist for a recorded lecture stream discusses the connection side of the decision.
Before you automate a playlist, check the rights for every video and its audio. YouTube scans live streams for third-party content. It may warn you, replace the stream image, interrupt or terminate the stream, or apply a strike. Owning a copy of a track or having a licence does not necessarily mean the rights holder has added your channel to a Content ID allowlist, where one is required for uninterrupted use. YouTube explains its copyright rules for live streams.
Use material you own or are authorised to broadcast, and confirm the scope of permission for a continuous YouTube stream, including any required allowlisting. Do not assume that devotional, ambient, study or local-business content is exempt because it is being looped rather than played once. Rights issues are not solved by Windows or OBS settings, and no setup guarantees that YouTube will approve a broadcast.
If running the PC overnight is the part that makes the workflow difficult, StreamNeo can remove the need to keep your own computer switched on by turning an uploaded video into a YouTube live stream. It does not change the need to choose the right content or check broadcast settings.
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 adding OBS to Windows startup make YouTube go live?
No. It opens OBS when the Windows user signs in. Starting a broadcast is a separate action, unless you deliberately configure OBS’s --startstreaming option and YouTube’s auto-start settings to work together.
How do I make one video repeat in OBS?
Add the video as a Media Source and enable its Loop setting. For a queue of several files, use the VLC Video source instead and check that VLC is installed with the architecture that matches OBS.
What does --startstreaming do?
It tells OBS to begin streaming when OBS launches. It does not replace YouTube’s stream selection or auto-start controls, so test the signal and broadcast state before using it for an unattended stream.
Is there a separate India-specific rule for this setup?
The documented Windows, OBS and YouTube workflow is general, and the available research does not establish an India-only exception for this procedure. Check YouTube’s current eligibility and copyright guidance for your channel and content.