wppaste
WordPress

apply_filters( 'image_memory_limit', int|string $filtered_limit )

Since
3.5.0, 4.6.0
Filters the memory limit allocated for image manipulation.

Compatibility

WordPress
since 4.6.0
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0).

Parameters

$filtered_limitint|string
Maximum memory limit to allocate for image processing.
Default WP_MAX_MEMORY_LIMIT or the original php.ini memory_limit, whichever is higher.
Accepts an integer (bytes), or a shorthand string notation, such as '256M'.

Where this hook fires · 1

  • wp-includes/functions.php:8023wp_raise_memory_limit()

Source code

View on Trac View on GitHub 

			 * @param int|string $filtered_limit Maximum memory limit to allocate for image processing.			 *                                   Default `WP_MAX_MEMORY_LIMIT` or the original			 *                                   php.ini `memory_limit`, whichever is higher.			 *                                   Accepts an integer (bytes), or a shorthand string			 *                                   notation, such as '256M'.			 */			$filtered_limit = apply_filters( 'image_memory_limit', $filtered_limit );			break; 		case 'cron':			/**			 * Filters the memory limit allocated for WP-Cron event processing.			 *

Changelog

Introduced in 3.5.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

4.6.0
The default now takes the original memory_limit into account.from the docblock
3.5.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.