WordPress rejects a theme, plugin, image, PDF, audio, video, or import because it exceeds the upload limit.
You do not have to become a server administrator because one part of your website stopped cooperating. Start with the checks that stay inside WordPress. If the problem moves into hosting or server configuration, I will show you where the risk begins—and where it may make more sense to hand the headache to me.
Start with the checks inside WordPress
- Confirm that the file you are uploading is the correct file, especially when several ZIP files have similar names.
- Open Media → Add New and compare the displayed maximum upload size with the actual file size.
- Open Tools → Site Health → Info and record the active PHP upload limits.
After each change, test the same action again. Change one thing at a time so you know what helped and what did not.
A good place to pause
When this leaves normal WordPress editing
If the file is larger than the limit WordPress reports, the change is usually made in the PHP settings area provided by your hosting company. It may be called PHP Options, PHP Selector, MultiPHP INI Editor, PHP Configuration, Site Tools, or Server Settings.
If you inherited the website, took over after parting ways with a developer, or normally use WordPress only to add photographs and text, you may have never opened cPanel before. That is normal, but if you are new to backend server configuration, you need to proceed with caution. This is where you can break your site.
You also do not need to end up with more damage than you bargained for just to solve one aggravating problem. The standard repair is $149.00 if you would rather hand it off.
If you are comfortable with backend server configurations, continue with the technical steps below.
Technical checks
- If you have more than one website, confirm that you are changing the PHP version used by the correct website. It is surprisingly easy to edit the wrong domain, a staging site, or an inactive PHP version.
- Compare upload_max_filesize with post_max_size; the total request limit must be large enough for the upload.
- Check memory and execution-time limits if the upload starts but fails before finishing.
- Confirm whether the host, web server, security layer, or WordPress multisite settings impose a lower limit than PHP.
Proceed with caution
Do not drop copied PHP directives into .htaccess unless your server specifically supports them. On the wrong server, one line can produce a 500 error.
Test the repair without making a second problem
- Keep a note of the original setting or filename before you change it.
- Make one change, clear only the relevant cache, and repeat the exact test.
- Check both the public page and the WordPress dashboard.
- If the error changes, stop and record the new message before continuing.
You can hand this off
If these checks have taken you beyond the part of WordPress you normally use, you can stop. I can trace the cause, make the repair, test the site, and tell you what was changed without turning one problem into your new full-time job.