Object storage tiers across AWS S3, Azure Blob Storage and Google Cloud Storage follow one principle: the colder the tier, the lower the price per gigabyte to store and the higher the price to read the data back. Standard tiers cost the most to hold but nothing extra to access. Cold and archive tiers cost a fraction to hold but add retrieval fees and minimum storage durations that punish early deletion or frequent reads. Choosing the right tier is therefore not about always picking the cheapest storage line, it is about matching the tier to how often the data is actually read, because a retrieval fee on a frequently accessed object can dwarf the storage saving.
This article is part of our complete guide to cloud storage and data cost optimization, the cluster pillar it links up to. It pairs with cold and archive storage: when it pays off, which goes deeper on the break-even math for the coldest tiers.
Every cloud trades storage price against retrieval price. A colder tier saves on storage and charges on access. The right tier is the one whose access price you will rarely pay, given how the data is actually read.
The tier ladder is the same shape on every cloud
Despite different names, the three major clouds offer the same conceptual ladder. AWS S3 runs from S3 Standard through Standard-Infrequent Access and One Zone-IA, then Glacier Instant Retrieval, Glacier Flexible Retrieval and Glacier Deep Archive, with S3 Intelligent-Tiering as an automatic option. Azure Blob Storage offers Hot, Cool, Cold and Archive access tiers. Google Cloud Storage offers Standard, Nearline, Coldline and Archive. In every case you descend from frequent-access storage that costs more to hold and nothing to read, toward archive storage that costs very little to hold but adds retrieval charges and a minimum storage duration. Pricing varies by region and changes regularly, so verify the current per-gigabyte rates, retrieval fees and minimum durations in each provider's pricing documentation before committing a lifecycle policy, as of May 2026.
| Access pattern | AWS S3 | Azure Blob | Google Cloud Storage |
|---|---|---|---|
| Frequent | S3 Standard | Hot | Standard |
| Monthly or less | Standard-IA / One Zone-IA | Cool | Nearline |
| Quarterly | Glacier Instant Retrieval | Cold | Coldline |
| Rarely, archival | Glacier Flexible / Deep Archive | Archive | Archive |
| Unknown / mixed | Intelligent-Tiering | Lifecycle rules | Autoclass |
The fees that catch people out
The storage price per gigabyte is the number everyone compares, and it is the wrong one to fixate on alone. Three other charges decide whether a tier actually saves money. Retrieval fees apply when you read data from cooler tiers, charged per gigabyte retrieved, and they can be large for archive tiers. Minimum storage durations mean an object deleted before a set number of days, typically thirty for cool tiers and ninety or more for archive, is still billed for the full minimum, so churny data in a cold tier costs more than in standard. And per-request charges for operations are higher on cooler tiers. The result is a counterintuitive rule: putting frequently read or short-lived data into a cold tier can cost more than leaving it hot, because the access and minimum-duration charges overwhelm the storage saving.
Want your storage on the right tiers automatically?
Our cloud cost audit profiles access patterns across your buckets, sets lifecycle policies that move data to the cheapest tier it actually fits, and proves the saving against a clean baseline on AWS, Azure, GCP and OCI. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →How to pick the right tier
The decision comes down to one measurement: how often is this data actually read? Data read daily or near-daily belongs in the standard or hot tier, where there is no retrieval penalty. Data read a few times a month fits the infrequent-access or cool equivalent, where the lower storage price beats the modest retrieval fee. Data read a few times a year fits coldline or its equivalents. Data you keep only for compliance and almost never read fits archive, where the storage price is lowest and the rare retrieval fee is worth paying. The way to get this right at scale is not to guess per object but to let the cloud move data automatically based on observed access, the subject of tiering data automatically by access pattern.
Automatic tiering versus manual lifecycle rules
You have two ways to put data on the right tier. Manual lifecycle rules transition objects on a schedule, for example to a cool tier after thirty days and archive after ninety, which works well when access genuinely tracks age. Automatic tiering, S3 Intelligent-Tiering on AWS and Autoclass on Google Cloud, moves objects between tiers based on actual access and removes the guesswork, at the cost of a small monitoring fee per object. For large buckets with unpredictable or mixed access, automatic tiering usually wins because it never strands a hot object in a cold tier or pays retrieval fees for misjudged data. For data with a clean age-based lifecycle, manual rules are cheaper because they carry no monitoring fee. Building those rules well is covered in building a storage lifecycle policy.
The Cloud Storage and Egress Cost Playbook includes the tier-selection matrix and the lifecycle rule templates we use to place data on the cheapest fitting tier across all three clouds.
Do not forget egress and redundancy
Tier choice is only part of the storage bill. Reading data out of the cloud entirely incurs egress charges that are separate from and often larger than storage and retrieval fees, the subject of data egress charges explained. And every tier has redundancy options, single-region, multi-region and zone-redundant, that multiply the storage price. A multi-region bucket in a hot tier is among the most expensive ways to hold data, while a single-region archive object is among the cheapest. Getting the full storage bill down means choosing the tier, the redundancy and the egress path together rather than optimizing one in isolation, which is exactly the See and Cut work in our See, Cut, Lock, Run method.
The short version
Object storage tiers across AWS, Azure and GCP share one shape: colder tiers cost less to store and more to read, with retrieval fees and minimum durations that punish frequent or short-lived data placed too cold. Pick the tier from how often the data is actually read, use automatic tiering for unpredictable access and manual lifecycle rules for clean age-based patterns, and account for egress and redundancy at the same time. Verify current rates per provider, since they change. When you want your storage placed on the right tiers and the saving proven across the estate, that is part of what our rightsizing and waste elimination service delivers.