{"id":212,"date":"2026-04-11T18:12:14","date_gmt":"2026-04-11T18:12:14","guid":{"rendered":"https:\/\/qfd.systems\/blog\/wordpress-resolving-413-request-entity-too-large-expanding-to-256mb\/"},"modified":"2026-04-11T18:12:14","modified_gmt":"2026-04-11T18:12:14","slug":"wordpress-resolving-413-request-entity-too-large-expanding-to-256mb","status":"publish","type":"post","link":"https:\/\/qfd.systems\/blog\/en\/wordpress-resolving-413-request-entity-too-large-expanding-to-256mb\/","title":{"rendered":"WordPress: Resolving 413 Request Entity Too Large (Expanding to 256MB)"},"content":{"rendered":"

[Guide] Expanding WordPress Multisite Upload Capacity to 256MB<\/h1>\n

This is a comprehensive ‘Full-Stack’ configuration guide to resolve upload limits restricted to 1MB<\/code> or 2MB<\/code> in WordPress (especially Docker-based Multisite) environments. It consists of 5 essential steps, from the server engine to application settings.<\/p>\n

—<\/p>\n

1. PHP Configuration (PHP-FPM Environment)<\/h2>\n

This is the cleanest way to override PHP settings in a Docker environment.<\/p>\n

– Filename:<\/strong> .user.ini<\/code>
– Path:<\/strong> \/var\/www\/html\/<\/code> (WordPress root directory)<\/p>\n

upload_max_filesize = 256M\npost_max_size = 256M\nmemory_limit = 512M\nmax_execution_time = 600\n<\/code><\/pre>\n
\n
Security Tip:<\/strong> To prevent external access to your .user.ini<\/code> file via a browser, add the following code to the top of your .htaccess<\/code> file:<\/p>\n
> <Files \".user.ini\">\n>     Require all denied\n> <\/Files>\n> <\/code><\/pre>\n<\/p>\n<\/blockquote>\n
—<\/p>\n
2. Forced WordPress Runtime Allocation (wp-config.php<\/code>)<\/h2>\n
When server configurations are ignored, this method forcibly injects PHP settings at the time WordPress initializes.<\/p>\n
– Filename:<\/strong> wp-config.php<\/code>
– Placement:<\/strong> Insert at the very top, immediately below the <?php<\/code> tag.<\/p>\n
@ini_set( 'upload_max_size' , '256M' );\n@ini_set( 'post_max_size', '256M' );\n@ini_set( 'memory_limit', '512M' );\n@ini_set( 'max_execution_time', '300' );\n<\/code><\/pre>\n
—<\/p>\n
3. Web Server Level Configuration (.htaccess<\/code>)<\/h2>\n
These settings apply when the Apache server processes requests.<\/p>\n
– Filename:<\/strong> .htaccess<\/code>
– Caution:<\/strong> Write these outside<\/strong> the # BEGIN WordPress<\/code> and # END WordPress<\/code> blocks to prevent them from being overwritten during WordPress updates.<\/p>\n
# --- PHP Upload Limits Start ---\nphp_value upload_max_filesize 256M\nphp_value post_max_size 256M\nphp_value memory_limit 512M\nphp_value max_execution_time 600\nphp_value max_input_time 600\n# --- PHP Upload Limits End ---\n<\/code><\/pre>\n
—<\/p>\n
4. Multisite Network Settings (The Core Solution)<\/h2>\n
In a Multisite environment, the Network Admin<\/strong> settings take precedence over all server-level configurations.<\/p>\n
1.  Navigate to My Sites > Network Admin > Settings<\/strong>.
2.  Locate the Max upload file size<\/strong> field.
3.  Change the value to 262144<\/code><\/strong> (KB unit, equivalent to 256MB) and save.<\/p>\n
<\/p>\n
—<\/p>\n
5. Nginx Reverse Proxy Configuration (Mandatory)<\/h2>\n
By default, Nginx blocks requests exceeding 1MB<\/code>. If you are using Nginx or a Reverse Proxy (e.g., Synology) in front of your server, this step is mandatory.<\/p>\n
– Configuration:<\/strong> Inside the http<\/code> or server<\/code> block.<\/p>\n
client_max_body_size 256M;\n<\/code><\/pre>\n<\/p>\n
—<\/p>\n
\u2705 Final Verification<\/h2>\n
After completing all settings, restart the container (docker restart<\/code>) and check the “Maximum upload file size: 256 MB” message under the Media > Add New<\/strong> menu.<\/p>\n
docker restart [wordpress_container_name]\n<\/code><\/pre>\n
<\/p>\n
—
Author:<\/strong> MASTER
Date:<\/strong> 2026-04-10<\/p>\n","protected":false},"excerpt":{"rendered":"
[Guide] Expanding WordPress Multisite Upload Capacity to 256MB This is a comprehensive ‘Full-Stack’ configuration guide to resolve upload limits restricted to 1MB or 2MB in WordPress (especially Docker-based Multisite) environments. … <\/p>\n","protected":false},"author":1,"featured_media":209,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[341,343,345,347,60,349],"class_list":["post-212","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tech-en","tag-10g_network-en-en","tag-dba_tuning-en-en","tag-docker-en-en","tag-nginx-en-en","tag-synology-en","tag-wordpress-en-en"],"_links":{"self":[{"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/posts\/212","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/comments?post=212"}],"version-history":[{"count":0,"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/posts\/212\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/media\/209"}],"wp:attachment":[{"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/media?parent=212"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/categories?post=212"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qfd.systems\/blog\/wp-json\/wp\/v2\/tags?post=212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}