Hetzner Hourly vs Monthly Billing: How the Cap Works

Hetzner Hourly vs Monthly Billing: How the Cap Works

Hetzner Cloud charges by the hour, but your bill for any single server never rises above that server's monthly price cap. In practice you pay the lower of two numbers: the hourly rate multiplied by the hours the server existed, or the monthly cap. That means "hourly vs monthly" is not a choice between two plans. It is one billing model with a ceiling, and the ceiling takes over once a server has run long enough.

The practical question is therefore how long your server will exist, not which billing mode you select. Short-lived servers pay hourly rates. Always-on servers pay the cap. Everything else follows from where your workload sits between those two.

What the Hourly Rate and Monthly Cap Actually Mean

On a Hetzner price listing, each server type shows a monthly price and a price per hour. The monthly figure is the maximum you can be charged for that resource in a calendar month. The hourly figure is what you pay for each hour the server exists, until the running total reaches the cap.

Two details in that mechanics matter more than they first appear.

First, the cap applies per resource and per month. If you create the same server type twice in one month, each instance carries its own cap. Running two identical servers for most of the month does not cost one cap; it costs two.

Second, the cap is a ceiling, not a discount you claim. Hetzner simply bills the minimum of the two calculations, so nothing needs to be configured or switched on.

When Hourly Billing Saves Money

Hourly billing wins whenever a server is deleted before its accumulated hourly charges reach the monthly cap.

Hetzner states that if you delete a cloud server before the end of the billing month, you are billed only for the hourly rate. That single rule makes temporary workloads cheap. Test environments, staging boxes, build agents, migration experiments and short bursts of extra capacity all fit this pattern: create, use, delete.

Two rounding rules shape how much you actually save.

  • Every started hour is billed in full. A server that exists for a few minutes still costs one whole hour.
  • Billing follows existence, not activity. A powered-off server keeps accruing charges until it is deleted.

The rounding rule punishes rapid create-and-destroy cycles. If you spin up and tear down a server ten times in an afternoon, you may pay for ten hours rather than the twenty minutes of actual use. For genuinely short tasks, that is still trivial next to a monthly cap. For a loop that recreates servers dozens of times a day, the hours add up.

The power-state rule catches people more often. Stopping a server in the Hetzner console does not pause billing; the server still exists, so it still costs money. If a project is dormant, a snapshot plus deletion is usually the cheaper path, provided you account for snapshot storage costs described below.

When the Monthly Cap Becomes Your Real Price

For a server that runs continuously, the hourly total will exceed the cap well before the month ends. From that point, the cap is the price, and further hours cost nothing extra.

A worked example makes the crossover visible. A CCX13 server newly ordered in Falkenstein since 15 June 2026 has a €42.99 monthly cap and a €0.0689 hourly rate, excluding VAT and IPv4. Running it for 100 hours costs €6.89. Running it for a full 720-hour month would calculate to €49.61 on pure hourly billing, but the cap holds the charge at €42.99.

Two lessons follow from those figures. The cap saves money on any always-on server, and the saving is modest rather than dramatic, because the hourly rate is already calibrated to the monthly price. The break-even point sits at roughly 624 hours (€42.99 ÷ €0.0689), or about 26 days of continuous existence. Servers that live longer than that in a month are capped; servers deleted before it pay hourly.

Treat those euro figures as illustrative of the mechanism rather than a price list. Hetzner Cloud prices rose on 15 June 2026, with CX and CAX types up 30 to 40 percent and CPX and CCX types more than doubling. Check the current listing for your server type and location before you budget.

How Partial Months and Started Hours Are Counted

Hetzner's billing system uses the hourly price as long as a product has not been used for almost the entire calendar month, and switches to the monthly price after that. Because the charge is always the minimum of the two, the switch is invisible to you: it just means the ceiling applies.

For partial-month usage, the arithmetic is straightforward once you accept the rounding rule.

  1. Count the hours the server existed, rounding any partial hour up to a full hour.
  2. Multiply by the hourly rate for that server type and location.
  3. Compare the result with the monthly cap.
  4. Pay whichever figure is lower.

Deletion ends the clock. Once a server is deleted, no further hours accrue for it, and the final invoice covers the hours it existed. Invoices are issued in arrears, in the month after use, so a server deleted mid-month appears on the following invoice rather than immediately.

Costs Outside the Server Price

The monthly cap covers the server. It does not cover everything attached to it, and these extras can change which workload pattern is cheaper.

Traffic. Only outgoing traffic is billed; incoming and internal traffic is free. Usage beyond the included allowance is charged in 100 MB blocks, rounded up. Independent pricing data puts overage at €1 per TB in the EU and US and €7.40 per TB in Singapore, though Hetzner's own current listing should be the reference.

Backups. Automatic backups are billed at a flat monthly price equal to 20 percent of the server price, and each server gets seven backup slots refreshed daily. A separate pricing source confirms the same 20 percent figure. Backups do not include attached Volumes.

Snapshots. Snapshots are created manually, kept until you delete them, and billed per gigabyte per month with pro-rating for partial months. One independent source lists snapshot storage at €0.0143 per GB per month and block storage at €0.0572 per GB per month. Snapshots are also the reason a "delete the idle server" strategy is not free: the snapshot persists and bills until removed.

IP addresses. Primary IPv4 addresses bill separately from the server, including when unassigned, until deleted. Primary IPv6 addresses are free and generally absent from the invoice. Floating IPs bill monthly with pro-rating for partial use.

The pattern across all of these is that small persistent resources can quietly outlast the server they were attached to. A deleted server with a forgotten snapshot and an unassigned IPv4 is still a line item.

Contract Terms, Cancellation and Billing Timing

Hetzner products do not cancel themselves. They keep running, and keep billing, until you actively cancel or delete them, even when idle.

Cancellation periods vary by product. Some can be cancelled immediately; others carry fixed notice periods such as 30 days to the end of the month, depending on the product and the interface used. For Hetzner Cloud servers, deletion is the action that stops billing, which aligns with the hourly model. Checking the cancellation terms for any add-on product before you rely on a short-lived deployment is worthwhile, because a notice period can outlast the workload.

A lower price tier or regional discount is not a substitute for checking these terms. Prices also vary by location, with Singapore roughly 20 to 40 percent more expensive than Germany and Finland, so the same server type can have a materially different cap depending on where you deploy it.

Estimating Your Own Monthly Cost

A short estimate beats guesswork here, and it needs only four inputs.

  1. Hours of existence. Estimate how long the server will exist this month, remembering that stopped servers still count.
  2. Hourly rate. Take it from the current Hetzner listing for your server type and location.
  3. The cap. Note the monthly price for the same server type and location.
  4. Add-ons. Add backups at 20 percent of the server price, snapshot storage at its per-GB rate, any Primary IPv4 charges, and expected traffic overage.

Then apply the rule: if hours × hourly rate is below the cap, that is your cost; if it is above, the cap is your cost. Multiply by the number of separate instances you will run this month, since each carries its own cap.

As a decision rule, hourly billing suits workloads you will delete within days, and the monthly cap suits anything that will run most of the month. If a server sits idle for long stretches, the usual fix is to snapshot it and delete it, accepting that snapshot storage carries its own modest ongoing cost. The billing model rewards matching resource lifetime to actual need, and it charges for every hour in between.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top