The short answer: a small WordPress website can often start on 1 vCPU and 2 GB RAM, but the correct Linux VPS depends on plugins, page generation, database activity, background jobs and where the audience is located. NVMe storage, sensible caching and operational headroom matter as much as the headline CPU count.
A practical WordPress starting point
Configure Start Cloud
Start Cloud provides 1 vCPU, 2 GB RAM and 50 GB NVMe for a self-managed Linux WordPress deployment. Review the selected location, software and billing term before payment.
What WordPress actually uses
A WordPress request can involve the Linux operating system, web server, PHP workers, database queries, object caching, scheduled tasks and third-party calls. A mostly cached brochure site behaves very differently from WooCommerce, a membership system or a site built around many dynamic plugins.
WordPress publishes a short list of software requirements, but those minimums are not a capacity plan. The official WordPress requirements describe supported PHP, database and HTTPS foundations. CPU and RAM still have to be chosen from the real workload.
WordPress VPS sizing table
| Workload | Practical starting point | What can change the decision |
|---|---|---|
| Landing page or cached company site | 1 vCPU / 2 GB RAM | Heavy builders, security scans, large media processing |
| Blog or small business website | 1 vCPU / 2 GB RAM | Traffic peaks, many plugins, frequent publishing |
| Several small WordPress sites | 2 vCPU / 4 GB RAM | Combined PHP workers, databases and backups |
| WooCommerce or membership site | 2 vCPU / 4 GB RAM or more | Concurrent sessions, search, checkout and integrations |
| Busy dynamic installation | Measure before choosing | Request rate, cache hit rate, slow queries and background jobs |
These are starting configurations, not performance guarantees. A well-cached site can serve more visitors with fewer resources than a lightly visited site with expensive database queries.
CPU: count PHP work, not page views
One vCPU is often enough when most pages are cached and background work is limited. More CPU becomes useful when requests regularly reach PHP, the database performs expensive queries, image processing runs during publishing, or several sites share the same server.
- Use full-page caching where the application permits it.
- Inspect slow database queries before buying capacity.
- Schedule backups and scans away from traffic peaks.
- Watch sustained CPU use and load, not one short spike.
RAM: leave space for the whole stack
Two gigabytes must cover Linux, the web server, PHP workers, the database and any cache service. It is a sensible small-site starting point, but not a promise that every plugin combination will fit. If memory repeatedly approaches the limit, PHP workers are killed or the system swaps during ordinary traffic, move to a larger configuration after checking for leaks and unnecessary services.
Why NVMe and free disk space matter
WordPress reads code, writes uploads, updates caches and queries a database. Fast storage helps those operations, while free capacity is required for updates, temporary files, logs and backups. Do not size disk space from the current media library alone. Keep remote backups outside the VPS and verify that they can be restored.
Choose location from the audience
A region closer to the majority of visitors usually reduces network round-trip time, but the best choice also depends on payment services, APIs, administration and legal requirements. DigitalCloud currently lists 11 VPS locations. Use the DigitalCloud server-location guide to compare the available regions before deployment.
A seven-point checklist before ordering
- List the CMS, theme, plugins and background jobs.
- Estimate concurrent dynamic requests, not only monthly visitors.
- Choose enough RAM for Linux, PHP, database and caching together.
- Reserve disk space for growth, logs, staging and local temporary backups.
- Place the server near the main audience and dependent services.
- Plan monitoring, patching, firewall rules and off-server backups.
- Measure after launch and resize from sustained evidence.
WordPress VPS FAQ
Is 2 GB RAM enough for WordPress?
It is often enough for one small, cached site with a restrained plugin set. Stores, membership systems, several sites or heavy background jobs commonly need more headroom.
Does WordPress need a control panel?
No. A control panel can simplify administration, but it also consumes resources. DigitalCloud offers optional control-panel choices where available; check the current configurator.
Is DigitalCloud managed WordPress hosting?
No. DigitalCloud Cloud VPS is unmanaged Linux infrastructure. You control the server and are responsible for WordPress maintenance, security and backups.
Can I upgrade later?
Choose a practical starting configuration, monitor CPU, RAM and storage, and review the available resize or migration options in the client area when sustained demand grows.