GCP storage classes cost: Standard, Nearline, Coldline, Archive
Google Cloud Storage has four classes trading storage price against retrieval cost and minimum durations. Standard is cheapest to access, Archive cheapest to store. Here is how the classes are priced and how to pick the right one for each data set.
Quick answer
Google Cloud Storage offers four classes that trade storage price against access cost and minimum storage duration: Standard (highest storage price, no retrieval fee, for hot data), Nearline (cheaper storage, a small retrieval fee, 30-day minimum, for monthly-ish access), Coldline (cheaper still, higher retrieval fee, 90-day minimum, for quarterly access), and Archive (cheapest storage at roughly a dollar or so per TB per month range dynamics, highest retrieval fee, 365-day minimum, for rarely accessed data). The right class depends on how often you read the data, not just how much you store.
Google Cloud Storage is not one price. It is four storage classes that make the same tradeoff in different proportions: the colder the class, the cheaper it is to store data but the more you pay to retrieve it and the longer the minimum time you are billed for. Picking the class by access pattern, not just by data size, is where the savings are.
The four classes
| Class | Storage price | Retrieval fee | Minimum duration | For data accessed |
|---|---|---|---|---|
| Standard | Highest | None | None | Frequently (hot) |
| Nearline | Lower | Small per GB | 30 days | About monthly |
| Coldline | Lower still | Higher per GB | 90 days | About quarterly |
| Archive | Lowest | Highest per GB | 365 days | Rarely (yearly) |
Standard is for hot data you read often: highest per-GB storage price but no retrieval fee. Nearline suits data accessed roughly monthly, Coldline roughly quarterly, and Archive data you rarely touch, with Archive storage dropping into the very low per-TB-per-month range while its retrieval fee is the highest. The colder classes also impose minimum storage durations (30, 90, 365 days), so deleting or moving data early still bills for the minimum.
Retrieval and minimum-duration traps
The classic mistake is putting frequently accessed data in a cold class to save on storage, then paying more in retrieval fees than you saved. If you read Archive data monthly, the retrieval charges dwarf the storage savings. Likewise, storing short-lived data in a class with a long minimum duration means paying for 30, 90, or 365 days even if you delete after a week. This is the same tension as Glacier versus Deep Archive on AWS: cold storage is cheap to hold and expensive to touch.
Object lifecycle management
The right way to use the classes is to let data age into colder ones automatically. Object lifecycle management rules move objects from Standard to Nearline to Coldline to Archive based on age, and can delete old objects, so hot data stays cheap to access and cold data drifts into cheap storage without manual work. This mirrors the lifecycle approach that controls snapshot cost creep: automate the tiering so it actually happens.
Choosing the right class
Match the class to real access frequency: Standard for anything read regularly, Nearline for backups and data touched monthly, Coldline for quarterly archives, Archive for compliance data and long-term retention you almost never read. Model retrieval frequency, not just volume, since a class that looks cheap on storage can be expensive if you read often. Watch egress on retrievals too, and price your storage footprint against the resource catalog before committing large data sets to a class.
FAQ
What are the GCP storage classes?
Standard (highest storage price, no retrieval fee, for hot data), Nearline (cheaper storage, small retrieval fee, 30-day minimum, for monthly access), Coldline (cheaper still, higher retrieval fee, 90-day minimum, for quarterly access), and Archive (cheapest storage, highest retrieval fee, 365-day minimum, for rarely accessed data). They trade storage price against access cost and minimum storage duration.
Which GCP storage class is cheapest?
Archive is cheapest to store, dropping into the very low per-TB-per-month range, but it has the highest retrieval fee and a 365-day minimum storage duration. It is only cheapest overall for data you almost never read. For frequently accessed data, Standard is cheaper overall despite its higher storage price, because it has no retrieval fee, so cheapest depends on access pattern.
What is a retrieval fee in Cloud Storage?
Colder classes (Nearline, Coldline, Archive) charge a per-GB fee each time you read data, on top of the storage price, and the fee grows as the class gets colder. This is why putting frequently accessed data in a cold class can cost more than Standard: the retrieval fees on regular reads can exceed the storage savings you were chasing.
What are minimum storage durations?
Nearline, Coldline, and Archive bill for a minimum of 30, 90, and 365 days respectively, even if you delete or move the object sooner. So storing short-lived data in a cold class means paying the full minimum duration regardless. Match the class to how long the data will actually live, not just how often you read it.
How do I automatically move data to cheaper classes?
Use object lifecycle management rules, which move objects from Standard to Nearline to Coldline to Archive based on age, and can delete old objects automatically. This keeps hot data cheap to access and lets cold data drift into cheap storage without manual intervention, which is the reliable way to capture the storage-class savings across a large bucket.
Does C3X price GCP storage classes?
C3X reads your infrastructure code and prices the storage resources you define, including storage class choices, against a live catalog before you deploy. That lets you compare the monthly cost of Standard versus colder classes for a given data set in the pull request, factoring in the storage price differences before you commit large volumes.
What to do next
Pick the right storage class by cost before you deploy. C3X prices your storage from code against a live catalog. Start with the quickstart and the resource catalog.
Share this post
Try C3X on your own Terraform
Free and open source. No API key required. One command to install, one command to estimate.