{"id":2171,"date":"2026-06-05T15:33:40","date_gmt":"2026-06-05T12:33:40","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=2171"},"modified":"2026-08-02T12:09:57","modified_gmt":"2026-08-02T12:09:57","slug":"post-max-size-vs-upload-max-filesize-in-wordpress","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/post-max-size-vs-upload-max-filesize-in-wordpress\/","title":{"rendered":"post_max_size vs upload_max_filesize in WordPress"},"content":{"rendered":"

A 20 MB file can be below upload_max_filesize<\/code> and still fail because the complete multipart request exceeds a 16 MB post_max_size<\/code>. PHP may reject the body before WordPress receives either the file or the accompanying fields.<\/p>\n

Treat individual file size and total request size as separate limits, then account for every upstream layer in the same upload path.<\/p>\n

\nTable of contents<\/strong><\/p>\n
    \n
  1. What it means<\/a><\/li>\n
  2. A realistic WordPress example<\/a><\/li>\n
  3. Why it matters and when to use it<\/a><\/li>\n
  4. A straightforward route for beginners<\/a><\/li>\n
  5. The advanced route<\/a><\/li>\n
  6. Risks, common mistakes, backup, and rollback<\/a><\/li>\n
  7. How AIOWS helps: AIOWS PHP Limits<\/a><\/li>\n
  8. Related AIOWS articles<\/a><\/li>\n
  9. Conclusion and recommended route<\/a><\/li>\n
  10. Official sources<\/a><\/li>\n<\/ol>\n<\/div>\n

    What it means<\/h2>\n

    upload_max_filesize<\/code> limits one file accepted by PHP. post_max_size<\/code> limits the entire POST body, including all files, form fields and multipart overhead.<\/p>\n

    Every file must fit the first value, while the combined request must fit the second. Web servers, proxies, WordPress and application code can impose lower ceilings of their own.<\/p>\n

    A realistic WordPress example<\/h2>\n

    A media form allows a 20 MB video under the individual PHP setting, but its complete request is larger than the total POST allowance. The form arrives empty and the user sees an unhelpful validation error.<\/p>\n

    The team verifies both active values in the web handler, gives the total limit measured headroom and tests one large file as well as several medium files.<\/p>\n

    Why it matters and when to use it<\/h2>\n

    Understanding the two scopes prevents repeated changes to the wrong directive. It also explains why multi-file uploads can fail when every individual file appears valid.<\/p>\n

    Increase limits only for a defined upload need whose storage, processing time and security impact are acceptable. Large bulk workflows may be better split into batches.<\/p>\n

    A straightforward route for beginners<\/h2>\n
      \n
    1. Record each file size, the number of files and the other form data.<\/li>\n
    2. Check effective upload_max_filesize<\/code> and post_max_size<\/code> in the failing web context.<\/li>\n
    3. Identify lower WordPress, proxy, web-server or hosting limits.<\/li>\n
    4. Choose an individual ceiling that covers the required file.<\/li>\n
    5. Set a larger total allowance with room for all files, fields and multipart overhead.<\/li>\n
    6. Test a boundary file and a multi-file request through the real form.<\/li>\n<\/ol>\n

      The advanced route<\/h2>\n

      Inspect PHP warnings and raw response behavior when the POST body is rejected. An empty the parsed POST and file arrays can be a more useful clue than the application message.<\/p>\n

      Compare FPM pool or handler configuration with CLI values and trace body-size controls at the CDN, proxy and web server. Do not assume a changed php.ini<\/code> is loaded by the affected request.<\/p>\n

      Risks, common mistakes, backup, and rollback<\/h2>\n

      Large request allowances increase memory, temporary-storage and processing exposure. Raising PHP values cannot overcome an upstream 413 or insufficient disk space.<\/p>\n

      Record the former settings and verify normal uploads after the change. Roll back if resource pressure rises or the provider refuses the intended values, then reduce or redesign the workload.<\/p>\n

      \n

      How AIOWS helps:<\/p>\n

      AIOWS PHP Limits<\/h2>\n

      AIOWS PHP Limits can display the effective per-file and total POST limits together, attempt server-supported changes and help verify the resulting values. Review both file and POST limits together in the WordPress web context.<\/p>\n

      Request a coherent pair with measured total headroom, note the requested and effective values, then exercise both single- and multi-file boundaries. A changed setting is useful only when the real form succeeds.<\/p>\n

      The server may reject an override, and AIOWS cannot raise a proxy body limit or provide storage capacity. Resolve whichever lower layer still controls the upload.<\/p>\n

      Explore AIOWS PHP Limits<\/a>Compare AIOWS plans<\/a><\/p>\n<\/section>\n

      Related AIOWS articles<\/h2>\n