413 Request Entity Too Large
Your upload or request body is larger than the server is configured to accept, so it was rejected before processing.
Quick checks
- Check the file size against the site's stated upload limit.
- Compress the file or split it into smaller parts.
If you’re visiting the site
Make the upload smaller
- Compress images or videos, or zip the files.
- Upload several smaller files instead of one large one.
If you run the site
Raise the limit at every layer
- nginx:
client_max_body_size 50m;in the http, server or location block (default 1 MB), then reload. - Apache:
LimitRequestBody. - PHP:
upload_max_filesizeandpost_max_sizein php.ini. - Proxies and CDNs in front have their own limits (Cloudflare's depends on your plan).
- nginx:
For very large files
- Use chunked or resumable uploads, or presigned URLs straight to object storage.
Still not working?
If small files fail too, the limit may be set very low or a proxy in front rejects the upload. Owners should check each layer from the CDN inward.
See what’s happening
LightAtom's connections view shows the upload rate of each app, so you can see whether a large upload is actually moving.
Frequently asked questions
What does 413 Request Entity Too Large mean?
The request body, typically an uploaded file, is bigger than the server's configured maximum. The status is now officially called 413 Content Too Large.
How do I fix 413 in nginx?
Set client_max_body_size to the size you need (for example 50m) in the right block and reload nginx. The default is 1 MB.
Why do I get 413 in WordPress?
The upload exceeds the web server's or PHP's limit. Raise client_max_body_size (nginx) and upload_max_filesize and post_max_size (PHP), or ask your host.