413 Content Too Large

What it means

Formerly called Payload Too Large. Web servers and proxies enforce a maximum body size.

Common causes

• Uploading a file above the server's size limit.

How to fix it

1. Reduce the file size or split the upload.
2. Raise the limit, for example client_max_body_size in Nginx.

Example response

HTTP/1.1 413 Content Too Large
Content-Type: text/plain; charset=utf-8

Worked example

A client sends a request the server cannot fulfill as submitted. Check the response body and request details, correct the input or permissions, and retry only after the relevant issue is resolved.

How to read this response

1. Find the status line in your browser's Network panel, API client, or server access log.
2. Read the response body and headers shown above; headers such as Location, Allow, Retry-After, and WWW-Authenticate explain the next step.
3. Use the code's class to orient your diagnosis: informational, successful, redirected, request-related, or server-side.

How to check a status code

Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.

Frequently asked questions

What it means: HTTP 413

413 Content Too Large: The request body is larger than the server allows.

Common causes: 413

Uploading a file above the server's size limit.

How to fix it: HTTP 413

Reduce the file size or split the upload. Raise the limit, for example client_max_body_size in Nginx.

Tools