Skip to main content

Frequently Asked Questions

Why does Cloud Storage charge for early deletion even though the object is already gone?

Each storage class below Standard (Nearline: 30 days, Coldline: 90 days, Archive: 365 days) has a minimum storage duration built into its lower per-GB price, since the discount assumes the data stays put for a while. Deleting, overwriting, or moving an object to a different class before that minimum elapses triggers a pro-rated early-deletion charge equal to the remaining minimum duration, regardless of whether the object still physically exists.

What's a common mistake when applying Object Lifecycle rules across storage classes?

Setting an aggressive lifecycle rule that transitions objects to Archive after just a few days, then having application logic that regularly overwrites or deletes those same objects, silently racks up early-deletion fees that don't show up until the monthly bill. The fix is aligning lifecycle transition timing with actual access patterns — data genuinely accessed rarely belongs in colder tiers, but frequently-touched data should stay in Standard regardless of its age.