You drag a JPEG into the WordPress media library and instead of an upload bar finishing, a red message pops up: “An error occurred in the upload. Please try again later.” or simply “HTTP error”. You retry, you compress the image, you wait 5 minutes. Same result. The WordPress image upload HTTP error is one of the most maddening because it gives you almost no clue what is wrong.
Here is the good news: there are only nine real causes behind this error in 2026, and each has a clear fix. This guide takes you through all of them in priority order, starting with the ones that solve 80 percent of cases. By the end, your media library will be back to working in under 15 minutes.
What “HTTP error” actually means in WordPress
WordPress shows the generic HTTP error any time the upload fails for a server-side reason it cannot pin down. The browser sent the file, your server got it (or did not), something choked, and WordPress hides the actual PHP or server error behind that one phrase. The real cause is one of these:
- PHP memory limit too low to process the image
- PHP
upload_max_filesizeorpost_max_sizetoo small - PHP
max_execution_timekilling the upload mid-process - The image library (GD or Imagick) missing or misconfigured
- A security plugin blocking the upload as a false positive
- A browser cache or extension interfering with the AJAX request
- File permission errors on the
/wp-content/uploads/folder - A
.htaccessrule blocking large file requests - An overly aggressive Cloudflare or CDN rule
Fix 1: Switch the image library from Imagick to GD
This single change fixes about half the HTTP error reports we see. Open functions.php in your active theme (or use a code snippets plugin) and add:
function debrajx_force_gd_editor( $editors ) {
return array( 'WP_Image_Editor_GD', 'WP_Image_Editor_Imagick' );
}
add_filter( 'wp_image_editors', 'debrajx_force_gd_editor' );This forces WordPress to use the GD library, which is far more forgiving than Imagick on shared hosts. Save the file and try the upload again. If it works, you have your answer.
Fix 2: Increase PHP memory and upload limits
Your hosting plan may default to 64M of memory and a 2MB upload size. Modern phone photos are 5MB to 12MB. Edit wp-config.php and add:
define('WP_MEMORY_LIMIT', '256M');
define('WP_MAX_MEMORY_LIMIT', '512M');Then in your .htaccess (root folder), add:
php_value upload_max_filesize 64M
php_value post_max_size 64M
php_value max_execution_time 300
php_value max_input_time 300If your host blocks .htaccess PHP overrides (LiteSpeed servers often do), open the hPanel or cPanel “MultiPHP INI Editor” and change the same values there. Save, then refresh wp-admin.
Fix 3: Resize the image before uploading
Even on a fast plan, a 6000 x 4000 pixel JPEG taken on your phone is overkill for a blog post. Most blog images render at 1200 to 1600 pixels wide. Resize before upload using the free TinyPNG site or the Squoosh app. A typical hero image should be under 200KB. Smaller images upload reliably even on slow connections and rank better because of faster page load.
Fix 4: Disable the security plugin temporarily
Wordfence, iThemes Security, and Sucuri can flag certain uploads as suspicious. EXIF data with unusual tags, files saved from camera apps, or images dragged from Google Drive sometimes trigger this. Pause your security plugin for 60 seconds, retry the upload. If it works, whitelist the file type or your own IP in the plugin’s settings, then re-enable.
Fix 5: Try a different browser or incognito window
Browser extensions are a surprisingly common culprit. Ad blockers, privacy extensions, and password managers occasionally interfere with the AJAX upload request. Open an incognito window with all extensions disabled, log in to wp-admin, retry. If the upload works, you have an extension conflict. Disable extensions one by one to find which one.
Fix 6: Check uploads folder permissions
WordPress writes new images to /wp-content/uploads/year/month/. If those folders are not writable, every upload fails. In your File Manager, set:
/wp-content/uploads/: 755- All subfolders: 755
- Files inside: 644
If your host is on shared Apache, ownership matters too. Run “Fix Ownership” or open a support ticket if the folder shows as owned by nobody or root.
Fix 7: Pause Cloudflare and CDN rules
Cloudflare’s “Under attack” mode, aggressive firewall rules, or Rocket Loader can break large multipart uploads. Pause Cloudflare for 5 minutes from the Overview page (just for your domain). Retry the upload. If it works, go to Cloudflare → Security → WAF and look at the recent firewall events. Add an exception for /wp-admin/async-upload.php.
Fix 8: Rename the file before uploading
Spaces, accents, and special characters in filenames sometimes trip up servers. Rename my photo (1).jpg to my-photo.jpg. Lowercase, hyphens, no parentheses, no Hindi or regional characters in filenames. This also helps SEO. WordPress will use the filename as the alt-text suggestion, so a clean name is better for image search ranking too.
Fix 9: Use the Add From Server plugin or FTP upload
If nothing else works, you can bypass the WordPress AJAX upload entirely. Upload your image to /wp-content/uploads/2026/05/ through FTP. Then install the free Add From Server plugin. It scans the uploads folder and lets you import any file you placed there into the media library. Slow but unbreakable.
Bonus: Test for the real PHP error
Want to see what is actually breaking? Enable WP_DEBUG (covered in our white screen guide) and check /wp-content/debug.log after a failed upload. The log usually points to a specific PHP function or memory line, which tells you exactly which fix above to apply.
FAQ
Why does the HTTP error happen only on big images?
Big images need more memory and time to process. Small images upload because they fit inside default limits. Increasing PHP memory and execution time in step 2 fixes this for most users.
Does using a CDN cause the HTTP error?
It can. CDNs like Cloudflare and BunnyCDN sometimes block multipart upload requests as part of their bot protection. Pause the CDN, retry, and if that fixes it, add a rule to bypass /wp-admin/ from the CDN.
Can I upload images by FTP and skip WordPress entirely?
Yes. Upload to the matching /wp-content/uploads/year/month/ folder, then use the Add From Server plugin or the Media → Library refresh to register them. The image will not have automatic responsive sizes generated unless you regenerate thumbnails afterward.
Why does it work on Chrome but not Firefox?
Browser extensions and cache differ between browsers. If only one browser fails, you have an extension or cache issue in that one browser. Clear cache or test in incognito to confirm.
What is the safe maximum image size to upload to WordPress?
For a typical blog, keep hero images under 300KB and inline images under 200KB. There is no technical maximum if your PHP limits are generous, but small images are better for visitors and SEO.
Will increasing upload limits slow down my site?
No. The limits only apply to upload requests, not normal page loads. You can safely raise them to 64M without any performance impact on visitors.
Final word
The WordPress image upload HTTP error feels random because the message tells you nothing. Once you know the nine real causes, you can fix it in under 15 minutes. Start with the GD library switch and PHP memory increase. Those two solve almost every case. If you also keep your phone photos resized to 1200 to 1600 pixels and under 300KB, you will not see this error again. For ongoing media library health, set up monthly maintenance using our WordPress maintenance checklist.