To start an OBS stream after a Hetzner Windows VPS restarts, three separate links must work: Windows has to launch OBS, OBS has to begin sending the encoder feed, and YouTube has to permit that feed to start the broadcast. Configure and test each link independently; launching OBS is not proof that a scheduled event will go live without a person taking action.
The steps below assume a Hetzner Cloud server running a supported Windows installation and an OBS scene built for that machine. Other Hetzner products, Windows versions and capture sources can behave differently. Start with a test broadcast, and confirm what happens in YouTube Studio before relying on the setup overnight.
Confirm the Hetzner and Windows setup
First identify which Hetzner product you are using, which Windows version is installed, and how you connect to its desktop. Hetzner’s Windows on Cloud guidance describes its Cloud-specific Windows installation and licensing considerations. It also notes that Windows Server is unsupported on CAX Cloud servers, which use Arm64 processors. Do not assume that instructions for a Cloud VM apply identically to another Hetzner offering.
A VPS is a virtual machine, not necessarily a replacement for a local streaming workstation. In particular, check whether your OBS scene depends on a desktop window, a capture device, a logged-in user session, or media stored on a drive that may not be available after reboot. A scene with a video file at a fixed path is a different case from a scene capturing a user’s desktop. The server’s operating system, available devices and session state can all affect what OBS sees.
Hetzner’s Cloud overview can help you verify that you are reading documentation for the product you actually have. Neither that overview nor the Windows installation guidance establishes that a particular VM will perform well as an OBS machine. Check your own scenes, media paths, network connection and stream health rather than treating the hosting choice as a guarantee.
Before you change startup settings, sign in to Windows, open OBS manually and verify that the intended scene and media are present. If the source is missing after a manual restart, adding automation will only make OBS start with the same broken scene. For additional continuity considerations, see this guide to keeping OBS media files available after a Windows update.
Check YouTube’s stream and event settings
In YouTube Studio’s Live Control Room, select the stream configuration you intend OBS to use. You need its stream URL and stream key. YouTube explains that the key identifies the stream and directs encoder output; treat it as a password. Do not include it in screenshots, public notes, or logs, and avoid sharing an OBS profile that contains it. See YouTube’s stream settings help for the current controls.
Distinguish a persistent or reused stream configuration from a scheduled event. YouTube’s auto-start and auto-stop settings govern whether encoder activity can start or stop a broadcast. They do not open OBS in Windows. A scheduled encoder workflow may instead ask you to inspect the incoming preview and click Go live. The exact behaviour depends on the YouTube configuration, so inspect the controls for the stream or event you will actually use rather than inferring it from an old test.
If auto-start is available and you want encoder activity to start the broadcast, enable it in the relevant stream settings and confirm the saved selection. If a scheduled event requires a human to approve it, plan for that person to be available. YouTube’s encoder workflow describes the preview and go-live process; it should not be read as a promise that every scheduled event will start unattended when OBS connects.
A private or unlisted test is useful for learning what your channel’s chosen settings do without treating a public event as an experiment. Record the event type, auto-start state and what action actually changed the broadcast to live. Recheck those settings if you create a new event or reuse different stream settings. For a broader example of a continuous setup on another host, see how to set up a continuous YouTube stream on an AWS Lightsail VPS.
Put the stream URL and key into OBS
In OBS, open the streaming settings and select YouTube or the appropriate custom ingest configuration. Enter the stream URL and key from the intended YouTube stream. Labels and menus can change between OBS releases, so check the current OBS interface rather than relying on a click sequence from an older screenshot. If you use a profile or collection for more than one channel, make sure the active profile points to the intended destination.
The stream key is credential material. Keep it out of documents shared with helpers who do not need access, and do not paste it into a support request or public troubleshooting post. If it is exposed, replace or reset it in YouTube Studio and update OBS with the new value. OBS can save the configuration for future launches, but saving it does not validate that the key still matches the stream you intend to use.
Before automating startup, press Start Streaming while signed in and watch both OBS and YouTube Studio. Confirm that OBS reports a connection, the Live Control Room receives a preview, and the picture and sound are the intended ones. OBS’s quick start guide recommends testing settings before a first real stream. A visible moving image and audible sound are more informative than seeing OBS open successfully.
If YouTube receives a blank picture, investigate the source and scene before adding a reboot task. A black-screen diagnosis for a different encoder can still help frame the general distinction between an encoder feed and a visible programme; see how to fix YouTube Live showing a black screen from an FFmpeg stream. OBS and FFmpeg are not interchangeable, so use the steps as context, not as a direct OBS fix.
Set Windows to launch OBS after startup
There are two common launch paths: a shortcut in the signed-in user’s Startup folder, or a Task Scheduler task. A Startup shortcut is straightforward and runs in that user’s session after sign-in. Task Scheduler offers more control over triggers and recovery settings, but a task configured to run before sign-in may not have the interactive desktop that some OBS sources need. Choose based on the scene, not on the assumption that a more elaborate task is automatically more reliable.
For a simple test, create a shortcut to obs64.exe in the Windows Startup folder for the account that will run the stream. In the shortcut’s Target, include OBS’s --startstreaming launch argument after the executable path. Set Start in to the folder containing obs64.exe. OBS specifically documents this working-directory requirement for scheduled or otherwise automated launches on Windows. Its launch parameters page describes --startstreaming as the option to start streaming automatically.
If you use Task Scheduler instead, configure it to launch the OBS executable, supply the argument, and set its Start in or working-directory field to the OBS installation folder. Windows’ labels and available options can vary by version, and this guidance is not a universal task recipe. Start by triggering the task manually while signed in and observe whether it opens the expected profile and scene. Then test the actual reboot-and-sign-in path on the target Windows installation.
Avoid assuming that a task running whether or not a user is logged on can capture a desktop, game window or other interactive source. Such a task may start OBS but leave it without the same desktop context you see during a manual launch. If your scene needs an interactive session, use a launch method that runs in the intended signed-in account and verify the source after reboot. If a human must sign in, that is a real dependency to plan for, not a detail that the OBS command-line argument removes.
Enable OBS’s streaming startup behaviour
Windows launching OBS and OBS starting to stream are separate actions. OBS documents --startstreaming as a launch parameter that automatically starts streaming. Add it to the shortcut or task arguments; do not mistake an OBS window appearing at sign-in for proof that the encoder has connected.
Check the exact command you have configured. The executable should point to the installed obs64.exe, the argument should be passed separately as --startstreaming, and Start in should point to the containing OBS folder. A path with spaces needs appropriate quotation around the executable path, not around the argument as part of the path. If your installation differs from the example, use its actual executable location.
OBS may start with prompts or other conditions that interrupt an unattended launch, including a first-run setup, a profile-selection choice or a dialog caused by a failed source. Clear these manually before you test the automation. Confirm what OBS does when the stream key is invalid or the network is unavailable; a launch argument cannot repair those conditions. Keep a way to sign in and inspect the machine when the stream does not connect.
For a channel with a fixed file loop, review whether the scene starts from the right frame and whether audio is present after a fresh launch. For a devotional stream, for example, OBS might be open and connected while the intended bhajan file is missing or muted. If the underlying content needs rights checks, see how to check whether music is licensed for a 24/7 YouTube radio stream. Licensing and startup are separate checks, but both matter before you leave a channel running.
Reboot and test each link in the chain
Do not test only by closing and reopening OBS. A full Windows restart tests the actual startup path, saved credentials, user-session assumptions and source availability together. Schedule this test when you can watch it, and use a private or unlisted test configuration where appropriate. Tell anyone who might see the channel what to expect, and avoid using a live scheduled event as an unobserved experiment.
Use this checklist in order:
| Link to verify | What to check after reboot | What it does not prove |
|---|---|---|
| Windows launches OBS | Sign in as the intended Windows account and confirm OBS opens without a prompt blocking it | That OBS has started streaming or that the scene is correct |
| OBS starts the encoder feed | Confirm the expected profile and scene load, OBS indicates a connection, and the outgoing picture and sound are right | That YouTube has made the broadcast public or live |
| YouTube permits the broadcast | Check the selected stream’s settings, incoming preview and broadcast state in Live Control Room | That a different scheduled event will behave the same way |
If OBS does not open, inspect the shortcut or task target, account, trigger and working directory. If OBS opens but does not connect, check the argument, active profile, stream URL and key, and network access. If it connects but the programme is wrong, inspect media paths, scene sources and audio. If YouTube shows a preview but the event is not live, check the stream’s auto-start behaviour and whether YouTube is waiting for Go live.
Repeat the test after changing the Windows account, OBS installation, profile, key, event settings or source files. A successful test proves what happened in that configuration at that time; it does not guarantee the next reboot or a different event will behave identically. Keep a short record of the date, account used, OBS result and YouTube result so a later change can be compared with a known test.
Verify YouTube actually goes live
When OBS connects, open the corresponding stream in YouTube Studio’s Live Control Room. Check that a preview arrives, then verify the broadcast status itself. A preview means YouTube is receiving the encoder feed; it is not the same as the public broadcast having begun. For a scheduled stream, follow the displayed workflow and click Go live if YouTube asks for that action.
YouTube’s live streaming tips recommend setting up the encoder in advance, checking the preview, and monitoring stream health. Apply that advice during your restart test: check that audio and video are present, and look for a warning or health issue before relying on the stream. Do not infer a healthy broadcast from an OBS status indicator alone.
Keep the test event’s visibility and audience in mind. A private or unlisted test can reveal connection problems while limiting who can view it, but it may not reproduce every detail of a scheduled public event. If the channel depends on a scheduled programme, arrange a supervised rehearsal using the same event type and settings. Note whether YouTube required a person to start it. Do not treat an auto-start toggle in a separate test configuration as evidence about the scheduled event.
Plan for human checks and failure cases
Automatic startup reduces the number of steps a person must perform, but it does not remove the need to observe the result. A Windows update, changed password, expired or reset stream key, disconnected media path, new OBS prompt, network interruption or YouTube event setting can break a chain that previously worked. Decide who can sign in, inspect OBS and check YouTube Studio if the channel is not live when expected.
For unattended use, write down the recovery path: how to access the Windows session, where the intended OBS profile is, where to check the stream key without exposing it, and who can approve a scheduled event if needed. Avoid placing the stream key in a shared checklist. A reminder to check the channel after a planned reboot is more useful than assuming the word “automatic” means no supervision is ever needed.
If you need a system that turns an uploaded video into a YouTube stream without keeping OBS open on your own Windows session, StreamNeo removes the specific burden of having that computer launch and maintain the broadcast. It remains YouTube-only, and you still need to prepare the video and channel settings and verify the result in YouTube Studio. It does not change YouTube’s event workflow or establish that a scheduled broadcast will start without any human action.
If the file and channel are ready, compare the operating options before choosing a routine:
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 Windows starting OBS mean my YouTube event will go live?
No. Windows launching OBS, OBS sending a feed and YouTube starting the broadcast are separate links. A scheduled event may show a preview and still require someone to click Go live, so test the exact event configuration and plan for that possibility.
What does OBS’s --startstreaming argument do?
OBS documents it as a launch parameter for automatically starting streaming. It tells OBS what to do when launched; it does not make Windows launch OBS, supply a valid stream key, or change YouTube’s event settings. Set the working directory to the folder containing obs64.exe for an automated Windows launch.
Should I use a Startup shortcut or Task Scheduler?
A Startup shortcut is simpler and runs in the signed-in user’s session, which can suit scenes needing an interactive desktop. Task Scheduler provides more control, but a task running outside that session may not see interactive sources. Test the actual reboot and sign-in behaviour on your Windows version before depending on either method.
How can I safely test automatic startup?
Use a supervised full reboot and a private or unlisted test where appropriate. Check that Windows opens OBS, OBS loads the right scene and connects, and YouTube receives a preview; then confirm whether the broadcast itself needs an explicit action. Repeat the test after material changes to the event, profile, key or source files.