File storage on a VPS: disks and object storage
A project's files, such as user uploads, product photos, videos, documents and archives, grow faster than the database and the code. You can keep them on the server's disk, on a separate volume or in object storage, and the choice determines the price per terabyte, the speed and what happens to the files when you change servers. Here are the options and prices according to the accsly.io catalog.
While a site is small, its files sit in a folder next to the code, and that is fine. Problems start as it grows: the disk runs out, a plan with a bigger disk drags along cores and memory you do not need, a full server backup takes hours, and a move means copying hundreds of gigabytes together with the site. That is why it pays to keep files separate from the system from the very start and to know where you can move them.
The local VPS disk: NVMe, SSD and HDD
The disk included in the plan is the fastest and simplest place for files. Its drawback is that its size is tied to the plan: to get more space, you have to take a plan with resources you do not need.
- NVMe and SSD are needed for the system, the database and files that are read all the time: thumbnails, static assets and cache. According to the accsly.io catalog as of November 2026, a VPS plan with an NVMe disk of about 1 TB costs a median of about $200 a month, and with SSD about $206: such disks come bundled with large amounts of memory and many cores. The catalog keeps prices in roubles; dollar figures are converted at the catalog rate of 7 November 2026. Disk types are compared in the article NVMe or SSD: does it matter for a website.
- HDD is cheap capacity for archives, backups, videos and rarely opened documents. Plans with hard drives are rare: 830 of the 29,603 VPS plans in the catalog, under 3%, from 172 hosts. On the other hand, a plan with an HDD of about 1 TB costs a median of $13.5 a month, and among plans with 500 GB or more the median price per terabyte is $11 a month, with the cheapest tenth at $4 or less. Collections: Storage VPS with a large disk and VPS with HDD.
If you need more than ten terabytes, a dedicated server with several disks is better value: the catalog has 800 configurations with 4 TB or more of HDD from 47 hosts, with a median price per terabyte of $35 a month, but that price includes a whole physical server with its processor and memory. These servers are collected on the page Dedicated servers for data storage. Their disks are combined into RAID so that the failure of one does not mean data loss, but RAID protects against a broken disk; it is not a backup.
Attachable volumes
Many cloud hosts sell additional disks called volumes (block storage), which attach to a VPS as one more disk and are billed per gigabyte separately from the plan. This is convenient when you need space but not cores and memory: you enlarge the volume without changing the server, and when you move to a new VPS you detach it from the old one and attach it to the new one in the same data centre.
What to check before buying:
- the speed and IOPS limit of the volume, which for network disks are often lower than for a local NVMe;
- whether the volume can be attached to a server in another data centre (usually not, a volume lives in a single zone);
- whether volume snapshots are included in the price and where they are stored;
- how the volume is mounted at boot: in
/etc/fstabit is specified by UUID with thenofailoption, which, as described in the fstab manual, keeps the boot from stopping if the device is not found.
S3 object storage
Object storage works differently from a disk: files (objects) live in containers (buckets) and are uploaded and read over HTTP through an API. The Amazon S3 interface has become the standard, and many hosts and clouds offer S3-compatible storage that works with the same libraries and programs; rclone, for example, supports dozens of such providers.
- Pros: capacity is unlimited and you pay for what you use, files are not tied to a server and survive its deletion, and they can be served to visitors directly or through a CDN without loading the VPS. The storage keeps several copies by itself: for Amazon S3 storage classes, according to the AWS description, the designed durability is 99.999999999% over a year. S3-compatible storage from other providers has its own durability figures; check them in their documentation.
- Cons: you cannot open a file and append to it as on a disk, and the application has to be able to work with the API (WordPress, Laravel and Nextcloud have plugins and drivers for this). Besides gigabytes, you pay for requests and outbound traffic, as the S3 pricing shows, and for a site that serves a lot of files the traffic can cost more than the storage itself.
The accsly.io catalog has no object storage prices, so compare providers on three lines of their price list: gigabytes per month, requests and outbound traffic. To serve images and videos to visitors, storage is usually placed behind a CDN; see the article CDN: when a website needs one.
What goes where
- the system, code and database go on the server's local NVMe or SSD; databases are covered in the article A database on a VPS: PostgreSQL or MySQL;
- user uploads and media that grow without limit go to object storage or a separate volume;
- archives, backups and videos that are rarely opened go to an HDD server or a cold storage class of object storage;
- a shared folder for the team goes on a VPS with Nextcloud and a large disk; plans are on the page VPS for Nextcloud.
Even if everything sits on one disk for now, keep uploads in a separate directory and put its path in the application settings, not in the code. Then moving the files to a volume or to storage comes down to copying them and changing one setting. Add free disk space to monitoring with an alert at 80%: a full disk stops both the database and log writing, and not every host lets you upgrade the plan or attach a volume in five minutes.
Backing up files
Wherever the files are, their copy must be somewhere else. The classic 3-2-1 rule, cited for example by the US agency CISA, means three copies of the data, on two different media, with one off site. For a VPS, this means that a copy on the same server, or at the same host in the same data centre, is not a backup in case of an account suspension or a fire.
Hosts often offer their own backups, but read the terms carefully: in the accsly.io catalog, 1,644 of 2,248 VPS hosts describe backups, and quite often copies are made only for shared hosting, cost extra or work on a "best effort" basis. Your own copies are more reliable:
- programs such as restic make encrypted, deduplicated copies, where each subsequent copy transfers only the changes, and can write straight to S3-compatible storage;
- in object storage, turn on versioning, so an overwritten or deleted object can be recovered from an older version;
- once a month, restore a copy to a test server; that is the only way to know it works.
Schedules, storage and testing of copies are covered in more detail in the article VPS backups: strategies and tools, and plans with a large, cheap disk for copies are on the page VPS for backups.