Complete Proxmox storage planner
Proxmox Storage Hardware Calculator: SSD and ZFS Planner
This calculator combines the decisions that are usually split across several buying guides: guest capacity, snapshot reserve, growth, write intensity, ZFS or LVM-thin, redundancy, available interfaces and budget. The result is not an exact bill of materials; it is a conservative hardware target that tells you how many terabytes and what SSD class to price before you start shopping.
Quick answer
What complete SSD layout fits the Proxmox host?
Enter the guests you expect to run, not only the ones installed today. The planner converts those allocations into a usable-capacity target, adds reserve, maps the target to the selected redundancy level and recommends a consumer TLC or enterprise-oriented drive class. It deliberately does not treat thin provisioning as free capacity.
Live Amazon SSD listings
Current drives that fit this Proxmox decision
These cards come from this sprint's dedicated catalogue. NVMe, SATA and enterprise SSDs are classified separately. External drives, enclosures, adapters, barebones systems, multipacks and ambiguous capacity listings are rejected.
Buying decision
Calculate capacity, topology and SSD class together
Use the result as a floor, then verify the motherboard, HBA, M.2 slots, PCIe lanes and backup target. The cheapest route to “enough storage” can become expensive if it uses every slot, leaves no growth room or relies on one device for both active guests and the only backup copy.
Interactive decision tool
Proxmox Storage Hardware Calculator
Size capacity, layout and drive class before comparing SSDs. The result is planning guidance, not a substitute for checking current Proxmox documentation, motherboard slot support, exact SSD endurance specifications and independent backups.
Compatibility checklist
Four checks before buying Proxmox storage
Endurance before headline speed
VMs, databases, logs and snapshots can turn a light desktop SSD workload into sustained writes.
Redundancy changes capacity
A mirror or RAIDZ layout changes usable space, failure tolerance and the number of drives you must buy.
Interface is not the whole answer
PCIe 5.0 can benchmark faster than PCIe 4.0, but many homelab workloads are limited elsewhere.
Backups remain separate
Snapshots and mirrors improve recovery options but they do not replace an independent backup target.
Count workloads before hardware
The first input is the number of VMs and containers because every guest creates a capacity claim and some create sustained I/O. A server described only as “a Proxmox box” gives no useful sizing information. Ten tiny infrastructure containers and ten desktop VMs are different storage projects.
Use realistic future counts. The cost of buying one capacity tier higher at the start may be less than migrating every guest when the datastore fills six months later.
Average disk size is a planning shortcut
The calculator uses one average guest size to stay fast and understandable. In a final design, separate large Windows desktops, small Linux appliances and database volumes so a few outliers do not distort the result.
If uncertain, choose a larger average. Conservative storage arithmetic is easier to live with than a design that depends on every VM staying below its initial thin-provisioned usage.
Write-heavy guests change SSD class
Capacity alone cannot identify the right NAND or endurance. Databases, CI runners, log collectors and surveillance metadata can write continuously while large file-serving guests may spend most of the day reading.
The tool therefore counts write-heavy guests separately. As that number rises, the recommendation moves from ordinary TLC toward high-endurance or enterprise SSDs even when the total terabytes stay the same.
ZFS and LVM-thin solve different needs
Proxmox supports several local storage backends. ZFS brings native snapshots, clones and copy-on-write behavior; LVM-thin provides thin-provisioned block storage. The SSD itself cannot decide which management model fits your recovery and operational needs.
Choose the backend first, then interpret the storage reserve accordingly. Both approaches still require monitoring because physical space remains finite even when virtual disks are thin provisioned.
Redundancy multiplies the shopping list
Selecting a mirror, RAIDZ1 or RAIDZ2 changes the number and size of SSDs needed to hit the same usable target. This is why shopping by one-drive price is misleading for a resilient host.
The calculator maps the target to a starting drive count and per-drive capacity. It intentionally rounds upward to common terabyte steps so the output leaves room for real formatting and filesystem overhead.
Interface availability keeps recommendations realistic
A motherboard with SATA only cannot use an M.2 NVMe recommendation without additional hardware. A mini PC with two M.2 slots may have no space for a four-drive RAIDZ pool. Hardware topology constrains storage topology.
Select the interface the host actually exposes and confirm lane sharing in the motherboard manual. If both interfaces are available, reserve NVMe for workloads that benefit from concurrent I/O and use SATA where it provides cheaper capacity.
Budget per drive can change topology
A strict per-drive budget may make a larger SATA SSD or mainstream Gen4 NVMe more sensible than a flagship Gen5 model. When redundancy is required, every premium is multiplied by the number of members.
Compare the total pool price. A pair of 4TB value drives can provide more useful headroom than a pair of 2TB flagships when the workload is capacity-constrained rather than bandwidth-constrained.
Keep free capacity for operations
Snapshot creation, VM clones, migrations and package updates all need temporary working space. A datastore that is technically large enough for steady-state data can still fail an operation when there is no room for a second copy.
The reserve input combines snapshots and growth into one practical planning margin. Increase it when the host is used for experiments, frequent cloning or unpredictable datasets.
Backups require another failure domain
No primary-pool layout should be interpreted as a complete backup plan. Mirrors and RAIDZ protect against device failures; backups protect against additional classes of loss and provide historical recovery points.
Plan the backup target alongside the primary SSD budget. If the only backup lives on the same node, a motherboard or power event can still remove both copies at once.
Enterprise features must be verified, not inferred
Marketplace titles often use words such as server, data center or enterprise loosely. Cloudzat classifies known enterprise-family searches separately, but it still does not infer PLP, NAND type or warranty from the category name alone.
Before deployment, verify the exact manufacturer part number and current specification sheet. This is especially important for OEM drives, which may have different firmware or support channels from retail products.
Price per TB is the final filter
Once the correct interface, capacity and endurance class are known, current price per TB becomes extremely useful. It can reveal when a 4TB model is better value than two 2TB drives or when enterprise SATA is priced close enough to consumer NVMe to deserve consideration.
Do not reverse the order. Starting with the cheapest $/TB can lead directly to the wrong form factor, condition or workload class.
Recalculate after the host changes
Storage is not a one-time calculation. Adding Frigate, Immich, a Windows lab or a database service can transform both capacity and write intensity. The right SSD for the original eight guests may not be right for the expanded twenty-guest host.
Keep the calculator as an upgrade tool. When sustained free space falls or SSD wear rises faster than expected, model the next pool before the existing one becomes an emergency.
Questions people ask
Proxmox Storage Hardware Calculator questions
What does the Proxmox storage calculator recommend?
It estimates usable capacity, starting drive count/capacity, SSD endurance class and interface direction from guest count, reserve, redundancy and workload.
Is the result exact for ZFS?
No. It is conservative shopping arithmetic. Final ZFS capacity depends on filesystem overhead, metadata, ashift and actual device geometry.
Why does the calculator round SSD capacity up?
Commercial SSDs are sold in discrete sizes, and the host needs operational headroom. Rounding down would create a misleadingly tight design.
Should I choose mirror or RAIDZ?
Choose from VM I/O, capacity efficiency, failure tolerance, bay count and expansion strategy. The calculator does not force one layout for every host.
Can I use LVM-thin with one SSD?
Yes, but a single device has no storage redundancy. Independent backups are especially important.
Does the calculator account for snapshots?
The reserve input is intended to cover snapshots plus future growth. Increase it for heavy snapshot use.
How are write-heavy VMs handled?
A higher count moves the drive-class recommendation toward higher-endurance TLC or enterprise SSDs.
Can I choose SATA only?
Yes. The interface input keeps the recommendation within the hardware the node can actually use.
Why show both consumer and enterprise listings?
They serve different workloads and budgets. The page keeps the classes separate so a cheap consumer drive is not presented as an equivalent enterprise replacement.
Does the calculator replace backups?
No. It sizes primary storage. Build and test a separate backup path.
Official references and methodology
Verify Proxmox and OpenZFS behavior before deployment
The hardware calculator combines Cloudzat’s Proxmox storage decision rules into one conservative estimator. It uses Proxmox’s storage model for thin-provisioning and backend behavior, OpenZFS for topology concepts, and live catalogue data only after the recommended class is determined.
- Proxmox VE Storage Manager
- Proxmox VE Administration Guide - ZFS
- Proxmox VE Administration Guide - Installation
- Proxmox VE Administration Guide - Backup and Restore
- OpenZFS - RAIDZ
- OpenZFS - zpool properties
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, exact SSD revisions, warranty terms, firmware, endurance ratings and marketplace conditions can change. Verify the exact model before purchase.