IT HAS BEEN a difficult week for many WordPress site owners trying to upload media. On a regular basis, users encounter a frustrating error when attempting to add a large image or video file. One of the main culprits will be the PHP file upload limit, a server-side setting that controls the maximum size for uploads. Another will be those who have unspecified "connections" to older hosting configurations where these limits are set very low. It is unclear exactly how wide the net will be cast and how many users will be forced to find workarounds. But for anyone thinking about where to host their media-rich site, a server with restrictive PHP limits now looks a dicey proposition.
This common barrier isn't a WordPress flaw, but a safeguard set at the server level using PHP directives. When you try to upload a file that exceeds this limit, the process is halted, often with a generic error that doesn't clearly point to the upload_max_filesize setting. This can be especially confusing when you're simply trying to upload a high-resolution header image for your WordPress site. Understanding that this is a server configuration issue is the first step to resolving it, moving the problem out of WordPress's core functionality and into the realm of server management.
The primary settings involved are upload_max_filesize and post_max_size in the php.ini configuration file. The upload_max_filesize dictates the largest single file you can upload, while post_max_size must be larger than that, as it governs the total size of all data in a POST request. If you're building a site and need to test code changes, being familiar with editing configuration files on a Mac can be very helpful for local development before applying changes to your live server. These values are often set conservatively by hosting providers to ensure server stability and fair resource usage across all accounts on a shared server.
How to Increase the PHP File Upload Limit in WordPress
Increasing your PHP file upload limit is a standard procedure, but the method depends on your level of server access and your hosting environment. For most users, the process involves modifying a PHP configuration file. Here is a clear, step-by-step guide to the most common methods.
- Step 1: Check Your Current Limits. First, confirm what your current limits are. You can do this by creating a simple PHP info file or by checking within your WordPress admin dashboard if your hosting control panel (like cPanel) provides a tool for it. Knowing the starting point is crucial.
- Step 2: Access the php.ini File (Preferred Method). The most effective way is to edit the php.ini file. You can often find this in your site's root directory via FTP or your host's file manager. If you don't see one, you may need to create it. Look for the lines containing upload_max_filesize and post_max_size.
- Step 3: Modify the Key Values. Change the values to your desired limit, for example: upload_max_filesize = 64M and post_max_size = 128M. Remember to use M for Megabytes. Always ensure post_max_size is larger than upload_max_filesize.
- Step 4: Alternative via .htaccess. If you cannot use a php.ini file (common on some shared hosts), you can try adding directives to your .htaccess file. Add lines like: php_value upload_max_filesize 64M and php_value post_max_size 128M. Note: This only works if your host allows PHP settings to be overridden in .htaccess.
- Step 5: Save and Test. After saving the file, clear any server or site cache you might have. Then, try uploading a file that was previously too large to confirm the change worked. A quick page reload or cache purge is often necessary for the new settings to take effect.
Sometimes, after making backend changes, you might need to perform a full reset of your managed WordPress hosting environment to ensure all services recognize the new configuration, especially if you're not seeing the changes apply. It's also wise to consider the structure of your site; organizing your media into specific WordPress media categories can help you manage larger libraries more efficiently once you've increased your upload capacity. For site administrators handling lots of user-generated content, understanding how to manage and parse RSS feeds with PHP can be another useful skill for automating content flow. And if you ever need to clean house, knowing the correct way to permanently delete a WordPress post and its associated media is key to maintaining a tidy and performant database.
What is the default PHP file upload limit?
The default PHP file upload limit varies significantly depending on your hosting provider and their server configuration. There is no single universal default. However, in many shared hosting environments, it is commonly set to a conservative 2MB or 8MB. This is done to prevent a single user from consuming excessive server resources and to maintain stability for all sites on the server.
You can easily check your specific limit by looking at the "Upload max filesize" information in your hosting control panel (like cPanel under PHP Options) or by using a plugin that displays server information in your WordPress dashboard. Some premium or developer-focused hosts may set higher defaults, such as 64MB or even 256MB, to accommodate more robust sites. Always verify your actual limit rather than assuming.
Can I use a plugin to increase the upload limit?
No, you cannot use a standard WordPress plugin to directly and permanently increase the PHP file upload limit. This is a critical server-level configuration that is controlled by the php.ini or .htaccess files, which are outside of WordPress's operational scope. Plugins run within the WordPress environment, which is itself subject to these server rules.
Some plugins may claim to help by providing an interface to check your current limit or by offering instructions, but they cannot override the core PHP settings on the server. The change must be made at the server configuration level. Relying on a plugin for this can create a false sense of a fix. For sourcing design elements, it's better to use trusted resources like a reputable free design file website that offers properly sized assets to help you stay within common limits before you adjust them.
What's the difference between upload_max_filesize and post_max_size?
It's important to understand that these are two distinct but related settings. The upload_max_filesize directive specifies the maximum size for a single uploaded file. The post_max_size directive sets the maximum total size allowed for the entire POST request, which includes the file data plus any form field text.
Because the file is part of the POST request, post_max_size must always be set to a value larger than upload_max_filesize. If they are set to the same value, you may still encounter errors because the total request size exceeds the post limit once other form data is added. A good practice is to set post_max_size to about double your upload_max_filesize to ensure smooth operation.
| Setting | Purpose | Example Value | Must Be |
|---|---|---|---|
| upload_max_filesize | Max size for one file | 64M | Less than post_max_size |
| post_max_size | Max size of entire POST request | 128M | More than upload_max_filesize |
| max_execution_time | Max script run time | 300 | Increased for large uploads |
| memory_limit | PHP script memory allocation | 256M | Sufficient for processing |
Why do I still get an error after changing php.ini?
If you've updated your php.ini file but still receive upload errors, the most common reason is that the new configuration has not been loaded. Servers cache PHP configurations, so you often need to restart your web server (like Apache) for changes to take effect. On shared hosting, this might happen automatically after a short delay, or you may need to use a "Restart PHP" option in your control panel.
Other reasons
