Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Explainer

How Much RAM Does WordPress Need?

Short answer

Most WordPress sites need a PHP memory limit of 256 MB. A plain blog can run on 128 MB, while a WooCommerce store or a site with a page builder and many plugins often needs 512 MB. Check your current limit in Tools, then Site Health, then Info, and raise it in wp-config.php only if your host allows a higher PHP limit.

Key takeaways

  • Most WordPress sites need a PHP memory limit of 256 MB, with 128 MB as a minimum for a plain install.
  • WordPress asks for 40 MB on a single site and 64 MB on multisite, with 256 MB allowed in the admin area.
  • The PHP memory limit caps one request, while server RAM is shared by the web server, database, and all requests.
  • WooCommerce asks for a WordPress memory limit of 256 MB or more, as of November 2026.
  • Check the real limit under Tools, then Site Health, then Info, then Server before you change anything.
  • WP_MEMORY_LIMIT cannot lift you above the server PHP limit, so ask your host if the value does not change.

How much RAM does WordPress need?

Most WordPress sites need a PHP memory limit of 256 MB, with 128 MB as a minimum and 512 MB for heavy sites.

That 256 MB figure is a per-request PHP limit, not the total RAM in your server.

The WordPress Hosting Handbook gives hosts starting points of 128M as a minimum for a plain install, 256M as a recommended default, and 512M or more for resource-heavy sites, as of November 2026. See the Server Environment guidance for the full list.

WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS support, as of November 2026. See the WordPress requirements for the current baseline.

Your real need depends on your theme, plugins, and traffic. A plain blog with few plugins fits in 128 MB, while a store with a page builder and many plugins often needs 256 MB or 512 MB.

For the full software baseline, see WordPress hosting requirements.

PHP version affects security and compatibility as well as memory. Which PHP version should you use for WordPress explains which version to run.

What is the difference between server RAM and the PHP memory limit?

Server RAM is the total memory in the machine, while the PHP memory limit caps what one PHP request may use.

The PHP Manual defines memory_limit as the maximum amount of memory in bytes that a script is allowed to allocate, with a default of 128M when no php.ini file is loaded, as of November 2026. See the core php.ini directives for the full list.

The manual also notes that PHP 8.5 adds max_memory_limit, a startup-only cap on memory_limit, with -1 as the default for no upper bound.

A limit of 256 MB does not reserve 256 MB for every page view. PHP allocates memory as a request needs it, up to that ceiling, then releases it when the request ends.

Server RAM is shared by everything on the machine at once:

  • The web server that answers requests
  • The database that stores posts, orders, and settings
  • The operating system and monitoring tools
  • Every PHP worker handling a request at the same time
  • Any object cache running on the server

A 256 MB PHP limit on a server with only 256 MB of total RAM would leave nothing for the rest of the system. Our guide to reading a hosting plan's CPU and RAM limits shows what to check before you choose a size.

What are the WordPress memory defaults?

WordPress asks for 40 MB on a single site and 64 MB on a multisite network, with 256 MB allowed in the admin area.

The WordPress Developer Resources page on wp-config.php states that WordPress will attempt to increase memory allocated to PHP to 40 MB for a single site and 64 MB for multisite. See Editing wp-config.php for the full text.

The same page notes that the admin area can use WP_MAX_MEMORY_LIMIT, which defaults to 256 MB.

WordPress only ever raises the limit, never lowers it. If PHP already allows 256 MB, setting WP_MEMORY_LIMIT to 40 MB changes nothing, because WordPress checks the current value first.

Some hosts do not allow WordPress to raise the PHP memory limit on its own. The same developer page says to contact your host in that case, since the server setting wins.

Multisite networks start at 64 MB instead of 40 MB, because they serve more than one site from one install. A network with many sites still needs the same per-request headroom as a busy single site, so start at 256 MB.

How much memory does each type of site need?

A plain blog needs 128 MB, a typical business site needs 256 MB, and a heavy store or membership site needs 512 MB or more.

Site typePHP memory limitWhy that amount
Plain blog, few plugins128 MBA simple theme and a handful of plugins fit in the minimum
Business site, 10 to 30 plugins256 MBExtra plugins, forms, and SEO tools add memory use
Store, page builder, or membership site512 MBCheckout, builders, and member pages run heavier code
Multisite network or large imports512 MB or moreMore sites and large imports push single requests higher

These figures are starting points, not guarantees. If errors appear after you add a plugin, that plugin may be using more memory than the limit allows.

Do not size a plan from the PHP limit alone. A site with 10 visitors at once needs far less total RAM than the same site with 100 visitors at once, because each uncached request uses memory at the same time.

What does WooCommerce need?

WooCommerce needs a WordPress memory limit of 256 MB or more, as of November 2026.

WooCommerce's server recommendations list WordPress 6.9 or greater, PHP 8.3 or greater tested up to PHP 8.4, MySQL 8.0 or greater or MariaDB 10.6 or greater, HTTPS support, and a WordPress memory limit of 256 MB or greater. See the WooCommerce server recommendations for the current list.

A store also needs enough workers and database headroom, not just memory. What hosting resources does WooCommerce need covers the full set of resources a store needs.

Kinsta notes that a WooCommerce site should keep at least 128 MB of memory per PHP thread, or it may see downtime and errors. Its PHP performance add-on costs $10 per additional 500 MB per month, as of November 2026. See the Kinsta add-ons page for the current price.

How do you check your current memory limit?

Open Tools, then Site Health, then Info, then Server in your WordPress dashboard to see your PHP memory limit.

  1. Go to Tools, then Site Health in wp-admin.
  2. Click the Info tab at the top.
  3. Open the Server section and find “PHP memory limit”.
  4. Open WordPress Constants to see WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT.

The Server value is the real ceiling. If it reads 128M and your wp-config.php asks for 256M, the host setting wins until the host raises it.

WooCommerce stores can also check WooCommerce, then Status. That page lists the WordPress memory limit alongside the PHP and database versions, and flags values that fall short.

Check before you change anything. A limit that already reads 256M needs no edit, and a higher value will not fix a slow page that fits in memory.

How do you raise the WordPress memory limit?

Add define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php above the stop-editing line, then check Site Health again.

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '256M' );

Put both lines before the line that loads wp-settings.php. The developer page notes that the definitions must sit before that inclusion, or WordPress will ignore them.

If the value does not change, your host has locked the PHP limit. Ask the host to raise memory_limit in php.ini, or raise it in your hosting panel if that option is offered.

On a server you control, you can also set memory_limit = 256M in php.ini. Restart PHP after the change, then confirm the new value in Site Health.

Back up wp-config.php before you edit it. A single typing error in that file can stop the whole site from loading.

What happens when WordPress runs out of memory?

When WordPress runs out of memory, PHP stops the request with an “Allowed memory size exhausted” fatal error.

The WordPress wp-config.php page gives that message as the sign that the memory setting needs to be raised. The number in the message is in bytes, so 134217728 bytes means a 128 MB limit and 268435456 bytes means a 256 MB limit.

A memory error on one page does not always mean the limit is too low. A faulty plugin or theme can keep asking for more memory until it hits any ceiling, so find the cause before you keep raising the limit.

If the error appears only during imports, updates, or image uploads, the admin limit may be the one that matters. Those jobs run under WP_MAX_MEMORY_LIMIT, which defaults to 256 MB.

Does more RAM make WordPress faster?

More RAM only helps speed when memory was the bottleneck, and a cached page or a slow database will not improve from a higher limit.

Raising the limit from 128 MB to 256 MB stops memory errors, but it does not speed up a page that already fits in memory. Caching, image size, and database queries decide most load times.

Memory and concurrency are separate limits. Kinsta gives a 1 GB pool as an example: 4 threads at 256 MB each, or 2 threads at 512 MB each. See PHP threads vs PHP memory limit for that trade-off.

Raising memory per thread from the same pool cuts the number of requests handled at once.

PHP workers decide how many uncached requests run at once. What are PHP workers explains that limit in detail.

If your pages are slow but show no memory errors, look at caching and other speed work first. How to speed up WordPress walks through those steps in order.

What mistakes should you avoid?

The most common mistake is raising WP_MEMORY_LIMIT in wp-config.php while the server PHP limit stays lower, so nothing changes.

  • Setting WP_MEMORY_LIMIT above the PHP limit and expecting it to work.
  • Setting memory_limit to -1 on a live site, which removes the safety cap.
  • Raising the limit again and again instead of finding a plugin that keeps eating memory.
  • Confusing the PHP limit with total server RAM when choosing a plan.
  • Forgetting to check Site Health after a change, so you never confirm it worked.

Frequently asked questions

Is 128 MB of RAM enough for WordPress?

Yes, 128 MB is enough for a plain WordPress blog with a simple theme and a few plugins. It matches the minimum starting point in the WordPress Hosting Handbook. A business site with more plugins, a page builder, or a store should start at 256 MB, and heavy sites may need 512 MB.

How much RAM does a WooCommerce store need?

A WooCommerce store needs a WordPress memory limit of 256 MB or more, according to WooCommerce's own server recommendations as of November 2026. Checkout, cart, and account pages are not cached, so more requests reach PHP. Stores with large catalogs or many extensions may need 512 MB.

What is the difference between WP_MEMORY_LIMIT and PHP memory_limit?

PHP memory_limit is the server ceiling for one PHP request, set in php.ini or by your host. WP_MEMORY_LIMIT is WordPress asking PHP for more memory, set in wp-config.php. WordPress can only raise the limit up to the server ceiling, never above it, and it never lowers a higher PHP value.

Can I set the WordPress memory limit to 512 MB?

Yes, if your host allows a PHP limit of 512 MB. Add the WP_MEMORY_LIMIT line with 512M in wp-config.php, then check Tools, then Site Health, then Info, then Server to confirm the change. If the value stays lower, your host has capped PHP memory and only the host can raise it.

Why does my memory limit not change after I edit wp-config.php?

The most likely cause is that your host has locked the PHP memory limit at the server level. WordPress asks PHP for more memory, but PHP cannot grant more than the server allows. Check the Server section in Site Health to see the real ceiling, then ask your host to raise it or change it in your hosting panel.

Does increasing the memory limit make WordPress faster?

No, not on its own. A higher limit only stops memory errors and lets heavy requests finish. It does not speed up a page that already fits in memory. Slow pages usually need caching, smaller images, fewer plugins, or faster database queries, so check those first if you see no memory errors.

Sources

  1. Editing wp-config.php WordPress Developer Resources
  2. Description of core php.ini directives PHP Manual
  3. Requirements WordPress.org
  4. Server Environment Make WordPress Hosting
  5. WooCommerce Server Recommendations WooCommerce
  6. PHP Threads vs PHP Memory Limit Kinsta
  7. WordPress Hosting Add-Ons Kinsta

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test