Complete Guide to Fixing WordPress Memory Limit Errors

WordPress Memory Limit Solutions

“Allowed memory size exhausted” errors are among the most common WordPress performance issues. This comprehensive guide will walk you through understanding memory limits, diagnosing the root causes, and implementing professional solutions to fix these errors permanently.

Enable debug mode by adding these lines to your wp-config.php file (above the “That’s all, stop editing!” line):

// Enable WP_DEBUG mode
define('WP_DEBUG', true);

// Enable Debug logging to /wp-content/debug.log
define('WP_DEBUG_LOG', true);

// Disable display of errors
define('WP_DEBUG_DISPLAY', false);

// Enable script debugging
define('SCRIPT_DEBUG', true);

After triggering the error, check /wp-content/debug.log for memory-related warnings and the specific files/plugins causing issues.

Step 1: Access Your wp-config.php File

Locate the file in your WordPress root directory using:

• FTP/SFTP: FileZilla, WinSCP, or your preferred client
• cPanel File Manager: Navigate to public_html or your WordPress directory
• SSH: Use commands like nano wp-config.php

Step 2: Add Memory Constants

Insert this code before the line that says “That’s all, stop editing! Happy publishing.”:

// Increase WordPress memory limit
define('WP_MEMORY_LIMIT', '256M');
define('WP_MAX_MEMORY_LIMIT', '256M');

Recommended Memory Limits

Step 3: Verify the Changes

After saving the file, verify the new memory limit is active:

// Create a test file (memory-test.php) in your root directory with:
<?php
// Output current memory limit
echo 'Current memory limit: ' . ini_get('memory_limit');
?>

Access this file via your browser (e.g., yoursite.com/memory-test.php) to confirm the new limit.

Troubleshooting Tips

• If changes don’t take effect, your hosting provider may have server-level restrictions
• Check for syntax errors in wp-config.php – a single typo can break your site
• For WordPress Multisite, you may need higher limits (256M-512M recommended)
• If you get 500 errors after editing, restore from backup and try again

Option A: php.ini Modification

; WordPress optimized PHP configuration
memory_limit = 256M
upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 180
max_input_time = 180
max_input_vars = 3000

Locate php.ini in your root directory or create one if it doesn’t exist. Common locations:

• /public_html/php.ini
• /etc/php/8.1/fpm/php.ini (version may vary)
• Your hosting control panel’s PHP configuration section

Option B: .htaccess Configuration

# WordPress memory configuration
php_value memory_limit 256M
php_value upload_max_filesize 64M
php_value post_max_size 64M
php_value max_execution_time 180
php_value max_input_time 180

1. Plugin Conflict Analysis

1. Deactivate all plugins via FTP by renaming the /wp-content/plugins folder to plugins_deactivated
2. Create a new empty plugins folder
3. Reactivate plugins one by one while checking memory usage
4. Use the Health Check plugin’s troubleshooting mode for safer testing

2. Theme Testing

1. Switch to a default WordPress theme (Twenty Twenty-Three)
2. If the error disappears, your theme may be the culprit
3. Check theme requirements and compatibility
4. Contact the theme developer with debug.log findings

3. PHP OpCache Configuration

[opcache]
opcache.enable=1
opcache.memory_consumption=128
opcache.max_accelerated_files=10000
opcache.revalidate_freq=60
opcache.enable_cli=1

Add these settings to your php.ini file to optimize PHP’s built-in caching mechanism.

1. Database Optimization

• Clean up post revisions, spam comments, and transients
• Use WP-Optimize or similar plugins
• Optimize database tables via phpMyAdmin
• Limit post revisions in wp-config.php: define('WP_POST_REVISIONS', 5);

2. Media Optimization

• Compress images before uploading (use Imagify or Smush)
• Implement lazy loading for images
• Serve WebP images with WebP Express
• Use a CDN for media delivery

3. Caching Solutions

• Object Caching: Redis or Memcached
• Page Caching: WP Super Cache or W3 Total Cache
• Browser Caching: Configure via .htaccess or hosting panel
• OPcache: Enable in PHP configuration

Resolving WordPress memory limit errors requires a systematic approach:

1. Start with Method 1 (wp-config.php) – The most WordPress-friendly solution
2. Implement Method 2 if needed – For server-level configuration changes
3. Optimize rather than just increase – Address root causes through performance tuning
4. Monitor continuously – Use tools mentioned in our FAQ section

When to Seek Professional Help

Consider consulting a WordPress specialist if:

• Errors persist after trying all recommended solutions
• Your site has complex custom functionality
• You’re running a high-traffic eCommerce site
• You need enterprise-grade optimization