How Much RAM and CPU Does a WordPress Website Need?

How Much RAM and CPU Does WordPress Need?

There is no single answer because WordPress is used for very different kinds of websites. A five-page brochure site and a busy WooCommerce store may both run WordPress, but the amount of work they ask the server to do can be completely different.

The useful question is therefore not “What does WordPress need?” in isolation. It is “What resources does this WordPress workload need?”

A small website with caching, a lightweight theme and a few well-chosen plugins may use very little processing time. A site with ecommerce, logged-in customers, live searches, membership features, scheduled tasks or heavy plugins can create far more PHP and database work.

Does WordPress Have Official RAM or CPU Requirements?

WordPress.org publishes software requirements for running WordPress, including supported PHP and database versions and HTTPS. It does not publish one fixed amount of server RAM or a required number of CPU cores for every WordPress installation.

The current requirements can be checked directly on the WordPress.org requirements page.

That is sensible because the WordPress core software is only one part of the workload. Themes, plugins, traffic, database queries, media processing and background jobs all affect what the hosting account needs.

What Does RAM Do for WordPress?

RAM is working memory. The hosting environment uses it while PHP, the database, caching and other services are processing website activity.

A WordPress page request may involve loading PHP code, reading settings and content from the database, running plugins and building the response sent back to the visitor. More simultaneous work means more memory may be needed at the same time.

WordPress can use more RAM when

• Several visitors are generating uncached pages at the same time.
• The site uses large or complex plugins.
• WooCommerce is processing carts, checkout or account pages.
• Many users are logged in.
• Imports, backups or image processing run in the background.
• The database or cache needs more working memory.
• Several websites share the same hosting allocation.

Running out of memory can lead to failed requests, slow administration pages or memory-related PHP errors. But simply buying more RAM will not fix a website whose real bottleneck is CPU, database design or a badly behaved plugin.

What Does CPU Do for WordPress?

CPU is the processing capacity used when the server executes PHP, handles database work, compresses or transforms data and performs background tasks.

A cached page may require very little PHP work because much of the finished result can be served without rebuilding the page for every visitor. Logged-in areas, checkout pages and dynamic searches often need more processing because the response has to be generated for the individual request.

WordPress can use more CPU when

• Traffic creates many simultaneous dynamic requests.
• Pages are not effectively cached.
• A plugin performs expensive PHP or database work.
• WooCommerce processes products, carts and orders.
• Search, filtering or membership features run frequently.
• Cron jobs, imports or backups run during busy periods.
• Several active sites share the same account or server.

If you specifically want to understand virtual CPU sizing for a server, see our separate guide to how many vCPU a VPS needs. This article stays focused on WordPress hosting rather than root-access server sizing.

Server RAM and PHP Memory Are Not the Same

This is one of the easiest hosting specifications to misunderstand.

Hosting or server RAM is the wider memory available to the hosting environment. It may be used by PHP, the database, caching, the control panel and other services.

PHP memory limit controls how much memory an individual PHP process or request is permitted to use. WordPress can also define its own application memory limits within that wider environment.

For example, increasing a WordPress PHP memory limit to 256 MB does not mean the entire server only needs 256 MB of RAM. Several PHP requests may run at once, while the database and other services need memory too.

Practical WordPress Starting Points

The figures below are planning examples, not universal requirements. A well-cached site can perform comfortably with less, while a badly optimised site can struggle with considerably more.

On Website Hosts UK, smaller shared hosting routes provide modest account resources, while Shared Cloud Web Hosting provides configurable RAM and vCPU when a website needs more room to grow. The point is to move up because the workload requires it, not because WordPress automatically needs a server.

When Does WordPress Need More RAM?

More RAM becomes useful when the website is genuinely memory-constrained. Look for patterns rather than assuming every slowdown means memory.

Signs memory may be part of the problem

• PHP reports an allowed memory size exhausted error.
• Large administrative tasks fail part-way through.
• Imports or backups fail when memory use rises.
• WooCommerce system checks report a low PHP memory limit.
• The hosting resource panel shows repeated memory-limit events.
• Several simultaneous PHP processes regularly exhaust the account allowance.

If the problem is an individual PHP memory limit, increasing total hosting RAM without correcting the PHP configuration may not solve it. Likewise, increasing the PHP limit cannot create physical memory that the hosting environment does not have.

When Does WordPress Need More CPU?

CPU becomes important when the site is spending too much time processing requests. A website can have plenty of unused RAM and still feel slow because PHP or database work is using the available processing capacity.

Signs CPU may be part of the problem

• CPU usage repeatedly reaches the hosting limit during normal traffic.
• Uncached pages become slow under simultaneous visitors.
• WordPress administration slows during imports or scheduled jobs.
• WooCommerce checkout or account pages slow during busy periods.
• A plugin creates heavy PHP processing or repeated database queries.

Before adding CPU, identify what is consuming it. A broken plugin, aggressive crawler, inefficient search feature or poorly scheduled backup can waste additional CPU just as easily as it wastes the original allocation.

How Much RAM and CPU Does WooCommerce Need?

WooCommerce is still WordPress, but ecommerce introduces more dynamic work. Products, carts, customer sessions, checkout, orders, stock updates and scheduled actions can all increase server activity.

WooCommerce currently recommends a WordPress memory limit of at least 256 MB. That is an application memory recommendation, not a complete server RAM specification.

You can check the current recommendation in the WooCommerce server requirements.

For a self-hosted WooCommerce server baseline, WooCommerce developer guidance has also used 1 vCPU with at least 2 GB RAM as a starting point, alongside caching. That is useful context for a server build, but it should not be treated as a guarantee for every shop because catalogue size, plugins, traffic and checkout activity vary.

If the site is simply a small brochure website, those WooCommerce-specific recommendations should not be used to oversize the hosting unnecessarily.

When Does WordPress Cloud Hosting Make Sense?

Cloud hosting becomes useful when a growing WordPress website needs more resource headroom but the owner does not want to manage a root-access server.

That is particularly useful when you want to choose more RAM or vCPU around a website and retain normal control-panel management for files, databases, SSL, email and WordPress.

Consider cloud hosting when

• The website is regularly reaching shared hosting resource limits.
• WooCommerce or heavier plugins need more headroom.
• Traffic and simultaneous activity have increased.
• You want selectable RAM and vCPU rather than a fixed smaller plan.
• You need a straightforward upgrade path without managing Linux yourself.

For AI-assisted WordPress specifically, AI WordPress Cloud Hosting combines the AI-assisted WordPress setup route with configurable cloud resources. If you do not need extra resources yet, AI WordPress Hosting remains the simpler starting option.

Do You Need a VPS for WordPress?

Usually, no. Needing more resources and needing a server are two different decisions.

A cloud hosting plan can provide more RAM and CPU while the hosting provider still manages the underlying server platform. A VPS gives you root access and makes you responsible for more of the operating system, web server, database, updates, security and configuration.

Choose a VPS when you need that control, not simply because a WordPress website has grown. For even more predictable processor allocation, VDS can make sense for workloads where dedicated CPU resources are important.

This distinction is also covered in our guide to dedicated vs shared hosting resources.

What Should You Check Before Upgrading?

Resource upgrades are most useful when they solve an identified constraint. Before moving the website, check what the current site is actually doing.

1. Check CPU usage. Look for repeated peaks or account limits during normal traffic.
2. Check memory usage. Identify whether total hosting RAM or PHP memory is being exhausted.
3. Check caching. A cacheable brochure site should not rebuild every page unnecessarily.
4. Check plugins. Disable or replace tools creating excessive processing or database work.
5. Check scheduled tasks. Backups, scans and imports can create temporary spikes.
6. Check database activity. Slow queries can make a site CPU-heavy even when traffic is modest.
7. Check traffic patterns. A short spike and constant sustained usage require different responses.
8. Upgrade the actual bottleneck. Add RAM, CPU or a stronger hosting tier only when the evidence points there.