Skip to content
Permo Docs

WP_MAX_MEMORY_LIMIT

WP_MAX_MEMORY_LIMIT is the amount of memory WordPress asks PHP for when it has demanding work to do: in the admin area, when it processes images, and since WordPress 6.3 also when it runs scheduled tasks. It’s the higher of WordPress’s two memory values; normal page views use WP_MEMORY_LIMIT.

Why it matters

Section titled “Why it matters”

Some tasks need much more memory than showing a page: resizing a large photo, running an update, importing content. WordPress raises the limit to this value for exactly these moments, so the normal pages can stay with less.

Like WP_MEMORY_LIMIT, it’s a request. It works only if the hosting provider allows sites to change the memory limit, and WordPress never lowers a limit that’s already higher.

What influences it

Section titled “What influences it”

WordPress: When nobody sets the value, WordPress uses a default. It can be set in wp-config.php. Plugins can adjust the amount for particular tasks, such as image processing or scheduled tasks.

Server: Whether the increase takes effect depends on PHP. When the provider has fixed the memory limit, WordPress can’t raise it.

In Permo

Section titled “In Permo”

The value is in System info, tab WordPress, as the note on the Memory limit card: Admin and background tasks and the amount, or no limit. The card itself shows WP_MEMORY_LIMIT. If wp-config.php doesn’t set the constant, Permo shows the value WordPress uses instead. The card gives context; Permo doesn’t rate it.

Reference values

Section titled “Reference values”

When the constant isn’t set, WordPress asks for 256 MB, or keeps the current limit if it’s higher (source: developer.wordpress.org, wp_initial_constants(), accessed October 16, 2026).

Section titled “Related”

Sources