When WordPress refuses a media upload because the file is too large, the number shown on the Media Add New screen usually comes from the hosting PHP configuration, not from a switch inside WordPress. The right repair is a measured hosting change followed by a public check, not simply choosing the largest number available.
This guide covers the account-level paths in cPanel and Plesk, along with the checks that keep a larger upload allowance from becoming a storage, performance, or security surprise. For broader troubleshooting, start at the WordPress support hub.
Before you increase the limit
Take a current backup and choose a limit that matches a real workflow. A site that occasionally receives a large product image needs a different allowance than a team importing media archives. Also check available disk space, temporary storage, and the account’s resource limits before changing PHP settings. A failed upload can be caused by a file type restriction, an image-processing memory limit, a timeout, or a full account even when the displayed size limit looks generous.
In WordPress, open Media > Add New and note the maximum upload size currently displayed. Keep that number with the active PHP version and handler so you can prove the change took effect. The WordPress Media Add New documentation confirms that the displayed maximum is set by the hosting provider.
Understand the three PHP values that matter
- upload_max_filesize is the per-file upload ceiling.
- post_max_size is the maximum size of POST data, which includes uploads. Keep it larger than the file ceiling.
- memory_limit needs enough headroom for WordPress, the image editor, and the upload workflow. It is not an upload-size substitute.
cPanel’s MultiPHP INI Editor documentation identifies both upload-related values and recommends keeping the POST limit above the upload limit and below the memory limit. Make only the smallest change that solves the documented need.
Increase the limit in cPanel
- Sign in to cPanel and confirm which PHP version the domain uses.
- Open Software > MultiPHP INI Editor, then choose the domain or the active PHP mode provided by the host.
- Raise upload_max_filesize to the planned file ceiling.
- Set post_max_size to a slightly larger value, then review memory_limit rather than raising it blindly.
- Save the configuration and reload the WordPress Media Add New screen after the panel has applied it.
Shared hosts can restrict which values an account may change. If the editor is absent, the control is locked, or the visible WordPress maximum does not change, ask the host to confirm the active PHP handler and the effective upload, POST, memory, timeout, and proxy limits. Do not edit server-managed configuration files from a WordPress account to work around a panel restriction.
Increase the limit in Plesk
- In Plesk, open Websites & Domains, find the affected domain, and select PHP or PHP Settings.
- Confirm the current PHP version and handler before changing settings.
- Adjust upload_max_filesize and post_max_size, then review the memory limit and save the change.
- Allow the domain configuration to apply, then return to WordPress and recheck the displayed maximum.
Plesk documents that domain-level PHP settings and available choices can be controlled by the subscription or hosting provider. Its PHP Settings guide also notes that each domain can have its own PHP version, handler, and editable directives. If the required controls are unavailable, request the change from the provider rather than changing the PHP version just to expose a different menu.
Verify the fix without creating a new problem
- Reload the Media Add New screen and confirm the maximum now matches the intended policy.
- Upload a non-sensitive test file near the expected working size, then confirm it appears correctly in the Media Library.
- Review the site’s available storage and remove any failed test uploads you do not need.
- If image uploads still fail, check image dimensions, available PHP memory, account resource limits, and the site’s error log before increasing values again.
Use this WordPress media and storage check to find oversized files, and review the active runtime with the WordPress PHP version and extensions guide. If the site is slow or resources are already constrained, work through WordPress hosting resource limits before raising upload allowances further.
When the upload limit is not the real issue
A larger PHP limit will not fix a blocked file type, exhausted disk space, a reverse-proxy request limit, a low timeout, or a server-side malware policy. Treat the visible WordPress maximum as one checkpoint in the upload path. Keeping the limit intentional, reviewing who can upload files, and validating the full workflow after each change gives you a more dependable result than making the number unlimited.