To optimize snapshot lifecycle across clouds, inventory and delete orphans, automate retention, and archive cold snapshots. EBS snapshots are about $0.05 per GB-month standard and $0.0125 for the archive tier, with Azure and GCP priced similarly per GB-month on incremental data. Find and remove snapshots whose source volume is gone, set automated retention with Data Lifecycle Manager, Azure snapshot policies, or GCP snapshot schedules, move long-retention snapshots to an archive tier, and limit cross-region copies to what recovery requires. Clearing this backup waste is part of the 31% average bill reduction across the 500+ environments we have optimized.
Last updated: June 2026 · Written by Morten Andersen and reviewed by Fredrik Filipsson · See, Cut, Lock, Run method
A snapshot is a point-in-time copy of a disk or volume, taken for backup and recovery, and on every major cloud it bills per GB-month on the changed data it stores. Because snapshots are trivial to create from automation, scripts, and consoles, they accumulate far faster than anyone reviews them: orphans left after a volume is deleted, retention chains kept far longer than the recovery plan needs, and copies replicated to regions no recovery will ever use. This guide is part of our complete guide to cloud storage and data cost optimization, the cluster pillar it links up to.
How much do cloud snapshots cost?
Amazon EBS snapshots cost about $0.05 per GB-month on the standard tier and $0.0125 per GB-month on the archive tier, billed on incremental changed data, with Azure and Google Cloud priced similarly per GB-month. Per the Amazon EBS pricing page, standard snapshots store only the blocks that changed since the previous snapshot, and the EBS Snapshot Archive tier holds a full, independent copy at roughly a quarter of the standard rate when restore time of hours is acceptable. Azure managed disk snapshots and Google Cloud persistent disk snapshots follow the same incremental, per-GB-month model with their own rates. The cost on most estates is not the per-GB price but the volume: orphaned snapshots that never get deleted, deep retention, and cross-region copies. Verify current rates against each provider before modeling, since snapshot pricing varies by region and tier.
How do I optimize snapshot lifecycle step by step?
Optimize snapshots by removing orphans, automating retention, and archiving cold copies. Work through these steps:
- Inventory snapshots and find orphans. List every snapshot across clouds and flag those whose source volume no longer exists, since orphaned snapshots bill indefinitely for data nothing will restore.
- Set an automated retention policy. Use Amazon Data Lifecycle Manager on AWS, snapshot policies on Azure, and snapshot schedules on GCP to expire snapshots past a defined window automatically.
- Use incremental snapshots correctly. Keep snapshot chains incremental and let the native tooling manage deletion, since deleting the wrong base can force a full copy and raise rather than lower cost.
- Archive cold snapshots. Move long-retention snapshots to an archive tier, such as EBS Snapshot Archive at $0.0125 per GB-month versus $0.05 for standard, when a restore time of hours is acceptable.
- Limit cross-region snapshot copies. Copy snapshots only to the regions your recovery plan requires, since each copy adds storage in the second region plus data transfer.
This is the same waste-elimination work in our rightsizing and waste elimination service. The streaming counterpart, where event-pipeline retention drives storage cost, is covered in the sibling guide how to optimize streaming and event pipeline storage costs.
The single largest pool of snapshot waste is almost always orphaned snapshots, copies whose source volume was deleted long ago. They keep billing every month and no one will ever restore them, because the system they backed is gone. A one-time sweep to identify and delete orphans, followed by automated retention so new ones cannot accumulate, is the fastest snapshot saving on every cloud.
Should I use a snapshot archive tier?
Use a snapshot archive tier for snapshots you must keep long term but rarely restore, and keep frequently restored snapshots on the standard tier. The decision is a trade between cost and restore speed. EBS Snapshot Archive is about $0.0125 per GB-month against $0.05 for standard, a roughly 75 percent saving, but it stores a full copy and restoring it takes hours rather than minutes, and it has a minimum archive period. That makes it ideal for compliance retention, year-end copies, and any snapshot held to satisfy a policy rather than to support fast operational recovery. Snapshots that back live systems and might be restored on short notice should stay on the standard tier where restore is quick. The same archive-versus-standard logic applies on Azure and GCP cold storage options. The table summarizes the trade.
| Tier | EBS rate | Restore time | Best for |
|---|---|---|---|
| Standard snapshot | ~$0.05 / GB-month | Minutes | Operational recovery |
| Snapshot archive | ~$0.0125 / GB-month | Hours | Long-term and compliance retention |
Verdict: archive long-retention snapshots you rarely restore, and keep operational recovery copies on the standard tier.
How many orphaned snapshots are on your bill?
Our cost audit inventories every snapshot across AWS, Azure, and GCP, deletes the orphans, automates retention, and proves the saving against a clean baseline. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →The Cloud Storage and Egress Cost Playbook includes the snapshot retention and archive checklist we run across all three clouds.
Frequently asked questions
How much do cloud snapshots cost?
Amazon EBS snapshots cost about $0.05 per GB-month for standard storage and $0.0125 per GB-month for the archive tier, billed on incremental changed data. Azure and Google Cloud price snapshots per GB-month with incremental billing as well. Cost comes from retention depth, orphaned snapshots, and cross-region copies rather than the per-GB rate alone.
What is an orphaned snapshot?
An orphaned snapshot is a snapshot whose source volume has been deleted, so nothing references it but it keeps billing for storage every month. Orphaned snapshots are one of the largest sources of snapshot waste because they accumulate silently and are never restored, which is why inventory and cleanup come first.
Should I use snapshot archive tiers?
Use an archive tier for snapshots you must retain long term but rarely restore, such as compliance copies. EBS Snapshot Archive is about $0.0125 per GB-month versus $0.05 for standard, a roughly 75 percent saving, in exchange for a restore time measured in hours rather than minutes. Keep frequently restored snapshots on the standard tier.
How do I automate snapshot retention?
Use the native scheduler on each cloud: Amazon Data Lifecycle Manager on AWS, snapshot policies on Azure, and snapshot schedules on Google Cloud. Define how many snapshots to keep and for how long, and the service creates and expires them automatically so retention does not drift and old snapshots do not accumulate.
The short version
Snapshots bill per GB-month on every cloud, and the cost is driven by orphans, deep retention, and cross-region copies. Inventory and delete orphans, automate retention with the native scheduler, archive cold snapshots at roughly a quarter of the standard rate, and limit cross-region copies. When you want every snapshot reviewed and the saving proven down, that is part of what our rightsizing and waste elimination service delivers.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: FinOps Foundation Framework ↗ and FinOps Rate Optimization capability ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.