Overview of Storage Classes
Cloud Storage offers four storage classes — Standard, Nearline, Coldline, and Archive — that all share the same API, latency, and durability, but differ in price and in the minimum storage duration you commit to. The right class is chosen based on how frequently you expect to access the data, not on the data's size or importance: frequently accessed data belongs in Standard, while data you rarely touch belongs progressively further down the Nearline-to-Archive spectrum to cut storage cost.
Cricket analogy: It's like a team choosing which players to keep in the active XI (Standard, ready every match) versus which to keep on the domestic circuit for occasional call-ups (Archive), based on how often they're actually needed.
Standard and Nearline
Standard storage has no minimum storage duration and no retrieval fee, making it the right choice for data accessed multiple times per month, such as website assets, active application data, or streaming media. Nearline storage costs less per gigabyte but carries a 30-day minimum storage duration and a per-gigabyte retrieval fee, so it's economical specifically for data you access roughly once a month or less, such as monthly backups or older logs kept for occasional analysis.
Cricket analogy: It's like the wicketkeeper's gloves being grabbed every single delivery with zero setup cost (Standard), versus the third umpire's replay kit that's pulled out only for the occasional DRS review each session (Nearline).
Coldline and Archive
Coldline storage is priced for data accessed roughly once per quarter or less, carries a 90-day minimum storage duration, and is a common choice for disaster-recovery data and infrequently referenced compliance records. Archive storage is the cheapest tier, intended for data accessed at most once a year, with a 365-day minimum storage duration and the highest retrieval cost and latency of the four classes — ideal for long-term regulatory archives, cold backups, and data kept purely for legal retention.
Cricket analogy: It's like a board's quarterly review of pitch report data pulled up once every three months (Coldline), versus a decade-old match ball preserved in a museum case, examined maybe once a year (Archive).
# Upload directly into Coldline storage class
gcloud storage cp ./quarterly-backup.tar.gz gs://acme-backups/2026/ \
--storage-class=COLDLINE
# Change the storage class of an existing object
gcloud storage objects update gs://acme-backups/2026/quarterly-backup.tar.gz \
--storage-class=ARCHIVE
# Example lifecycle rule: move to Nearline after 30 days, Archive after 365
cat lifecycle.json
{
"rule": [
{"action": {"type": "SetStorageClass", "storageClass": "NEARLINE"},
"condition": {"age": 30}},
{"action": {"type": "SetStorageClass", "storageClass": "ARCHIVE"},
"condition": {"age": 365}}
]
}
gcloud storage buckets update gs://acme-backups --lifecycle-file=lifecycle.jsonAutoclass and Lifecycle Management
Rather than manually setting lifecycle rules based on object age, you can enable Autoclass on a bucket, which automatically transitions each object between Standard, Nearline, Coldline, and Archive based on its actual observed access pattern, and moves it back to Standard immediately if it's accessed again — removing the need to predict access patterns up front. For workloads where access patterns are predictable, explicit lifecycle rules based on object age remain cheaper because Autoclass carries a small per-object monthly management fee.
Cricket analogy: It's like an analytics system automatically promoting a domestic player to the national squad the moment they start performing well, rather than a selector manually reviewing form every quarter on a fixed schedule.
Nearline, Coldline, and Archive all charge an early deletion fee if you delete or overwrite an object before its minimum storage duration (30, 90, and 365 days respectively) has elapsed. Moving an object to a cheaper class too early can end up costing more than leaving it in a warmer class.
- All four storage classes — Standard, Nearline, Coldline, Archive — share the same API, latency, and eleven-nines durability.
- The right class is chosen by expected access frequency, not by data size or importance.
- Standard has no minimum duration or retrieval fee; ideal for data accessed multiple times a month.
- Nearline (30-day minimum), Coldline (90-day minimum), and Archive (365-day minimum) each add retrieval fees and early-deletion fees.
- Archive is the cheapest per-gigabyte but has the highest retrieval cost and latency, suited to yearly-or-less access.
- Lifecycle rules automate class transitions based on object age; Autoclass automates it based on observed access instead.
- Deleting or overwriting an object before its minimum storage duration elapses triggers an early deletion fee.
Practice what you learned
1. Which storage class has no minimum storage duration and no retrieval fee?
2. What is the minimum storage duration for Coldline storage?
3. What does Autoclass do?
4. What happens if you delete a Nearline object 10 days after uploading it?
5. Which storage class is best suited for data accessed roughly once a year, such as long-term compliance archives?
Was this page helpful?
You May Also Like
Cloud Storage Basics
An introduction to Google Cloud Storage's object model — buckets, objects, naming, access control, and the durability and consistency guarantees behind it.
Choosing the Right GCP Storage
A decision framework for picking between Cloud Storage, Persistent Disks, and Filestore based on access pattern, cost, and performance needs.