HTTP status code 413 — Payload Too Large
Quick answer
Status code 413 (Payload Too Large): Request body exceeds server limits. Shrink the upload, chunk it, or raise the proxy/body size limit.
Shrink the upload, chunk it, or raise the proxy/body size limit.
413 often comes from nginx, CDNs, or API gateways before your app runs. Check client_max_body_size and similar caps.
Common causes
- Uploading a file/JSON body larger than the server or proxy allows
- A CDN or API gateway body-size cap that is stricter than your app code
How to fix it
Compress or chunk the upload, or (if you control the server) raise client_max_body_size / the gateway's body-size limit.
Related: 415410409408418405500502
Frequently asked questions
What is status code 413?
413 Payload Too Large: Request body exceeds server limits. Shrink the upload, chunk it, or raise the proxy/body size limit.
When should I expect HTTP 413?
413 often comes from nginx, CDNs, or API gateways before your app runs. Check client_max_body_size and similar caps.
What usually causes HTTP 413?
Uploading a file/JSON body larger than the server or proxy allows; A CDN or API gateway body-size cap that is stricter than your app code.
How do I fix HTTP 413?
Compress or chunk the upload, or (if you control the server) raise client_max_body_size / the gateway's body-size limit.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.