A continuous YouTube stream sends data from your encoder to YouTube for as long as it runs. On Hetzner Cloud, that outgoing traffic uses the monthly allowance for your specific server family and datacentre; the allowance is not the same thing as a promise of stable streaming.
You can estimate the traffic from your encoded bitrate and hours streamed, then compare it with Hetzner’s current allowance and overage terms. A VPS workflow can keep your own computer switched off, but you still need to configure YouTube Live, check stream health, and plan for failures at every link in the path.
What a 24/7 VPS workflow does
A VPS-based workflow runs the media source and encoder on a rented virtual machine rather than on your home computer. The source might be a looping video, an audio playlist with a still image, or a locally stored sequence of files. An encoder such as FFmpeg reads that source, converts it into a live audio-video feed and sends it to YouTube’s ingest address using the stream key shown in Live Control Room.
The data flow is straightforward: media files on the VPS go into the encoder; the encoder sends one outgoing stream to YouTube; YouTube processes and distributes the live broadcast to viewers. For the VPS traffic estimate, count the encoder’s outbound feed. Do not multiply the stream rate by your audience size: viewers receive playback from YouTube, not as separate copies sent by your VPS in this workflow.
This arrangement removes the need to leave a personal computer running at home, but it does not remove operational work. You are responsible for the VPS, source files, encoder process, network path, stream key and YouTube settings. If a file is missing, an encoder exits, the VPS is stopped, or YouTube rejects the feed, a cloud machine being switched on will not by itself fix the broadcast.
If your content is a pre-recorded playlist, decide how it should move from one file to the next before starting. A playlist that ends and stops is not a loop. The practical points in this guide to looping pre-recorded videos on YouTube Live also apply to non-children’s content: test transitions, file order and what happens when the last item finishes.
Enable live streaming and allow for first-time activation
Before configuring an encoder, sign in to the YouTube account that owns the channel and enable live streaming if it has not been enabled already. YouTube may require phone verification and may take time to activate the feature for a channel using live streaming for the first time. Do not schedule a launch on the assumption that activation will be immediate; complete the setup in advance and confirm that the account can open the live controls.
Use YouTube’s official Live Control Room to manage the broadcast. The interface can change, so follow the current YouTube prompts for activation, channel eligibility and any notices on the account. A stream key is sensitive: anyone who obtains it may be able to send a feed to your channel. Keep it out of public notes, screenshots and files shared with people who do not need it.
For a first test, use an unlisted broadcast or another visibility setting that suits your channel, and check it from a separate browser or device. This helps distinguish an encoder connection from a viewer playback issue. An unlisted-stream test before committing to a cloud loop is useful even if you are building the loop yourself on a VPS.
Create or select a stream in Live Control Room
In Live Control Room, create a stream or select an existing stream event, then inspect its stream settings. YouTube displays the ingest URL and stream key used by an encoder. Depending on the workflow and interface, YouTube may offer a default or reusable key; check that the selected key belongs to the intended channel and stream setup before copying it.
Keep the ingest URL and key together only where the encoder needs them. The URL identifies the destination; the key identifies the broadcast stream associated with the channel. They are not interchangeable. Treat both as configuration secrets, but take particular care with the key. Avoid embedding it in a public repository, a command shared in a support forum, or a recording of your terminal.
Choose the stream’s title, visibility and other settings in YouTube rather than assuming the encoder controls them. If you are using a scheduled event, confirm the event is the one the encoder should feed. A successful network connection does not necessarily mean that the correct event is live, that the intended audience can see it, or that the title and visibility are right.
There is a separate set of risks around changing keys or encoder profiles. If a saved key seems to disappear from a desktop workflow, this stream-key recovery checklist explains the kind of account and configuration checks to make. On a VPS, document where the key is stored and how to replace it without exposing it in logs.
Configure the encoder with the displayed URL and key
Install or prepare an encoder on the VPS, select the media source, then configure it to send to the displayed YouTube URL with the selected stream key. FFmpeg is one common command-line choice for a file or playlist, but the exact command depends on codecs, audio, loop behaviour and how you want the process supervised. Avoid pasting an untested command into a production session and assuming it will continue after a disconnect.
YouTube’s live encoder settings guidance gives recommended settings by resolution, frame rate and codec, and covers supported ingest protocols. For example, its 1080p60 table recommends 12 Mbps for AV1 or H.265 and 17 Mbps for H.264. Those are YouTube recommendations for the encoder output, not a statement about a Hetzner allowance, a VPS’s sustained capacity or a guaranteed result. Your content and chosen resolution may call for different settings.
The outgoing bitrate is the relevant starting point for traffic estimation. Include audio as part of the total encoded rate, and remember that the actual output may vary with encoder settings and content. A constant-bitrate estimate is convenient, but real usage can also include protocol overhead, reconnects and other server traffic. A lower bitrate sends less data, but may not provide the image or sound quality you need.
YouTube also advises leaving bandwidth headroom for reliability in its streaming tips. That recommendation concerns available upload capacity, not monthly data volume. A server can have plenty of monthly allowance yet struggle to sustain the feed; conversely, a stable connection can still run over a small allowance if the stream continues long enough.
Estimate monthly traffic before choosing a plan
For a quick decimal estimate, use: monthly GB ≈ total Mbps × streaming hours × 0.45. This comes from converting megabits to bytes and multiplying by duration. It is an arithmetic estimate, not a published consumption figure. Use the combined video and audio bitrate, and add room for overhead, restarts and unrelated egress.
A 30-day month has 720 hours. At a constant 10 Mbps, the estimate is 10 × 720 × 0.45, or about 3,240 GB (3.24 decimal TB). This assumes the feed runs for the entire month at that rate. It is not a forecast for a variable-bitrate setup or a promise about the bill.
The same method puts the YouTube 1080p60 recommendations above into context: 12 Mbps comes to roughly 3.89 TB over 720 hours, while 17 Mbps comes to roughly 5.51 TB. Those estimates exclude overhead and other outgoing traffic. They show why the codec and bitrate matter for a continuous stream, but do not tell you which Hetzner product is suitable.
| Continuous encoded rate | Approximate traffic over 30 days | How to read the estimate |
|---|---|---|
| 1 Mbps | 324 GB | A low-rate reference point, before overhead |
| 10 Mbps | 3,240 GB (3.24 TB) | A sustained rate, not a plan recommendation |
| 12 Mbps | 3,888 GB (3.89 TB) | Approximation for the cited 1080p60 AV1/H.265 setting |
| 17 Mbps | 5,508 GB (5.51 TB) | Approximation for the cited 1080p60 H.264 setting |
The arithmetic is approximate, and decimal TB here means 1,000 GB. Compare your estimate with the included egress allowance for the exact server family and region, then check usage during the month. Do not select a plan from a bitrate example alone: also consider sustained throughput, monitoring, other workloads and what you are willing to pay if usage exceeds the included amount.
Understand what Hetzner counts and bills
Hetzner’s Cloud traffic documentation says allowances vary by product family and location. Its listed EU CX, CPX and CAX Cloud allowances are 20 TB each, while US and Singapore figures vary by plan; CCX allowances also vary by product and location. Confirm the current allowance for the particular server and datacentre you intend to use. Do not assume that every Cloud server includes 20 TB.
The billing distinction is direction of traffic. Hetzner counts outgoing traffic towards the allowance; incoming and internal traffic are free under the stated Cloud billing rules. Some cross-zone Cloud traffic over public IPs can count as outgoing, so traffic between Cloud instances is not automatically free. For a one-way YouTube ingest stream, the encoded feed leaving your VPS is the main usage to estimate.
Hetzner measures usage by calendar month. Its documentation describes excess use as billable in 100 MB increments, with partial increments rounded up. The Cloud billing FAQ also explains that notifications at 75% and 100% are alerts rather than controls that stop or cap traffic. They can help you notice use, but should not be treated as a spending limit.
The overage amount depends on the applicable terms and location. Check the live Hetzner information for the server and datacentre before relying on a cost estimate; do not infer an overage price from the allowance or from another region. If an unexpected bill would be a problem, use a lower planned bitrate, monitor usage during the month and decide in advance what action you will take near the allowance.
Start the source, verify health and prepare recovery
Start the media source and encoder, then wait for Live Control Room to show that YouTube is receiving the feed. Check the stream-health indicators and preview, and confirm that sound and picture are present. Also verify the broadcast from a viewer’s perspective: an ingest connection can appear healthy while the wrong file, wrong event, muted audio or unintended visibility setting causes a practical failure.
Run a test long enough to exercise the transitions that matter. For a single file, see what happens at the end. For a playlist, observe at least one change between items. For an audio channel with a still image, confirm both remain present. These checks catch source and configuration errors that a short connection test may not reveal.
Recovery is a separate part of the workflow. An encoder can exit, a process can lose its network connection, the VPS can restart, or YouTube can stop receiving a valid feed. Use process supervision or a restart policy appropriate to your setup, and test it deliberately. A restart should restore the source and reconnect the encoder, not repeatedly launch a broken command without making the cause visible.
Keep useful logs and a simple runbook: where the files are, how the encoder starts, where its key is stored, how to inspect its status and how to stop it safely. Do not put the stream key in logs that are broadly accessible. A carefully configured retry can help after a brief interruption; this FFmpeg recovery guide for a YouTube RTMP drop covers reconnect behaviour, but reconnecting cannot repair a missing source or a revoked key.
A VPS workflow also shifts the burden of watching for trouble. If you cannot check it continuously, arrange useful alerts and decide who will respond. StreamNeo addresses the specific problem of leaving your own computer running by taking an uploaded video and keeping its YouTube broadcast running without that computer; it does not remove the need to choose suitable content, check YouTube status or understand the limits of the full path.
Understand server availability without overpromising
Availability is a chain: your source must be readable, the encoder must run, the VPS must be available, the network path must reach YouTube, YouTube must accept the feed, and the stream must be configured for viewers. A provider’s server availability commitment or effort can apply to its service component, not automatically to every other component in this chain. Do not read a monthly availability figure as a guarantee that your YouTube channel will stream continuously.
Traffic allowance and availability are also different questions. An allowance concerns the quantity of outgoing data that is included or billed. It does not promise a certain upload rate, low latency, uninterrupted connectivity or healthy ingest. YouTube’s advice to test, leave capacity headroom and monitor stream health addresses delivery quality, not the VPS provider’s monthly quota.
Before choosing a setup, compare the location-specific included egress, the current overage terms, expected sustained bitrate, and your ability to monitor and recover the encoder. Check Hetzner’s current documentation and account usage rather than relying on a remembered plan table. For a station that cannot tolerate an unnoticed interruption, treat alerting and human response as part of the operating plan, not optional extras.
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
How much traffic does Hetzner Cloud include?
It depends on the Cloud product family and datacentre region. Hetzner lists 20 TB for EU CX, CPX and CAX Cloud servers, but US and Singapore CX/CPX figures vary by plan and CCX allowances also vary. Check the current entry for your exact product and location before estimating a continuous stream.
Does Hetzner count outgoing traffic?
Yes. Hetzner’s Cloud billing information counts outgoing traffic towards the allowance, while incoming and internal traffic are free under the stated rules. For a VPS that sends an encoder feed to YouTube, estimate the feed leaving the server and include other egress separately.
Will a 10 Mbps stream exceed the allowance?
A continuous 10 Mbps stream is approximately 3.24 decimal TB over a 30-day month, before overhead and other traffic. Whether that exceeds the allowance depends on the specific plan and region, so compare the estimate with the current product details and monitor usage.
Does enough monthly traffic mean the stream will stay live?
No. Monthly egress is a volume limit or billing threshold, while a live broadcast also depends on the source, encoder, server, network route, YouTube ingest and recovery process. Test the complete workflow and monitor stream health; no traffic allowance guarantees an uninterrupted broadcast.