4xx Client error

413 Content Too Large

The request body is bigger than the server allows.

What 413 means

Formerly "Payload Too Large". Common for file uploads and for proxies like nginx (default limit 1 MB).

Common causes

Uploading a file over the API's limit.
nginx's client_max_body_size or a cloud function's payload limit.

How to fix it

If you're calling an API

Compress or split the upload, or use the API's multipart or presigned-upload endpoint.

If you run the server

Raise the limit (nginx: client_max_body_size) or offer direct-to-storage uploads.

Should you retry?

Not with the same body.

Example response

HTTP

HTTP/1.1 413 Content Too Large
Content-Type: application/problem+json

{
  "type": "about:blank",
  "title": "Content Too Large",
  "status": 413,
  "detail": "The request body is bigger than the server allows."
}

Defined in: RFC 9110 (HTTP Semantics). 413 is a client error: change the request before retrying.

Debugging an API call? Convert your request with the cURL converter, check the response with the JSON formatter, or see whether the API is down on its status page.

HTTP 413 FAQ

What does HTTP 413 mean?

413 Content Too Large: The request body is bigger than the server allows. Formerly "Payload Too Large". Common for file uploads and for proxies like nginx (default limit 1 MB).

Is 413 a client or server error?

It's a client error (4xx): something about the request needs to change before it can succeed.

How do I fix a 413 error?

Compress or split the upload, or use the API's multipart or presigned-upload endpoint.

Should I retry after a 413?

Not with the same body.

Other 4xx status codes

All HTTP status codes