Azure Blob storage tiers cost: hot, cool, cold, and archive compared

Quick answer

Azure Blob storage has four access tiers that trade storage cost against access cost and retrieval time: hot (highest storage price, cheapest and instant access, for frequently used data), cool (lower storage price, higher access cost, for infrequently accessed data held at least 30 days), cold (lower still, for rarely accessed data held at least 90 days), and archive (lowest storage price by far, but data is offline and needs a rehydration step of up to hours to read, for long-term retention). The rule: the colder the tier, the cheaper to store and the more expensive and slower to access. Match each dataset to how often you actually read it.

Azure Blob storage lets you place each blob in an access tier tuned to how often you read it, and the price differences between tiers are large. Storing rarely-accessed data in the hot tier, or actively-served data in archive, both waste money. Matching data to the right tier is one of the simplest, highest-return storage optimizations on Azure.

The four tiers

Tier	Storage price	Access cost / latency	Use for
Hot	Highest	Lowest cost, instant	Frequently accessed data
Cool	Lower	Higher access cost, instant	Infrequent, held 30+ days
Cold	Lower still	Higher access cost, instant	Rare access, held 90+ days
Archive	Lowest by far	Highest, offline, rehydrate to read	Long-term retention

The tiers trade storage price against access price and latency. Hot costs the most to store but the least to read, and reads are instant. Cool and cold progressively lower the storage price while raising the per-read cost, still with instant access, and carry minimum retention periods (about 30 and 90 days) below which early deletion incurs a charge. Archive is the cheapest to store by a wide margin but the data is offline: to read it you must rehydrate the blob, which can take hours and costs a retrieval fee.

Why the access-cost tradeoff matters

The colder tiers are cheaper to store but more expensive to access, so they only save money if you rarely read the data. A dataset in cool or cold that you actually access frequently can cost more in total than leaving it hot, because the access charges pile up. This is the crucial subtlety: tiering is not free savings, it is a bet that you will rarely read the data, and it pays off only when that bet is right. This mirrors the S3 tier logic in object storage compared.

Archive and the rehydration catch

Archive is tempting because the storage price is so low, but archived data is offline. Reading it requires rehydration, which takes up to hours (standard priority) or less for high priority at extra cost, plus a per-GB retrieval fee. So archive suits data you must retain but almost never read: compliance records, long-term backups, old logs. If you might need the data quickly, archive's retrieval latency makes it unsuitable regardless of the low storage price.

Matching data to tiers

Put actively-used data in hot, infrequently-accessed data in cool or cold (respecting the minimum retention periods), and long-term retention you rarely read in archive. Use lifecycle management policies to move blobs automatically as they age (hot to cool to cold to archive), so the tiering happens without manual effort. Watch the early-deletion and retrieval charges so a policy does not move data too aggressively and trigger fees. And because storage prices vary by region, checkingAzure region pricing is worth a look for large datasets. Done well, tiering can cut a storage bill substantially with no loss of function.

FAQ

What are the Azure Blob storage tiers?

Four access tiers: hot (highest storage price, cheapest and instant access, for frequently used data), cool (lower storage price, higher access cost, for infrequent data held at least 30 days), cold (lower still, for rarely accessed data held at least 90 days), and archive (lowest storage price by far, but data is offline and needs rehydration of up to hours to read, for long-term retention). The colder the tier, the cheaper to store and the more expensive and slower to access.

Which Azure Blob tier is cheapest?

Archive is by far the cheapest to store, but the data is offline: reading it requires a rehydration step that can take hours plus a per-GB retrieval fee, so it only suits data you almost never read. Among the instant-access tiers, cold is cheapest to store, then cool, then hot. But cheaper storage tiers charge more per access, so the truly cheapest tier for a given dataset depends on how often you read it.

What is the difference between cool and cold tiers in Azure?

Both offer instant access at a lower storage price than hot, with higher per-access costs. Cold is cheaper to store than cool but has a longer minimum retention period (about 90 days versus about 30 for cool) and somewhat higher access costs. Use cool for infrequently accessed data and cold for even rarer access you still need instantly, respecting each tier's minimum retention to avoid early-deletion charges.

Is Azure archive tier worth it?

For data you must retain but almost never read, yes, the storage price is dramatically lower than any other tier. The catch is that archived data is offline: reading it requires rehydration that can take hours (or less at higher priority and cost) plus a per-GB retrieval fee. So archive suits compliance records, long-term backups, and old logs, but is unsuitable if you might need the data quickly, regardless of the low storage price.

Can moving data to a cooler tier cost more?

Yes. Cooler tiers are cheaper to store but more expensive to access, so if you move frequently-read data to cool, cold, or archive, the access charges can exceed the storage savings and cost more in total. Tiering is a bet that you will rarely read the data; it only pays off when that bet is right. Also watch early-deletion charges if you move data out before its minimum retention period.

Does C3X price Azure Blob storage?

C3X prices infrastructure from Terraform before deploy against a live catalog, so an Azure storage account and its configured access tier are costed in the pull request. Because access and retrieval charges depend on runtime usage, the exact bill varies with how often you read the data, but seeing the storage tier and its base cost before deploy helps you match data to the right tier from the start.

What to do next

Match your storage to the right tier before you deploy. C3X prices your Terraform against a live resource catalog. Start with the quickstart.