HTTP 413 Content Too Large
Status code 413 · Class 4xx
Content Too Large
Also searched as: error 413, HTTP 413, 413 request entity too large, 413 payload too large
What it means
The server refused the request because the body is larger than it allows, typically a file upload or large form/API payload. Older documentation calls it '413 Payload Too Large' or 'Request Entity Too Large'. It is almost always a server size limit, not a broken file.
Applies to: nginx, Apache, IIS, PHP, WordPress, Cloudflare
How to fix HTTP 413 Content Too Large
- Compress or resize the file (images, videos, PDFs) and upload again
- Split the upload into smaller files, or use the service's dedicated large-file uploader
- If you own the site on nginx: raise 'client_max_body_size' (default 1m) in the http, server or location block and reload nginx
- If you own the site on PHP: raise 'upload_max_filesize' and 'post_max_size' in php.ini, then restart PHP-FPM
- If you own the site on Apache: check 'LimitRequestBody'; on IIS check 'maxAllowedContentLength' under requestLimits
- If you own the site behind a CDN: check its upload limit (Cloudflare Free and Pro plans cap request bodies at 100 MB)
- If you own the site on WordPress: confirm the new limit under Media > Add New after the PHP change
Why it happens
Every layer (CDN, load balancer, web server, PHP or app framework) enforces its own maximum request body size, and the smallest one wins. nginx's default of 1 MB is the most common cause of surprise 413s.
FAQ
How do I fix 413 Request Entity Too Large on WordPress?
Raise upload_max_filesize and post_max_size in PHP and client_max_body_size in nginx (or LimitRequestBody in Apache), then reload the services.
Is 413 caused by my internet connection?
No. It is a size limit on the server; a faster connection will not help.
Related errors
Source: IANA HTTP Status Code Registry · fixes written and reviewed by the editors (see our editorial policy)
Last updated: