WordPress Login Redirect Loop: Fix Being Sent Back to wp-login
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
Upload errors in the media library have specific causes. Read the exact message, then check size limits, server resources, the image file and permissions.
A WordPress image upload HTTP error appears in the media library when WordPress, your browser or your server cannot finish an upload. The message you see matters, because WordPress uses different wording for different problems: a file that is too large, a server that cannot process the image, a file type it cannot handle, or an unexpected response. This guide shows how to read the message and then check the usual causes in order: size limits, server resources, the image file, folder permissions and security rules.
Look at the exact error text first. If it says the file exceeds the maximum upload size, compare the file with your upload limit under Media → Add New or Tools → Site Health → Info. If it says the server cannot process the image, the server may be busy or short of memory, so try a smaller image. If only one file fails, convert it to JPEG or PNG. If every upload fails, check folder permissions and disk space, then security rules and plugins.
How this guide was prepared: it is research-based. We read the WordPress source code and the Site Health documentation listed under Sources, checked on October 23, 2026. We did not reproduce your error on a live host. The generic text “An error occurred in the upload” can also come from hosts or plugins, so the steps work from the specific messages that WordPress itself defines.
WordPress’s uploader defines several messages in its code, and each points somewhere different:
| Message (shortened) | What it points to |
|---|---|
| “… exceeds the maximum upload size for this site” | The file is bigger than the allowed upload size |
| “The server cannot process the image. This can happen if the server is busy or does not have enough resources…”, with a suggested maximum of 2560 pixels | Image processing failed, often because of memory, time or a very large image |
| “Unexpected response from the server. The file may have been uploaded successfully. Check in the Media Library or reload the page.” | An HTTP error after the upload; check whether the file arrived |
| “The web server cannot generate responsive image sizes for this image. Convert it to JPEG or PNG before uploading.” | A file format the image library cannot handle |
| “Please try uploading this file with the browser uploader.” | A larger file failed in the modern uploader; the older browser uploader may work |

Write down the exact text. For the “unexpected response” message, WordPress itself says that the file may have been uploaded successfully, so open Media → Library and reload before you try again. Test with a small JPEG too: if a small file works and a big one fails, the cause is size or resources; if both fail, look at permissions or security.
In WordPress, the maximum upload size is the smaller of PHP’s upload_max_filesize and post_max_size, as the core code shows. Media → Add New shows the maximum file size, and Tools → Site Health → Info → Media handling lists the maximum size of post data, the maximum size of an uploaded file, the maximum effective file size and the maximum number of files. If your file is bigger than the effective limit, resize or compress it first, or ask your host to raise the limits.
The message about the server being busy points to memory, time or CPU. WordPress also scales down very large images to a threshold of 2560 pixels by default, and the message suggests uploading a smaller image of up to that size. Resize big camera or design files before uploading. If memory is the cause, see Allowed memory size exhausted. Site Health shows whether your site uses the GD or Imagick image library; a host can tell you if one has limits.
If one file fails, open it in an image editor and save it again as JPEG or PNG, which are the formats WordPress’s image library handles most reliably. Remove unusual colour profiles and check that the file is not damaged. Try the browser uploader if WordPress suggests it.
If every upload fails, the wp-content/uploads folder may not be writable or the account may be out of disk space. Site Health’s Filesystem Permissions section shows whether WordPress can write to its folders, as the Site Health documentation explains. Ask your host to correct ownership and permissions, and check your storage quota.
A web application firewall, a security plugin or a host rule can block uploads, especially large files. Pause the likely plugin on a staging copy or ask your host to check the firewall log; our guide to finding the plugin that broke your site shows a safe order. If errors also appear in the block editor, see WordPress REST API error.
The uploader received an unexpected response from the server. WordPress says the file may still have arrived, so check the Media Library.
Raise upload_max_filesize and post_max_size in your host’s PHP settings or ask your host. The effective limit is the smaller of the two.
They need more memory and time to process. Resizing them first usually solves it.
Yes, security, image optimisation and caching plugins can. Test with them paused.
Read the message, check the limits and try a smaller JPEG. If uploads still fail, wpallsolution offers plugin support and an emergency WordPress fix. We cannot promise a result without seeing your hosting setup.
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
Most break-ins start at the login screen. Use this practical checklist for passwords, two-step login, admin accounts, attempt limits and HTTPS.
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout