Hetzner's backup policy covers infrastructure resilience and an optional automatic server backup product, but it does not shift the duty of keeping a complete, independent backup away from you. The Hetzner Terms and Conditions state that if data is transmitted on your servers, you are obligated to make regular backup copies of that data. They also require a complete data backup before any change you make on your own behalf or on behalf of a third party.
That contract clause is the foundation for judging every technical feature below. Built-in backups reduce risk. They do not replace your own copy.
What Hetzner Cloud Backups Actually Do
Cloud Backups are copies of a server's disk created automatically on a daily basis. You do not schedule them manually once the feature is enabled; Hetzner's documentation links to a getting started guide for turning them on.
Each server has a total of seven backup slots, and the limit is listed as up to seven slots per server. When all slots are full and a new backup is created, the oldest one is deleted. That rotation is the key limitation for planning: seven daily copies give you a moving window, not a permanent archive. Hetzner's documentation does not state the exact number of days the window covers, so treat the slot count as the reliable fact and the calendar span as unconfirmed.
Two exclusions matter before you buy. Backups and Snapshots do not include any Volumes attached to your server. If you store databases, uploads or logs on a separate Volume, that data is outside the automatic protection. Hetzner also directs readers to the Limits page in the Hetzner Console for additional current product limits, so the slot count should be checked against your account rather than assumed.
Snapshots Versus Backups: Manual Control or Automatic Rotation
Snapshots are manual copies of a server's disk, and they are never deleted or updated automatically. They stay until you delete them. That makes them useful before a deployment, a migration or a risky configuration change, where you want a fixed point you control.
The trade-off is operational discipline. A snapshot protects you only if you remember to take it, and the same Volume exclusion applies. Snapshots can be used to duplicate a configured server once or several times, which is why they are popular for cloning staging environments as well as for rollback.
| Feature | Cloud Backups | Snapshots |
|---|---|---|
| Creation | Automatic, daily | Manual |
| Retention | Seven slots, oldest replaced | Kept until you delete them |
| Attached Volumes | Not included | Not included |
| Typical use | Routine daily rollback point | Point-in-time copy before a change |
Neither feature covers attached Volumes, so plan separately for that data regardless of which one you choose.
The Contract Clause Most Buyers Miss
Hetzner's terms place the backup obligation on the customer in two distinct ways. The first is ongoing: you must make regular backup copies of data on your servers. The second is event-driven: you must perform a complete data backup before any change you make on your own behalf or on behalf of a third party.
Enabling Cloud Backups does not discharge either obligation. A rotating seven-slot product is not a complete independent backup, and it does not exist to satisfy a contractual duty that the terms assign to you. Buyers evaluating Hetzner for production workloads should read the backup clause as a statement about who is accountable, not as a description of what the platform will do for them.
The terms also reserve Hetzner's right to change the Terms and Conditions, System Policies and prices with prior notification to the customer. Backup features and pricing are therefore not frozen at the moment of purchase. Separately, Hetzner's employees and commissioned third parties are not authorized to make verbal agreements or provide verbal guarantees to the customer, so any promise about data safety should be traceable to the written terms or official documentation rather than a support conversation.
Cost: What You Pay and What Is Confirmed
Hetzner's official backup documentation does not state a rate. It points readers to the info box at hetzner.com/cloud for current backup pricing. That is the figure to trust at the point of purchase.
Third-party sources report a 20% surcharge on the monthly server price for Cloud Backups, with all seven slots included. Those figures are consistent with each other but are not confirmed by Hetzner's own documentation, so treat 20% as a reported planning estimate and verify it on the official pricing page before committing. One third-party guide describes weekly scheduled backups at 20% of the server price, which conflicts with Hetzner's official documentation stating that backups are created daily. The official daily cadence is the reliable description.
Snapshots are priced on stored data rather than on the server price, and third-party sources report a per-gigabyte monthly rate. Hetzner's supplied documentation does not confirm the exact snapshot rate, so budget from the official console or pricing page rather than a secondary estimate.
If you want an independent offsite target, a Hetzner Storage Box is a separate product with its own pricing. Plans are listed from €3.20 per month excluding VAT for BX11 with 1 TB of storage. Storage Boxes have no minimum contract period and can be scaled up or down without losing data or migrating it manually, which makes them easy to trial before a wider rollout.
Adding an Independent Offsite Layer
The practical gap in a Cloud Backups-only setup is independence. A backup that lives inside the same account as the server does not protect against account-level mistakes, deletion of the server, or a location-level event. Whether Cloud Backups are stored separately from the source server and whether they survive server deletion are claims made by third-party blogs, not confirmed in Hetzner's official documentation, so plan as if they might not.
A Storage Box closes part of that gap because it is a separate product rather than a server disk copy. It supports access protocols including FTP, SFTP, SCP and RSYNC, so standard tools such as rsync, restic, borg or a NAS backup app can write to it. Storage location can optionally be Germany or Finland, which lets you place the copy away from your server's location.
Two cautions apply. Hetzner states that Storage Box data is protected by a RAID configuration that can withstand several drive failures, and that the data is not mirrored onto other servers. RAID protects against disk failure, not against your own deletion of files or a compromised credential. And Storage Box snapshots are a feature of the Storage Box itself: they create an image of the box and can restore it if necessary, with automated snapshots schedulable at a specific time. They protect the backup target, not the source server. Your external backup tool still has to do the copying.
A workable pattern for most Cloud users looks like this:
- Enable Cloud Backups on every production server for an automatic daily disk copy.
- Take a Snapshot before deployments and major changes, since it is retained until you delete it.
- Back up attached Volumes separately, because neither Backups nor Snapshots include them.
- Run an external job to a Storage Box over SFTP or RSYNC, keeping at least one copy outside the server's own account.
- Schedule Storage Box snapshots so a bad sync or accidental deletion on the target can be reversed.
- Restore from a copy on a schedule you set, and record how long it takes.
This follows the general 3-2-1 pattern of multiple copies on different media with one offsite, which is industry practice rather than a Hetzner requirement. Hetzner's own terms simply require regular and complete backups; how you meet that is your design choice.
Restore Expectations and Where Gaps Appear
Hetzner's documentation describes restore at the feature level. You can rebuild the server using a Backup or Snapshot, or create a new duplicate server. When you restore, you will lose any data that is not saved in that Backup or Snapshot. That single sentence is the most useful line in the documentation for planning: recovery returns you to the state of the copy, not to the state of the server at the moment of failure.
The practical gaps follow from that. Anything written after the last daily backup is gone. Anything stored on an attached Volume was never in the copy. Anything deleted from the server more than seven daily slots ago has rotated out of Cloud Backups. And if a restore is needed because of a compromised server, restoring from a copy that already contained the compromise returns you to the same problem, which is why retention depth and offsite copies matter.
Hetzner's supplied documentation does not state recovery time objectives for restores, so do not plan around a guaranteed recovery duration. Measure it yourself with a test restore and use that number in your incident plan.
Who Can Rely on Built-in Backups and Who Cannot
Cloud Backups alone fit low-stakes environments: development servers, staging systems, internal tools and anything that can be rebuilt from code and configuration within a day. In those cases, an automatic daily disk copy with seven rotating slots is proportionate, provided you accept the contractual duty to keep your own backups.
Snapshots alone fit buyers who need manual point-in-time control, such as capturing a known-good state before a risky deployment and keeping it indefinitely. They are a poor substitute for scheduled protection because they depend on someone remembering to take them.
Buyers with production data, customer records, financial information or anything difficult to recreate need a fuller plan. That means Cloud Backups or Snapshots as one layer, an external copy to a Storage Box or another provider as a second layer, and a tested restore procedure. The contractual obligation to keep regular and complete backups sits with the customer either way, and Storage Box data is not mirrored onto other servers, so redundancy on the target remains your responsibility too.
If your workload includes attached Volumes, the built-in features are structurally insufficient on their own regardless of how many slots you have. Add a Volume-level backup job before you rely on Hetzner for that data.
The decision rule is straightforward: enable the built-in features because they are cheap insurance, but treat them as a convenience layer rather than your backup strategy. The policy that actually protects your data is the one you write, run and test yourself.


