What Size VPS Do You Need? A Plain-English Guide to CPU, RAM, and Storage

You do not want to overpay for a server that sits mostly idle, but you also do not want your site to crawl the first time a few people visit at once.

Choosing a size feels technical because providers sell numbers: CPU cores, RAM, storage, bandwidth. But the decision is simpler when you treat the server like a small workspace. You need enough hands to do the work, enough table space to keep things open, and enough closet space to store what matters.

Start with what the server has to carry

Before you pick numbers, name the job.

A small brochure website is like a quiet shop with a few visitors browsing shelves. A WordPress site with plugins is busier: it has to build pages, talk to a database, and sometimes send email. A web app has more moving parts, especially if it has background jobs, file uploads, or real users logged in. A self-hosted service, like a private file cloud, may care more about storage than raw speed.

Here is a plain starting point:

These are not laws. They are safe starting lines. If you are moving away from shared hosting, your old host probably hid these limits from you. Our guide on how to move from cPanel shared hosting to your own server explains that shift in more detail.

CPU: how many hands are doing the work

CPU (central processing unit) is the worker doing the thinking. When someone visits your site, the CPU helps build the page, run the app code, resize images, process logins, and answer database questions.

One CPU is enough for many small sites because web requests are short. The worker picks up a task, finishes it, and moves on. You need more CPU when many tasks arrive at the same time, or when each task is heavy.

Choose more CPU if you run:

• WordPress with lots of plugins or page builders
• An app with frequent user actions
• Image or video processing
• Search indexing
• Multiple sites on one server

Do not buy extra CPU just because it sounds faster. If your site mostly waits for visitors, those extra hands may spend the day standing around.

RAM: the size of the workbench

RAM (memory) is the workbench. It holds the things your server is actively using right now: the web server, database, app code, cache, and open tasks.

When RAM is too small, the server starts shuffling things in and out of slower storage. That is like trying to cook dinner on a cutting board the size of a postcard. You can do it, but everything takes longer and spills are likely.

For beginners, RAM is often the limit you feel first.

A very small site can run on 1 GB, but it leaves little room for comfort. A small WordPress site or app usually feels better with 2 GB. If you run a database on the same server, handle file uploads, or host several services, 4 GB is a much calmer place to start.

If you are deploying a small app, this is where planning helps. The app itself may be light, but the database, background worker, and cache all need bench space too. We cover that bigger picture in deploy a small web app without DevOps.

Storage: the closet, not the engine

Storage is where your files live when they are not actively being used. Website files, uploaded images, database data, logs, backups, and system updates all need space.

Storage does not usually make a simple website faster once you have enough of it. It is more like closet space. Too little is a problem. A huge empty closet does not make the house better.

The mistake is counting only your website files. A site that is 5 GB today may need much more room for:

• Database growth
• Uploaded media
• Temporary files
• Log files
• Software updates
• Backup copies before they are moved elsewhere

For a basic site, 30–50 GB is usually comfortable. For a private file service, the right number depends on what you plan to store. If you are self-hosting something like a private cloud, storage becomes the main decision, not an afterthought. Our self-hosting Nextcloud guide walks through that kind of use case.

Leave room for spikes and backups

Your server does not need to be sized for your busiest dream day. But it should survive normal surprises.

A spike can be a newsletter going out, a social post getting attention, a backup running, a search engine crawling your site, or a plugin doing scheduled work. If your server is already full on a quiet day, a small spike can tip it over.

A good rule: do not aim for the smallest size that barely starts. Aim for the smallest size that still has breathing room.

Backups matter here too. A backup is not just a safety copy; it is also a job your server has to perform. It reads files, packages data, and sometimes uses extra temporary space. If your storage is almost full, backups can fail at the exact moment you need them most. If you are unsure about that part, start with how to back up your server.

The shortcut

Server Manager gives you a clear view of what your server is carrying, so sizing stops being a guessing game. You can see the outcome that matters: your site is online, the important services are running, secure basics are in place, and you have enough headroom to grow without paying for a machine that mostly sleeps.

Your win: right-sized, not oversized

The right server size is not the biggest one you can afford. It is the one that fits the job with a little room to breathe.

Start with the thing you are hosting. Give it enough CPU for busy moments, enough RAM to keep its workbench clear, and enough storage for growth and backups. That is how you avoid both common mistakes: buying too much out of fear, or buying too little and fighting slow pages later.