A Windows Hetzner server can run an encoder for a YouTube Live stream while your own computer is off, but first confirm that Hetzner supports and licenses the Windows installation you plan to use on Cloud. The available guidance on custom ISOs is not proof of Windows Cloud support or a Windows licence.
Once that route is confirmed, the practical sequence is to provision the server and network, secure remote administration, install an encoder, connect it to a YouTube Live event, and test while monitoring the result. An always-on setup is an operating goal, not a promise of uninterrupted delivery or one continuous archived video.
Confirm the Windows route before creating the server
Do not begin by attaching an ISO and assuming the rest is routine. Ask Hetzner directly whether your proposed Windows image and installation method are supported on a Cloud server, how licensing works, whether additional Windows costs apply, and which Windows-specific installation instructions to follow. Confirm any licence obligations with Microsoft as well. Keep the answer you receive with your deployment notes so that a later rebuild does not depend on guesswork.
This check matters because Hetzner's Cloud server creation guide describes images and custom ISOs as general provisioning options, but that does not establish a supported Windows image, a valid Windows licence, or a Windows installation procedure for Cloud. Do not substitute information about a Windows Server add-on for Hetzner dedicated root servers: it is not evidence of an equivalent Cloud offer. If either party cannot confirm your route, pause and choose an installation path they do support rather than treating a successful boot as proof of compliance.
Manual ISO installation also changes the support burden. Hetzner warns that an ISO installation can have DHCP configuration trouble and may need a gateway configured manually. Its example uses Linux-specific commands, so it is not a recipe for Windows. Ask for Windows-specific network steps and make sure you can recover access if the guest comes up without working connectivity.
Provision the server and its network deliberately
After the Windows path is clear, create the Cloud server in Hetzner Console. The creation workflow asks you to choose a server type, location, image, networking, firewall and backup options. These choices affect different parts of the job: the server type supplies the compute and storage you rent, the location determines where it runs, the network settings determine how you reach it, and the firewall controls which traffic is admitted.
Plan the address and management route before provisioning. Hetzner allows a server to have public IPv4 and IPv6, one public address, or no public address. A server without a public address needs to connect through a private Network. That may suit a deployment with an existing private access path, but it is not a shortcut: establish how you will administer the machine before removing public reachability. If you need a public address for initial setup, decide how you will restrict management access instead of leaving it broadly reachable.
Treat image changes as destructive. Hetzner says changing the operating-system image after creation erases disk data. Do not use a casual image change as a fallback after uploading stream media, configuring the encoder, or storing other files. Keep source videos and configuration backups somewhere separate, and plan a rebuild as a recovery procedure rather than assuming the server disk is a safe archive.
You will find a broader discussion of what to weigh when choosing a rented machine in cloud platform choices for a 24/7 YouTube stream. For this Windows-specific route, the deciding point is not a broad ranking: it is whether the exact Windows deployment, network path and operating costs make sense for your workload.
Secure remote access to Windows
Remote access is part of the system you are operating, not a one-time convenience. Hetzner documents Cloud Firewall behaviour: traffic matching defined rules is allowed, inbound traffic not covered by rules is blocked by default, and outbound traffic is permitted by default. That gives you a useful restrictive starting point, but the cited firewall guidance is not a full Windows Remote Desktop Protocol hardening recipe and does not decide which RDP policy is appropriate for you.
Before enabling remote administration, work through Windows-specific guidance and check both the guest's Windows firewall and the Hetzner Cloud Firewall. Decide how administrators will authenticate, who needs access, and how you will regain control if a rule or Windows update blocks your normal route. Avoid opening remote desktop access to everyone on the internet simply because that makes the first connection easier. If you use a private network or another controlled access method, document its requirements and test it from outside your everyday workstation before relying on it.
Keep administration separate from viewing the stream. A working YouTube player does not show that the Windows host is safely configured; conversely, a remote desktop session can fail while an already-started stream continues. Test recovery access while you still have a planned maintenance window and a known-good configuration, not during a live incident.
Hetzner's ISO networking warning is especially relevant here. If Windows does not acquire the expected address or route during a manual install, use Windows instructions and Hetzner support to diagnose it. Do not paste Linux interface or route commands into Windows. Also check whether any temporary network adjustment survives a restart; a setup that works only until the next reboot is not ready to carry an unattended channel.
Install and configure an encoder
Once Windows is licensed, supported, reachable and updated according to your maintenance plan, install an encoder from its official source. OBS is one possibility: YouTube lists it as open-source software available at no charge. YouTube describes an encoder as the software or hardware that converts video into a digital format for streaming. Choose it because it fits your content and your need for control, not because the word “server” makes one encoder automatically suitable.
Prepare the actual programme before configuring the live output. A devotional channel might use a sequence of permitted bhajan recordings and a visual loop; a local business might show a schedule and notices; a study channel might replay a lesson. Confirm that your source files are available on the Windows machine, that the video and audio are in the right order, and that the stream will not silently end when one file reaches its last frame. For a prerecorded playlist, use a small test set first and watch whether transitions, audio levels and repeat behaviour are what you expect.
The research for this setup does not verify a particular current OBS Windows version, unattended startup procedure, or crash-recovery setting. Do not rely on an assumed menu setting or a copied script without checking current OBS documentation and testing it on your installation. Decide separately how you will start the encoder after a planned restart, how you will notice that it has stopped, and how you will restart it safely. Automatic recovery can help, but repeated crashes or an expired credential still need diagnosis.
A Windows desktop environment is useful when you specifically need a Windows application or its interface, or want direct control of an encoder such as OBS. It also means you must maintain Windows, remote access and the encoder as a system. If your actual need is only to loop prerecorded videos, compare that with a service built for cloud-based 24/7 prerecorded playback; YouTube identifies Gyre as such a tool. That is a different fit from arbitrary live capture inside a Windows desktop. For another self-managed route, see the practical comparison of OBS on a spare PC versus a VPS.
Connect the encoder to a YouTube Live event
YouTube requires a verified channel with no live-streaming restrictions during the preceding 90 days. First-time activation may take up to 24 hours, according to YouTube's encoder setup help. Complete this check before the day you intend to go live; do not leave channel eligibility or activation to the final setup session.
In Live Control Room, create or select the event or stream you intend to use, then copy its server URL and stream key into the encoder's stream settings. The names of fields can vary by encoder, so use the current instructions for the software you installed. Confirm which event is selected and keep a note of the intended schedule and title so you do not accidentally send a test signal to a public event.
Treat the stream key as a password. Anyone who obtains it may be able to send video to the associated stream. Do not place it in a public screenshot, share it in a support forum, or store it in a broadly accessible document. If it is compromised, YouTube says you can reset the key in Live Control Room; then update the encoder with the replacement and test again. A reset key will not help if the old value remains saved in a machine or configuration that someone else can still access.
For additional planning around credentials and stream selection, the guide to choosing a YouTube stream key for a scheduled 24/7 playlist covers the practical distinction between a key and the event it feeds. Use the current Live Control Room display as the authority for the actual URL and key, rather than relying on an old note from a previous broadcast.
Test the stream and keep watch
Do not call the setup ready because the encoder shows a green indicator. Start with a private or otherwise controlled test where appropriate, check the Live Control Room preview, and confirm that video and audio reach the expected YouTube event. Then view the watch page on the devices your audience uses, including a mobile device. Listen for muted audio, clipping, an unexpected source, or a loop that freezes while the encoder continues sending frames.
Check bandwidth with the complete output in mind. YouTube's streaming tips recommend upload capacity with 20% headroom above the total stream bitrate. If you plan primary and backup encoders, YouTube's guidance is primary bitrate plus backup bitrate plus 20%. This is capacity guidance, not a guarantee that a particular Hetzner server, region or network route will remain stable. Include other traffic that uses the same upload path when you assess available capacity.
Run a test through the failure modes you can reasonably exercise: a planned Windows restart, an encoder restart, a short network interruption, and loss of remote administration followed by recovery. If you use a backup encoder, YouTube recommends testing failover by stopping the primary encoder or disconnecting its Ethernet and confirming that the player moves to the backup. A single machine and a single network route do not become redundant simply because a backup stream has been configured; test what viewers actually see.
Write down what you will check during operation. Useful signals include whether YouTube still receives the expected event, whether audio and video remain present, whether the loop advances, and whether you can reach Windows to investigate. Agree who will respond if an alert arrives overnight. If you do not have someone available to respond, design the content and schedule so that a short interruption can be handled without making unsupported promises to viewers.
The distinction between a content issue and a transport issue matters. If a video repeats incorrectly while the encoder is still connected, troubleshoot the media sequence and encoder scene or playlist. This OBS guide to a YouTube Live store promo loop skipping videos is relevant to that sort of playback fault, though its precise steps may not apply to every Windows build. If the stream itself has gone offline, check encoder state, host connectivity and Live Control Room before changing the playlist.
Always-on delivery is not a single archive
“24/7” describes the intended schedule, not a guarantee that the broadcast will stay connected without interruption. Windows maintenance, a server restart, an encoder failure, a network issue or a YouTube-side interruption can all break continuity. Testing and monitoring reduce the chance that a fault goes unnoticed; they do not make one machine immune to faults. Decide in advance what you will do after a drop, whether the event can be resumed, and how you will communicate a gap to viewers.
A continuous broadcast is also different from an automatically preserved recording. YouTube's encoder help says streams under 12 hours are automatically archived. That statement does not establish how YouTube will archive a single longer 24/7 broadcast, nor does it promise that one long event remains available as a single video. Check YouTube's current guidance and your event and archiving workflow before treating the live feed as a permanent copy of your programme.
If you need an archive, make a separate plan: retain the source media, decide whether you need local or other recording, and test how you will split or preserve the material over time. Do not rely on a live stream as the only copy of a devotional playlist, lesson or business announcement. For a prerecorded nature or ambience loop, the YouTube Live settings guide for a 24/7 nature video playlist can help frame the content workflow, but current YouTube behaviour should still govern your archive expectations.
The alternative to a self-managed Windows host is not automatically better; it depends on what is being broadcast. A rented Windows server makes sense when you need a Windows desktop and want to manage the encoder yourself. A cloud playback service may fit better when the job is continuous playback of prerecorded files and you do not need a Windows desktop. StreamNeo removes the need to leave your own computer running for an uploaded prerecorded video by running the YouTube broadcast after you provide the stream key, but it is YouTube-only and is not a replacement for arbitrary live capture in your Windows session.
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 Hetzner Cloud support a Windows Server installation?
The guidance described here does not settle whether a particular Windows image, installation route or licence is currently supported on Hetzner Cloud. Ask Hetzner to confirm the exact Cloud route and check licensing with Microsoft before provisioning; general custom ISO support is not proof of Windows support.
Can I use OBS on the server with my computer switched off?
If Windows and OBS are installed and configured, the encoder can run on the server rather than on your local computer. You still need to plan for maintenance, remote access, encoder restarts and monitoring, and a running process is not a guarantee of uninterrupted delivery.
Will YouTube save my entire 24/7 stream as one video?
Do not assume so. YouTube says streams under 12 hours are automatically archived, but that does not establish the archive behaviour for one longer continuous broadcast. Check current YouTube guidance and arrange a separate recording or archive workflow if you need a durable copy.
What should I do if the stream key is exposed?
Reset it in YouTube Live Control Room, then replace the value in the encoder and test the connection. Also remove the old key from places or systems where it remains accessible.