How to Increase the WordPress Memory Limit

Three values decide the memory a WordPress request may use: PHP's memory_limit, WP_MEMORY_LIMIT for the front end and WP_MAX_MEMORY_LIMIT for admin tasks. Knowing which one is binding saves you from editing a file that cannot help.

WordPress only ever raises memory, never lowers it. At start-up it compares WP_MEMORY_LIMIT with PHP's current memory_limit and, if its own value is higher, calls ini_set() to lift PHP to it. That works only when the host allows the change. If the host has locked memory_limit (for example with php_admin_value in the PHP-FPM pool, or by disabling ini_set), a wp-config value of 512M on a 128M server does nothing.

Add the two define lines to wp-config.php above the "That's all, stop editing!" comment, then reload the failing page. Use this when PHP already has room but WordPress is still running at its 40M front-end default.

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

/* That's all, stop editing! Happy publishing. */

Position is not cosmetic. Everything below that comment runs after require_once ABSPATH . 'wp-settings.php';, by which point WordPress has already defined its default limits. A define placed there raises a "Constant WP_MEMORY_LIMIT already defined" warning and is ignored. If the file already contains the constant, change that line instead of adding a second one.

With WP-CLI on the server, one command does the same edit and anchors it in the right place:

wp config set WP_MEMORY_LIMIT 256M
wp config set WP_MAX_MEMORY_LIMIT 512M

Keep a copy of wp-config.php before editing by hand; a missing quote or semicolon gives a blank page, which the WordPress white screen guide helps you trace.

Start with the file path in the error, then measure peak memory per page with the Query Monitor plugin; a higher limit only buys time if the code keeps growing. Most cases trace to a backup, import, page builder or oversized image.

• Read the path: the folder under wp-content/plugins/ or themes/ is the first suspect; check it for an update.
• Measure: Query Monitor shows peak memory use for each request in the admin bar.
• Halve the plugins: deactivate half, test, then split again; five rounds isolate one plugin among thirty.
• Check the error log: repeated entries at the same hour point to a cron job; the PHP error log guide shows where cPanel keeps it.
• Shrink uploads: WordPress makes several resized copies of each image, so a 6,000-pixel photo can exhaust memory on its own. Upload around 2,000 pixels wide.

On WebJi® WordPress hosting the hosting panel exposes PHP's memory_limit, so you can raise it yourself without a ticket. If the value reverts or the field is locked, email support@webji.services with the domain, the figure Site Health shows and the full error line; support runs 24/7 in Hindi and English with an average first reply under 60 minutes. Stores that outgrow shared limits usually move to WooCommerce hosting, and the upload ceiling sits on the same screen, as explained in increasing the WordPress upload size.