KIKOMONOThree kinds of storage, one job
Every VPS plan stores your files, database and system on one of three technologies. An HDD keeps data on spinning magnetic platters and reads it with a moving head, so each request waits for physical movement. A SATA SSD stores data on flash chips with no moving parts, but talks to the computer through an interface designed in the hard-drive era. An NVMe drive also uses flash, but connects through PCI Express with a protocol designed for flash, so it can queue and complete far more small reads and writes at once.
The ranking is consistent: NVMe is fastest, SATA SSD is in the middle and HDD is slowest by a wide margin, especially at the small random reads a database performs. What varies is how much of that gap your particular website can feel.
Where storage speed shows up — and where it does not
A static page or image is usually served from memory, a cache or a content delivery network after the first read. For those requests the disk is barely involved, and upgrading storage changes little. Storage speed appears in the work behind the page instead.
| Workload | Storage effect | What may matter more |
|---|---|---|
| Static pages and images | Small after caching | Cache setup, CDN and network region |
| Database queries and site search | Large — many small random reads | Enough memory to hold the working set, indexed queries |
| Admin pages, logins and checkouts | Noticeable on busy dynamic sites | CPU time and application code |
| Backups, restores and reboots | Large — bulk reading and writing | Backup schedule and retention |
| Uploads and media processing | Moderate | CPU for resizing and encoding |
If your site is a generated publication, storage type is a minor line in the plan. If it runs a database-backed application that editors log into all day, storage is part of the daily experience, not a benchmark detail.
Separate speed from size
Plan pages put a number in gigabytes next to the storage type, and the two answer different questions. Type is about speed; gigabytes are about capacity. A fast small disk still fills up. A large slow disk is still slow.
Estimate capacity from what grows: the database, uploaded media, logs and the backups you keep on the server. Leave headroom for updates and for the temporary copies made during a restore. Running out of space stops a site as completely as any hardware failure, and it happens on NVMe exactly as it does on HDD.
Read the plan label carefully
Storage on a VPS is usually shared hardware, whatever the label says. An "NVMe" plan means the host machine uses NVMe drives; it does not promise you the full speed of a dedicated drive, because neighbours on the same machine read and write too. Peak figures in marketing copy are measured under ideal conditions that a shared plan will not reproduce.
Check what the provider actually documents: whether storage is local to the host or attached over a network, whether extra volumes can be added later, and whether the plan can move to a larger disk without a rebuild. Those operational answers matter more over a year than a one-line speed claim.
A practical choice
For most small websites, any SSD is enough and NVMe is a welcome default rather than a requirement. Choose NVMe when the price difference is small, when the site is database-heavy, or when slow admin pages are already a complaint. Accept HDD only for archival or backup roles, or when price is the whole decision and the workload is patient. Do not pay a storage premium while the plan is short of memory: a database that cannot hold its working set in RAM will be slow on any disk.
Finish by comparing the whole plan, not the storage line. Size the server with our first VPS guide, check current plans in the verified offer comparison and read the promotion checklist before paying.
Current provider records
Sources
Source review date: 2026-10-20. Based on the sources above, not a product performance test. Source links are non-affiliate links; check current terms before buying.