You enabled the DigitalOcean backup add-on, paid your 20%, and moved on. A month later you noticed you've also been clicking the "Take Snapshot" button before every deployment. Now you have both. Are they protecting the same thing? Can you drop one? Are you actually covered, or just paying twice for the feeling of being covered?
The short answer: they are different mechanisms, with different triggers, different billing models, different retention behavior, and different failure modes. Treating them as interchangeable is how teams end up with a gap where they thought they had coverage.
We back up DigitalOcean every day. What follows is what we actually see in how these two mechanisms behave.
What DigitalOcean means by "backup"
When DigitalOcean says "backup," it means the Droplet Backup add-on: a paid feature you enable at the Droplet level. It costs 20% of the Droplet's hourly price and runs on a schedule that DigitalOcean controls, not you.
On standard Droplets, backups run weekly. On Premium Droplets (CPU-optimized, memory-optimized, and others in the Premium tier), they run daily. Either way, DigitalOcean decides when within that window the backup actually runs. You can see the schedule in the control panel, but you cannot change it.
The backup captures the entire Droplet: disk, OS, installed packages, configuration files, your data. DigitalOcean keeps the last four weekly snapshots (roughly four weeks of history). When the fifth backup completes, the oldest one is deleted automatically. There is no option to extend this.
A few constraints worth knowing before you depend on this feature:
- You cannot download a Droplet backup. It lives in your DigitalOcean account, inaccessible outside of their restore flow.
- You cannot copy a Droplet backup to another provider or a different account.
- Block storage volumes attached to the Droplet are not included. If your application stores data on a volume rather than the root disk, the backup add-on does not touch it.
- If your Droplet is deleted, the backups associated with it are deleted too.
For the full technical detail on enabling the backup add-on, the DigitalOcean docs on Droplet backups are accurate and current.
What backups cover
The Droplet Backup add-on protects the root disk on a regular schedule without any manual effort from you. That is its job. It does that job well. It does not protect volumes, it does not export off-site, and it does not let you control the cadence.
What DigitalOcean means by "snapshot"
A snapshot is a point-in-time image of a Droplet or a Block Storage volume. Unlike the backup add-on, snapshots are on-demand. Nothing happens automatically. You trigger a snapshot manually through the control panel, the doctl CLI, or the DigitalOcean API.
Billing is $0.06 per GB per month, charged for the compressed snapshot size. A 20 GB Droplet whose snapshot compresses to 8 GB costs $0.48/month to keep around. If you take ten snapshots and never delete any, the bill grows with each one. There is no expiry. Snapshots persist until you explicitly delete them.
The rules for Droplet snapshots and volume snapshots are the same: on-demand, billed at $0.06/GB/mo, retained until you delete them. But they cover different things: a Droplet snapshot captures the root disk; a volume snapshot captures the attached Block Storage volume. The two are separate operations and separate line items.
One region-transfer capability that snapshots have and the backup add-on lacks: you can copy a Droplet snapshot to another DigitalOcean region. This is useful for pre-positioning images before a migration or spinning up a clone in a second region. It is not off-site storage (it's still inside your DO account), but it does give you geographic redundancy within the platform.
The DigitalOcean docs on Droplet snapshots walk through the manual and API-based snapshot workflows.
Snapshots are not automatic. If you're relying on snapshots as your primary protection against data loss, you need a cron job, a doctl script, or a third-party tool to trigger them on a predictable schedule. A snapshot taken two weeks ago protects you against data loss from two weeks ago.
The five differences that matter
The table below locks in the comparison. The five rows that follow explain the implications of each difference.
| Dimension | Droplet Backup (add-on) | Droplet Snapshot |
|---|---|---|
| Trigger | Automatic, by DigitalOcean | Manual, by you (or your script) |
| Schedule | Weekly (standard) / Daily (Premium) | Whenever you run it |
| Retention | Fixed: last 4 weeks, then auto-deleted | Indefinite: until you delete it |
| Pricing model | 20% of Droplet price per month | $0.06/GB/month (compressed) |
| Region transfer | Not transferable | Transferable within DigitalOcean |
| Volume coverage | Root disk only (volumes excluded) | Root disk (Droplet) or volume (Volume snapshot, separately) |
| Downloadable | No | No |
| Off-site | No | No |
1. Trigger: you vs. DigitalOcean
The backup add-on runs because DigitalOcean scheduled it. Snapshots run because you (or something you set up) told them to. This sounds like a minor distinction until 3am on a Wednesday when your application is six hours into a bad data state and your last snapshot was the one you took before the deploy two weeks ago.
Automatic beats manual for protection against forgetting. Manual beats automatic for protection against specific moments: before a dangerous migration, immediately after a clean restore test, immediately after provisioning a new Droplet you want to be able to roll back.
2. Schedule and cadence
Weekly cadence means a Droplet backup captures at most one point per week. Your maximum possible data loss window on a standard Droplet is seven days. That is a meaningful number. If your application writes anything important between Tuesday afternoon and the following Tuesday morning, a weekly backup may not be enough.
For context on whether the weekly vs. daily tradeoff is worth the Premium tier price difference, the cost comparison between weekly and daily backups covers the math in detail.
3. Pricing: percentage vs. per-GB
Backup add-on pricing scales with the Droplet. A $6/month Basic Droplet pays $1.20/month for backups regardless of how much data is on it. A $48/month Droplet pays $9.60/month.
Snapshot pricing scales with storage consumed. A sparse Droplet with 2 GB of actual data produces a small compressed snapshot. A Droplet with 80 GB of database files produces a large one. If you keep many snapshots, the bill adds up faster than a flat percentage.
For most workloads the backup add-on is cheaper if you only keep one or two copies. For long-lived snapshot archives, per-GB billing gets expensive quickly.
4. Retention: fixed window vs. open-ended
The backup add-on's four-week rolling window is predictable and automatic. You always have four recovery points. You can never have five.
Snapshots give you as many recovery points as you're willing to pay for. The discipline problem is the inverse: without a deletion policy, snapshots accumulate. We've seen teams log into the control panel and find sixty snapshots from two years of pre-deploy triggers, paying $30/month for history they'll never use.
Neither model is inherently better. The backup add-on's fixed window is enough for many workloads. Open-ended snapshot retention is valuable for workloads with compliance-driven long-term recovery requirements. Knowing which you have is the prerequisite.
5. Region transfer
You can copy a Droplet snapshot to a second DigitalOcean region. Backup add-on images cannot be transferred. If geographic redundancy within DO matters to your architecture, snapshots are the only native path.
What neither provides is a copy at a different provider. Both snapshots and backups live inside your DigitalOcean account. If the account is compromised, suspended, or caught in a regional incident, both are gone. We return to this point in the compliance section below.
When to use backups
The backup add-on is the right default for most Droplets. Enable it on every Droplet that runs something you would miss, then stop thinking about it. It costs 20% of an already-small monthly line item. The operational cost is zero: DigitalOcean handles scheduling, retention, and deletion.
Use the backup add-on when:
- You need automated, hands-off protection for the root disk.
- A weekly recovery point (or daily, on Premium) is sufficient for your workload.
- You want predictable costs that scale with your Droplet, not your data volume.
- You're setting up a new Droplet and want the simplest possible safety net.
The backup add-on is not optional for production Droplets. The only debate is whether it's sufficient on its own. In most cases, for most teams, it isn't, but that's different from not enabling it.
For a deeper look at what the backup add-on actually captures and how its internals work, how DigitalOcean native backup works covers the mechanism in detail.
When to use snapshots
Snapshots are the right tool for moments, not for continuous protection. The on-demand nature is a feature, not a limitation, as long as you treat it as such.
Use snapshots when:
- You're about to do something dangerous (kernel upgrade, schema migration, dependency update) and want a clean rollback point.
- You need to clone a Droplet to a second region for a migration or failover test.
- You want to capture the current state after a successful configuration change.
- You're archiving a Droplet before decommissioning it (snapshots survive Droplet deletion; backup add-on images do not).
- You need to protect a Block Storage volume. The backup add-on does not reach volumes; volume snapshots are the only native option.
The failure mode with snapshots is drift: you take one before a deploy and then don't take another for three weeks. Your "current snapshot" is increasingly stale without you noticing. If you're using snapshots as your primary protection layer, you need to automate the trigger. The guide to automating DigitalOcean Droplet backups covers how to schedule snapshot creation via the API and doctl.
When you need both
Most production setups need both, covering different parts of the stack for different reasons.
Use the backup add-on for: your root disk, continuous automated protection, the recovery-point cadence you've agreed to with your team or your users.
Use snapshots for: pre-deploy checkpoints, volume protection, cross-region copies, long-term archives of specific known-good states.
A common gap that teams miss: the backup add-on does not protect Block Storage volumes. If your application's database writes to a mounted volume (a common pattern for Managed Database-adjacent workloads and self-hosted databases), the backup add-on captures the Droplet's OS and config but misses the data entirely. Volume snapshots are required for the data layer.
For the complete inventory of what native backup misses, what DigitalOcean native backup doesn't cover maps each gap with the recommended mitigation.
A practical default for production: enable the backup add-on on the Droplet, enable volume snapshots on any attached volumes, and automate both. If you're doing this manually, you'll eventually forget one. Automation is not optional for anything you actually need back.
The compliance angle: neither alone satisfies off-site
Compliance
Both snapshots and backups live inside the same DigitalOcean account. For SOC 2, ISO 27001, GDPR, or any framework that requires off-site copies at a separate provider, neither alone is sufficient.
This is the part the DigitalOcean control panel doesn't tell you clearly, so let's be direct about it.
Every native backup mechanism DigitalOcean provides, including the backup add-on and all snapshot types, stores the data inside your DigitalOcean account. Region transfers move data between DigitalOcean regions, still under the same account. If that account is compromised, suspended, or caught in a regional incident, your backups are in the same blast radius as your production resources.
For frameworks like SOC 2 Type II, ISO 27001, or GDPR data protection requirements, auditors typically require evidence that backup copies are stored at a distinct provider with independent access controls. "We have snapshots in a second DigitalOcean region" does not satisfy that requirement. "We have an encrypted copy on Backblaze B2 or AWS S3 with a separate IAM account" does.
The same-host risk is not theoretical. DigitalOcean has had account-level suspensions due to billing disputes, terms of service issues, and security flags. When that happens, backup add-on images are inaccessible at the same moment the Droplets are inaccessible. The point of a backup is that it's available when the primary is not.
For the full breakdown of off-site requirements by compliance framework and how to implement them on DigitalOcean, DigitalOcean off-site compliance covers what each standard actually requires and what tools satisfy it.
The gap the generic comparison of backups vs. snapshots makes clear is also true here: neither snapshots nor backups are substitutes for an off-site copy. They are complements to it.
What to do tonight
If you haven't enabled the Droplet backup add-on, do that first. It's the simplest, lowest-friction thing you can do. Cost is 20% of the Droplet; setup takes thirty seconds.
Then check your volumes. List every Droplet and confirm whether it has attached volumes. If it does, confirm you have volume snapshot automation in place. The backup add-on does not help you here.
Then decide whether the four-week window is enough. For most development and staging Droplets, it is. For production systems with compliance requirements or high write rates, it likely isn't. The answer to that question determines whether you need off-site copies, longer retention, or a different snapshot cadence.
The reason we built SimpleBackups for DigitalOcean is exactly the gap this article describes: native backup covers the easy part, and none of the hard part. If you want off-site snapshots and volume backups without writing any of it yourself, that's what it does.
Keep learning
- How DigitalOcean native backup works — What happens under the hood when the backup add-on runs.
- What DigitalOcean native backup doesn't cover — The full inventory of gaps: volumes, Spaces, DOKS, Managed Databases on older tiers.
- Backups vs. snapshots: differences and examples — The generic version of this comparison, useful context before going platform-specific.
- Automate DigitalOcean server and volume snapshots — How to trigger snapshots on a schedule via the API and doctl.
- The complete guide to DigitalOcean backup — The hub for this entire cluster.
FAQ
Are DigitalOcean snapshots the same as backups?
No. In DigitalOcean's terminology, "backup" refers specifically to the Droplet Backup add-on: a paid feature that runs on an automatic schedule (weekly or daily) and keeps four weeks of history. Snapshots are on-demand point-in-time images that you trigger manually and that persist until you delete them. They use different billing models, different retention logic, and have different coverage. Using them interchangeably leads to gaps.
Do snapshots count toward my backup retention?
No. Snapshots and backups are independent mechanisms. Snapshots do not contribute to or extend the four-week backup retention window. If the backup add-on is disabled, taking snapshots does not give you equivalent coverage. If snapshots are deleted, the backup add-on history is unaffected. They are separate line items in separate systems.
Can I convert a snapshot into a scheduled backup?
Not directly. The backup add-on is scheduled by DigitalOcean; you cannot replace that schedule with your own snapshots and call it the backup add-on. What you can do is use the DigitalOcean API or doctl to automate snapshot creation on a cron schedule, which gives you snapshot-based recurring copies. That is a different mechanism with different billing and no built-in retention management.
Are snapshots billed differently than backups?
Yes. The backup add-on costs 20% of the Droplet's hourly price, regardless of the data volume on the disk. Snapshots cost $0.06 per GB per month based on the compressed snapshot size. For small Droplets with modest data, the backup add-on is usually cheaper per protected copy. For large volumes of data kept across many recovery points, snapshot billing adds up faster.
Which is better for disaster recovery: snapshots or backups?
Neither is sufficient on its own for serious disaster recovery. The backup add-on provides automated continuity but has a fixed retention window, no volume coverage, and no off-site copy. Snapshots provide flexible point-in-time recovery but require manual or automated triggering and have no inherent retention policy. For actual disaster recovery, especially in a compliance context, you need both plus an off-site copy at a provider separate from DigitalOcean.
This article is part of The complete guide to DigitalOcean backup, an honest, practical reference from the team that backs up DigitalOcean every day.