413 Payload Too Large — Causes & Fix
HTTP 413 (Payload Too Large) means the request body is larger than the server is willing or able to process — the upload/payload exceeds a size limit.
- Applies to
- Any website or web server (HTTP standard)
- Time to fix
- 5–30 minutes
What it means
Causes include uploading a file bigger than the server allows, or a large request body exceeding limits (e.g. Nginx client_max_body_size). HTTP status 413 is defined in RFC 9110 (HTTP Semantics). This is a client-side (4xx) error — the request itself had a problem, so the fix is usually on the requester's side or in how the server validates the request.
Symptoms
- "413 Payload Too Large" / "Request Entity Too Large"
- Large file uploads fail
How to fix it
- 1
Reduce the upload size
1. As a user: compress or split the file to stay under the limit.
- 2
Raise the server limit (developers)
1. Increase the body-size limit (e.g. client_max_body_size in Nginx, upload_max_filesize in PHP).
Frequently asked questions
Why does my file upload fail with 413?
The file exceeds the server's request-size limit. Either shrink the file or raise the server's upload/body-size limit.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.