A reliable monthly budget for a 24/7 YouTube stream on Hetzner Cloud starts with the current monthly price cap for your chosen server, then adds any separately billed resources, applicable traffic overage and tax. There is no dependable single total without knowing the server, location, project currency, stream settings and current tariff.
For a full billing period, treat the server’s monthly cap as the compute figure rather than multiplying an hourly rate by an assumed number of hours. Then verify each other line in the live quote; do not carry an old price table forward as if it were current.
What belongs in a 24/7 stream budget
A stream running all day and night uses the server for the full billing period. That affects which compute charge is relevant, but “24/7” is not a special billing multiplier applied on top of the monthly cap. Hetzner’s billing rules charge hourly while a server exists, rounded up to full hours, up to the applicable monthly amount. The lower of the hourly charges and monthly cap applies.
A useful planning formula is:
Monthly estimate = current server monthly cap + separately billed resources + applicable traffic overage + tax.
The first term is the server itself. The next terms depend on what you add to the project and how the stream is configured. For example, a public IP address, storage volume or backup may have its own price. Outbound data may be covered up to an applicable allowance and charged beyond it; the allowance and any overage rate need checking for the selected server and location. Tax depends on the billing circumstances and the price display you are using.
Do not confuse a cloud bill with the cost of producing the programme. If you use paid music, licensed footage, a separate monitoring service or a second backup channel, those can be relevant to the overall operating budget but are not automatically Hetzner Cloud line items. Keep the server estimate focused on what Hetzner bills, then track production and YouTube-related costs separately.
A useful first distinction is whether the VM is encoding the video or merely relaying an already encoded file stream. Software encoding can place substantially different demands on CPU than sending a prepared stream, so you should not choose a server from the duration alone. Decide how the media is prepared, what quality you intend to send, and whether local buffering or recording is needed before comparing plans.
Choose server type and location
Hetzner’s current price depends on server type, location and project currency. Compare candidate servers within the same currency and region wherever possible. Otherwise, a difference in the displayed total might come from exchange or location rather than the server’s underlying fit for your workload.
For each candidate, record the current monthly cap shown in your account or quote. Also note whether the CPU is shared or dedicated, the RAM and disk available, and whether your software uses CPU for encoding. A playlist loop that sends a pre-encoded file is not the same workload as converting live video into a new resolution and frame rate. The research available for this article does not establish that any particular small server will encode a specified quality reliably, so test the actual configuration rather than treating a plan label as a performance guarantee.
Location is also part of the decision, not just a price selector. Consider the path from your server to YouTube ingest and the needs of your audience, but do not assume that a nearby data centre by itself guarantees a stable broadcast. A stream has more dependencies than the VM: source files, encoder process, network route, reconnect behaviour and YouTube ingest all matter.
If you are deciding between one channel and two, first outline whether the streams share the same media and encoding work. The practical questions in running two YouTube live streams from one FFmpeg server are useful for identifying shared versus duplicated workloads, but do not assume that a second stream will cost nothing just because it reuses a server.
Account for traffic and included amounts
The encoder sends data from the server to YouTube continuously. Video bitrate is therefore a major driver of outbound data volume. The higher the selected bitrate and the longer the stream runs, the more data the connection carries. This is why the quality setting belongs in a cost estimate alongside the server choice.
YouTube’s live encoder guidance asks you to specify resolution, frame rate and bitrate. Use its current table to select the target bitrate for the quality you actually intend to broadcast, and note that YouTube recommends RTMPS for Live. See [YouTube’s live encoder settings] (https://support.google.com/youtube/answer/2853702) for the current guidance. The precise traffic volume also depends on protocol overhead and the actual schedule, so a bitrate-based calculation is an estimate rather than a Hetzner invoice total.
Next, check the current included outbound traffic for your selected server and location, then find the applicable rate for any excess. Do not assume that all traffic is included, or that a particular allowance or overage price applies to every location or server family. The research for this article did not establish a complete current allowance and overage amount for a specific configuration, so a numeric transfer charge cannot be responsibly supplied here.
For a budget worksheet, write down the stream resolution, frame rate, target bitrate, expected hours on air, and the region in which the VM will run. Compare the resulting transfer estimate with the allowance stated in the live quote. If the stream changes quality during the month, or if you upload media and backups from the same machine, those uses can also affect the amount of data moved. Keep those assumptions visible instead of presenting one unexplained traffic number.
A channel that plays a prepared playlist may have a simpler traffic profile than one that repeatedly uploads or processes large source files, but both send the live output to YouTube. If your programme is a sequence of clips, setting up an automatic video playlist for YouTube Live with FFmpeg can help you think through the playback workflow; the cost calculation still needs your chosen bitrate and the current traffic terms.
Add other billable resources and taxes
The server price is not necessarily the whole account total. Check whether your design adds a separately priced public IPv4 address, storage volume, snapshot or backup. Record each resource, its billing basis and the current amount displayed for your project. A resource that looks small by itself can still matter over a full month, especially if you keep it attached after you stop using a stream.
A server continues to incur charges while its server object exists, even when powered off. Hetzner states in its billing FAQ, “We will bill you for each cloud server until you choose to delete them.” If you are testing a setup and want server billing to end, turning the VM off is not equivalent to deleting it. Before deletion, preserve any files or configuration you need; removing the server is an operational action, not a pause button.
The resource structure is a reason to check the live catalogue rather than use a figure remembered from an old tutorial. A historical Hetzner overview page listed Primary IPv4 separately and quoted a monthly amount excluding VAT, but that page dates from 2022 and is not a current price quote. Use it only as an illustration of why a resource can be separate from server compute, not as a price for a budget today.
Tax must be handled as its own line in your working. First determine whether the displayed price includes tax for your billing context; then use the tax basis shown in the account or invoice. Do not assume taxes are always included or always added at one universal rate. Your country, customer details and billing treatment can affect what applies, so check the current official billing information and the final account quote.
Check current Hetzner pricing
Before settling on a monthly number, open the current account pricing or the official Cloud pricing information and select the actual server type, location and project currency. Hetzner’s pricing API documentation explains that server prices vary by location and project currency, and provides a live pricing endpoint. See the Hetzner Cloud API pricing reference and verify the resulting quote for the project you will use.
This is especially important because Hetzner announced updated Cloud prices for new orders and server rescales starting 15 June 2026. The notice says existing servers are not affected unless they are rescaled. A price printed before that change cannot be treated as a current price for a new order. Check the relevant current listing rather than infer a new price from an old plan table.
When you check, save the date, project currency, location, server type and any selected resources with the quote. Those details make the number reproducible. If you are comparing more than one candidate, capture the same fields for each one and avoid mixing an old server price in euros with a current resource price in another currency.
A practical comparison should include the monthly compute cap, CPU model or allocation, RAM, disk, outbound allowance, excess traffic terms, IP requirement and any backup or storage choice. Compare like with like. If the quote changes after you select a location or resource, update the worksheet instead of retaining the earlier subtotal.
Estimate your configured monthly total
Use a short worksheet and fill it only with values from the current project configuration. The blanks below are intentional: without a chosen plan and location, a numeric total would create false precision.
| Budget line | What to enter | Where to verify |
|---|---|---|
| Server compute | Current monthly cap for the selected server | Current Hetzner quote or pricing API |
| Other resources | Current price for IP, volumes, backups or other selected items | Resource selector or current price list |
| Traffic overage | Applicable charge only if projected output exceeds the included amount | Current terms for the selected location and server |
| Tax | Tax treatment for your account and billing context | Account quote and invoice information |
| Estimated total | Sum of the applicable lines above | Your dated worksheet |
For a full-month stream, use the monthly cap for compute. For a short test or a partial-month deployment, hourly billing may be relevant, but remember that Hetzner rounds hourly usage up to full hours and applies the lower-of-hourly-or-monthly-cap rule. Do not estimate a full month by multiplying an hourly figure by a generic 720 hours when the monthly cap governs the charge.
Here is how to keep the estimate honest. Suppose you plan to run a pre-encoded 1080p programme continuously. Record the exact frame rate and target bitrate taken from YouTube’s current encoder guidance; select the Hetzner region and server you intend to order; read the matching monthly cap and traffic terms; and list any IP, storage or backup resource. Add only a traffic overage if the calculated transfer exceeds the stated included amount, then apply the tax treatment shown for your account. This is a method, not a quoted price or a claim that a particular server can sustain that format.
If the setup software-encodes the stream instead, keep the same budget structure but reassess the server based on a measured workload. A trial run can show whether CPU capacity is adequate and whether the stream restarts correctly after a process failure. No benchmark was performed for this article, so a plan recommendation would be guesswork. If you need help deciding between a local machine and a VM, the Mac mini versus cloud server cost comparison for a nonstop playlist helps identify which operating costs belong on which side of the comparison.
Once your worksheet is complete, retain the quote date and revisit it when you change region, server type, stream quality or attached resources. The monthly total is a property of that configuration, not a universal “cost of 24/7 streaming”.
Why old price tables can mislead
Old tutorials are often useful for explaining how to install an encoder or create a server, but their cost tables age differently. A price can change while the server name remains familiar. A separate resource can also be repriced, and the amount included for traffic may depend on a choice the old article never states. A table without a date, location and currency is not enough to reproduce the bill.
The June 2026 pricing change makes that caution concrete: updated prices apply to new orders and rescales from 15 June 2026, while existing servers are described separately in Hetzner’s notice. That distinction means a new customer should not copy the historic price paid by someone who has not rescaled an older server. Neither should an existing customer assume that every future change applies in exactly the same way; check the notice and the current account details.
A provider’s availability statement also needs its own context. Hetzner’s Cloud and vServer service agreement describes a 99.9% monthly availability effort for an individual Cloud Server, subject to its terms and definitions. That is not a guarantee that a YouTube broadcast will be uninterrupted. Your encoder can stop, media can be unavailable, a route can fail, or YouTube ingest can disconnect even if the server itself is available. Review the Hetzner Cloud service agreement and design monitoring and reconnect behaviour as separate parts of operating the channel.
For a nightly devotional or study stream, the practical test is not only whether the VM stayed up. Check that playback resumed after a reboot, the encoder reconnected after a network interruption, and a notification reaches someone who can act. A server budget should make those choices visible, even though the monitoring and recovery design may not appear as a single line on the server quote.
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
Is 24/7 billing simply the hourly rate multiplied by the month?
No. Hetzner bills hourly usage rounded up to full hours, up to the applicable monthly cap, and charges whichever is lower. A full-month stream should generally be budgeted using the current cap for its selected server, not an assumed 720-hour multiplication.
Does turning off the server stop the charge?
No. The server is billed while the server object exists, including when it is powered off. Deleting the server ends that server charge, so save anything you need before removing it.
Are traffic and taxes included in the server price?
Do not assume either way. Check the current traffic allowance and any overage terms for the selected server and location, then check whether the quote includes tax for your billing context. The final total depends on those specifics.
Can I use an old Hetzner price table to estimate today’s bill?
Not for a current new order without checking it against the live quote. Updated prices for new orders and rescales apply from 15 June 2026, according to Hetzner’s notice. Use the current account pricing or API for your project currency, location and selected resources.