
Core takeaway
- A VPS moves work to you: you gain control and dedicated resources, but you take on the updates, security, backups and repairs that shared hosting quietly did for you.
- True cost: monthly price + (hours of upkeep × what your time is worth).
- Decide with the scorecard: the guide covers what you gain, what you take on, and four ways to run WordPress on a VPS.
- Rule: a VPS is worth it when the site needs what it gives and you are willing to maintain what it takes.
Disclosure: con1ainer.com participates in affiliate programs. This article contains no affiliate links. See the Affiliate & Commercial Disclosure.
Every hosting advertisement implies the same story. Your site grows, shared hosting becomes the thing holding it back, and a VPS is the grown-up answer.
Sometimes that is true. Often it is not.
A VPS gives you more control, dedicated resources, and the freedom to install what you need. It also gives you a server to keep updated, secured, backed up, and repaired. Shared hosting quietly does most of that work for you, and that work does not disappear when you leave. It transfers to you.
This guide gives you the honest version: what you gain, what you take on, what it costs in time as well as money, how to run WordPress on a VPS if you decide to, and how to tell whether you should. Every term is explained as it appears.
What Actually Changes
The difference is mostly about who does which job.
| Job | Shared hosting | VPS you manage |
|---|---|---|
| Operating system updates | The host | You |
| Web server, PHP, and database software | The host | You install, configure, and update them |
| Security of the server | The host | You |
| Security of your WordPress site | You | You |
| Backups | Usually the host, with limits | You, or a service you set up |
| Email mailboxes | Usually included | Not included. You use a separate service |
| Support when something breaks | The host, for server issues | The provider, for hardware only |
| Resource limits | Strict and shared, and often hidden | Fixed allocation that you can see |
| Installing custom software | Not possible | Yes |
| Cost | Lowest | Low monthly price, plus your time |
The fourth row is the one people miss. Moving to a VPS does not make WordPress itself any harder or easier to secure. Outdated plugins are a risk everywhere. What changes is that the server underneath your site is now also yours to look after. For the full breakdown of this split, read Managed VPS vs Unmanaged VPS: What Are You Responsible For?
What You Gain
These are the real advantages, stated concretely.
- Dedicated resources you can see. A VPS gives you a fixed amount of CPU, memory, and storage. On shared hosting, limits exist but are often hidden in a policy page, and a busy neighbor can affect you.
- No artificial caps. Shared plans commonly limit how many processes you can run, how many files you can store, and how much CPU you can use per minute. When you hit them, visitors see an error page. A VPS has only the limits of the hardware you chose.
- Software your host will not install. A newer PHP version, a Redis object cache, a specific PHP extension, a search engine, or an image-processing tool. On a VPS you install what you need.
- Real caching control. You can run server-level page caching, which is faster than caching done by a plugin.
- Command-line control of WordPress. WP-CLI is a tool that runs WordPress tasks from the command line: updating plugins, exporting the database, clearing caches, and creating users, all in seconds.
- Several sites on one server. One VPS can host many WordPress sites, each in its own folder with its own database.
- Your own scheduled tasks. You decide when background jobs run, rather than depending on visitors to trigger them.
- Staging and testing. You can copy a site to a test address, try an update there, and only then apply it to the live site.
What You Take On
The work is predictable. It helps to see it as a routine rather than a mystery.
| Job | How often | Typical time once set up |
|---|---|---|
| Apply operating system security updates | Weekly to monthly | 5 to 15 minutes |
| Update WordPress core, plugins, and themes | Weekly | 10 to 20 minutes |
| Check that backups ran, and restore one occasionally | Weekly check, quarterly test | 5 minutes, then 30 to 60 minutes |
| Review monitoring alerts and disk space | Weekly | 5 to 10 minutes |
| Renew and verify certificates | Automatic, check monthly | 2 minutes |
| Fix something that broke | Occasionally | Unpredictable |
These are rough planning figures, not guarantees. Add the initial setup, which usually takes a few hours for someone doing it for the first time, including the stack install, the migration, and the hardening.
The unpredictable row is the real cost. When shared hosting breaks, you open a support ticket. When your VPS breaks at 11 p.m., you are the support ticket.
The Email Problem
This surprises more people than anything else.
Many shared hosting plans include email mailboxes at your own domain, such as you@example.com. A VPS does not. Running your own mail server is difficult, and badly configured ones get blocked or filtered as spam very quickly. Most providers also restrict outgoing mail by default.
There are two separate needs, and each has its own solution.
| Need | What to use |
|---|---|
| A mailbox you read and send from | A hosted email service for your domain |
| WordPress sending notifications, password resets, and form submissions | An SMTP plugin connected to a transactional email service, meaning a service built to send automated messages |
SMTP (Simple Mail Transfer Protocol) is the standard way programs send email. Whichever services you choose, you will add three records to your domain’s DNS: SPF, which lists the servers allowed to send mail for your domain; DKIM, which adds a digital signature that proves a message was not altered; and DMARC, which tells receiving servers what to do with messages that fail those checks. Your email service provides the exact values. Without them, your messages are likely to land in spam.
If your email lives at your old host, keep that account active when you move the website. Changing the website’s address records does not move the mailboxes.
Is It Worth It? A Plain Scorecard
Go through both columns honestly.
| Signs you should move | Signs you should stay |
|---|---|
| You see resource-limit errors, or your host throttles the site during busy periods | The site loads well and you have not hit a limit |
| Response time stays slow even after page caching is on | The site is a blog or brochure site with steady, modest traffic |
| You need software or a PHP setup your host does not allow | The default setup does everything you need |
| You run several sites and are paying for separate plans | You have one site and a hosting plan that fits it |
| Your store or membership site is growing and needs consistent performance | You do not want to maintain a server and have no one to hand it to |
| You want staging, command-line tools, or custom scheduled tasks | You depend on included email, and moving it would be a burden |
| You enjoy learning how servers work | Your time is better spent on writing or running the business |
If most of your answers fall on the left, a VPS is probably worth it. If most fall on the right, staying put is a good decision, and upgrading to a better shared or managed WordPress plan is a lighter step than a VPS.
There is also a middle road. A managed WordPress host looks after the server and tunes it for WordPress, usually at a higher price per site. A managed VPS gives you a VPS with part of the maintenance handled by the provider. Both buy back time. For the wider comparison, read Shared Hosting vs VPS vs Dedicated Hosting: What Should You Choose?
The True Cost
The monthly price on the pricing page is not the cost.
True cost = monthly price + (hours of upkeep × what your time is worth)
As an illustration, suppose a VPS costs less per month than a managed WordPress host, but needs two hours of upkeep each month. If your time is worth more than the monthly price difference per two hours, the managed host is the cheaper choice for you, despite the larger bill. If you enjoy the work, or your time is not scarce, or you run enough sites to share the cost, the VPS wins.
This is not an argument against VPS hosting. It is a reason to choose with the whole price in view.
Four Ways to Run WordPress on a VPS
| Method | What it is | Effort | Control | Best for |
|---|---|---|---|---|
| Manual stack | You install Nginx or Apache, PHP, and MariaDB yourself | Highest | Full | Learning, and servers you want to understand completely |
| Provider one-click image | The provider creates a VPS with WordPress already installed | Low to start | Good | Getting started quickly. Check how updates are handled afterwards |
| Control panel | Software that gives a web interface for sites, databases, certificates, and backups | Low | Moderate | Hosting several sites, or anyone who prefers a dashboard to the command line |
| Docker Compose | WordPress and its database run as containers, described in one file | Moderate | Good | Running several applications and wanting reproducible setups |
A few notes on those:
- Control panels range from free, open-source ones to paid, licensed products. Check current licensing and what the panel installs before choosing, because some replace large parts of the server’s configuration.
- One-click images are convenient, but read what the image contains and who updates it. An image that is never updated becomes an old, unpatched server.
- The manual stack is the one this site documents most fully, because it teaches what every other method hides. The steps are in How to Move a Website to a VPS Without Downtime, and the web server choice is in Nginx vs Apache: Which Web Server Should You Run?
- Docker is covered in Docker on a VPS: A Practical Starting Point, including a complete WordPress and database file.
What Size of VPS Does WordPress Need?
Base the choice on what the site does, not on how large the site feels.
| Workload | Typical starting point |
|---|---|
| One light WordPress site with page caching | 1 vCPU, 1 to 2 GB RAM |
| One active site, or two or three light sites | 2 vCPU, 2 to 4 GB RAM |
| Several busy sites, or a growing online store | 2 to 4 vCPU, 4 to 8 GB RAM |
| Heavy store, membership site, or large database | Size from measured usage |
A vCPU is a virtual processor core. For storage, 25 to 50 GB is usually plenty for the site itself, but leave room for local backups, logs, and growth. These are starting points. Measure after launch, using the checks in How to Monitor a VPS: Uptime, Resources, and Alerts, and resize when the numbers show you need to. The reasoning behind the memory figures is in How Much RAM Does a Web Server Need?
A Clean WordPress Install With WP-CLI
If you are starting a new site rather than moving one, WP-CLI makes a fresh install quick and repeatable. It assumes you have already installed the web server, PHP, and database, and created an empty database, as described in the migration guide.
Install WP-CLI:
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
chmod +x wp-cli.phar
sudo mv wp-cli.phar /usr/local/bin/wp
wp --info
The commands download the tool, make it runnable, move it to a folder that is searched for commands, and print its details to confirm that it works.
Then download and install WordPress inside your site folder. The sudo -u www-data part runs each command as the web server’s own user, so every file WordPress creates has the right owner:
cd /var/www/example.com
sudo -u www-data wp core download
sudo -u www-data wp config create --dbname=example_wp --dbuser=example_user --dbpass='a-long-random-password'
sudo -u www-data wp core install --url=https://example.com --title='Site Title' --admin_user=yourname --admin_password='another-long-password' --admin_email=you@example.com
Commands typed in a terminal are saved in a history file, and that includes the passwords. On Ubuntu, starting a command with a space keeps it out of the history. Better still, delete the history entries afterwards, or use the --prompt option so WP-CLI asks for secrets interactively.
These are the maintenance commands you will use most:
| Task | Command |
|---|---|
| Check the WordPress version | sudo -u www-data wp core version |
| Update WordPress core | sudo -u www-data wp core update |
| Update all plugins | sudo -u www-data wp plugin update --all |
| Update all themes | sudo -u www-data wp theme update --all |
| List plugins and their status | sudo -u www-data wp plugin list |
| Export the database | sudo -u www-data wp db export /tmp/backup.sql |
| Clear the object cache | sudo -u www-data wp cache flush |
Take a backup before running any update.
Settings That Matter on a VPS
Replace WordPress’s built-in scheduler
WordPress runs scheduled tasks, such as publishing scheduled posts and checking for updates, through a system that triggers whenever someone visits a page. On a quiet site, tasks run late. On a busy site, the check runs on many visits needlessly. On a VPS you can use the real system scheduler instead.
First, turn off the visitor-triggered version by adding this line to wp-config.php:
define( 'DISABLE_WP_CRON', true );
Then create a system scheduled task that runs every five minutes:
sudo nano /etc/cron.d/wordpress-cron
*/5 * * * * www-data cd /var/www/example.com && /usr/local/bin/wp cron event run --due-now > /dev/null 2>&1
The fields mean: every five minutes, as the www-data user, go to the site folder and run any WordPress tasks that are due. Scheduled posts now publish on time, and page visits no longer carry the cost.
Harden wp-config.php
Two more lines in the same file close common gaps:
define( 'DISALLOW_FILE_EDIT', true );
This removes the built-in code editor from the WordPress dashboard. If an attacker gains access to an admin account, they cannot use that editor to inject code.
Set correct file ownership as well. If WordPress ever asks you for “FTP credentials” when you try to update something, the cause is that the files are owned by the wrong user. The fix is:
sudo chown -R www-data:www-data /var/www/example.com
Speed
A VPS does not make WordPress fast by default. Page caching, OPcache, an object cache, and correctly sized PHP workers do. The full diagnosis is in Why Is My VPS Slow? How to Find the Bottleneck, and the cheapest fixes come first in that guide.
Security and Backups Are Now Your Job
Two habits matter more than all the others.
Patch quickly. Most hacked WordPress sites are running a plugin or theme with a known flaw that already had a fix available. Update weekly, remove plugins you do not use, and prefer plugins that are actively maintained. Add login protection: strong unique passwords, two-factor authentication for every administrator, and a limit on repeated login attempts. The server side, including SSH keys, the firewall, and automatic security updates, is in How to Secure a VPS: Essential Setup Checklist.
Back up somewhere else, and test the restore. A backup stored on the same server disappears if the server does. Keep at least one copy off the VPS, in a different location. Save both the files and the database. Then actually restore one to a test location every few months, because an untested backup is a hope. The full method is in VPS Backup Strategy: How to Back Up a VPS and Actually Restore It.
Common Mistakes
| Mistake | What happens | What to do instead |
|---|---|---|
| Cancelling the old hosting immediately | No way back if the new server has a problem, and email may stop | Keep it for at least a week |
| Leaving backups on the same server | One failure loses the site and its backups | Store a copy somewhere else |
| Skipping updates because the site works | A known flaw sits open until someone uses it | Update weekly and after checking a backup |
| Running everything as the root user | A single mistake or compromise has total control | Use a normal user with sudo, and www-data for the website |
| Installing many plugins to fix small things | More code, more memory, more risk | Keep only the plugins you can justify |
| No monitoring | You learn about problems from visitors | Set up an outside uptime check first |
| Expecting hosted email to come with the VPS | Mailboxes vanish when the old plan ends | Choose an email service before you move |
Frequently Asked Questions
Will a VPS make my WordPress site faster?
Not automatically. A VPS gives you resources and control, but a site with no page caching and many heavy plugins can be slow on any server. Speed comes from configuration, which a VPS lets you do properly.
How much Linux do I need to know?
You need to be comfortable connecting over SSH, editing text files, and copying commands carefully. You do not need to be an expert. The routine jobs are the same few commands every time, and this site explains each one.
Can I host several WordPress sites on one VPS?
Yes. Give each site its own folder, its own database with its own user, and its own web server configuration. For stronger separation, give each its own PHP-FPM pool, which is a separate group of PHP workers running as a separate user. That limits the damage if one site is compromised.
Can I go back to shared hosting later?
Yes. Your site is just files and a database, and either can be moved anywhere. That freedom is one of the benefits of understanding where everything lives.
Is managed WordPress hosting better than a VPS?
It depends on what you are buying. Managed WordPress hosting buys back your time and usually costs more per site. A VPS buys control and room to grow, at the cost of your time. For one site and little interest in servers, managed hosting is often the better fit. For several sites, custom needs, or an interest in learning, a VPS is.
What should I do first if I decide to move?
Choose a provider, then follow the step-by-step plan in the migration guide, which keeps your old site running while you build and test the new one.
Move Because the Site Needs It
A VPS is a good home for WordPress when the site needs what it offers and you are prepared to maintain it. It is a poor choice when it is just the next tier up on a pricing page.
Start by measuring what your current host is actually limiting. Decide how much of the upkeep you want to own. If the answers point to a VPS, move carefully, test privately, and keep the old plan alive until the new one has proven itself.
A VPS is worth it when the site needs what it gives and you are willing to maintain what it takes.