Hetzner can be genuinely inexpensive for the right workload, but the advertised monthly price is not your monthly bill. Your real total depends on three things: which product line you choose, which add-ons you attach, and how much traffic you actually push. Get those wrong and a €5.99 server can cost noticeably more, especially outside Europe.
The Short Answer: When Hetzner Is Cheap and When It Is Not
Hetzner's cheapest cloud plans start at €5.99 per month excluding VAT for a CX23 with 2 vCPU, 4 GB RAM and 40 GB NVMe storage. That is aggressive pricing for the specification. Hetzner Cloud bills hourly up to a monthly price cap, so a server's bill never exceeds its monthly cap. If you delete a server before the end of the billing month, Hetzner bills only the hourly rate for hours used.
The catch sits around that low headline number. Hetzner lists prices excluding VAT, and a primary IPv4 address is a separate charge rather than part of the plan price. Traffic allowances are generous in EU locations but much smaller elsewhere. Hetzner has no free tier, so every running resource costs something.
This makes Hetzner a strong fit when your workload is small to medium, runs on ARM or commodity x86 hardware, sits in an EU location, and you are comfortable managing the server yourself. It is a weaker fit if you need high outbound traffic from Singapore, require dedicated vCPU performance, or want managed support wrapped into the price.
What the Advertised Price Actually Covers
The headline monthly figure on Hetzner's cloud pages is the instance price: CPU, RAM, local NVMe storage and the included traffic allowance. It is a cap on the hourly billing for that resource, not an all-in quote.
Two exclusions matter more than others:
- VAT. Every listed price is exclusive of VAT, and your local tax treatment determines what you actually pay.
- The IPv4 address. A primary public IPv4 is charged separately from the server plan. Hetzner's third-party price trackers reference different figures for this charge, so check the IPv4 pricing documentation directly rather than relying on a remembered number.
Backups, snapshots and volumes are also billed on top. Third-party pricing calculators describe backup pricing as a percentage of instance cost and snapshot and volume pricing as per-gigabyte metered charges. Those rates are not confirmed on Hetzner's own plan pages in the material available, so treat any precise percentage you see quoted elsewhere as unverified. The structural point is reliable: if you enable backups or retain snapshots, your bill rises above the plan price.
Cloud Plans, Dedicated Servers and How the Pricing Structures Differ
Hetzner's server products split into Cloud and dedicated servers, and the pricing logic behind each is different.
Cloud Plans
Hetzner Cloud offers four instance families: CX cost-optimized, CAX ARM-based, CPX regular performance and CCX dedicated vCPU. The families sit at different price points for broadly comparable specifications, and the gap between them is the main decision you will make.
Representative cost-optimized and ARM prices, all excluding VAT, are shown below.
| Plan | Family | vCPU | RAM | NVMe | Price per month |
|---|---|---|---|---|---|
| CX23 | Cost-optimized | 2 | 4 GB | 40 GB | €5.99 |
| CAX11 | ARM | 2 | 4 GB | 40 GB | €6.49 |
| CX33 | Cost-optimized | 4 | 8 GB | 80 GB | €8.99 |
| CAX21 | ARM | 4 | 8 GB | 80 GB | €10.99 |
| CX43 | Cost-optimized | 8 | 16 GB | 160 GB | €16.49 |
Two things stand out. First, the ARM CAX11 costs slightly more than the x86 CX23 at identical specifications, so you are not paying extra for ARM, but you are not getting a discount for it either. Second, going from 2 vCPU to 4 roughly doubles the specification for about 50 percent more money, which is why the mid-tier plans tend to be the value sweet spot for small production apps.
Cost-optimized plans are positioned for test and development environments, smaller projects, private blogs and low to medium CPU usage. That positioning matters: Hetzner states that these plans use older hardware generations and that this limits the number of available servers. A cost-optimized plan is not simply a cheap version of the same hardware. Availability can be constrained, and the hardware generation is behind the regular performance line.
CPX and CCX plans sit above the cost-optimized tiers for workloads that need regular performance or dedicated vCPU. Exact figures for those families were not captured in the material here, so check Hetzner's price page rather than assuming the step-up cost.
Dedicated Servers
Dedicated servers are a separate portfolio with their own price logic. Hetzner standardized its offering around server types carrying the designations -1, -2 and -3, plus a limited -1-Ltd type. The press release describing this change refers to a significant reduction in one-time setup fees for most dedicated servers.
Individual dedicated server list prices are not included here because a complete, current price table was not available. Use Hetzner's dedicated server pages for current figures. The structural point is that dedicated hardware carries setup fees, which cloud plans generally do not.
The Server Auction is a third route. It was not affected by the June 2026 price adjustment, and it remains a qualitative option rather than a predictable one, since auction pricing depends on what hardware is available.
The Costs Outside the Headline Price
The line item most likely to surprise you is traffic overage, and the size of the surprise depends heavily on region.
Traffic Allowances by Region
Cloud servers in Hetzner's EU locations include at least 20 TB of traffic. That is enough for most small and mid-sized sites to stay inside the allowance indefinitely.
Outside the EU the picture changes. An independent analysis reports allowances of 20 TB in the EU, 1 TB in the US and 0.5 TB in Singapore. Those figures come from third-party reporting rather than Hetzner's own plan pages, so verify them against Hetzner's location-specific pricing before committing to a bandwidth-heavy deployment in those regions.
Traffic Overage Rates
Overage pricing shows the same regional split. The same independent analysis reports €1.00 per TB in the EU and US but €7.40 per TB in Singapore.
There is a documented inconsistency worth flagging. Hetzner's own cost-optimized page states a charge of €1.00 per additional TB at EU-Central locations, but labels the unit as per hour rather than per TB. That is either a typographical error on the page or a different billing structure than the per-TB framing used elsewhere. Either way, a €1.00 per hour reading would be a very different number from €1.00 per TB, roughly 730 times larger over a month. Check the current price page and, if you expect overage, confirm the unit with Hetzner support before you rely on a budget.
For a Singapore deployment, the combination of a 0.5 TB allowance and a €7.40 per TB overage rate means outbound-heavy workloads can exceed the server price quickly. For an EU deployment pushing a few terabytes, overage is unlikely to matter at all.
IPv4, Backups, Snapshots and Volumes
Each of these is billed separately from the plan:
- Primary IPv4: a recurring charge per address, separate from the plan price.
- Backups: described by third-party calculators as a percentage of the instance price. Confirm the current rate directly.
- Snapshots and volumes: metered per gigabyte, with rates published in third-party calculators but not confirmed here at the exact figure.
If you run a small project with one IPv4, no backups and no volumes, your bill is close to the plan price plus VAT. If you run backups on every instance and retain snapshots, budget meaningfully above the headline figure.
Billing Mechanics: Hourly Rates, Monthly Caps and Partial Months
Hetzner Cloud bills hourly and rounds every partial hour up to a full hour. A server running for 20 minutes is billed for one hour. In practice this rarely matters for persistent servers, but it does add up if you are creating and destroying test instances repeatedly.
Four billing rules shape what you actually pay:
- The cap applies per resource, per month. A single server will not exceed its monthly price cap.
- Deletion changes the calculation. If you delete a server mid-month, the monthly cap does not apply and you pay the hourly rate for hours used.
- Stopping is not deleting. Stopping a Cloud resource does not stop billing. Only deletion does. A "stopped" server still costs money.
- Invoices arrive in arrears. Hetzner Cloud invoices are issued for the previous calendar month.
The practical implication of rule three is the one that catches people. If you spin up a test server, shut it down and forget it, you keep paying. Deleting it stops the charge and applies the hourly rate.
The June 2026 Price Adjustment and What It Did Not Touch
Hetzner announced a price adjustment for new orders effective 15 June 2026 affecting all dedicated servers and cloud plans at all locations. Independent reporting puts the scale of the cloud increase at roughly 30 to 40 percent on the CX and CAX lines, with CPX and CCX rising more sharply. That figure comes from a third-party calculator rather than Hetzner directly, so treat it as indicative rather than exact.
The grandfathering rule is the important detail. The adjustment applies exclusively to new orders and rescales of existing servers, so existing contracts keep their original terms. If you are already running a Hetzner server, your price does not change. If you resize an existing server, the new rates apply to it.
The adjustment did not affect web hosting, managed servers, Server Auction servers, IPs, storage products, load balancers, volumes, snapshots or object storage. Anyone budgeting for those products should not assume the June 2026 increase applies to them.
Taken together, this means prices are not static. Figures quoted in any article, including this one, should be checked against Hetzner's live price pages before you order.
Matching a Plan to a Workload
Plan choice should follow workload characteristics, not the lowest number on the page. A few practical mappings:
Test and development environments. The CX23 at €5.99 with 2 vCPU, 4 GB RAM and 40 GB NVMe is the natural starting point. The cost-optimized positioning explicitly covers new test and development environments. Watch the billing rules: delete rather than stop.
Private blogs and small sites. Also cost-optimized territory, and the 20 TB EU allowance means traffic is unlikely to be a factor. The availability constraint on older hardware is the main risk. If a specific plan is out of stock when you need it, you may need to move up a tier.
Small production apps. The CX33 at €8.99 with 4 vCPU, 8 GB RAM and 80 GB NVMe is a sensible step up. Moving from 2 to 4 vCPU roughly doubles compute for around 50 percent more, which is a better ratio than the entry-level step. If your application stack runs well on ARM, the CAX21 at €10.99 is the ARM equivalent, but confirm library and container compatibility before migrating.
Larger small-to-mid workloads. The CX43 at €16.49 with 8 vCPU, 16 GB RAM and 160 GB NVMe is the top of the captured cost-optimized range. Beyond this point, the older hardware generation and limited availability become harder to justify, and CPX or CCX plans are the more appropriate line.
Workloads needing consistent CPU performance or dedicated vCPU. Step up to CPX or CCX. The cost-optimized tiers are explicitly not aimed at sustained high CPU usage.
Workloads with heavy outbound traffic outside the EU. Model the traffic cost before anything else. A €6 server in Singapore with 5 TB of monthly outbound traffic would incur overage well above the plan price at the reported rate. Confirm the actual rate on Hetzner's location pages first.
Comparing Hetzner with Another Provider on a Like-for-Like Basis
The most common comparison mistake is lining up headline monthly prices from two providers. Those numbers rarely describe the same thing. Line up these metrics instead:
Same region. A Hetzner EU price and a competitor's US price are not comparable for a latency-sensitive workload, and Hetzner's own regional pricing and traffic allowances differ.
Same specification. vCPU count alone is not enough. Check whether the vCPU is shared or dedicated, the RAM-to-CPU ratio, and the storage type and size. Hetzner's own four families differ on exactly these axes.
Same included traffic, at your actual volume. Compare the allowance and the overage rate, not just the allowance. A provider with a smaller allowance but cheaper overage can win at high volume.
Same add-ons. Add the cost of a primary IPv4, backups, snapshots and any volumes on both sides. A plan that includes a free IPv4 is not cheaper if the base price is €2 higher.
Same billing model. Hetzner's hourly billing with a monthly cap and per-resource rounding favours short-lived and variable workloads. A competitor billing monthly in advance has a different cost profile for the same nominal price.
Same VAT position. Hetzner's prices exclude VAT. Compare ex-VAT figures on both sides, then apply your own tax treatment once.
Same contract terms. Hetzner's June 2026 adjustment applied only to new orders and rescales, with existing contracts holding their terms. Check whether a competitor reserves the right to raise prices mid-contract.
No overall winner can be declared on the evidence here, because a full like-for-like comparison against a named competitor was not available. The method above is the useful output: run it with current numbers from both providers.
What to Verify on Hetzner's Price Pages Before Ordering
Prices move, and several details in this article come from third-party reporting rather than Hetzner directly. Before you order, confirm the following on Hetzner's official pages:
- The current monthly price for your chosen plan, excluding VAT, at your chosen location.
- The included traffic allowance for that location, and the overage rate with its unit (per TB or per hour).
- The current primary IPv4 charge.
- The current backup pricing, expressed as a rate rather than a percentage you have seen quoted elsewhere.
- The current snapshot and volume per-gigabyte rates.
- Whether the plan is in stock. Cost-optimized plans have limited availability.
- Whether any price adjustment is pending for new orders.
- The current dedicated server list prices and setup fees if you are going that route.
The Hetzner pressroom release on the June 2026 adjustment is useful for confirming which products changed and which did not, and independent price trackers such as CloudTally's Hetzner Cloud pricing page can help you spot a figure that has moved since publication.
Conclusion: A Decision Guide by Workload
Hetzner's pricing is competitive at the low end and structurally simple, but the headline number is a starting point rather than a budget.
- Test, development and hobby projects in the EU: start with the CX23 at €5.99 or the CX33 at €8.99 if you need more headroom. Delete rather than stop to avoid ongoing charges.
- Small production apps in the EU: the CX33 or CAX21 gives a better compute-to-price ratio than the entry tier. Check ARM compatibility first if you go the CAX route.
- ARM-compatible workloads: the CAX line is worth evaluating on its own merits rather than as a cheaper alternative, since CAX11 costs slightly more than the equivalent x86 plan.
- CPU-intensive or dedicated-vCPU workloads: move to CPX or CCX rather than stretching the cost-optimized line.
- Dedicated hardware: evaluate the -1, -2 and -3 server types and factor in the reduced setup fees, but pull current list prices directly.
- Heavy outbound traffic outside the EU: model the overage before anything else and confirm the rate unit on Hetzner's pages.
The one rule that applies to every workload: check the live price page before you order. The figures here are anchored to Hetzner's published prices at the time of writing, and the June 2026 adjustment shows that they can move.


