Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

PHP upload limits: why large uploads fail before WordPress sees them

Published August 2026 · 2 min read · Updated 2026-09-05

PHP upload limits come from several separate boundaries, not one setting. The browser, reverse proxy/web server, PHP request limits, application checks, filesystem quota, temporary directory, and post-processing step can each reject or truncate an upload.

Compare upload_max_filesize and post_max_size

PHP upload_max_filesize limits an individual uploaded file while post_max_size limits the entire request body. A multipart request needs room for form fields and overhead, so post_max_size normally needs to exceed the intended file size.

memory_limit is not identical to upload size, though applications that load the entire file into memory may still need headroom.

Check the web-server request boundary

nginx client_max_body_size, Apache directives, proxies, WAFs, and external platforms can reject the request before PHP sees it. Inspect HTTP status and server logs to locate the layer.

If a CDN/proxy is in front, its plan-level request limit may be outside server configuration entirely.

Verify temporary and destination storage

Uploads may first land in a temp directory and then move into an application directory. Check filesystem free space, inodes, quotas, ownership, permissions, and the PHP temp path.

An application can report a generic upload failure for a filesystem problem.

Prefer chunked/direct workflows for very large data

A huge single HTTP upload is fragile across browser, proxy, timeout, and application layers. Where supported, use resumable or chunked upload, or an appropriate file-transfer/storage workflow, so every web limit does not need to be raised dramatically.

  • Check PHP file and request limits.
  • Check proxy/web-server body limits.
  • Verify temp/destination storage.
  • Use resilient transfer methods for large files.

Next step

Compare upload_max_filesize, post_max_size, web-server limits, temporary storage and application checks to find the layer rejecting a large upload.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move