WordPress 'Allowed Memory Size Exhausted': The WP_MEMORY_LIMIT vs PHP Limit Trap (2026)

The error: "Fatal error: Allowed memory size of X bytes exhausted" — a script (almost always a plugin/theme) hit the memory ceiling. The trap most guides miss: there are TWO limits — WP_MEMORY_LIMIT (what WordPress requests) and the server's memory_limit (the hard cap). Setting WP_MEMORY_LIMIT higher than the server cap does nothing. Here's the fix that accounts for both.

Step 1: Check the Real Limit First (Don't Edit Blind)

Tools → Site Health → Info → Server shows PHP memory limit — that's the ceiling. Elementor users: Elementor → System Info shows both limits. WooCommerce: WooCommerce → Status → System Status. Knowing the real cap determines whether your fix works at all.

The Two-Limit Distinction (What Most Guides Get Wrong)

• memory_limit (server, php.ini) — the hard cap PHP enforces. Your host controls this; you can't exceed it from WordPress.
• WP_MEMORY_LIMIT (wp-config.php) — what WordPress requests. Default ~40M (64M multisite). Cannot exceed memory_limit.

So the logic is: if Site Health shows memory_limit = 128M and you set WP_MEMORY_LIMIT = 256M, WordPress still gets 128M. The wp-config.php edit alone only works when the server cap is already higher.

Step 2: Raise WP_MEMORY_LIMIT in wp-config.php

In wp-config.php, above /* That's all, stop editing */:

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

256M is healthy for most sites; heavy WooCommerce/Elementor setups may need 512M. If Site Health showed memory_limit ≥ 256M already, this alone fixes it.

Step 3: Raise the Server Cap (When wp-config.php Isn't Enough)

If Site Health showed a lower cap, raise it at the server level — whichever your host allows:

• php.ini — memory_limit = 256M (if your host exposes php.ini edits)
• .htaccess — php_value memory_limit 256M (works on Apache when allowed)
• Hosting panel — many hosts (SiteGround Site Tools, cPanel MultiPHP INI Editor) have a PHP settings UI
• Ask support — on managed hosts, a ticket is often fastest

Step 4: Find the Memory-Hungry Plugin

If the error persists even at high limits, a plugin/theme is leaking memory — not hitting a cap, consuming everything. Disable plugins one at a time, reload, watch for the error. Query Monitor plugin shows per-plugin memory usage. A plugin that needs 512M+ is usually broken, not demanding — replace it.

When It's a Hosting Problem, Not a Config Problem

If every limit is raised correctly and the error still appears under normal traffic, the server's actual RAM allocation is the ceiling — not a setting you can edit. Oversold shared hosting enforces tight memory caps because hundreds of sites share the box. At that point the fix is a host with real headroom: Bluehost's WP Cloud tiers run WordPress on isolated infrastructure where memory_limit is generous by default, not throttled by neighbors.

Related: critical error fix, white screen of death, 500 internal server error.