Nearline, Coldline and Archive Storage
The colder storage classes trade a much lower per-gigabyte rate for two things you have to plan around: a minimum storage duration (30, 90, and 365 days) and a retrieval fee. Move data that is genuinely cold and they are dramatically cheaper; move data you still read and they are more expensive than Standard.
Billed: Per gibibyte-month at progressively lower rates, each with a minimum storage duration and a per-gibibyte retrieval fee.
What triggers this charge
- Objects placed in a colder class by a lifecycle rule or at upload.
- Retrieval fees on every read, which is what makes an over-aggressive lifecycle policy backfire.
- Early-delete charges when an object is deleted or moved before its minimum duration — you are billed for the remainder as if it had stayed.
How to reduce it
Match the class to real access patterns
Use Storage Insights or access logs before writing a lifecycle rule. Archiving data that is still read monthly costs more than leaving it in Standard.
Prefer Autoclass when access is unpredictable
Autoclass reacts to actual access rather than to a guess, and avoids the retrieval fees a manual policy incurs when the guess is wrong.
Respect the minimum durations
Do not move short-lived data into Coldline or Archive. The early-delete charge means you pay the full minimum period regardless.
Rates
Related charges
Now find out how much of this you are actually paying.
Finitizer breaks your Google Cloud bill down to the SKU, shows how each one has moved since last week, and separates rate changes from usage changes — so you know whether to talk to engineering or to procurement.