HTTP 413 Content Too Large vs 422 Unprocessable Content
Both HTTP 413 (Content Too Large) and 422 (Unprocessable Content) belong to the 4xx Client Error category. 413 indicates that the request payload exceeds the server's size limit. Meanwhile, 422 means that the server understands the content type and syntax, but was unable to process the contained instructions. Common in API validation errors.
Description
The request payload exceeds the server's size limit.
When You See It
When uploading files that exceed the server's maximum upload size.
How to Fix
Reduce the payload size. Check server limits (Nginx: client_max_body_size, Apache: LimitRequestBody).
Description
The server understands the content type and syntax, but was unable to process the contained instructions. Common in API validation errors.
When You See It
When form validation fails — correct syntax but invalid data (e.g., email format wrong, date in the past).
How to Fix
Check the response body for specific validation errors and correct the input data.
Key Differences
HTTP 413: The request payload exceeds the server's size limit.
HTTP 422: The server understands the content type and syntax, but was unable to process the contained instructions. Common in API validation errors.
You encounter 413 when when uploading files that exceed the server's maximum upload size.
You encounter 422 when when form validation fails — correct syntax but invalid data (e.g., email format wrong, date in the past).
When to Use Which
For 413 (Content Too Large): Reduce the payload size. Check server limits (Nginx: client_max_body_size, Apache: LimitRequestBody). For 422 (Unprocessable Content): Check the response body for specific validation errors and correct the input data.