A WordPress upload limit increase is two limits, not one. The form refuses a file for its size, and the import refuses a request for its weight, and both values come from PHP on the server, not from the theme.
The message that starts the search is usually “the uploaded file exceeds the upload_max_filesize directive”. The fix is a line in a config file, and the hard part is knowing which file and who controls it.
Three numbers behind one error
upload_max_filesize caps a single file. post_max_size caps the whole request, so a form with three files hits this one first. memory_limit caps what PHP may allocate while handling the request, and an image that needs 40 MB to resize fails there even when both size limits allow it.
A working order: memory above post size, post size above file size. If upload_max_filesize is 64M, then post_max_size should be at least 64M, and memory_limit at least 256M. Reversed values produce errors that look unrelated to the file the user chose.
The fourth number is the host. max_execution_time ends a slow import halfway, and no upload setting will help if the process is killed at thirty seconds.
Where to change it
On a server you control, the value goes into php.ini, or into .user.ini in the site root, or into the pool config of PHP-FPM. The first is global, the second is per directory and works only with PHP as FastCGI, the third is per pool and needs a reload.
On shared hosting the value is often locked. .user.ini may be ignored, and the panel shows a limit the tariff does not allow to raise. In that case the answer is a ticket to the host, or a move to a plan where the number is real.
wp-config.php is not a place for these values. ini_set there runs too late for upload_max_filesize, which is read at request start. Code that appears to work in wp-config.php usually changes a different setting.
Check what the server actually reports
A settings screen that reads ini_get is the only trustworthy source. The number in the hosting panel describes the plan, not the running process, and the two disagree after every PHP upgrade.
Load a page with a phpinfo block or read the site health screen, then compare the three values. If the site says 2M and the panel says 64M, the panel is wrong and the ticket writes itself.
After the change, restart PHP-FPM or the web server. A value in php.ini that has not been reloaded is a note in a file.
When the file is fine and the upload still fails
A plugin adds its own rule. Some form plugins check the file extension against a list, and a .webp or .zip is refused before PHP sees the size. The error names the plugin, not PHP.
The disk is full. The upload passes the size check and fails on write, and the log shows a filesystem error while the browser shows a generic message.
The proxy in front refuses the body. nginx has client_max_body_size, and a CDN has its own cap. Both sit above PHP, and both return a code before WordPress loads. When the limit is 1 MB and the plan says 64, look at the proxy first.
A limit that protects the server
Raising the number to one gigabyte is not a fix. Every request can then allocate that much, and a form left open with a large file can exhaust memory on a busy hour. Set the value to what the site really needs: media uploads, plugin archives, import files.
The login and the forms are the other half of the same problem. A large body from an unknown address is a cheap way to test a server. A rate limit and a firewall rule in front of PHP cost less than another gigabyte of memory.
Questions we hear
Can I change the limit without server access?
Rarely. .user.ini works on some hosts and is ignored on others. Without access to PHP config or the panel, the limit belongs to the host.
Why does the number revert after an update?
The panel or the deployment rewrites the config. Put the value in the file the panel does not touch, and check it after every update.
Does a bigger limit slow the site?
No. The limit is a cap, not an allocation. The memory is used only when a large request arrives.
What about multisite?
Each site can have its own .user.ini only if the host allows it. On most networks the value is set once for the whole server.
Next step
Read the three numbers on the site health screen before changing anything, then fix the smallest one that fails. The PHP configuration page lists the values that matter, the server comparison explains where PHP-FPM reads them, and the prices name the tier. PHP documents the directives in its core ini reference.
