WordPress Image Upload HTTP Error
What Is This Error?
When you try to upload an image through your WordPress Media Library and see a plain “HTTP Error” — with no further detail — that’s this error. It’s frustratingly vague: WordPress tells you something went wrong on the server side but gives you nothing else to go on.
This error doesn’t mean your site is broken. Your pages still load and your admin dashboard still works — but images simply won’t upload. The failure lives at the server level, where something in your PHP configuration or file system is blocking the process before the file ever gets saved.
The good news is that this error almost always comes down to a handful of well-known causes, and every one of them has a clear, repeatable fix.
Get free WordPress & AI tips
Join 500+ readers. No spam, unsubscribe anytime.
Why Does This Happen?
- PHP memory limit is too low: WordPress needs enough memory to open, process, and resize an image. When the limit is set too low — often 32M or 64M by default — the upload runs out of memory mid-way and fails silently.
- Incorrect permissions on the uploads folder: WordPress must have write access to
wp-content/uploads. If the folder permissions are too restrictive, the server refuses to save the file at all. - Image library conflict (Imagick vs GD): WordPress uses either Imagick or GD to process images. If Imagick is installed but misconfigured on your server, uploads fail with no meaningful feedback.
- File size exceeding PHP upload limits: PHP enforces its own
upload_max_filesizeandpost_max_sizecaps. If your image exceeds those values, the upload is rejected before WordPress even sees it. - A plugin conflict: Security or optimization plugins can interfere with the upload process by blocking file writes or modifying the HTTP request in a way that breaks it.
How to Fix It — Step by Step
-
Increase the PHP memory limit. Open
wp-config.phpand add this line just before the “That’s all, stop editing!” comment:define('WP_MEMORY_LIMIT', '256M');You should see: Image uploads start working immediately. If not, continue to the next step.
-
Fix the permissions on your uploads folder. Connect to your server via SSH and run:
find wp-content/uploads -type d -exec chmod 755 {} \; find wp-content/uploads -type f -exec chmod 644 {} \;You should see: The uploads directory becomes writable and images save without error.
-
Switch the image editor from Imagick to GD. Add this to your theme’s
functions.phpor a site-specific plugin:function ceevee_prefer_gd_editor( $editors ) { $gd = array_search( 'WP_Image_Editor_GD', $editors ); if ( $gd !== false ) { unset( $editors[$gd] ); array_unshift( $editors, 'WP_Image_Editor_GD' ); } return $editors; } add_filter( 'wp_image_editors', 'ceevee_prefer_gd_editor' );You should see: WordPress now uses GD to process images, bypassing any Imagick misconfiguration on your server.
-
Raise PHP upload limits. Create or edit a
php.inifile in your WordPress root — or update these via your host’s control panel:upload_max_filesize = 64M post_max_size = 64M max_execution_time = 300You should see: Larger images upload without being cut off by size or timeout restrictions.
-
Test with all plugins deactivated. Go to Plugins > Installed Plugins, bulk-deactivate everything, and try uploading an image. Then reactivate plugins one by one until uploads break again.
You should see: If the upload succeeds with plugins off, the last plugin you reactivated is the conflict — deactivate or replace it.
-
Regenerate your .htaccess file. Go to Settings > Permalinks and click Save Changes — no other changes needed. This rewrites your .htaccess without touching your permalink structure.
You should see: A fresh .htaccess that clears any corrupted upload-related directives that may have been blocking the process.
Common Mistakes When Fixing This
- Editing php.ini directly on a managed host: Most shared hosts ignore a manually placed php.ini file in your root. Use a
.user.inifile instead, or contact your host and ask them to raise the limits from their end. - Setting an unrealistically high memory limit: Writing
define('WP_MEMORY_LIMIT', '2048M')in wp-config.php will not override your server’s actual PHP memory cap. Match the value to what your hosting plan genuinely supports. - Compressing images as a permanent workaround: Shrinking files before uploading can get around the size limit, but it hides the root problem. Fix the underlying cause so any image uploads cleanly at full resolution.
- Regenerating .htaccess without a backup: Saving Permalinks overwrites your existing file. If you have custom redirect rules or security headers in .htaccess, back up the file first or those changes will be lost.
Frequently Asked Questions
Why does the error message give me no useful information?
The “HTTP Error” text comes from WordPress’s JavaScript uploader, which only receives a failed HTTP response — not the underlying PHP error that caused it. The real failure message lives in your server’s PHP error log. Ask your host for access to it, or enable WP_DEBUG_LOG in wp-config.php to start capturing errors to a local log file.
Does this error affect all image formats or only specific ones?
Usually all formats fail together, but sometimes only PNG or WebP images trigger it while JPEGs upload fine. That pattern is a strong signal the image processing library (Imagick or GD) is the culprit, since different formats follow different processing paths through those libraries.
Will switching from Imagick to GD reduce my image quality?
Marginally. Imagick tends to produce slightly sharper thumbnail resizes. However, GD is reliable and more than acceptable for the vast majority of sites. Once your server environment is properly configured, you can always switch back to Imagick if the quality difference matters to you.
My host says all my PHP settings are correct — what should I check next?
Ask your host to pull the PHP error log for the exact timestamp when your upload failed. At that stage the cause is almost always a disabled PHP function, a mod_security rule silently blocking the request, or a server-level file size restriction that only your host can adjust — not you.