How to Fix the WordPress “HTTP Error” When Uploading Images

You drag an image into the Media Library, the progress bar fills, and then WordPress shows a vague “HTTP error” (newer versions sometimes say “Server cannot process the image” instead). The upload fails and WordPress gives no reason. I’ve traced this error to the same handful of causes over and over. Work through them in this order, from quickest to most involved.

1. Refresh and try again

It sounds too simple, but an expired login session causes this more often than you’d think. Reload the dashboard, log in again if asked, and retry the upload. Also try a different browser, which rules out an extension interfering.

2. Check the image’s size

There are two limits, and either one can trigger the error:

• File size. Your server sets a maximum upload size. You’ll find it at the bottom of Media → Add New (“Maximum upload file size”). If your file is larger, either compress it or raise upload_max_filesize and post_max_size in your host’s PHP settings.
• Pixel dimensions. A photo straight off a modern phone or camera can be 6000 pixels wide. WordPress has to load the whole thing into memory to create its thumbnail sizes, and that’s often where it fails, even when the file size looks fine. Resize images to around 2560 pixels wide before uploading. That’s already the largest size WordPress keeps for big images.

3. Give PHP more memory

Processing large images takes memory. If your limit is low, the upload fails partway through. Raise it to 256M (or 512M for media-heavy sites). Our guide to increasing the WordPress memory limit shows how on xCloud, Cloudways and cPanel hosts.

4. Switch the image library

WordPress processes images with one of two PHP libraries: Imagick or GD. On some servers Imagick runs into resource limits that GD doesn’t. Telling WordPress to try GD first often fixes the error immediately. Add this snippet with a snippets plugin like WPCodeBox, or to your child theme’s functions.php:

add_filter( 'wp_image_editors', function () {
    return array( 'WP_Image_Editor_GD', 'WP_Image_Editor_Imagick' );
} );

If uploads work afterwards, leave it in place and let your host know, since their Imagick settings may need adjusting.

5. Look for a security rule blocking the upload

Security plugins and server firewalls (ModSecurity, for example) sometimes block uploads that look unusual, especially file types like MP3s or SVGs. If the error started after you added or changed a security setting, turn that setting off, test the upload, then turn it back on with uploads allowed. Your host can also check their firewall logs for the blocked request.

6. Rule out a plugin or theme conflict

Some plugins hook into the upload process to compress, rename or move files, and a bug in one can break uploads for everyone. Temporarily deactivate plugins that touch images or media, then retry. If that fixes it, reactivate them one at a time to find the culprit. Our plugin conflict guide walks through doing this safely on a live site.

7. Rename the file

Apostrophes, accents and other special characters in a filename occasionally cause trouble. Rename it to plain letters, numbers and hyphens, like team-photo-2026.jpg, and try again.

Still getting the HTTP error?

If you’ve worked through the list and uploads still fail, the cause is usually something on the server only your host or a developer can see. Our $79 one-time fix covers it: we find the cause, fix it, and tell you what went wrong. Related: fixing “upload folder is not writable”.