HTTP 413 Payload Too Large

What Does HTTP 413 Mean?

HTTP 413 Payload Too Large (formerly 'Request Entity Too Large') indicates that the request body exceeds the server's configured maximum size. The server refuses to process the request because the payload is too large.

Common scenarios include: file upload exceeding the server's maximum upload size, API request with a body larger than allowed, and POST data exceeding the configured limit. Web servers like Nginx (client_max_body_size) and Apache (LimitRequestBody) have configurable limits.

The server may close the connection to prevent the client from continuing to send data. To fix this, either reduce the payload size, increase the server's limit, or implement chunked uploads for large files.

Common Causes of 413 Payload Too Large

The request payload exceeds the server's maximum size limit. Common causes: file upload too large, request body exceeding API limits, and bulk data submission exceeding configured maximums.

Server limits: Nginx default 1MB (client_max_body_size), Apache default 1GB (LimitRequestBody), and various API-specific limits.

How to Fix 413 Payload Too Large

Reduce the file or payload size. For website owners: increase the upload limit in server configuration (Nginx: client_max_body_size, Apache: LimitRequestBody, PHP: upload_max_filesize and post_max_size). For large file uploads, implement chunked uploading.

Consider implementing client-side file size validation to provide immediate feedback before upload.

Related Status Codes

Frequently Asked Questions

What does HTTP 413 mean?

HTTP 413 Payload Too Large is a client error response. HTTP 413 Payload Too Large (formerly 'Request Entity Too Large') indicates that the request body exceeds the server's configured maximum size. The server refuses to process the request because the pay

Is HTTP 413 an error?

Yes, HTTP 413 is a client error. Client Error responses (cli) indicate the request contains an error.

How do I fix HTTP 413?

Reduce the file or payload size. For website owners: increase the upload limit in server configuration (Nginx: client_max_body_size, Apache: LimitRequestBody, PHP: upload_max_filesize and post_max_size). For large file uploads, implement chunked uplo

What causes HTTP 413 Payload Too Large?

The request payload exceeds the server's maximum size limit. Common causes: file upload too large, request body exceeding API limits, and bulk data submission exceeding configured maximums.

Is HTTP 413 permanent or temporary?

HTTP 413 is situational — it depends on the underlying cause. Fix the root cause to resolve it.

🔍 Check Your IP Address

While you're here, find out your public IP address, location, and ISP details instantly.

Check My IP →