Azure Blob Storage Pricing: The Egress Trap Nobody Warns You About (2026)

The $0.023 That Was Never the Problem

In 2023, deep into building Clickly — my Bitly-style URL shortener that never made a rupee — I needed somewhere to dump files. Not the click data (that lived in Postgres), but the boring stuff: user avatars, QR-code PNGs, a few demo videos for the landing page. Object storage. The most solved problem in computing.

I opened the Azure pricing calculator because a former colleague swore Azure Blob was “basically free.” And on paper, it was. Two cents per gigabyte per month. I did the mental math for a hundred users with a few MB each and laughed. This would cost me less than a chai.

Then I actually read the rest of the page. And the rest of the page is where they keep the real money.

That afternoon taught me the single most important thing about every hyperscaler’s object storage — Azure, AWS S3, Google, all of them. The price to store your data is bait. The price to serve it is the business. Let me break down exactly how Azure Blob Storage prices in 2026, where the traps are hiding, and why a broke founder should probably run somewhere else entirely.

---

How Azure Actually Prices Blob Storage

Azure Blob has four “access tiers,” and the whole model is a bet: the less often you read your data, the cheaper it is to keep, and the more it costs to pull back out. Here’s the sticker price (standard general-purpose v2, LRS redundancy, first 50 TB):

Tier	Storage / GB / mo	Best for	The catch
Hot	~$0.023	Files served constantly	Highest storage cost
Cool	~$0.013	Accessed monthly-ish	30-day early-deletion fee
Cold	~$0.004	Quarterly access	90-day early-deletion fee
Archive	~$0.00099	Cold backups, compliance	Hours to retrieve, 180-day lock

Look at that Archive number. A tenth of a cent per GB. You could park a terabyte of old backups for about a dollar a month. This is the number people screenshot and post as “cloud storage is basically free now.”

And for storage alone, it’s true. The problem is that nobody stores data for the joy of storing it. You store it to give it back to someone. And giving it back is a completely separate menu.

---

The Part They Don’t Put on the Sticker

Three things bill on top of that clean per-GB number, and Azure’s own pricing page splits them across different tables so you never see the total in one place.

1. Egress — the bandwidth to send your files to the internet. This is the big one. Azure gives you the first 100 GB per month free, and after that you pay roughly $0.087 per GB for the first 10 TB out of a Zone 1 region (US, EU, UK). Ingress — uploading to Azure — is free. It’s the leaving that costs.

Sit with that asymmetry for a second. Storing a gigabyte in Hot: 2.3 cents a month. Serving that same gigabyte to your users just once: 8.7 cents. Serving your data once costs nearly four times more than storing it for a month. If your files get downloaded even a handful of times, the storage line on your bill becomes a rounding error and bandwidth becomes the whole invoice.

2. Transactions — you pay per operation. Every read, write, and list is metered. On Hot it’s about $0.081 per 10,000 writes and $0.005 per 10,000 reads — cheap enough to ignore at small scale. But it climbs sharply as tiers get colder, which brings us to the nastiest line:

3. Retrieval fees on cold tiers. This is the trap inside the trap. Cold and Archive look almost free to hold, but reading from them costs extra per gigabyte retrieved, plus punishing per-operation fees. Reading from Archive runs about $6.50 per 10,000 operations — that’s not a typo, it’s roughly 1,300× the Hot read rate — on top of a per-GB retrieval charge and a multi-hour wait. Cold tier retrieval adds about $0.03/GB. People dump data into Archive to save money, forget about it, then get walloped the day they actually need it back.

So the real cost of an Azure blob isn’t one number. It’s storage + egress + transactions + retrieval, and the tier you pick just shuffles which of those four buckets hurts.

---

The Math That Ruined My Afternoon

Let me make it concrete, because this is the calculation I ran in 2023 that made me close the tab.

Say you’ve built a modest little app. A few thousand users, some image uploads, a couple of demo videos, nothing wild. You’re storing 200 GB and serving 1 TB of egress a month — that’s not viral, that’s just “a real product with real usage.”

• Storage (Hot): 200 GB × $0.023 = $4.60/mo. Fine. Great, even.
• Egress: ~1,024 GB minus the free 100 = 924 GB × $0.087 ≈ $80/mo.
• Plus transaction fees on top.

Eighty dollars. For bandwidth. On a product that might be making nothing yet. That’s the exact $80–$90/month tax I paid for years on a product with $0 MRR — except this time it’s just to hand my own files back to my own users. (If that monthly-burn dread sounds familiar, I added up everything it really costs to run a SaaS line by line.)

And the storage — the thing the whole pricing page is built to advertise — was five dollars. The bait was $4.60. The hook was $80.

This is not an Azure-specific villain, to be clear. S3 does the same thing (its egress is around $0.09/GB, basically identical). Google Cloud too. It’s the hyperscaler model: get you in with cheap storage, bill you forever on bandwidth, and make leaving expensive enough that migrating feels harder than just paying. I ranted about this whole family of clouds in Azure vs AWS for a broke founder — the short version being you probably want neither yet.

---

What a Bootstrapper Should Actually Use

Here’s the good news, and it’s the reason I write these posts at all: once you know the egress game exists, you can just… refuse to play it. There’s a whole category of S3-compatible storage that charges zero for egress, and for 90% of what a solo founder builds, it’s strictly better.

Cloudflare R2 — the zero-egress default

Cloudflare R2 is the one that broke the model open. Storage is about $0.015/GB/month and egress is $0 — not “100 GB free then billed,” genuinely zero, forever. You pay for storage and for operations (roughly $4.50 per million writes, $0.36 per million reads), and that’s the whole bill. The free tier is generous too: 10 GB of storage, a million writes, and ten million reads a month before you pay a paisa.

Run my earlier example on R2: 200 GB stored is $3/month, and that 1 TB of egress that cost $80 on Azure costs nothing. Same files, same users, same traffic — the bill goes from ~$85 to ~$3. This isn’t a small optimization. It’s the difference between a product that can afford to have users and one that can’t.

Bunny Storage — my actual pick

If you’ve read me before you know where this is going. Bunny Storage is $0.01/GB/month for standard (HDD) storage, and crucially, traffic from your storage into Bunny’s CDN is free — so you get storage and a genuinely fast global CDN in one product with no egress ambush. Minimum spend is a dollar a month. One. Dollar. It’s an S3 + CloudFront replacement for the price of nothing, and it’s the setup I’ve quietly used across projects for years. I wrote the full love letter to Bunny here if you want the deep dive — it started with this exact fear of egress costs.

DigitalOcean Spaces — flat and boring (a compliment)

If you hate metered pricing entirely, DigitalOcean Spaces is the flat-rate answer: $5/month gets you 250 GB of storage and 1 TB of outbound transfer, with a CDN included. Overages are $0.02/GB. For a predictable monthly number with a built-in CDN and no math, it’s hard to beat — and it fits neatly with the rest of the DigitalOcean ecosystem if you’re already there. (It shows up in my tier list of cheap places to deploy for the same reason: it’s the AWS-for-humans of storage.)

---

When Azure Blob Actually Makes Sense

I’m not going to pretend Azure Blob is bad software. It’s rock-solid, it scales to petabytes, and the tiering model is genuinely clever for the right workload. Reach for it when:

• You already live in Azure. If your compute, your identity, your whole stack is on Azure and traffic stays inside the same region, egress to the internet isn’t your main cost — and staying in one ecosystem has real value.
• You have a compliance or enterprise contract that mandates it, or committed-use discounts that change the math entirely.
• You’re genuinely archiving — cold backups you’ll almost never read, where Archive’s tenth-of-a-cent storage is the whole point and you’ve planned for the retrieval cost.

For a bootstrapper serving files to the public internet, though? None of those usually apply. You’re not archiving — you’re serving. And serving is the one thing the hyperscalers price to punish.

---

The Bottom Line

Azure Blob Storage pricing isn’t a lie. It’s just told in the wrong order. The two-cent-per-GB storage number is real and it’s front-and-center; the eight-cent-per-GB egress, the per-transaction metering, and the brutal cold-tier retrieval fees are real too, and they’re the part you actually pay. Read the whole menu, not the appetizer.

The lesson I dragged out of that 2023 afternoon is one line: object storage is cheap to hold and expensive to hand out. So when you’re broke and every dollar is a punch to the gut, pick a provider that doesn’t charge you to hand things out at all. Cloudflare R2 or Bunny for zero egress, DigitalOcean Spaces if you want one flat number. Save Azure for the day you have an enterprise contract and someone else’s money to spend on the bandwidth.

This is the Broken Engineer Guide — I over-engineer everything, fail at business, and read the fine print so you don’t get a surprise invoice. Go build something, and keep your egress bill boring.