
You drag an image into the Media Library, the progress bar runs, and then a short message appears: HTTP error. No detail, no reason, just those two words. When wordpress image upload http error blocks every image you try to add, publishing a post with pictures becomes impossible, and the vague message gives you nothing to work with.
The good news is that the message is a symptom, not a diagnosis, and the real causes are well known. The image may be too large, the server may run out of memory while processing it, a plugin may interfere with the upload, or the uploads folder may refuse the file. This guide works through those causes in order, from the simplest check to the deeper server fixes. Before you edit any file on the server, take a full backup of the site, including the database, so you can restore it if anything goes wrong.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Rename the File and Try the Upload Again
- Fix 2: Reduce the Image Size Before Uploading
- Fix 3: Clear the Browser Cache and Try Another Browser
- Fix 4: Check the File Format and Remove Special Characters
- Fix 5: Deactivate Plugins and Test for a Conflict
- Fix 6: Switch to a Default Theme Temporarily
- Fix 7: Increase the PHP Memory Limit
- Fix 8: Ask Your Host to Raise the Time and Upload Limits
- Fix 9: Check the Uploads Folder Permissions
- Fix 10: Switch the Image Editor from Imagick to GD
- Fix 11: Check the Error Log and Ask Your Hosting Provider
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
Uploading an image is a small chain of jobs: the browser sends the file, the server receives it, WordPress checks it, and the image editor creates smaller copies. If any job in the chain fails, WordPress shows the same short HTTP error message, whatever the cause. These are the reasons the chain breaks most often.
1. The Image Is Too Large for the Server to Process
Large images, especially photos straight from a camera, can be several megabytes with very high dimensions. The server must load the whole image into memory to create thumbnails, and a very large image can use more memory than the server allows. When the memory runs out mid-upload, the process stops and WordPress shows the HTTP error. This is the most common cause of wordpress image upload http error, and it often starts when you switch to a better camera or a new phone.
2. The PHP Memory Limit Is Too Low
PHP is the programming language WordPress runs on, and every hosting account gives it a memory limit. Image processing is hungry work: a single large image can need far more memory than a normal page load. If the limit is set low, the upload fails at the thumbnail step, even though the file itself uploads fine. The limit is a server setting, not a WordPress setting, which is why the error message gives no clue about it.
3. A Plugin Interferes with the Upload
Image optimisation plugins, security plugins, and media plugins all hook into the upload process. If one of them has a bug, conflicts with another plugin, or blocks the upload for a security reason, the upload fails with the generic HTTP error. The plugin may have worked fine for months and then break after an update — to the plugin, to WordPress, or to PHP on the server.
4. The Uploads Folder Will Not Accept the File
WordPress stores uploads in the wp-content/uploads folder, organised by year and month. If that folder, or the month folder inside it, has the wrong permissions, or if the server user does not own the folder, WordPress cannot write the file. The upload reaches the server and then has nowhere to go, so it fails. This cause often appears after moving the site to a new host, when folder ownership changes.
5. The Image Editor on the Server Fails
WordPress uses an image editing library on the server — usually Imagick or GD — to resize images and create thumbnails. If the library is missing, outdated, or crashes on a particular image format, the upload fails at the processing step. Some servers run an Imagick version with a known fault that fails on certain images while others upload fine, which makes the problem look random.
6. The Server Times Out or Blocks the Request
Uploads take time, and servers enforce time limits. A slow connection, a very large file, or a busy server can push the upload past the time limit, and the server stops the request. Security rules on the server can also block uploads that look suspicious, including files with unusual names or formats. In both cases WordPress receives a failed request and shows the HTTP error, so wordpress image upload http error can be a server rule rather than a WordPress fault at all.
Quick Checks
Two minutes before the deep fixes.
- Try uploading a small image, under 200 KB — does it upload, while large images fail?
- Check the file name — does it contain spaces, apostrophes, or special characters?
- Try the same image in a different browser, or in a private browsing window.
- Check Media, then Add New, and read any message shown under the upload box.
- Think about when it started — did wordpress image upload http error begin after a plugin update, a move to a new host, or a new camera?
- Check whether other people who edit the site see the same error, or only you.
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| Small images upload, large ones fail | Image too large or memory too low | Fix 2 |
| Every image fails, any size | Plugin conflict or permissions | Fix 5 |
| Error started after a plugin update | Plugin interfering with uploads | Fix 5 |
| Error started after moving hosts | Folder ownership or permissions | Fix 9 |
| Some images fail, others upload fine | Image editor fault on certain files | Fix 10 |
| Upload stalls, then fails slowly | Server time limit reached | Fix 8 |
| Error in one browser only | Browser cache or extension | Fix 3 |
| File name has spaces or symbols | File name rejected by the server | Fix 1 |
Fix 1: Rename the File and Try the Upload Again
Start with the file name, because it is the simplest cause and the fastest test. Spaces, apostrophes, and special characters in a file name can make the server reject the upload, even though the image itself is fine.

- Find the image on your computer and check its file name for spaces, apostrophes, brackets, or non-English characters.
- Rename the file using only lowercase letters, numbers, and hyphens, such as
garden-shed-photo.jpg. - Keep the name short and descriptive, and keep the original file extension unchanged.
- Go to Media, then Add New, in the WordPress dashboard.
- Drag the renamed file into the upload box, or click Select Files and choose it.
- Wait for the upload to finish and check whether the image appears in the Media Library.
- If it uploads now, the file name was the cause — use the same naming habit for future images.
File names matter more than most people expect. A name with an apostrophe can break the request, a name with brackets can confuse security rules, and a very long name can exceed a server limit. WordPress does clean up file names when it saves them, but the original name still travels with the upload request, and the server can reject it before WordPress ever sees it. Renaming on your computer, before uploading, avoids the whole problem. Keep a simple habit: lowercase letters, numbers, and hyphens, no spaces, no symbols. If the renamed file still fails, the size of the image is the next suspect, and Fix 2 reduces it. For uploads that fail with a different message, our guide to WordPress image upload failed covers that problem.
Fix 2: Reduce the Image Size Before Uploading
Large images are the most common cause of this error. A photo straight from a camera can be far larger than a web page needs, and the server can run out of memory trying to process it. Reducing the image before uploading solves the problem at the source.
- Check the image file size on your computer — right-click it and choose Properties or Get Info.
- If the image is wider than 2000 pixels, resize it to a web-friendly width, such as 1600 pixels, in any image editor.
- Save a copy as a JPEG for photos, which keeps the file size small without visible quality loss.
- Aim for a file under 500 KB for a normal article image, and under 200 KB where you can.
- Upload the smaller copy through Media, then Add New, and check whether it succeeds.
- If it succeeds, the original was too large — keep the resized version and delete the failed attempts from the Media Library.
- Make resizing part of your routine: resize every image before uploading, rather than relying on the server to do it.
Resizing before uploading has a second benefit: faster pages. A 5 MB photo slows every reader’s page load, while a 200 KB version looks the same on screen and loads quickly. Free image editors, and the built-in photo apps on Windows and Mac, can all resize an image in a minute. Do not rely on WordPress to shrink huge originals — the upload must succeed before WordPress can resize anything, and the memory needed to process a huge image is exactly what causes the failure. If you must upload large originals, your host may need to raise the memory limit, which Fix 7 covers. If small images fail too, the cause is not size, and Fix 3 checks the browser side. For images that fail because they exceed the size limit WordPress shows, our guide to WordPress image upload exceeds maximum file size covers that limit.
Fix 3: Clear the Browser Cache and Try Another Browser
A stale browser cache, or a browser extension that interferes with uploads, can break the upload request. The server never receives a clean request, so WordPress shows the HTTP error even though the site itself is fine.
- Open a private browsing window — in Chrome, press Ctrl+Shift+N — and log in to WordPress there.
- Try uploading the same image in the private window, where extensions are usually disabled.
- If it uploads, a browser extension or a cached script is the cause — disable extensions one at a time in your normal browser.
- Clear the browser cache and cookies for your site, then log in again and retry the upload.
- Try a completely different browser, such as Firefox if you normally use Chrome.
- Check that your browser is up to date, since an old browser can mishandle the upload request.
- If the upload works in another browser, keep using that browser for uploads until you find the faulty extension.
Private browsing is a clean test because it runs without most extensions and with a fresh cache. If uploads work there, the site is fine and the browser is the problem. Ad blockers and privacy extensions are the usual suspects: they can block the upload request or strip parts of it, and the failure looks exactly like a server error. Clearing the cache also helps after a WordPress update, when the browser may hold old JavaScript files that no longer match the new WordPress version. If every browser fails the same way, the cause is on the server or in WordPress, and Fix 4 checks the file itself before moving to plugins.
Fix 4: Check the File Format and Remove Special Characters
WordPress accepts common image formats, but unusual formats, corrupt files, and files with a mismatched extension can fail the upload check. A file that opens fine on your computer can still fail on the server if its format is not what its name claims.

- Check the file extension: JPG, JPEG, PNG, GIF, and WebP are the formats WordPress handles routinely.
- If the file uses another format, such as HEIC from a phone, convert it to JPEG before uploading.
- Open the image in an image editor and save a fresh copy with Save As, using the correct format.
- Check that the file is not corrupt: if it will not open in an image editor, the file itself is damaged.
- Remove any double extensions, such as
photo.jpg.png, and keep a single correct extension. - Upload the fresh copy through Media, then Add New, and check whether it succeeds.
- If it succeeds, the original file was corrupt or mislabelled — use the fresh copy.
HEIC deserves a special mention. Many phones save photos in HEIC format by default, and WordPress cannot process HEIC files on most servers. The file may upload partway and then fail with the HTTP error, because the image editor cannot read it. Converting to JPEG on the phone or the computer before uploading solves it. Corrupt files are rarer, but they happen: a download interrupted halfway, or a file copied from a failing memory card, can look fine in a thumbnail and still be unreadable. Saving a fresh copy in an image editor rebuilds the file cleanly. If the format is correct and the file is healthy, the next suspect is a plugin, and Fix 5 tests for that.
Fix 5: Deactivate Plugins and Test for a Conflict
Plugins hook into the upload process, and one faulty plugin can break every upload. Deactivating plugins one group at a time finds the culprit without deleting anything.
- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Go to Plugins, then Installed Plugins, in the WordPress dashboard.
- Deactivate all plugins at once using the bulk actions menu, then test an upload.
- If the upload works, reactivate the plugins one at a time, testing an upload after each one.
- When uploads fail again, the last plugin you reactivated is the culprit — leave it deactivated.
- Check whether that plugin has an update available, and check its support page for known upload problems.
- If the plugin is essential, look for a replacement, or ask the plugin author for help through the official support forum.
Image optimisation and security plugins are the most common culprits, because they inspect or modify every uploaded file. A security plugin can block an upload it considers suspicious, and an optimisation plugin can crash while processing an image. Deactivating all plugins at once is safe: it does not delete settings, and reactivating restores everything. If you cannot reach the dashboard because a plugin broke it, rename the plugin folders through your host’s File Manager or FTP — renaming a folder deactivates that plugin. Ask your host for help with FTP if you have not used it before. If uploads fail even with all plugins off, the theme is the next suspect, and Fix 6 tests it. For a broader guide to plugin problems, our guide to WordPress plugin conflict fix covers the full process.
Fix 6: Switch to a Default Theme Temporarily
A theme can hook into the upload process too, especially themes with built-in image handling or media features. Switching to a default WordPress theme for a few minutes shows whether the theme is the cause.
- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Go to Appearance, then Themes, in the WordPress dashboard.
- Note which theme is active now, so you can switch back to it afterwards.
- Activate a default theme, such as Twenty Twenty-Five, if it is installed. If not, install it from Appearance, then Themes, then Add New.
- Try uploading the same image that failed before.
- If it uploads, the theme is interfering — check for a theme update, or ask the theme author for help.
- Switch back to your normal theme, and keep the default theme installed for future tests.
Switching themes does not delete your content, your posts, or your settings. It changes how the site looks while the default theme is active, so do this test at a quiet time, or put the site into maintenance mode first if your host offers that. Some themes add custom image sizes, and a theme that registers a very large number of sizes can push image processing past the memory limit — the upload fails not because the theme is broken, but because it asks the server to create too many copies. If the theme is the cause, a theme update often fixes it, because theme authors fix upload problems quickly when they are reported. If uploads fail with the default theme too, the cause is deeper, on the server, and Fix 7 raises the memory limit.
Fix 7: Increase the PHP Memory Limit
Image processing needs memory, and a low PHP memory limit starves it. Raising the limit in the wp-config.php file gives WordPress more room to create thumbnails, and it is the fix that solves this error for many sites.
- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Open your host’s File Manager, or connect with FTP, and find the wp-config.php file in the site’s main folder.
- Download a copy of wp-config.php to your computer before editing it, so you can restore it if anything goes wrong.
- Open wp-config.php for editing and find the line that says
/ That's all, stop editing! /. - Add the following line just above that line, then save the file.
define( 'WP_MEMORY_LIMIT', '256M' );
- Try uploading the same image again and check whether it succeeds.
- If it still fails, ask your hosting provider to raise the server memory limit, because the server limit overrides this setting.
The line above tells WordPress to request 256 megabytes of memory for each request, which is enough for most images. Do not set it higher than your hosting plan allows — if the server limit is lower, the server limit wins, and the setting changes nothing. That is why step 7 matters: only your host can raise the true server limit. Never edit wp-config.php without a copy saved first, and never paste code from unknown websites into it. The line above is the standard WordPress setting, documented in the official WordPress documentation linked below. If you are not comfortable editing files, ask your host to make the change for you — most hosts will do it as part of support. If the memory limit is already high and uploads still fail, the time limits may be the problem, and Fix 8 covers those. For a Media Library that will not load at all, our guide to WordPress media library not loading covers that problem.
Fix 8: Ask Your Host to Raise the Time and Upload Limits
Servers enforce time limits on requests, and a slow upload can run past them. The upload limit also caps how large a file the server will accept. Both limits live on the server, so your hosting provider is the right person to change them.
- Check Tools, then Site Health, then Info, then Server, in the WordPress dashboard, and note the upload and time limits shown.
- Note the PHP version shown there too, since a very old PHP version causes upload problems of its own.
- Contact your hosting provider’s support and describe the error, including the image size and the limits you noted.
- Ask them to raise the maximum execution time and the maximum upload size to values that suit your images.
- Ask them whether the PHP version can be updated to a version WordPress currently supports.
- After they confirm the change, try uploading the same image again.
- If the upload still fails, ask them to check the server error log for the exact failure, and keep their reply for Fix 11.
Do not try to change server limits by editing server configuration files yourself unless you know exactly what you are doing — a wrong change can take the whole site down. Your host changes these limits routinely, and most hosts will do it within one support message. When you contact them, include the details from step 1: the error message, the file size, and the limits shown in Site Health. Those details save a round of questions and get the fix applied faster. A PHP update is worth asking about even if the limits are fine, because old PHP versions have image-handling faults that newer versions fixed. If the host confirms the limits are generous and uploads still fail, folder permissions are the next suspect, and Fix 9 checks them.
Fix 9: Check the Uploads Folder Permissions
WordPress writes uploads into the wp-content/uploads folder. If that folder has the wrong permissions, WordPress cannot save the file, and the upload fails. Permissions are numbers that control who can read, write, and run files, and they must be set correctly.

- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Open your host’s File Manager and go to the wp-content folder.
- Right-click the uploads folder and choose Permissions or Change Permissions.
- Check that folders are set to 755 and files inside are set to 644 — these are the standard WordPress permissions.
- If the permissions are different, set folders to 755 and files to 644, applying the change to the folder and its contents.
- Never set permissions to 777 — that gives everyone full access and leaves the site open to attack.
- Try uploading the same image again, and check whether it appears in the Media Library.
Permissions problems often appear after moving a site to a new host, because the move can change who owns the files. If the permissions look right but uploads still fail, the folder ownership may be wrong, and only your host can fix ownership — ask them to check that the web server user owns the uploads folder. Do not guess at ownership changes yourself. Some hosts offer a permissions repair tool in their control panel, which sets the standard values safely — use that if your host provides it. If permissions are correct and uploads still fail, the image editor library may be the fault, and Fix 10 switches it.
Fix 10: Switch the Image Editor from Imagick to GD
WordPress uses either Imagick or GD to resize images. Some servers run an Imagick version with a fault that fails on certain images. Telling WordPress to use GD instead often fixes uploads that fail only for some images.
- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Check Tools, then Site Health, then Info, then Media Handling, to see which image editor is active.
- If Imagick is listed first, it is the editor WordPress uses.
- The safest way to switch editors is to ask your hosting provider to disable Imagick or update it, so WordPress falls back to GD.
- Alternatively, a developer can add a small code snippet to the site that changes the editor order — do not add code snippets yourself unless you understand them.
- After the switch, try uploading the images that failed before, and check whether they succeed.
- If uploads now work, leave the editor setting as it is — GD handles normal article images well.
Do not install random plugins that promise to fix the image editor — many are outdated, and a bad plugin can make the problem worse. The host route in step 4 is the safe one, because the host can test the change and revert it if needed. If your host confirms Imagick is up to date and healthy, the editor is not the cause, and the error log in Fix 11 will show the real fault. Some images fail with one editor and work with the other because of how the image file itself is built — a fresh copy saved in an image editor, as in Fix 4, sometimes fixes those files without any server change. If the editor switch does not help, Fix 11 gathers the evidence your host needs.
Fix 11: Check the Error Log and Ask Your Hosting Provider
When every fix so far has failed, the server error log holds the exact reason. The log records the real failure behind the short HTTP error message, and your host can read it in seconds.

- Note the exact time of a failed upload, and the exact file name and size.
- Contact your hosting provider’s support and describe the error, the time it happened, and the fixes you have already tried.
- Ask them to check the server error log for that time and tell you the exact error recorded.
- Ask them to check whether a security rule, a firewall, or a resource limit blocked the upload.
- Apply whatever fix they recommend, and test an upload while they are still helping you if you can.
- If they find a server fault, ask them to confirm the fix in writing so you have a record.
- Keep a note of the cause and the fix, so the same error is faster to solve if it ever returns.
The error log is the difference between guessing and knowing. It may show a memory error, a timeout, a permissions denial, or a security block — each with a different fix, and each invisible from the WordPress dashboard. If wordpress image upload http error survives every fix in this guide and the host finds nothing in the log, ask the host to test an upload on a fresh WordPress installation on the same server. If the fresh installation fails too, the server itself is at fault, and the host must fix it. If the fresh installation works, the fault is in your site’s files or database, and restoring from a backup taken before the problem started is the fastest way forward. Do not keep editing server files at random — each untested change adds a new possible cause.
What to Avoid
- Do not set folder permissions to 777 — it leaves the site open to attack and most hosts will flag it.
- Do not edit wp-config.php without saving a copy first — one wrong character can take the site down.
- Do not paste code from unknown websites into your site files — use only the standard settings in the official documentation.
- Do not install random fixer plugins from unknown sources — they often make upload problems worse.
- Do not keep uploading the same huge original image and hoping — resize it first, then upload.
- Do not ignore the backup step before server changes — a backup turns a risky edit into a safe one.
- Do not change server limits yourself unless you know the server well — ask your host instead.
Frequently Asked Questions
Why do small images upload but large ones fail?
Because large images need more memory and more time to process. The server runs out of memory while creating thumbnails, or the upload passes the time limit. Resize the image before uploading, and ask your host to raise the memory limit if large originals are essential. Fixes 2, 7, and 8 cover this.
Why did uploads work yesterday and fail today?
Something changed: a plugin update, a theme update, a PHP update on the server, or a new camera producing larger files. Think about what changed, test with plugins deactivated, and check Site Health for server changes. Fixes 5 and 8 help you find the change.
Is the HTTP error caused by my internet connection?
It can be, if the connection is very slow or drops during the upload. A slow connection pushes the upload past the server time limit. Try the same upload on a faster connection, or with a smaller image, to test this. If the upload fails on every connection, the cause is on the server.
Does the error mean my site has been hacked?
No, not on its own. The HTTP error is a common, ordinary upload failure with many everyday causes. If you also see strange files, unknown admin users, or unexpected redirects, those are separate warning signs — ask your host to scan the site. The upload error alone is not evidence of hacking.
Can I upload images another way while I fix this?
Yes. Your host’s File Manager or FTP can place files in the uploads folder directly, but WordPress will not list them in the Media Library until they are registered there. Use that route only as a temporary workaround, and fix the upload itself, because the Media Library is how WordPress manages image sizes and thumbnails.
Should I increase the memory limit as high as possible?
No. Set it to a sensible value such as 256M, and no higher than your hosting plan allows. A very high limit lets one bad request use far too much server memory. If 256M does not fix uploads, the cause is something else — work through the remaining fixes instead of raising the limit further.
Conclusion
When wordpress image upload http error blocks your images, the fix is almost always the file size, the file name, a plugin, or the memory limit — not a broken WordPress. Rename the file and resize it first, then test with plugins off, then check the memory limit and the folder permissions, and finally ask your host to read the error log. Finish with a simple test: upload one normal article image and watch it appear in the Media Library with its thumbnails. That one successful upload is the proof that counts. Shrink it, name it simply, test it, and publish with pictures again.
