Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Direct answer: A WordPress VPS must provide supported PHP and MySQL-compatible database versions, HTTPS, a properly configured Apache or Nginx server, fast SSD or NVMe storage, and enough RAM for Linux, the database, PHP workers, caching, backups, and traffic bursts. There is no honest universal vCPU count or VPS-RAM number. A brochure site and a busy WooCommerce store can both run WordPress, but they do not have the same resource requirements.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Start with the software versions WordPress expects
Hardware cannot compensate for an obsolete software stack. WordPress.org currently lists PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.0 or newer, and HTTPS as its recommended baseline. Apache and Nginx are the recommended web servers because they offer the broadest feature support, although any server that supports PHP and MySQL can technically run WordPress.
As an Amazon Associate I earn from qualifying purchases.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteFor production, the WordPress Hosting Team recommends PHP 8.4 or later. PHP 8.3 entered security-only support on 31 December 2025, while PHP 8.2 reaches end of life on 31 December 2026. That makes a new VPS running PHP 8.2 a poor long-term choice even if WordPress still starts on it.
For WordPress 6.9, the Hosting Team recommends PHP 8.3.x or 8.4.x, MySQL 8.0.x or 8.4.x, and MariaDB 10.11.x or 11.4.x. The same compatibility guidance lists backward-compatible minimums of PHP 7.4+, MySQL 5.7+, and MariaDB 10.3+, but those floors should be treated as compatibility fallbacks, not targets for a new deployment. Older PHP and database releases may be out of security support.
#1 Best Overall
- Required baseline for a new site: PHP 8.3 or newer, preferably 8.4 or later; MySQL 8.0+ or MariaDB 10.11+; HTTPS.
- Web server: Apache or Nginx with WordPress rewrite rules configured correctly.
- Alternative server engines: WordPress 6.9 compatibility information also lists supported LiteSpeed and OpenLiteSpeed versions.
- Operational access: root or administrator access, a recovery console, firewall controls, and a documented backup-and-restore process.
How much RAM does WordPress need on a VPS?
The answer depends on what is running inside each PHP request and how many requests are active at once. WordPress itself can be very small; plugins, themes, image processing, import jobs, page builders, multilingual features, and e-commerce sessions are what usually increase memory pressure.
The Hosting Handbook publishes PHP memory_limit tiers that are useful starting points:
| PHP memory limit | Intended workload | What it means |
|---|---|---|
| 128M | Vanilla WordPress with no additional plugins or themes | Minimum PHP process allowance, not a complete VPS size |
| 256M | Typical production site with a modern theme and a handful of plugins | Recommended default PHP allowance and comfortable application headroom |
| 512M or more | WooCommerce, page builders, multilingual plugins, import/export tools, and other heavy workloads | Higher starting allowance for resource-intensive PHP requests |
These figures limit an individual PHP process. They are not the total RAM allocation for the VPS. The server also needs memory for the Linux kernel, web server processes, PHP-FPM workers, database buffers, object caching, monitoring, backups, and temporary spikes. A VPS advertised with 256M of RAM cannot safely be treated as a “256M WordPress server” merely because PHP is configured to allow 256M.
Is 1 GB of RAM enough?
One gigabyte can be workable for a low-traffic brochure site with efficient page caching, a small plugin set, and little background processing. It leaves limited room for database buffers, several PHP-FPM workers, security scans, backup compression, or a sudden traffic increase. If swap activity begins or the operating system repeatedly kills services, the allocation is too small regardless of the nominal PHP limit.
For a production site, choose a plan that leaves measurable free memory during normal traffic and scheduled jobs. Treat 1 GB as a constrained starting experiment, not a universal WordPress requirement or a safe default for WooCommerce.
What CPU do you need for a WordPress VPS?
There is no universal vCPU minimum. A WordPress request can be limited by PHP execution, database queries, external API calls, disk latency, or a plugin that performs expensive work. Two sites with identical visitor counts can have very different CPU demand.
Free tools Windows power users keep installed
One-click scans. No signup required.
When comparing plans, identify whether the vCPUs are shared, dedicated, or subject to burst and throttling rules. A plan that briefly bursts to a high clock speed may perform well for short peaks but struggle under sustained imports or checkout traffic. Conversely, a smaller dedicated allocation may deliver more predictable response times.
| Workload pattern | CPU decision | Measure before increasing capacity |
|---|---|---|
| Cached brochure or documentation site | Start with the smallest allocation that keeps uncached requests responsive; page caching reduces PHP executions. | CPU saturation during cache misses, PHP-FPM queueing, and response time |
| Content site with frequent publishing | Allow headroom for admin requests, search, image handling, and scheduled tasks. | Admin-request latency, cron execution time, database load, and disk I/O |
| WooCommerce or membership site | Favor predictable sustained CPU capacity because carts, sessions, checkout, and account pages are often dynamic. | PHP worker exhaustion, checkout response time, database CPU, and lock waits |
| Imports, exports, or page-builder work | Prioritize burst capacity or schedule jobs in off-peak periods; these tasks can consume CPU for minutes rather than milliseconds. | Job duration, CPU saturation, memory growth, and timeouts |
Choosing between two and four vCPUs should follow these measurements rather than a rule of thumb. Add vCPUs when CPU is consistently saturated while memory, database capacity, and storage latency are otherwise healthy. More cores will not fix a slow disk, an inefficient query, or an exhausted RAM allocation.
Storage: SSD or NVMe, and how much space?
SSD-backed storage is preferable because WordPress performs many small reads and writes: PHP files are loaded, plugin and theme files are scanned, upload metadata is updated, logs are appended, and database files are accessed continuously. NVMe can reduce latency further, especially for busy databases and concurrent PHP requests, but the useful benefit depends on the provider’s actual IOPS, durability, and contention policy.
There is no official universal gigabyte minimum. Calculate capacity from the real footprint instead:
- Measure the current WordPress files, uploads, themes, plugins, and database.
- Add expected media and database growth for the period between capacity reviews.
- Reserve space for at least one usable backup set, staging or migration copies, temporary exports, and compressed logs.
- Keep recovery margin available. A disk that is nearly full can prevent updates, database repairs, image processing, and log rotation.
Ask whether snapshots consume the same storage pool, how long backups are retained, and whether IOPS are guaranteed or shared. A large disk with poor latency can perform worse than a smaller, durable NVMe volume.
Database requirements and placement
WordPress uses a MySQL-compatible database. For new deployments, select a supported long-term version rather than an old compatibility floor. The Hosting Handbook lists MySQL 8.4 LTS and 8.0 LTS, plus MariaDB 11.8, 11.4, 10.11, and 10.6 LTS, each with its own lifecycle dates. Verify the lifecycle at purchase time because support windows change.
A local database is simple and avoids network latency, but it shares RAM, CPU, and disk I/O with the web server. A separate or managed database can isolate those resources, yet it adds network dependencies, connection limits, and another service to secure and back up. Whichever arrangement you choose, check maximum connections, buffer allocation, backup consistency, and restore procedures.
HTTPS, rewrites, and the server configuration
HTTPS is part of the current WordPress recommendation, not an optional polish item. Configure a valid certificate, redirect HTTP to HTTPS, and ensure that renewal is automated or has an explicit maintenance owner.
Apache and Nginx both work well when rewrite rules, PHP-FPM handling, file permissions, and static-file caching are configured correctly. A technically compatible server can still produce broken permalinks, redirect loops, or exposed files if the virtual host is incomplete. Test the home page, a nested post, the login screen, media uploads, and a cache-cleared request after deployment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Operational features that should be part of the specification
WordPress core does not require a particular control panel or managed service, but reliable operations do require more than a CPU and disk. Confirm these items before buying:
Best Value
- Backups: automated frequency, off-server retention, encryption, and a documented restore test.
- Monitoring: CPU saturation, available memory, swap, PHP-FPM workers, database load, disk latency, disk fullness, and HTTP response time.
- Recovery access: web console or serial console for a failed network configuration, plus a clear rebuild process.
- Security controls: firewall rules, operating-system updates, SSH key support, least-privilege accounts, and malware-response procedures.
- Upgrade path: the ability to add RAM, vCPU, storage, or a separate database without rebuilding the site.
- Geography: a data-center region close to the main audience, balanced against provider reliability and backup location.
A managed VPS is a service decision. Its value comes from who handles updates, hardening, monitoring, incident response, backups, and restores. Verify those obligations in writing instead of assuming that “managed” includes every task.
Recommended Free Tools
A practical sizing process
- Classify the site. Record whether it is a cached brochure site, content publication, membership site, store, multilingual installation, or a site that runs imports and exports.
- Inventory the application. Count active plugins, identify page builders and e-commerce components, note scheduled jobs, and record the database and media footprint.
- Set the software baseline. Use a supported PHP release, MySQL or MariaDB version, HTTPS, and a correctly configured Apache or Nginx stack.
- Choose initial memory headroom. Use 256M as the PHP allowance for a typical site; start at 512M or more for memory-heavy workloads. Allocate additional VPS RAM for every other service.
- Evaluate CPU behavior. Compare shared versus dedicated resources, burst limits, and sustained-load policies. Do not select a core count from visitor numbers alone.
- Size storage from measurements. Include content, growth, backups, logs, staging, and free recovery space rather than only today’s WordPress directory.
- Test under realistic work. Exercise uncached pages, the administrator area, searches, media handling, scheduled jobs, and checkout if applicable. Observe PHP workers, database load, I/O, swap, and response time.
- Define resize triggers. Decide in advance what sustained CPU saturation, worker exhaustion, swap usage, disk latency, or slow response time will trigger an upgrade.
Common sizing mistakes and their fixes
Confusing PHP memory_limit with VPS RAM
Raising memory_limit does not create physical memory. It only permits one PHP process to consume more. Fix the misunderstanding by monitoring total RAM and PHP-FPM concurrency, then setting a process limit that leaves room for the database and operating system.
Buying by vCPU count alone
Extra cores cannot compensate for insufficient memory, slow storage, or inefficient queries. Check the full resource profile and provider throttling policy before upgrading CPU.
Using end-of-life software because it is “compatible”
Compatibility floors such as PHP 7.4+ or MySQL 5.7+ do not make those versions good production choices. Select supported releases and plan upgrades before the security window closes.
Leaving no room for backups
A full volume can make both the site and its backup job fail. Keep backups off-server where possible, monitor free space, and test restoration rather than merely checking that a backup file exists.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Ignoring burst and background work
Traffic is not the only load. Cron tasks, image processing, imports, security scans, and backup compression can coincide with visitor requests. Schedule heavy jobs, limit concurrency where appropriate, or increase resources when measurements show contention.
The decision in one sentence
Buy the smallest supported VPS that maintains memory, CPU, database, storage-I/O, and response-time headroom under your real workload, then choose a provider with backups, monitoring, recovery access, and a clear upgrade path. The 128M, 256M, and 512M+ figures describe PHP process allowances; they are not universal VPS-RAM requirements, and no fixed vCPU number can replace measurement.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
