If you are choosing between AWS Lightsail and Hetzner for a server-based YouTube playlist stream, compare the exact server region, workload and monthly transfer your stream needs. Neither provider is a universal winner, and a plan’s listed resources or allowance do not ensure a healthy broadcast.
The key distinction is whether the server sends an already encoded feed or also decodes and re-encodes video. Then compare complete regional costs, including public IPv4 where relevant, and make a test stream part of the decision rather than relying on a plan description.
Why there is no universal winner
“Which is cheaper?” is not answerable without a workload and a location. A low-bitrate audio-led stream sent from a server near its audience has different transfer and routing requirements from a 1080p video loop aimed at viewers on another continent. Prices and allowances also vary by region and product class.
Lightsail presents virtual servers as monthly bundles that combine resources and transfer. Hetzner Cloud Server prices vary by resource class and location, and Hetzner documents public IPv4 separately from the Cloud Server price. Those billing differences matter, but they do not settle which will cost less for your channel. Compare the specific offers available in the same region, with taxes and any separate network costs included.
There is also an operational difference between a server that forwards a ready-to-send file and one that performs video processing. A transfer allowance cannot tell you whether the CPU has enough headroom to encode. A vCPU count on its own does not establish performance for a sustained encoding workload either. Test the actual task on the proposed server before committing.
Finally, the VPS is only one part of a live path. Your playlist process, encoder settings, network route, connection to YouTube’s ingest, stream key and recovery behaviour all matter. YouTube advises creators to test before a stream and monitor stream health during it. A provider’s plan details cannot establish that this whole chain will stay healthy.
Define the workload and audience before comparing plans
Write down what the server will do. If it loops a file that is already encoded for YouTube, the job may be mostly to read, package and send the stream. If it transcodes, resizes, adds graphics or combines media in real time, the server also has to process video. Fetching media remotely rather than reading it from local storage changes network use as well. These are different workloads, so do not shop by a generic “playlist stream” label.
Next, choose the stream settings and audience region you are planning for. YouTube’s encoder guidance lists 14 Mbps as its recommended H.264 bitrate for 1080p30. That is a useful planning example, not a requirement that every channel should select. A lower resolution or bitrate may better suit a devotional audio loop, local news bulletin or study station. Check the 24/7 bitrate comparison before deciding how much picture detail your channel needs.
Audience location influences where a server may be useful, but proximity alone is not a guarantee of a good route. List the country or countries you primarily serve, then check which regions each provider offers for the server class you need. Hetzner documents Cloud Server locations in Europe, the USA and Singapore. Lightsail’s available regions and plan details vary; check the current selection in AWS’s Lightsail pricing information.
If most of your viewers are in India, for example, a Singapore or India-region server might be worth investigating, but the best choice depends on actual availability and the path from the server to YouTube ingest as well as the audience. Run a test from the candidate region. Watch for dropped frames and warnings, and test audio and movement representative of the real stream. A static test card alone may not exercise the same encoding path as a playlist with music, motion or changing scenes.
For a practical outline of how a file-loop broadcast is assembled, see a YouTube radio station workflow with RadioDJ and OBS. That can help you identify which parts belong on the server, even if you use a different player or encoder.
Compare complete regional server costs
Compare the same job in the same region, not a headline price from one provider against a differently sized or located server from the other. Start with the resource class you need, then account for storage, transfer, public IP, taxes and any excess-traffic terms. If you are using a monthly plan, check whether the stated cost assumes Linux/Unix, public IPv4 or another configuration.
AWS’s current Lightsail pricing page lists a Linux/Unix public-IPv4 entry bundle at $5 per month, with 0.5 GB memory, 2 vCPUs, 20 GB SSD and 1 TB transfer, as listed on AWS’s site in September 2026. This is an example of the bundled-plan model, not an encoding recommendation or a claim that the entry bundle suits every playlist. The region can also affect the transfer allowance, so do not assume that the same allowance applies everywhere.
Hetzner’s Cloud Server overview says prices depend on resource class and location, and excludes public IP addresses from the Cloud Server price. Its documentation lists Primary IPv4 at €0.50 per month excluding VAT, as listed on Hetzner’s site in September 2026; confirm that this applies to the product and region you select. The published amount is an item to check in a cost comparison, not a complete server quote.
A useful comparison worksheet has one column for each provider and a row for each requirement: region, CPU class, memory, disk, IPv4, included transfer, excess traffic, tax and any paid backup or volume you choose. Use the smallest configuration you can test for a relay workload, but allow for headroom if the server also processes video. Do not convert an attractive starting figure into an expected monthly bill until you have checked all of the rows.
| Cost or capacity item | AWS Lightsail | Hetzner Cloud Server | What to verify |
|---|---|---|---|
| Billing structure | Monthly virtual-server bundles combine resources and transfer | Price varies with resource class and location | Compare equivalent region and usable capacity |
| Public IPv4 | The cited entry bundle is for a public-IPv4 configuration | Public IP is excluded from the Cloud Server price in the overview | Include the address cost and confirm the selected product terms |
| Transfer | Allowance is part of the bundle; excess outbound may be chargeable | Allowances depend on product and location | Check the exact plan, region and overage terms |
| Compute | Bundle includes specified resources | Shared and dedicated resource classes are available | Test relay or encoding load rather than infer performance from vCPU count |
| Tax and extras | Check current regional pricing and applicable taxes | Check VAT and selected add-ons | Compare the amount you will actually pay |
This is a framework, not a quote. The documented entry bundle and IP figures above are dated references; verify current terms and your exact configuration before using them in a budget.
Check whether included outbound transfer is enough
For a continuous stream, transfer can be a substantial part of the comparison. A simple estimate for video payload is:
Decimal TB ≈ bitrate in Mbps × streamed seconds ÷ 8,000,000.
At 14 Mbps for 30 days, the calculation is 14 × 2,592,000 ÷ 8,000,000, or about 4.54 decimal TB of video payload. This is arithmetic based on a continuous bitrate and a 30-day month, not a published YouTube usage figure. It excludes protocol overhead and any other traffic, so leave room rather than planning exactly to the result. At another bitrate, the estimate scales in direct proportion: halving the bitrate halves the payload under the same assumptions.
This helps explain why transfer allowances need careful attention. The cited Lightsail entry bundle includes 1 TB, while a continuous 14 Mbps feed’s calculated payload is already more than that. AWS says both inbound and outbound traffic count against Lightsail’s transfer allowance; its FAQ says excess outbound traffic may be charged. The details of excess billing and the applicable allowance should be checked for the selected region and plan.
AWS also says the Lightsail transfer allowance is half the ordinary allowance in Mumbai, Sydney, Jakarta, Malaysia, Hong Kong and São Paulo. If one of those regions is under consideration, use the regional figure shown for the plan rather than carrying over an allowance seen for a different AWS region. Confirm the current terms before deciding whether a continuous stream fits.
Hetzner lists transfer allowances by product and location. Its traffic documentation reports 20 TB for EU CX Cloud Servers, as listed on Hetzner’s site in September 2026; check the exact plan and location, along with the current overage terms, before relying on that figure. An allowance shown for EU CX does not establish what a different resource class or region includes.
Estimate the server’s actual outbound feed first, then compare it with the exact allowance and terms for each candidate. Inbound use may matter too: for example, a server fetching a remote file can incur traffic separate from the broadcast output. Include monitoring, software downloads, updates and other workloads if they share the machine. The guide to reducing data use for an OBS 24/7 stream in India can help you think through the effect of bitrate and configuration on a continuous broadcast.
Understand Lightsail’s bundle and AWS integration
Lightsail’s main billing distinction is that compute, storage and a transfer allowance are packaged into a monthly virtual-server plan. That makes it straightforward to see what resources are included at a glance. It also means you should check the individual plan and region carefully: a bundle’s transfer allowance is not necessarily the same across regions, and usage beyond it can affect cost.
Lightsail may be convenient if you already work in AWS or want its integration with other AWS services. AWS describes it as suited to getting started with cloud applications, while its broader catalogue offers more configurable infrastructure. If your stream needs a particular network arrangement, a specialised video workload or consistently high CPU performance, compare Lightsail with other AWS compute products rather than assuming a Lightsail bundle is the right fit.
AWS’s Lightsail instance FAQ specifically recommends Amazon EC2 for highly configurable environments and instances with consistently high CPU performance, including applications such as video encoding. That is relevant when your playlist server performs sustained encoding, not a reason to move a simple relay to a larger machine without measuring it. If you need that degree of CPU control, compare the actual configuration and administration requirements as well as price.
A bundle does not remove the need to choose sensible settings or check the stream. Record the plan’s resources and regional transfer allowance, test your process, and review usage after the stream has been running. If you are evaluating cloud options beyond these two, the Oracle Cloud and Google Cloud comparison for 24/7 livestreams offers another framework, but the same workload-first approach applies.
Account for Hetzner resource class, location and IPv4
Hetzner’s Cloud Server catalogue distinguishes resource classes, including shared and dedicated resources. That lets you compare different capacity and resource arrangements, but a published CPU allocation is not a benchmark for your playlist process. A relay and a software encoder can behave very differently. Try the exact file, settings and duration you intend to use, then look for sustained CPU pressure, dropped frames and process restarts.
Location affects both what is available and what is included. Hetzner documents locations in Europe, the USA and Singapore; compare the specific candidate region with the audience and the YouTube ingest route. A lower listed server price in a distant region does not by itself show that it is the right choice for a stream serving India or another specific audience. Measure a test route where possible, and inspect YouTube’s own stream-health messages.
Keep public IPv4 in the price comparison. Hetzner’s Cloud Server overview excludes public IP addresses, and its documentation lists a Primary IPv4 charge separately. Check whether your selected setup needs that address, the current charge and any applicable tax. Do not treat a server headline as the complete bill when a needed component is listed separately.
The same caution applies to transfer. The allowance reported for a particular EU product is not a general Hetzner allowance. Open the traffic page for the exact product and location you intend to use, then read the relevant terms. If you select a plan with enough nominal transfer, that still says nothing by itself about your encoder’s stability or the availability of the full broadcast path.
Decide how much administration you will take on
With either provider, a server-based stream makes you responsible for the software and its ongoing operation. You need to configure the player or playlist loop, encoder, firewall and YouTube connection; protect the stream key; apply updates; and decide how to monitor and recover from a failure. The provider supplies a server product, not a completed, tested YouTube channel.
A playlist process can be configured to restart after it exits, but restarting a process does not prove that YouTube is receiving a healthy feed. The player might reopen a file while the encoder remains stalled, or the encoder might reconnect with unsuitable output settings. Define what you will watch: process status, outbound connection, YouTube’s stream-health indicators and the content itself. Rehearse a failure and confirm what you need to do when the automatic recovery you configured is not enough.
YouTube’s live encoder settings guidance recommends RTMPS for ingest, constant bitrate (CBR), a two-second keyframe interval and no more than four seconds between keyframes. Treat these as YouTube’s encoder guidance and check its current page when you configure the stream. A stream key is a credential: keep it out of public scripts, logs, screenshots and shared notes. YouTube also advises test runs that include representative audio and movement, and monitoring stream health during the event.
For a small business or community channel, the important administration question may be less “which console has more features?” and more “who will notice and repair the stream overnight?” Lightsail’s bundled presentation or Hetzner’s available server classes may suit different preferences, but neither choice answers that staffing question. If you do not want a computer you manage to stay on and recover the broadcast, StreamNeo addresses that specific burden by running an uploaded video as a YouTube live stream while your own computer is off. It is YouTube-only, so it does not replace a general-purpose VPS when you need custom software or processing beyond a file-based stream.
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 Lightsail or Hetzner cheaper for a 24/7 YouTube stream?
There is no reliable answer without a region, server class, stream bitrate and transfer estimate. Compare the full monthly cost for equivalent requirements, including applicable tax, public IPv4, transfer and any excess charges. Check the current product terms rather than relying on a starting price alone.
How much transfer does a 24/7 stream use?
Use the stream bitrate and duration to estimate payload: bitrate in Mbps multiplied by streamed seconds, divided by 8,000,000, gives decimal TB. For example, 14 Mbps running continuously for 30 days comes to about 4.54 decimal TB before overhead. This is an estimate, so allow for protocol overhead and other server traffic.
Can a small VPS encode a YouTube playlist continuously?
That depends on the input, output settings and the selected server’s sustained CPU performance. A server relaying an already encoded feed has a different job from one that transcodes or adds graphics. Test the actual workload; AWS points readers to EC2 for highly configurable instances with consistently high CPU performance for video encoding.
Does a VPS plan guarantee an uninterrupted live stream?
No. The broadcast also depends on your player, encoder, settings, network route, YouTube ingest and recovery process. Test the whole path and monitor YouTube’s stream-health messages; a server plan alone cannot confirm that every part is working.