What does this calculator do?
Raw capacity is what the drives add up to; usable capacity is what applications can actually store. The difference is made of several separate deductions, and this calculator applies them in order and shows each one: a reserved percentage for spare space, snapshots or vendor reserve; a filesystem and metadata overhead percentage applied to what is left; and finally a replication factor that divides the result, because storing every object three times leaves a third of the space. Deductions are applied multiplicatively, not added together, which is how they actually compose. Units follow the standards exactly: kB, MB, GB and TB are powers of ten (1 GB = 10⁹ bytes) while KiB, MiB, GiB and TiB are powers of two (1 GiB = 2³⁰ bytes). The two ladders are never mixed, so "1 GB = 1024 MB" is not treated as a universal rule.
Formula
Each percentage applies to what the previous step left behind.
usable = raw × (1 − reserved ÷ 100) × (1 − overhead ÷ 100) usableAfterReplication = usable ÷ replicationFactor lostToReserve = raw × reserved ÷ 100 lostToOverhead = raw × (1 − reserved ÷ 100) × overhead ÷ 100
How to use it
Enter the raw capacity — the sum of all drive capacities, or the nominal capacity of an array from the RAID Capacity Calculator. Set the reserved percentage for anything held back before the filesystem sees it, and the overhead percentage for filesystem structures, metadata and journals. Set the replication factor only for systems that keep multiple full copies, such as a three-way replicated object store or a distributed filesystem; leave it at 1 for a single copy.
Worked example
100 TB raw with a 5% reserve and 3% filesystem overhead: the reserve takes 5 TB, the overhead then takes 3% of the remaining 95 TB, which is 2.85 TB, leaving 92.15 TB usable — 92.15% of raw. With a replication factor of 3 the same array offers about 30.7167 TB of usable application capacity.
Frequently asked questions
Why not just add 5% and 3% into 8%?
Because the second percentage applies to what remains after the first, not to the original total. Sequentially the loss is 7.85 TB, not 8 TB. The gap grows as the percentages get larger.
What belongs in "reserved"?
Anything held back before the filesystem: vendor over-provisioning, hot spares you have already excluded from raw, snapshot reserve, and any capacity policy that keeps a pool from running past a threshold.
Does replication change my raw capacity?
No — it changes how much unique data fits in it. A replication factor of 3 means each object is stored three times, so 92 TB of usable space holds about 31 TB of unique data.
Sources
- SNIA Dictionary — vendor-neutral definitions of RAID levels, stripe, mirror, parity, IOPS and raw versus usable capacity.
- NIST — Prefixes for binary multiples (IEC 80000-13): a drive sold as 2 TB (2 × 10¹² bytes) is about 1.82 TiB as reported by most operating systems, which is why raw and usable figures are shown in the unit you choose.
- Nominal equal-drive capacity model used here: RAID 0 = N × S, RAID 1 = S, RAID 5 = (N−1) × S, RAID 6 = (N−2) × S, RAID 10 = (N/2) × S. Filesystem overhead, metadata, hot spares, vendor reservations, compression and deduplication are not modelled unless you enter them.
- Reviewed: 2026-08-10
Related calculators
Last updated: 2026-08-10 · v1.0.0 · Report an error