Compare the failing file with an ordinary upload
Compare the file size with the effective WordPress and PHP limits before asking for an account-level upload change.
This guide fits a large media upload that fails while smaller files still work. Record the file’s size, type and WordPress error without sharing private media. In Media → Add New, WordPress may display the maximum upload file size. An authorised administrator can also review Tools → Site Health → Info → Media Handling, which reports both the maximum file and post-data sizes and the smaller effective limit. Menu labels and visibility can vary with the installed version and role.
A small file that also fails suggests another problem: file type policy, temporary storage, disk capacity, image processing or permissions. Do not assume every upload error is solved by increasing a limit. Keep a suitable backup before changing application or account settings.
Identify the limiting layer
PHP distinguishes upload_max_filesize, the maximum for one uploaded file, from post_max_size, the maximum request body including its other form data. PHP says the latter must be larger for a large file upload. WordPress reports an effective limit that reflects the smaller of these values. Additional web-server or application controls may also reject a request. A panel value is useful evidence, but it is not proof that every intermediary accepts a file of that size.
If the file exceeds the shown limit, first ask whether a supported smaller image or compressed export meets the publishing need. Avoid lowering quality where the original is required for accessibility, downloads or archival purposes; the application owner decides.
Use only a changeable account setting
If a larger file is genuinely needed, check whether the purchased hosting service exposes an account-level PHP setting and what its documented ceiling is. Ask platform support to confirm the effective limit where the control is absent or unclear. Do not add arbitrary php.ini or .htaccess directives, widen filesystem permissions or request a server-wide increase. A limit change can affect memory and processing behaviour, so the operator may need to assess the file type, request size and plan before agreeing it.
Test the intended file without leaving duplicates
Upload a safe test file below the observed limit and verify that it appears in the Media Library and on a draft page. Then test the intended file after an approved change. If within-limit files still fail, record the exact time, file size/type and application error for the owner or support. Remove duplicate test uploads when finished. A successful upload does not prove image thumbnails or downstream processing worked; inspect the generated media view too.
For example, if a 4 MB file succeeds and a 12 MB file fails, note both sizes and the exact WordPress error. The displayed maximum is a clue; web-server or proxy limits may still be lower.
Frequently asked questions
Why can I upload a small file but not a large one? A per-file or request-size limit is one possibility; compare WordPress’s displayed values before changing anything.
Does free disk space mean there is no upload limit? No. Storage quota and the size allowed for one HTTP upload are different controls.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.