Why Is GCP Charging You for Snapshots? (And How to Stop Wasting Money)

A few days ago, I noticed something strange on my Google Cloud Platform billing dashboard. While my main compute engine cost remained constant, there was a recurring micro-charge—a few cents to a couple of dollars every month—under storage fees.

While a few cents or a couple of hundred Korean Won might seem trivial at first glance, recurring hidden charges add up over time. More importantly, I wanted to know where this money was going. After reviewing my billing detailed report, I discovered the culprit: GCP Compute Engine Snapshots.

If you use GCP to host a WordPress blog or server, here is why those small snapshot charges happen and how you can manage them effectively to prevent unnecessary spending.

Understanding How Snapshot Billing Works

A snapshot is a point-in-time backup of your server’s disk. When you create a snapshot manually or set up an automated snapshot schedule, GCP copies your disk state and stores it in Google Cloud Storage.

Many server owners assume snapshots are completely free or cost a fixed one-time fee. In reality, GCP charges for snapshots based on three main factors:

1. Storage Capacity (Gigabytes per Month): GCP charges approximately $0.026 per GB per month for standard snapshot storage. If you have a 30 GB disk snapshot stored for a month, you pay for that exact volume.
2. Differential Backups: GCP snapshots are incremental. The first snapshot saves the entire used disk space. Subsequent snapshots only save data that changed since the last snapshot. However, if you make heavy changes to your database or files daily, new snapshots can grow significantly larger than expected.
3. Retention Accumulation: If you set up an automated daily snapshot schedule without an expiration date, old snapshots sit in your account indefinitely. Over months, having dozens of old snapshots means you are paying for hundreds of gigabytes of cumulative backup data.

How to Clean Up and Reduce Snapshot Fees

To stop bleeding small charges every month, follow these practical cleanup steps inside the GCP Console.

Step 1: Delete Obsolete Manual Snapshots

1. Open the GCP Console and go to Compute Engine > Snapshots.
2. Review the list of all existing snapshots.
3. Keep only the 1 or 2 most recent snapshots for emergency recovery.
4. Select all older, outdated snapshots and click DELETE.

Step 2: Configure Auto-Deletion in Snapshot Schedules

If you use automated backup policies, make sure they don’t hold onto files forever:

1. Navigate to Compute Engine > Storage schedules.
2. Edit your active snapshot schedule.
3. Set the Snapshot retention policy to a reasonable time frame (e.g., automatically delete snapshots older than 7 or 14 days).
4. Save the policy.

Final Thoughts on Cloud Cost Optimization

Cloud hosting gives us immense flexibility and performance, but keeping an eye on micro-transactions is essential for maintaining a lean budget. By deleting unnecessary manual snapshots and keeping your backup retention cycle short, you maintain reliable disaster recovery protection while keeping your monthly storage bill as close to $0 as possible.