Synology Space Calculator
Your pool says 20 TB but your files only get 15. Enter the raw pool size and your DSM services to find every missing terabyte.
The total raw space of the storage pool in advertised terabytes.
DSM 7 is leaner with system metadata than DSM 6.
Space kept for Btrfs snapshots of shared folders. Enter 0 if you do not use snapshots.
Space held by files sitting in shared folder recycle bins. Enter 0 if recycle bins are disabled.
It is the most common mystery in home storage: you built a 20 TB pool, yet Storage Manager insists you have barely 15 TB for your files. No drive has failed and nothing looks wrong, because nothing is wrong. Between the raw pool and your files sit four quiet consumers of space: the decimal-to-binary unit conversion, DSM’s own system overhead, the room your snapshots occupy, and the files rotting in recycle bins you forgot to empty. The Synology Space Calculator above audits all four. Enter your raw pool capacity, your DSM version, and the percentage of space you want reserved for snapshots and recycle bins, and it shows your true usable space plus a line-by-line account of where every terabyte went.
What This Tool Audits
This calculator answers the overhead question: starting from the raw capacity of a storage pool, how much space actually ends up available for your files and folders? It works top-down from the pool size, subtracting each layer in turn. First the unit conversion, because the pool is measured in advertised terabytes while DSM thinks in tebibytes. Then the DSM system overhead, the metadata and system structures the operating system keeps. Then your snapshot reserve, the space Btrfs snapshots of your shared folders consume as your data changes. Finally the recycle bin reserve, the space held by deleted files that have not been emptied yet. What remains is the true usable space. Unlike a per-disk calculator, which measures one drive, or a RAID planner, which combines drives, this tool starts where those tools stop: the finished pool, and everything that nibbles at it afterward.
How to Use the Synology Space Calculator
Enter the raw pool capacity in terabytes, the total raw space of your storage pool before any of the deductions. Next, choose your DSM version: DSM 7.x is the current generation with leaner system metadata, while DSM 6.x carries slightly higher overhead. Then enter the snapshot reserve as a percentage; 10 percent is a sensible default for active snapshot schedules, and enter 0 if you do not use snapshots at all. Then enter the recycle bin reserve as a percentage; 5 percent is typical for shared folders with recycle bins enabled, and 0 if you keep bins disabled or emptied. Press Calculate to see your true usable space in large type, followed by the full audit: the pool in TiB, the unit conversion loss, the DSM overhead, the snapshot reserve, the recycle bin reserve, and the final usable figure. If an input is invalid, the calculator explains the problem instead of guessing.
The Overhead Formula Explained
The audit runs in five steps. Step one converts the raw pool to tebibytes with the standard factor (1000 ÷ 1024)⁴, about 0.9095, so a 20 TB pool becomes 18.19 TiB and the missing 1.81 TB is the unit conversion loss, the single biggest deduction. Step two subtracts the DSM system overhead: about 1 percent of the pool on DSM 7 and about 1.5 percent on DSM 6, covering the system partitions, volume metadata, and the structures DSM maintains. Step three computes the snapshot reserve as your chosen percentage of the remaining space: with 10 percent on an 18.01 TiB remainder, that is 1.80 TiB held back for snapshots. Step four computes the recycle bin reserve the same way: 5 percent of the remainder is 0.90 TiB of deleted-but-not-emptied files. Step five subtracts both reserves from the remainder: usable = remainder − snapshot reserve − recycle bin reserve. Each layer is a percentage of what is left, not of the original pool, which mirrors how the space is actually consumed.
Worked Examples
Example one. A 20 TB pool on DSM 7 with a 10 percent snapshot reserve and a 5 percent recycle bin reserve. Step one, convert: 20 × 0.9095 = 18.19 TiB, so the unit conversion loss is 20 − 18.19 = 1.81 TB. Step two, DSM 7 overhead is 1 percent: 18.19 × 0.01 = 0.18 TiB, leaving a remainder of 18.19 − 0.18 = 18.01 TiB. Step three, the snapshot reserve is 18.01 × 0.10 = 1.80 TiB. Step four, the recycle bin reserve is 18.01 × 0.05 = 0.90 TiB. Step five, usable space is 18.01 − 1.80 − 0.90 = 15.31 TiB. The calculator shows 15.31 TiB as the true usable space. Nearly five terabytes of the advertised twenty never reach your files, and now you can see each layer’s share.
Example two. A 12 TB pool on DSM 7 with no snapshots and a 10 percent recycle bin reserve. Step one, convert: 12 × 0.9095 = 10.91 TiB, a unit loss of 1.09 TB. Step two, DSM 7 overhead is 1 percent: 10.91 × 0.01 = 0.11 TiB, leaving 10.91 − 0.11 = 10.80 TiB. Step three, the snapshot reserve is 0 percent, so 0 TiB. Step four, the recycle bin reserve is 10.80 × 0.10 = 1.08 TiB. Step five, usable space is 10.80 − 0 − 1.08 = 9.72 TiB. The calculator shows 9.72 TiB. Disabling snapshots reclaims a full layer, which is the cheapest capacity upgrade available.
Example three. A 30 TB pool on DSM 6 with a 20 percent snapshot reserve and a 5 percent recycle bin reserve. Step one, convert: 30 × 0.9095 = 27.28 TiB, a unit loss of 2.72 TB. Step two, DSM 6 overhead is 1.5 percent: 27.28 × 0.015 = 0.41 TiB, leaving 27.28 − 0.41 = 26.88 TiB. Step three, the snapshot reserve is 26.88 × 0.20 = 5.38 TiB. Step four, the recycle bin reserve is 26.88 × 0.05 = 1.34 TiB. Step five, usable space is 26.88 − 5.38 − 1.34 = 20.16 TiB. The calculator shows 20.16 TiB. Heavy snapshot use on an older DSM is the most expensive combination, costing nearly a third of the pool.
Understanding Your Results
The headline number is your true usable space: the capacity your files, apps, and media can actually occupy. The audit rows beneath it tell the story in order. The raw pool row restates your pool in TiB, the honest starting point. The unit conversion loss row quantifies the biggest single deduction, the price of measuring in tebibytes. The DSM overhead row shows the operating system’s cut, with the percentage labeled so you can see the DSM 7 versus DSM 6 difference. The snapshot and recycle bin rows show your chosen reserves in both percent and TiB, which makes the trade-offs concrete: every extra snapshot percent costs real terabytes. The final row restates the usable space. The most useful habit is to experiment: lower the snapshot reserve and watch the usable number climb, or raise it and see what your safety net really costs.
Common Mistakes to Avoid
The most common mistake is treating the advertised pool size as available space and filling the NAS to 100 percent of it; the pool will report full while you still think terabytes remain. The second mistake is forgetting that snapshots consume space silently: a busy snapshot schedule on changing data can eat the entire reserve, and then some, without any warning in the headline number. The third mistake is never emptying recycle bins, which turns a 5 percent reserve into a permanent tax on deleted files. The fourth mistake is upgrading DSM in your head but not in the calculator: DSM 7’s lower overhead is real, so audit with the version you actually run. The fifth mistake is stacking this tool’s result with RAID math twice; the raw pool figure you enter should already be post-RAID, because this calculator starts from the finished pool. Finally, remember these are planning reserves, not hard walls: snapshots and bins can exceed their reserves when data churns, so treat the usable figure as a target with a safety margin, not a guarantee.
Frequently Asked Questions
1. Why does my 20 TB pool only give me about 15 TB?
Four layers take their cut: the TB-to-TiB conversion removes about 1.81 TB, DSM overhead takes about 1 percent, and your snapshot and recycle bin reserves take their percentages of the rest. With 10 percent snapshots and 5 percent recycle bins, the usable total is about 15.31 TiB.
2. What is the biggest single cause of missing space?
The unit conversion. Measuring the pool in tebibytes instead of decimal terabytes removes about 9 percent of every pool before anything else happens, which dwarfs the other layers on large pools.
3. What is DSM system overhead?
The space DSM reserves for its own structures: system partitions, volume metadata, and filesystem bookkeeping. It runs about 1 percent of the pool on DSM 7 and about 1.5 percent on DSM 6.
4. Do snapshots really use that much space?
They can. Snapshots store the changed blocks between versions, so on data that changes a lot, a 10 percent reserve can fill completely. The calculator lets you price the reserve before you commit to a schedule.
5. Should I disable the recycle bin to save space?
Only if you are comfortable without a safety net. The recycle bin protects against accidental deletion, which is worth 5 percent to most users. Empty it regularly instead of disabling it.
6. What snapshot reserve percentage should I use?
Ten percent suits most home users with daily snapshots and moderate data churn. Use more if you snapshot often or keep many versions; use 0 if you do not use snapshots at all.
7. Is DSM 7 really leaner than DSM 6?
Yes, its system metadata footprint is smaller, which is why the calculator uses 1 percent overhead for DSM 7 versus 1.5 percent for DSM 6. Upgrading DSM is a small but free capacity gain.
8. Does this calculator include RAID redundancy?
No. Enter the raw pool capacity after RAID is applied, because the tool starts from the finished pool. RAID redundancy is a separate layer handled by a RAID capacity planner.
9. Can snapshots exceed their reserve?
Yes. The reserve is a planning figure, not a hard limit. Heavy data churn can push snapshot usage past it, which is why you should monitor actual snapshot consumption in Snapshot Replication.
10. Why do deleted files still use space?
Because they sit in the shared folder recycle bin until you empty it. Until then they occupy real space, which is exactly what the recycle bin reserve models.
11. How do I free up space the calculator says is reserved?
Empty your recycle bins, delete old snapshots or shorten their retention, and disable snapshot schedules on folders that do not need them. Each action returns its reserve to usable space.
12. Should I enter TiB or TB for the pool size?
Enter TB, the advertised terabytes. The calculator performs the conversion itself; entering an already-converted TiB figure would double-count the conversion loss.
13. Does the calculator work for expansion planning?
Yes. Enter the planned larger pool size to see how much usable space the expansion really buys after all four layers, which keeps upgrade expectations honest.
14. What if I use 0 percent for both reserves?
Then the usable space is simply the pool in TiB minus DSM overhead. That is the theoretical maximum, and it assumes you never snapshot and never need the recycle bin’s protection.
15. Is the usable figure guaranteed?
No, it is a planning estimate. Real snapshot consumption and recycle bin contents vary with your usage, so keep a safety margin and monitor the pool in Storage Manager.
Final Thoughts
Missing terabytes are not missing at all once you can see the layers: the unit conversion, the DSM overhead, the snapshots, and the recycle bins, each taking its documented share. The Synology Space Calculator turns that invisible stack into a visible audit, so you can set reserves deliberately, empty what you do not need, and know your true usable space before the pool fills up. Audit first, then store with confidence.