How much storage does a VPS need?

Estimate disk space for the operating system, apps, databases, logs and backups on Linux and Windows, and learn how much headroom to leave so the disk never fills up.

  • Beginner
  • All
  • 4 min read

By RunRacks Team · Published

A full disk is one of the most common reasons a server stops working. Databases refuse writes, logs stop, updates fail and some services will not start. This guide shows you how to estimate the space you need on Linux and Windows, where the space really goes, and how much headroom to leave.

Before you start

Make a list of what will live on the disk:

  • The operating system.
  • Apps and their files (website code, game server files, trading terminals).
  • Data that grows: databases, uploads, logs, user files.
  • Any backups you keep on the server itself.

Where disk space goes

The operating system

A minimal Linux server install takes only a few gigabytes. Windows Server is much larger, and Windows updates need extra free space to download and install. Plan for Windows to take tens of gigabytes on its own once updates have run for a while.

Applications

Web server software and PHP are small. Larger items include:

  • Website files and media uploads. Images and video grow fastest.
  • Game servers. Game files and worlds can take many gigabytes, and worlds grow as players explore.
  • Trading platforms. Each MetaTrader terminal stores history data, which grows over time.
  • Docker images. Every image and old version you pull takes space until you prune it.

Databases

Databases grow with your content, orders or users, and need extra free space for temporary files during large queries and upgrades.

Logs

Web server, system and application logs grow every day. Log rotation normally keeps them in check, but a misbehaving app can write gigabytes quickly.

Backups

Local backup copies are useful for quick restores, but each copy takes space. Keep at least one backup off the server as well, so a disk failure or deletion does not take both.

Rough starting points

  • A Linux VPS with a VPN, bots or scripts: the smallest disk sizes are usually plenty.
  • A WordPress site: a few gigabytes for the site itself, plus whatever your media library grows to.
  • Several sites with databases: add up each site, then plan for growth.
  • Windows VPS or Admin RDP: leave generous room for the OS, updates and app data before adding your own files.
  • Game servers and Docker hosts: check the game or image sizes, then double them for updates and growth.

Leave headroom

Aim to keep at least 20–25% of the disk free under normal use. That leaves room for updates, temporary files, log spikes and a database export without panic. If your estimate fills more than three quarters of a plan's disk on day one, pick the next size up.

Check it works

On Linux

Show free space on each filesystem:

Terminal
df -h

Look at the Use% column for /. Find the largest folders under a path:

Terminal
sudo du -h --max-depth=1 /var | sort -h | tail -n 10

On Windows

Open File Explorer → This PC to see free space on C:. For detail, use Settings → System → Storage, or in PowerShell:

PowerShell
Get-PSDrive -PSProvider FileSystem

Troubleshooting

  • Disk full on Linux, but you cannot find big files: check logs under /var/log, the systemd journal with journalctl --disk-usage, and Docker with docker system df. See free disk space on Linux.
  • Windows updates fail with not enough space: run Disk Cleanup as administrator and include system files, then retry.
  • Disk fills overnight: an app or log is growing fast. Find it with du or Storage settings, then fix the cause, not just the symptom.
  • You upgraded the plan, but the disk is the same size: the partition may need extending. On Windows, see extend a disk in Disk Management.

Next steps

Was this guide helpful?

Still stuck?

Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.

Getting started

Edit files with nano: a beginner's guide

Open, edit, search and save files with the nano text editor on a Linux server, including cutting and pasting lines, showing line numbers and safely editing system config files with sudo.

  • Beginner
  • Linux VPS
  • 5 min read

Getting started

Your first hour with a new RunRacks server

A step-by-step roadmap for the first hour after your RunRacks server is delivered, from finding your login details to changing the password, updating the OS and picking your next guides.

  • Beginner
  • All
  • 5 min read

Getting started

How to choose a server location

Pick a data center location based on where your users, broker or team are, confirm it with ping tests, and weigh the legal and latency points that come with each choice.

  • Beginner
  • All
  • 4 min read