Jump to navigation Jump to search

Other languages:
Bahasa Melayu • ‎Deutsch • ‎English • ‎Nederlands • ‎català • ‎español • ‎français • ‎italiano • ‎polski • ‎português • ‎português do Brasil • ‎日本語
Images: $wgMaxImageArea
Don't thumbnail an image if it will use too much working memory.
Introduced in version:1.6.0 (r11398)
Removed in version:still in use
Allowed values:number (floating point)
Default value:1.25e7
Other settings: Alphabetical | By function


This value specifies the maximum number of pixels a source image can have if it is to be scaled down by a scaler that requires the full source image to be decompressed and stored in decompressed form, before the thumbnail is generated. This provides a limit on memory usage for the decompression side of the image scaler.

The limit is used when scaling images with any of the built-in image scalers, such as ImageMagick or GD. It is ignored for JPEGs with ImageMagick, and also when using the VipsScaler extension as these situations do not cause excess memory usage.

Default is 50 MB if decompressed to RGBA form, which corresponds to 12.5 million (1.25e7) pixels or 3500×3500.

This is a list of examples for alternate values that may be used to set this configuration parameter:

  • 25 million pixels or 5000×5000: 2.5e7
  • 36 million pixels or 6000×6000: 3.6e7
  • 49 million pixels or 7000×7000: 4.9e7
  • 64 million pixels or 8000×8000: 6.4e7
  • 72 million pixels or 9000×9000: 7.2e7
  • 100 million pixels or 10000×10000: 10e7
To be clear, this only prevents scaling of large images. Users are still allowed to upload large files.
Warning Warning: If you increase this value, you may also need to increase $wgMaxShellMemory (Or if using GD as your image scalar, $wgMemoryLimit ).

See also[edit]