How to copy DigitalOcean snapshots to a second region (and remove copies before they are billed)
A DigitalOcean Droplet snapshot is stored in the region where you took it. If that region has an outage, the snapshot is stuck there with your Droplet. You can add a copy of the snapshot to a second region and build a new Droplet from it there. Until now those extra copies cost nothing, so many people added every snapshot to several regions. DigitalOcean's release notes say that from January 1, 2027, copies in additional regions are billed at the same price as the original snapshot. This guide shows how to see where each snapshot lives, keep only the newest one in a second region, remove the copies you do not need, run it on a schedule, and restore in the second region to prove it works. Commands use doctl and the DigitalOcean API from any Linux or macOS machine.
What to keep in a second region, and why
A second-region copy protects you from one thing: losing access to the region your Droplet runs in. You do not need every snapshot there. One recent snapshot of each production Droplet is enough to rebuild somewhere else.
| Snapshot | Second-region copy? |
|---|---|
| Newest snapshot of a production Droplet | Yes |
| Older snapshots from a daily or weekly set | No. Keep them in the original region only |
| Snapshot taken before a risky change, once the change is done | No. Remove the extra copy, or delete the snapshot |
| Staging, test or throwaway Droplets | No |
This guide covers Droplet snapshots. A Droplet snapshot does not include attached Volumes, and your databases still need their own backups. A snapshot is a copy of the disk, not a database backup you can restore table by table. See snapshot vs backup.
See which regions each snapshot is in
Install doctl, create a personal access token in the control panel, and run doctl auth init once. Then list your Droplet snapshots with their regions:
doctl compute snapshot list --resource droplet \
--format ID,Name,Regions,Size,CreatedAtAny snapshot with more than one region in the Regions column has extra copies. To check one snapshot:
doctl compute snapshot get <snapshot-id> --format ID,Name,Regions,MinDiskSizeIn the control panel, go to Backups & Snapshots, then Snapshots, and open a snapshot's More menu. In the Remove from Region window, the region the snapshot was taken in is labeled (default). That copy cannot be removed on its own.
Add a snapshot to a second region
Pick a region away from your main one, for example nyc3 for a Droplet in sfo3, or fra1 for one in lon1. Then copy the snapshot there:
doctl compute image-action transfer <snapshot-id> --region <region-slug> --wait--wait keeps the command running until the copy finishes, which can take several minutes. In the control panel, the same thing is More, then Add to Region, on the snapshot.
With the API, it is a transfer action on the image:
curl -X POST \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
-d '{"type":"transfer","region":"<region-slug>"}' \
"https://api.digitalocean.com/v2/images/<snapshot-id>/actions"Remove copies you do not need
Removing a regional copy leaves the snapshot and its other copies in place. In the control panel, open the snapshot's More menu, click Remove from Region, choose the regions, and click Remove from selected regions. With the API, send a DELETE for each region:
export DIGITALOCEAN_TOKEN=<your-api-token>
curl -X DELETE \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
"https://api.digitalocean.com/v2/snapshots/<snapshot-id>/regions/<region-slug>"| Response | Meaning |
|---|---|
| 204 No Content | The copy in that region was removed |
| 400 | Unknown or invalid region slug |
| 404 | No such snapshot, or it has no copy in that region |
| 422 | You tried to remove the copy in the original region |
doctl compute snapshot delete deletes the whole snapshot, including every regional copy, and it cannot be undone. Use the region DELETE above when you only want to drop one copy.
Do this cleanup before January 1, 2027, so you are not billed for copies you forgot about.
Automate it: one fresh copy in the second region
This script takes a snapshot, copies it to the second region, removes the second-region copy from the previous snapshot, and keeps the newest seven snapshots in the original region. So you always pay for one extra copy per Droplet, not seven. Run it from a machine other than the Droplet it snapshots, so a compromised Droplet does not hold a token that can delete its own snapshots.
#!/bin/bash
set -euo pipefail
DROPLET_ID=<droplet-id>
PREFIX=<droplet-name> # snapshot names start with this
SECOND_REGION=<region-slug> # for example nyc3 or fra1
KEEP=7
DIGITALOCEAN_TOKEN=$(cat /root/.do-token) # same token as doctl auth init
NAME="$PREFIX-$(date +%Y-%m-%d-%H%M)"
# 1. New snapshot, then copy it to the second region
doctl compute droplet-action snapshot "$DROPLET_ID" --snapshot-name "$NAME" --wait
SNAP_ID=$(doctl compute snapshot list "$NAME" --resource droplet --format ID --no-header)
doctl compute image-action transfer "$SNAP_ID" --region "$SECOND_REGION" --wait
# 2. Remove the second-region copy from the previous snapshot (404 if it had none)
PREV_ID=$(doctl compute snapshot list "$PREFIX-*" --resource droplet --format Name,ID --no-header \
| sort -r | sed -n 2p | awk '{print $2}')
if [ -n "$PREV_ID" ]; then
curl -sS -o /dev/null -w "remove copy: %{http_code}\n" -X DELETE \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
"https://api.digitalocean.com/v2/snapshots/$PREV_ID/regions/$SECOND_REGION"
fi
# 3. Keep the newest $KEEP snapshots, delete older ones entirely
doctl compute snapshot list "$PREFIX-*" --resource droplet --format Name,ID --no-header \
| sort -r | tail -n +$((KEEP + 1)) | awk '{print $2}' \
| xargs -r doctl compute snapshot delete --forceThe names include the date and time, so sorting by name puts the newest first. Make the token file readable by root only, make the script executable, and run it once by hand:
sudo install -m 600 /dev/null /root/.do-token # then paste the token into it
sudo chmod 700 /usr/local/bin/do-snapshot-2region.sh
sudo /usr/local/bin/do-snapshot-2region.shThen schedule it with sudo crontab -e. Cron has a short PATH, so use the full path to doctl in the script if command -v doctl shows it outside /usr/bin or /bin.
30 3 * * * /usr/local/bin/do-snapshot-2region.sh >> /var/log/do-snapshot.log 2>&1Step 3 deletes every snapshot whose name starts with your prefix beyond the newest seven, including snapshots you took by hand with the same prefix. Give manual snapshots a different name.
Restore in the second region to prove it works
A copy you have never booted is a guess. Build a test Droplet from the snapshot in the second region, check it, then delete it. The size you pick needs a disk at least as large as the snapshot's MinDiskSize.
doctl compute snapshot get <snapshot-id> --format Name,Regions,MinDiskSize
doctl compute droplet create dr-test \
--image <snapshot-id> \
--region <region-slug> \
--size <size-slug> \
--ssh-keys <ssh-key-fingerprint> \
--wait
doctl compute droplet list --format ID,Name,PublicIPv4,RegionSSH in, check that your app's files and services are there, and that it starts. Remember the restored Droplet has a new IP address, so in a real outage you also change DNS or move a Reserved IP in that region. When you are done, delete the test Droplet:
doctl compute droplet delete dr-test --forceDo this test every few months, and after any big change to the server. Write down how long it took. That is your real recovery time.
Frequently asked questions
- Do DigitalOcean snapshot copies in other regions cost extra?
- Not until January 1, 2027. DigitalOcean's release notes say that from that date, copies in additional regions are billed at the same price as the original snapshot.
- Can I remove the original region's copy and keep only the new one?
- No. The copy in the original region is the default and the API returns 422 if you try to remove it. To get rid of it you have to delete the whole snapshot.
- Does deleting a snapshot delete its copies in other regions?
- Yes. Deleting the snapshot removes it and all of its copies. To drop only one copy, remove that region instead.
- Can doctl remove a single regional copy?
- DigitalOcean documents removing a regional copy in the control panel and through the API (
DELETE /v2/snapshots/<id>/regions/<region>). Adding a copy works withdoctl compute image-action transfer.
How this was checked
Commands, limits and prices were checked against these official pages, on November 16, 2026:
- DigitalOcean Docs: How to Add or Remove Droplet Snapshots in Other Regions
- DigitalOcean Docs: Recent Release Notes
- doctl reference: compute snapshot list
- doctl reference: compute snapshot get
- doctl reference: compute snapshot delete
- doctl reference: compute image-action transfer
- doctl reference: compute droplet-action snapshot
- doctl reference: compute droplet create