How to Increase the PHP Upload Limit for Joomla
Inspect the current effective PHP values
Before changing anything, inspect upload_max_filesize and post_max_size in the PHP runtime serving Joomla. Joomla System Information/PHP information or the hosting control panel can expose these values. Do not rely only on a shell command because CLI and web PHP can use different configuration files and handlers.
Choose a sensible target and preserve the size relationship
Set upload_max_filesize high enough for the largest legitimate file Joomla must accept. Set post_max_size higher because it limits the entire POST request, including the uploaded file and form data. PHP accepts shorthand sizes such as M for megabytes. Avoid setting unlimited or extremely large values without an operational need.
Use the hosting provider's supported configuration method
Depending on the environment, PHP values may be managed through a hosting control panel, php.ini, .user.ini, PHP-FPM pool, or server configuration. Some directives or hosts do not allow per-directory overrides, and managed plans may enforce hard ceilings. Follow the provider's documented method instead of adding unsupported directives to Joomla's .htaccess.
Reload the PHP service when the environment requires it
PHP-FPM or web-server configuration changes may require a pool reload or service restart before new values take effect. Shared hosting control panels often handle this automatically. After changing the limit, recheck the effective value from Joomla's web runtime; editing a file successfully does not prove the active PHP process loaded it.
Check Joomla and upstream limits too
Increasing PHP does not override a lower Media/extension limit, web-server body-size limit, CDN restriction, WAF rule, or hosting quota. Joomla's Update documentation notes that update-package uploads fail when the package exceeds PHP upload_max_filesize or post_max_size, but those are only two possible limits in the request path.
Confirm temporary storage and resource capacity
Larger accepted requests consume network time, temporary disk, PHP processing time, and potentially memory during later handling. Verify free disk space, temporary directories, timeouts, and hosting resource limits before allowing much larger uploads. Keep executable or otherwise dangerous file types restricted regardless of the byte limit.
Verify with a fresh Joomla upload
After the configuration is active, upload a known safe file near the new target size through the same Joomla feature that previously failed. Confirm the request completes and inspect logs for warnings. Document the final PHP values and where they are configured so a future PHP upgrade or server migration does not silently reset them.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.