Storage is normally sold as an accessory to mail. Occasionally the ratio inverts: what you actually want is a large, cheap, mountable drive, and the mailboxes are a bonus you'll barely touch. Buying email for storage is a legitimate configuration rather than a misuse, and because the mail plan and the storage add-on price independently, the arithmetic works out better than people expect.
This page covers what the combination costs, what you get that a pure object store won't give you, and the point at which you should buy the bucket instead.
The Configuration
Buying email for storage works because of one pricing detail. The mail plan controls domains, mailboxes and pooled mail storage. The Drive add-on is separate, priced by capacity, and doesn't care which plan it sits on.
So the cheapest route to a large drive here is the free mail plan plus the add-on. That's $3.20 a month for 250 GB, $11.20 for 1 TB, $1,120 for 100 TB — with no mail-plan cost underneath it at all. You still get ten domains and a hundred mailboxes you may never use, which is harmless.
Buying email for storage this way means the only line on the invoice is the capacity. There's no seat count, no per-user minimum, and no requirement to justify the ratio to anybody.
Why This Is Unusual
Most providers won't sell you this shape at all, which is why buying email for storage sounds odd until you see the pricing model behind it.
Google and Dropbox price team storage per user, so a large pool requires a large headcount or an enterprise conversation. Three people wanting 20 TB are an awkward customer: the revenue doesn't match the seat count, so the self-serve page has no answer for them.
Object stores like Backblaze B2 will happily sell capacity without seats, and they're cheaper per gigabyte than anything here. What they won't give you is a browsable interface, a mountable drive, sharing that ordinary people can use, or the absence of egress charges. Those are the things you're paying the difference for when buying email for storage rather than renting a bucket.
What the Storage Actually Does
Worth being concrete about what buying email for storage gets you, because "cloud storage" covers a wide range of usefulness.
It mounts as a network drive over WebDAV on Windows, macOS, Linux and phones, with per-device credentials that revoke individually — the detail is in syncing files across devices.
It shares by link, revocably, with download caps, so sending somebody a large file doesn't require a second service.
It shares by folder with another account, which is how ongoing collaboration works rather than reissuing links.
It takes scripted uploads over an API, which makes it a viable backup destination — covered in push-only backups.
It doesn't charge egress. Reading your own data back costs nothing, which changes the arithmetic considerably for anything you'll actually restore.
The Mail You Didn't Come For
Since it's included, it's worth knowing what the free mail plan gives you alongside the storage, because two of these turn out to be useful even to people buying email for storage.
Ten domains with catch-all means any domain you own can start collecting mail at no cost, which is worth doing regardless — the case is in parked domain email.
And oversized attachments route into the drive automatically as you compose, so the storage and the mail actually cooperate rather than merely coexisting. That only matters if you use the mailboxes, but it's the one integration that makes the bundle more than two products on one invoice.
What you don't get on the free plan is sending, filters, aliases or forwarding. If the mail side ever becomes real, $4 a month resolves most of it.
Where the Arithmetic Turns Against Us
Being straight about this matters more than the pitch, because the wrong choice here is expensive in a boring way.
At small sizes, consumer plans beat us outright. Google One is $9.99 for 2 TB; ours is $22.40. If you want a couple of terabytes for personal use and don't need any of the above, take the consumer plan.
At large sizes with cold data, object storage beats us on rate. If you're storing 50 TB you touch twice a year and you have the engineering to work with an API-only store, B2 or its equivalents will cost a fraction as much. Buying email for storage is not the cheapest gigabyte on the market and claiming otherwise would be checkable and false.
Where we win is the middle: capacity that needs to behave like a drive, be shared with non-technical people, and cost a predictable amount whether or not you read it. Plus the top end, where 100 TB is a slider position rather than a sales call.
What Happens If You Stop Paying
Worth knowing before you commit a large archive, because storage is the one purchase where the exit matters as much as the entry.
Cancelling the add-on doesn't delete anything immediately, but the account returns to the mail plan's own allowance, and anything above it has to come down. So the practical question is how long it takes you to retrieve what you're holding. Twenty terabytes over a domestic connection is a week of continuous transfer, and that is worth measuring before you need it rather than during.
The absence of egress charges helps here more than anywhere else. Pulling everything back out costs nothing beyond time, which is not true of the object stores that beat us on the monthly rate.
Deciding Between the Three Options
A short test decides between buying email for storage, a consumer plan and a bucket.
Will several non-technical people need to reach the files? If yes, a bucket is wrong regardless of price, and either a consumer plan or this is right.
Do you need more than about 30 TB? If yes, consumer plans have stopped and it's between this and object storage.
Will you read the data back regularly? If yes, egress charges make object storage less cheap than its rate card suggests, and the comparison narrows considerably.
Is the per-gigabyte rate the only thing you care about? If yes, buy the bucket and don't look back.
Buying email for storage makes sense when two or three of those point the same way — which is more often than the framing suggests, because most people asking about large storage want it to behave like a drive rather than a database.
