One of the greatest articles we ever published was the classic Yes, You Can Host 18 Static Sites on a 64MB Link-1 VPS.  I love that article because it busts the myth that you always need a big VPS to run a web server, MySQL, etc.

Of course, if you’re running a large, busy forum or a major ecommerce site, then sure, you need a bigger box.  But for the hobbyist, you probably don’t.  I still run some web apps on a 512MB box.  And certainly things like VPS and catch-all email don’t need a big VPS.

But how much do you need?

For a surprising number of workloads, the answer is: you probably need less than you think.

Modern VPS offers have trained us to think in increasingly large numbers. A few years ago, a 1GB VPS felt respectable. Today, providers casually advertise 4GB, 8GB, 16GB, and even 32GB virtual machines for prices that would have seemed absurdly cheap not long ago.

So how much VPS do you actually need?  Let’s look at some realistic workloads.

512MB: Tiny, But Still Quite Useful

A 512MB VPS sounds almost comically small in 2026.  You wouldn’t buy a PC with 512MB of RAM.  But here we’re talking Linux VMs, not PCs.

Sure, you’re not going to run a giant WordPress installation, a Java application stack, and twelve Docker containers on it. But 512MB is still perfectly usable for lightweight infrastructure.

Good candidates include:

• A small static web server
• A VPN with a small number of users
• A DNS server
• Monitoring
• Reverse proxies
• A small Git repository
• A jump host or SSH gateway

A minimal Debian or Alpine installation can leave quite a bit of that RAM available for applications.  Of course, you have to be disciplined.  Desktop environments, management panels, etc. are not appropriate.

Note that 512MB is the minimum RAM for Debian 13.  It may also be worth adding a small amount of swap. Swap is not a substitute for RAM, but it can save a small VPS from dying because of a brief memory spike.

1GB: The Useful Sweet Spot

Move up to 1GB and the possibilities expand considerably.

A 1GB VPS can comfortably handle many ordinary Internet services:

• Several low-traffic websites
• A small personal blog
• A WireGuard server
• Pi-hole or similar DNS filtering
• A personal Nextcloud instance
• Small Python, Perl, PHP, or Go applications

For a small WordPress site, 1GB can also be enough, particularly if you use a more memory-friendly web server like Nginx instead of Apache.  Now, if you also install Redis, Elasticsearch, a control panel, security scanners, statistics packages, and 47 plugins, then no, 1GB will probably not make you happy.  But nginx with PHP-FPM, MariaDB, and a modest WordPress installation can live quite happily in 1GB.

1GB is often the smallest package at various VPS providers today, so it’s likely this is your entry point.

2GB: Enough for Most Hobbyists

…or perhaps this is.  We increasingly see 2GB as the smallest offer, and the 2GB for $5/month price point is very popular.  Two gigabytes gives you enough room that you generally don’t have to obsess over every daemon consuming 30MB.

You can comfortably run everything at 1GB, with more traffic and users.  You can also get into small game servers, some federated social media apps (e.g., Mastadon if you run without Docker, though it’s tight).

4GB: Comfortable Territory

At 4GB, you can of course run everything listed above, but you have a lot more wiggle room.  You have enough RAM to run a fairly substantial collection of services, or one big one.  At this level, using Docker for things is much more reasonable.  (You can use it on smaller VPSes but if you have a large Dockerized web app with many containers, 4GB is where this starts to become plausible).

This is good because your time has value. Spending three hours tuning MariaDB to save 150MB of RAM makes little sense if upgrading the server costs another $1 per month.

Of course, this can go the other way.  Don’t let cheap resources encourage sloppy architecture.  One small website shouldn’t need 4GB because the you install Docker, Portainer, MySQL, Redis, Grafana, Prometheus, Elasticsearch, and three security products around it.

8GB: Do You Actually Need This?

Personally, I use 1GB for small nodes like monitoring and VPN, and then 2GB as my default for web/database .  I suspect I could squeeze some of that down to smaller sizes, but a 2GB VPS is so cheap today there’s no need.  Sometimes I buy 4GB because of a deal, but I’m rarely using all 4GB of RAM.

Beyond that, I personally don’t have a lot of experience because bigger stuff I run at home.  My Minecraft server lives at home, as do my bigger apps.

So How Much Should You Buy?

As an extremely rough starting point:

raindog308

raindog308 is a longtime community LETizen, technical writer, and self-described techno polymath. With deep roots in the *nix world, he has a passion for systems both modern and vintage, ranging from Unix, Perl, Python, and Golang to shell scripting and mainframe-era operating systems like MVS. He’s equally comfortable with relational database systems, having spent years working with Oracle, PostgreSQL, and MySQL.

As an avid user of LowEndBox providers, raindog308 runs an empire of LEBs, from tiny boxes for VPNs, to mid-sized instances for application hosting, and heavyweight servers for data storage and complex databases. He brings both technical rigor and real-world experience to every piece he writes.

Beyond the command line, raindog308 has a life-long love of German Shepherd Dogs, high-quality knives, target shooting, theology, tabletop RPGs, playing guitar, and hiking in deep, quiet forests.

His goal with every article is to help users, from beginners to seasoned sysadmins, get more value, performance, and enjoyment out of their infrastructure.

You can find him daily in the forums at LowEndTalk under the handle @raindog308.