WordPress Memory Limit Exhausted: PROVEN Fix Guide (2026)

You are working in your WordPress dashboard — installing a plugin, uploading an image, or running a backup — and suddenly everything stops:

“Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 2097152 bytes)”

Or more recently in WordPress 6.x, the more cryptic: “There has been a critical error on this website.”

Both mean the same thing: your site hit the WordPress memory limit and PHP stopped working.

Here is what most guides do not tell you — simply increasing the number is a temporary patch, not a real fix. If you keep hitting the WordPress memory limit, something on your site is consuming far more memory than it should. This guide covers not just how to increase the limit, but how to find what is causing the problem and fix it permanently.

The WordPress memory limit error — “Fatal error: Allowed memory size exhausted” — PHP stops working when your site exceeds the allocated memory ceiling

What Is the WordPress Memory Limit?

Every time someone visits a page on your WordPress site, PHP runs on your server — executing your theme’s code, running active plugins, querying the database, and assembling the page. All of this work consumes RAM on your server.

The WordPress memory limit is a cap on how much RAM PHP is allowed to use for a single request. When a page load or admin action tries to exceed this cap, PHP stops immediately and throws the memory exhausted error.

There are actually two separate WordPress memory limit settings you need to understand:

The most important thing to understand: WordPress cannot exceed the server-level memory limit no matter what you set in wp-config.php. If your hosting plan allocates 64MB at the server level, setting WP_MEMORY_LIMIT to 512M in wp-config.php will have zero effect. You need to increase both.

How Much Memory Does Your WordPress Site Actually Need?

Step 1 — Check Your Current WordPress Memory Limit

Before increasing anything, check what your current WordPress memory limit actually is. There are two quick ways:

Method A — WordPress Site Health

1. Go to WordPress Dashboard → Tools → Site Health
2. Click the Info tab
3. Expand Server section
4. Look for PHP memory limit — this shows the server-level cap
5. Also look for WordPress memory limit — this shows the WP_MEMORY_LIMIT value

WordPress → Tools → Site Health → Info → Server — shows your current PHP memory limit and WordPress memory limit values before making any changes

Method B — Add Temporary Debug Code

Add this line temporarily to any theme’s functions.php file to display current memory usage:

Visit your site, note the values, then remove this line immediately.

Fix 1: Increase WordPress Memory Limit in wp-config.php (Fastest)

This is the first and most reliable method to fix a WordPress memory limit error. It works on virtually all hosting environments and takes under 2 minutes.

1. Open Hostinger hPanel → File Manager → public_html
2. Find wp-config.php → right-click → Edit
3. Find the line that says /* That’s all, stop editing! */
4. Paste these two lines immediately before that comment:

1. Save the file → Click Save & Close
2. Refresh your site and attempt the action that caused the error

wp-config.php — add WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT before the “stop editing” comment — the fastest fix for the WordPress memory limit error

Fix 2: Increase PHP Memory Limit via Hostinger hPanel

If the wp-config.php method did not resolve the memory limit error, the server-level PHP memory cap is lower than what you set in WordPress. You need to increase it at the hosting level.

1. Log into Hostinger hPanel
2. Scroll down to the Advanced section
3. Click PHP Configuration
4. Find the memory_limit field
5. Change the value to 256M (or 512M for resource-heavy sites)
6. Click Save
7. Go back to WordPress and test the action that caused the error

Hostinger hPanel → Advanced → PHP Configuration → memory_limit — increase to 256M to raise the server-level PHP memory cap that limits your this limit

Fix 3: Increase Memory Limit via .htaccess

If neither wp-config.php nor hPanel resolved the PHP memory error, try the .htaccess method. This works on Apache servers where PHP runs as an Apache module.

1. Open cPanel → File Manager → public_html
2. Enable Show Hidden Files → find .htaccess
3. Right-click → Edit
4. Add this line at the very top of the file:

1. Save the file → test your site

The Real Fix: Find What Is Consuming Your Memory

Increasing the the memory cap stops the error — but it does not fix the underlying problem. If your site keeps hitting the limit, something is consuming abnormally high amounts of memory. Finding and fixing that is what permanently resolves the issue.

Think of it this way: increasing the memory limit is putting a bigger bucket under a leaking roof. The leak is still there.

How to Identify Memory Hogs — Query Monitor Plugin

1. Install Query Monitor plugin (free)
2. Visit different pages on your site with Query Monitor active
3. The toolbar at the top shows memory usage per page load in real time
4. Go to Query Monitor → PHP Errors to see memory-related warnings
5. Go to Query Monitor → Scripts to see which plugins are loading the most JavaScript
6. The page with the highest memory usage = start your investigation there

Query Monitor plugin — shows real-time PHP memory usage per page load, database queries, and plugin performance — the most reliable way to find what is exhausting your the limit

Common Memory Culprits — And Their Fixes:

Advanced: Increase PHP Memory via php.ini

If none of the above methods work for your specific hosting setup, editing the php.ini file directly raises the server-level memory cap:

1. Go to cPanel → File Manager → public_html
2. Check if a php.ini file already exists — if not, create a new file with that exact name
3. Add this line:

1. Save and test your site

When to Consider Upgrading Your Hosting Plan

Sometimes a recurring this limit error is not a configuration problem — it is a sign that your site has genuinely outgrown its current hosting plan’s resource allocation.

• You have set memory to 256M but still regularly hit the limit
• Your site runs WooCommerce, a membership plugin, or multiple page builders simultaneously
• Traffic has grown significantly and memory errors appear during peak periods
• Backup jobs consistently fail due to memory exhaustion
• Your hosting plan’s maximum PHP memory limit is below 256MB

How to Prevent PHP memory Errors

• Set memory correctly from the start: When installing WordPress, add both WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT to wp-config.php immediately. Do not wait for the error to appear.
• Audit plugins quarterly: Deactivate and delete any plugin you are not actively using. Even deactivated plugins can sometimes consume memory — delete them entirely.
• Compress images before uploading: Use Squoosh (free) to compress images before uploading to WordPress. Smaller files = less memory consumed during processing.
• Security scanner memory: If you recently recovered from a hack, your security scanner may be running continuously consuming excess memory. Read WordPress Site Hacked Recovery Guide to configure it correctly.
• Schedule heavy operations: Configure backup plugins to run at 3–5am when traffic is lowest. Memory-intensive operations during peak traffic is the most common cause of intermittent memory errors.
• Monitor memory usage: Keep Query Monitor installed (even if inactive) and check memory usage occasionally — catching a memory leak early is far easier than dealing with a crashed site.
• Update PHP version: PHP 8.x is significantly more memory-efficient than PHP 7.x. Update via hPanel → PHP Configuration. Newer PHP versions handle the same operations using less RAM.

The Bottom Line

A memory cap error is one of the most fixable problems in WordPress — but only if you address both the symptom and the cause. Increasing WP_MEMORY_LIMIT in wp-config.php and raising the server-level cap in hPanel resolves the immediate error in minutes.

But the real work is finding what is consuming the memory in the first place. Query Monitor makes this straightforward — run it, find the memory hog, fix or replace it. A site that operates well within its the memory cap is faster, more stable, and far less likely to crash during traffic spikes or admin operations.

Set your memory correctly, audit your plugins regularly, and schedule heavy operations for off-peak hours. These three habits eliminate memory errors permanently.

Related Articles

Frequently Asked Questions