Business Cloud Storage Cost per User

Short answer: Business cloud storage costs an illustrative $10 to $15 per user per month on a standard rung with a pooled allowance in the low terabytes, around $18 to $20 on a business rung with more storage, and a negotiated enterprise rate above that with storage effectively unbounded. Storage overage, compliance add-ons and migration from an old file server are the lines that sit on top of the per-user rate and rarely appear on the pricing page.

Business cloud storage cost looks like the simplest line item on a software budget, a flat per-user rate for space everyone already understands, right up until the storage model turns out to be pooled rather than per-person, the overage pricing turns out to be sold in blocks rather than by the gigabyte, and the compliance add-on everyone assumes is included turns out to be a separate per-user charge on top.

This verdict prices cloud storage the way a real bill arrives. It separates pooled storage from per-user allowances, because that single modelling choice decides what a given headcount can actually store, walks the rung ladder and the gates between rungs, prices overage and the add-ons most buyers either skip or overbuy, draws a clean line against document management software so neither category gets bought by mistake, and closes with a modelled total for a small team. It sits alongside the verdict on document management software cost, which prices the more governed cousin of this category, and the verdict on the true cost of business software, which takes per seat billing apart in general. Put your own headcount through the true-cost calculator and the companion on this page before you shortlist anything.

What business cloud storage actually costs per user

Ask what cloud storage costs and the honest answer has four parts, and only one of them is the number on the pricing page.

The first is the seat licence, sold per user per month and scaling directly with headcount, which bundles a storage allowance whose size depends on the rung. The second is storage overage, which applies once the bundled allowance, pooled or per person, runs out. The third is add-ons for admin controls, compliance and data loss prevention, each priced per user on top of the base rung. The fourth is a one-time migration cost if files are moving off an old file server, a shared drive, or a sprawl of personal accounts nobody centrally owns.

Those four scale on different things. The seat licence scales with people. Overage scales with how much a team actually stores, which correlates loosely with headcount and strongly with what kind of files a team generates, video and design files filling a pool far faster than spreadsheets and documents. Add-ons scale with specific obligations rather than general caution. Migration scales with how much legacy storage exists today. A quote that shows only the seat licence is showing a minority of a real deployment’s cost.

The headline: illustrative per-user pricing by rung

Start with the number people search for, framed as a planning band rather than a quote. Cloud storage pricing is heavily promoted, bundled with other productivity tools, and revised often, so treat the figures below as a shape to verify rather than a specification.

Standard commonly lands around $10 to $15 per user per month, with a pooled storage allowance in the low terabytes across the account, basic version history, and sharing controls at the folder level.

Business commonly lands around $18 to $20 per user per month and is the rung most growing small businesses land on, typically adding a larger pooled allowance, an admin console covering the whole account, and longer version history.

Enterprise is priced on request, commonly above $25 per user per month once negotiated, bought for storage that is effectively unbounded or priced separately by the terabyte, advanced admin and security controls, and dedicated account management.

Most plans also carry a minimum seat count, commonly three to five users, below which the advertised per-user rate does not apply and a solo user is pushed toward a personal-tier product instead.

Pooled storage versus per-user allowance: the model that decides your bill

This is the single modelling decision that most changes what a given headcount can actually store, and it is rarely stated plainly on a pricing page.

A per-user allowance gives each paid seat a fixed amount, commonly one to two terabytes, and that space belongs to the account it was issued to. A person who barely uses their allowance cannot lend the unused space to a colleague whose role generates large files, which means a business with uneven usage across roles can run out of room for one person while another sits mostly empty.

A pooled allowance adds every seat’s storage into one company-wide total that any user can draw from. A fifteen-person team on a pooled plan with a two-terabyte-per-seat allowance has thirty terabytes to share across the whole company, so a video-heavy marketing function and a document-light finance function draw from the same pool rather than each being capped individually.

Pooled storage is generally the better fit for small businesses with uneven usage, which describes most of them. The practical step is to ask each vendor directly which model a specific rung uses, because the word unlimited or a per-seat terabyte figure on a comparison page does not by itself say which one you are getting.

What gates each jump between rungs

Rung names are marketing. The gates are consistent enough across the category to be worth naming, because knowing which gate sits in front of you is the difference between a considered upgrade and a surprise renewal.

The first gate is the storage allowance itself, the most obvious lever and the one most buyers compare first, even though it is rarely the gate that actually forces an upgrade in practice.

The second gate is the admin console, present in a limited form at the entry rung and covering the whole account only from business upward, including the ability to see every user’s storage, reset access, and enforce sharing policy centrally rather than per person.

The third gate is version history length, commonly a short window at entry and extending considerably at higher rungs, covered in its own section below.

The fourth gate is external sharing controls, including the ability to restrict links to specific domains or require a password, which is often absent or crude at the entry rung and genuinely useful the moment client files are being shared regularly.

The fifth gate is single sign-on, arriving at business or above on most platforms and frequently the reason an IT team pushes for the upgrade before storage capacity becomes the issue.

The free tier and when it quietly runs out

The free tier deserves honest treatment rather than dismissal, because for a very small team it can be the correct purchase for a meaningful stretch of time.

What free commonly includes: a small fixed storage amount, typically a few gigabytes up to a couple of hundred, basic file sync across devices, and simple link sharing. What it commonly excludes: any admin console for managing more than one or two people, extended version history, and any of the compliance or security add-ons covered below.

The wall most small businesses hit on a free tier is not a feature gate. It is simply running out of space, because a few hundred gigabytes disappears faster than expected once a team is sharing design files, recorded meetings, or large spreadsheets with embedded data. The second, slower wall is needing to manage access for more than a couple of people centrally, which free tiers are structurally not built to do regardless of how much storage is added.

Storage overage and the per-TB add-on block

Running out of the bundled allowance, pooled or per user, triggers one of three outcomes, and which one your plan uses materially changes the bill.

The first and most common is a fixed overage block, sold per extra terabyte per month, illustratively around $8 to $12 per block, which lets a business add exactly the headroom it needs without changing anything else about the plan. The second is gating more storage behind a rung upgrade, where the only path to additional space is paying for the next tier up, which can mean paying for admin features a business does not need just to get more room. The third, less common but worth ruling out specifically, is a plan that simply stops accepting new uploads once the pool is full until space is freed or purchased, which can interrupt work with no warning if nobody is watching the usage dashboard.

Ask each vendor directly which of the three applies, what the overage block costs at your scale, and whether usage can be monitored and alerted on before the account runs out rather than after.

Shared drives, team spaces and the admin-only storage pool

Beyond individual accounts, most business plans offer a separate shared storage space, owned by the company rather than by any one person, and it is priced and structured differently from personal storage.

A shared or team drive typically draws from the same pooled allowance as everyone’s individual storage rather than carrying its own separate limit, and its defining feature is that files inside it belong to the company rather than to whoever uploaded them, so access survives that person leaving without anyone needing to transfer ownership manually. Admin-only folders, a further layer some platforms offer, restrict creation and top-level permission changes to administrators while still letting ordinary users work inside them, which is the structure most small businesses actually want for anything company-critical, like finance records or contracts, that should not disappear or change ownership because one employee moves on.

The practical setup mistake is leaving everything in personal folders by default, which works fine until the day someone leaves and an administrator discovers nobody knows what that person’s folder contained or who should inherit it.

External sharing, guest collaborators and link controls

Sharing files outside the company is where cloud storage earns its reputation for convenience, and also where its governance gaps show up fastest.

Entry-rung sharing is typically a simple link, anyone with the link can view or edit, with little control beyond that. Business and enterprise rungs add real controls: restricting a shared link to specific email domains, requiring a password or an expiration date on external links, and watermarking or disabling download on sensitive files shared with outside parties. A meaningful share of accidental external exposure in this category traces back to a link created with the default, most permissive setting rather than a deliberate choice, because the default is rarely the safest option.

The low-cost fix is a company-wide default policy, set once in the admin console at the business rung and above, that requires external links to expire or be domain-restricted unless someone deliberately overrides it. That single setting does more to limit exposure than any amount of after-the-fact auditing.

Version history and how long it is really kept

Version history is the cheapest feature in this category to describe and the easiest to misjudge the value of until the day it matters.

Entry rungs commonly keep deleted files and prior versions for a short window, illustratively around thirty days, after which they are gone for good. Higher rungs extend that window substantially, sometimes to a year or more, and some providers sell unlimited version retention as a specific, separately priced add-on rather than including it at any standard rung.

The window matters most during an incident rather than during ordinary work: a ransomware event, a bulk accidental deletion, or a sync error that overwrites good files with bad ones. If nobody notices within the retention window, the clean versions are gone regardless of how good the rest of the product is. Confirm the exact number of days in writing rather than trusting the word unlimited, which on some plans describes how many versions are kept rather than how long they are kept for.

Sync clients, selective sync and the local-disk cost nobody counts

Cloud storage is not purely a cloud cost, and the local side of the sync client is a real expense that never appears on a vendor’s pricing page.

Every synced file, by default, occupies space on the local device it syncs to, which means a company-wide pool measured in terabytes can quietly require terabytes of free space on every laptop that syncs the whole thing. Selective sync, choosing which folders actually download locally versus staying cloud-only until opened, is the practical fix, and it is present on every major platform but defaults to off or partially configured on many installs.

The cost that surfaces here is not a line on the vendor’s invoice. It is a hardware refresh cycle that arrives sooner than it should, because laptops bought with storage sized for a pre-cloud-storage world fill up fast once a large shared pool is syncing in full by default. Checking selective sync settings during rollout is one of the cheapest and least obvious cost controls in this category.

Admin console, device approval and the controls that gate the top rung

The top rung in this category is bought for administration far more often than for storage space, which is a pattern this category shares with most per-seat software here.

Device approval, the ability to see and revoke which specific laptops and phones are syncing company files, and to remotely wipe company data from a lost or stolen device without touching personal data on the same device, is a genuine security control that only exists at the higher rungs. Granular sharing policy, setting company-wide rules on external links rather than relying on individual judgement, sits alongside it. Detailed activity logging, who accessed, shared, or deleted what and when, rounds out the set.

None of that shows up in a demo focused on file sync speed, which is exactly why it gets underpriced by whoever evaluates the product against whoever will actually have to administer it once something goes wrong.

Single sign-on and the enterprise security add-on

Single sign-on earns its own section because it is one of the most common reasons a company upgrades for a reason that has nothing to do with storage at all.

Without it, every cloud storage account is one more separate password an IT team cannot centrally reset, revoke, or require multi-factor authentication on. With it, the storage account authenticates through the same identity provider as the rest of the company’s software, so offboarding one departing employee in one place closes every door, including the one holding every file they ever synced.

Single sign-on typically arrives at the business rung, sometimes gated specifically to an add-on even above that on some platforms. A company that already runs single sign-on everywhere else and leaves one storage product as the exception has created exactly the kind of gap that surfaces during a security review rather than during ordinary daily use, which is a more expensive time to find it.

eDiscovery, legal hold and compliance add-ons

Compliance add-ons are priced per user on top of the base rung, illustratively around $5 to $8, and they are worth buying against a specific named obligation rather than speculatively.

A legal hold preserves files relevant to active or anticipated litigation, overriding normal deletion and version-cleanup schedules for exactly the files a hold applies to. eDiscovery search lets an administrator or counsel search across the whole account’s content and metadata to respond to a legal request, rather than hoping someone remembers where a relevant file lives. An audit trail, who viewed, edited, downloaded or deleted a file, satisfies the kind of question a regulator or a client contract sometimes requires an answer to.

If none of those describes a real, current obligation, the add-on is a speculative purchase, and speculative compliance spend is one of the more common overspends in this category specifically because it sounds responsible to buy. If retention, audit trails and document-level permissions are the actual core requirement rather than an occasional add-on, that need is usually served better and more completely by dedicated document management software, which the FAQ above and the linked verdict cover directly.

Data loss prevention and classification add-ons

Data loss prevention, commonly abbreviated DLP, is a newer and more expensive add-on category, priced illustratively around $4 to $7 per user per month, and it solves a narrower problem than its name suggests.

What it actually does is scan files for patterns that look like sensitive data, a credit card number, a national identification number, a string that matches a client list format, and either block or flag an action, like sharing externally or downloading to an unmanaged device, that would expose it. What it does not do is understand context the way a person would, so a DLP rule tuned too broadly generates a stream of false flags that teams learn to ignore, which defeats the purpose it was bought for.

The add-on earns its cost when a business handles a genuine volume of regulated or sensitive data and has someone who will tune and review the rules. Bought and switched on with default settings and left alone, it is closer to a compliance checkbox than a working control, and the per-user cost accrues either way.

Migrating an existing file server or legacy storage in

Moving files out of an old on-premises file server, a sprawl of personal cloud accounts, or a previous vendor’s storage is a one-time project with its own cost shape, separate from the ongoing subscription.

Most vendors or their partners price migration either as a flat project fee, illustratively a few hundred to a couple of thousand dollars for a small business’s typical volume, or per terabyte moved, which scales more predictably for a larger legacy estate. The work itself covers mapping old folder structures and permissions onto the new platform’s model, which is rarely a clean one-to-one translation, and running the sync in parallel long enough to confirm nothing was lost or duplicated before decommissioning the old system.

The practical cost control is deciding what genuinely needs to move rather than migrating everything by default. A decade-old file server commonly holds a meaningful share of files nobody has opened in years, and migrating those at a per-terabyte rate is paying to move data that could instead be archived cheaply or retired on a retention schedule, a decision the verdict on migrating to new software covers in more general terms.

A worked example: a fifteen-person small business team

Fifteen people need business-rung accounts. The business rung at an illustrative $20 covers a pooled multi-terabyte allowance, full admin console and single sign-on. No compliance or DLP add-on is needed. A modest migration project moves three terabytes off an old file server.

Seat licences: $20 times 15 is $300 a month, so $3,600 a year. Migration: an illustrative $900 one time for the three-terabyte project. First year total: $3,600 plus $900 is $4,500, an effective $25 per user per month once migration is spread across the fifteen seats.

Add the compliance add-on for two people who handle contracts and need a defensible record, at an illustrative $8 each, and the recurring bill rises by $192 a year to $3,792, moving the effective first-year figure to $25.07 per user per month, a small change that shows how targeted add-on buying, two seats rather than fifteen, keeps the category’s cost close to its sticker.

First-year cost breakdown

A worked three-rung total: 15, 50 and 200 person teams

Fifteen people, business rung, one small migration. As modelled above: $4,500 in a first year, about $25 per user per month.

Fifty people, business rung, storage overage of two extra blocks, compliance add-on for an eight-person finance and legal group. Seat licences at $20 are $1,000 a month, $12,000 a year. Overage at $10 a block for two blocks is $20 a month, $240 a year. Compliance add-on for eight people at $8 is $64 a month, $768 a year. Migration for a larger legacy estate, illustratively $2,500 one time. First year: $12,000 plus $240 plus $768 plus $2,500 is $15,508, about $25.85 per user per month.

Two hundred people, enterprise rung, DLP across the account, compliance add-on for a thirty-person regulated team, single sign-on included. Seat licences at an illustrative $28 negotiated enterprise rate are $5,600 a month, $67,200 a year. DLP across two hundred people at $5 is $1,000 a month, $12,000 a year. Compliance add-on for thirty people at $8 is $240 a month, $2,880 a year. Migration for a large legacy estate, illustratively $6,000 one time. First year: $67,200 plus $12,000 plus $2,880 plus $6,000 is $88,080, about $36.70 per user per month.

Why cost per user does not fall cleanly with scale

In many software categories the effective cost per user falls as a company grows, because fixed costs spread across more people. Cloud storage follows that pattern loosely at the low end and then breaks from it once add-ons enter the picture, as the three worked examples show: $25.00, then $25.85, then $36.70 per user per month, roughly flat before rising sharply.

Two structural reasons sit behind the later rise. Add-on adoption, DLP and compliance in particular, tends to arrive as a company grows into regulated work or a larger regulated subset of its staff, which a fifteen-person business rarely needs and a two-hundred-person one often does. And enterprise-rung negotiated rates, while discounted against list, still sit above the business rung smaller companies use, because the admin depth that justifies the rung costs the vendor more to support regardless of company size.

The counterweight is negotiation, which genuinely does move at volume in this category. A two-hundred-seat deal paying list price has not been negotiated, and discounts against list, bundled migration services, and waived setup fees are available at that scale in a way they are not for a fifteen-seat account. Run your own headcount through the true-cost calculator and the companion to see where your version of that curve sits.

Signs your cloud storage bill has drifted

Cloud storage bills drift quietly because usage, unlike a clean seat count, is rarely reconciled against who actually needs access or storage. Five signals are worth checking annually.

Seats outnumber active users. Storage accounts are rarely deactivated when someone leaves, because files tied to that account can feel risky to touch, and a seat left live for that reason is pure recurring cost.

Storage overage with no explanation. A rising overage charge with no corresponding project or new hire usually means old files are accumulating with nobody reviewing what can be archived or deleted.

A compliance or DLP add-on applied company-wide for one team’s need. Bought during a rollout and never scoped down, this is one of the more expensive forms of drift in this category because it is priced per user.

External links created with no expiration. A rising count of permanent, unrestricted external links is worth auditing before one of them becomes the exposure this category’s security add-ons exist to prevent.

A renewal rate that moved without review. Compare the current effective per-user rate to what was signed, not to the current pricing page.

What to ask a vendor before you sign

Eight questions, all answerable in writing, all of which change the real number.

Is storage pooled across the company or fixed per user at the rung we are quoted? This single question decides what our headcount can actually store.

What does overage cost, and is it sold in blocks or gated behind a rung upgrade?

What is the exact version history and deleted-file retention window in days, not just the word unlimited?

Is single sign-on included at our rung, or is it a further add-on?

What specifically does the compliance add-on cover, and do we have a named obligation that requires it?

What does DLP actually flag, and who on our side will tune and review its rules?

What does migration from our current storage cost, priced against our real volume rather than a generic estimate?

What happens to our rate at renewal if we do nothing?

The bottom line

Business cloud storage is priced simply on the surface, a flat per-user rate for space everyone already understands, and that simplicity is exactly why the real cost hides in three places: whether storage is pooled or fixed per person, what happens the day the allowance runs out, and which add-ons were bought on a general sense of caution rather than a named obligation.

The parts that decide your actual number are structural rather than promotional. Whether your rung pools storage across the company or locks it per seat. Whether overage is a clean per-block add-on or a forced rung upgrade. Whether compliance and DLP add-ons are scoped to the people who actually need them or applied company-wide out of convenience. And whether your real need is cloud storage at all, or the more governed, more expensive document management category covered separately on this site.

On the illustrative figures modelled here, a fifteen-person small team lands near $25 per user per month in a first year, holding close to that level at fifty users and climbing toward $37 only once a two-hundred-person company adds enterprise negotiated rates, DLP and compliance across a meaningful share of its staff. None of those are quotations and all of them are the same lesson: confirm the storage model in writing, price add-ons against a real obligation, and ask every vendor for an all-in per-user figure before you compare a single sticker price.

VetLoft is funded by its readers rather than by the vendors it prices, and this verdict is written on that footing: educational material only, not procurement, IT or legal advice for your organisation. Every seat rate, overage figure, add-on price, migration estimate and worked total above is an illustrative planning number chosen to show how per-user cloud storage billing behaves, not a quotation from any provider, and pricing in this category is bundled, discounted and revised often enough that a figure typical when this was written may read differently by the time you shop. Which capability sits at which rung varies by provider and shifts between releases, so read the ladder here as a shape to verify rather than a specification. Confirm the storage model, overage pricing, retention windows, add-on scope, migration cost and renewal terms directly with each provider in writing before relying on any figure here.