You upload a perfectly fine JPEG or PNG, but WordPress hits you with: “The server cannot process the image. This can happen if the server is busy or does not have enough resources.” This error is notoriously vague, but at CODE TOT, we’ve fixed this across hundreds of client sites. It’s almost never about the “server being busy”—it’s almost always about resource limits in your PHP configuration or a conflict with the ImageMagick library.

Dev Insight: This error often happens with high-resolution photos (like those from a DSLR or Unsplash). Even if the file size is small (e.g., 2MB), the *pixel dimensions* might require more memory to process than your server allows during the resizing phase.

1. Increase PHP Memory & Execution Limits

Processing images is one of the most resource-heavy tasks WordPress performs. If your memory limit is too low, the process will crash halfway through. Update your wp-config.php or your server’s PHP settings (via RunCloud dashboard) to these recommended minimums:

# In wp-config.php
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
set_time_limit( 120 );

2. Check Your Upload Limits

Sometimes the error triggers because the file is partially uploaded but cut off. Ensure your php.ini (or RunCloud PHP settings) has enough room for modern high-quality images:

  • upload_max_filesize: 64M
  • post_max_size: 64M
  • max_input_time: 300

3. The ImageMagick vs. GD Library Conflict

WordPress uses two libraries to process images: ImageMagick (Imagick) and GD Library. Imagick is more powerful but can be prone to “threading” issues on some Ubuntu servers. A common fix we use is to force WordPress to use the GD library, which is often more stable for web-sized images.

Add this snippet to your theme’s functions.php or a custom mu-plugin:

add_filter( 'wp_image_editors', function( $editors ) {
    $gd_editor = 'WP_Image_Editor_GD';
    $editors = array_diff( $editors, array( $gd_editor ) );
    array_unshift( $editors, $gd_editor );
    return $editors;
} );

4. Fix Imagick Resource Limits (Advanced)

If you prefer to keep using ImageMagick on your VPS, you may need to adjust its security policy. On many Ubuntu installs, Imagick is limited to a single thread or restricted memory. Check your policy.xml file (usually at /etc/ImageMagick-6/policy.xml) and ensure the memory and map limits are high enough for your needs.

5. Optimize Before You Upload

From an SEO and performance perspective, you should rarely upload raw 5000px wide images to WordPress. Use a tool like Squoosh.app or TinyJPG to resize your images to a maximum of 2560px width before uploading. This prevents the “Server cannot process” error entirely and keeps your site fast.

Pro Tip: If you are on RunCloud, check your “Web Application” logs. If you see a “Segmentation Fault” or “Out of Memory” error specifically when uploading, it’s a definitive sign that your PHP worker is crashing during image processing.