HTTP 413 Content Too Large
What a 413 Content Too Large response means, why it happens, and the fastest ways to fix it.
The request body exceeds what the server accepts — file uploads and big JSON payloads are the usual triggers.
- Upload exceeding nginx client_max_body_size (default 1 MB).
- API gateway payload caps (AWS API Gateway: 10 MB).
- Multipart forms with large attachments.
- Raise the server limit (e.g. client_max_body_size in nginx).
- Compress or chunk the payload; use multipart/resumable uploads for files.
- Send large files to object storage via presigned URLs instead of through the API.
Notes
HTTP status codes are defined in RFC 9110 (which replaced RFC 7231). The first digit is the class: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.
Same class: 400 · 401 · 403 · 404 · 405 · 408 · 409 · 410 · 412 · 415 · 418 · 422 · 425 · 429 · 431 · 451
All codes: HTTP status code reference
Frequently asked questions
What does HTTP 413 mean?
HTTP 413 Content Too Large: The request body exceeds what the server accepts — file uploads and big JSON payloads are the usual triggers.
How do I fix a 413 error?
Raise the server limit (e.g. client_max_body_size in nginx). Compress or chunk the payload; use multipart/resumable uploads for files. Send large files to object storage via presigned URLs instead of through the API.
Is a 413 my fault or the server's?
413 is a client error — the request itself needs to change, though server misconfiguration can also trigger it.