All HTTP status codes

HTTP 413 Content Too Large

Client Error

The request body exceeds what the server is willing to process. Formerly called 'Payload Too Large'.

Defined in RFC 9110

Common causes

  • Upload exceeds server/proxy body-size limits (nginx client_max_body_size, serverless payload caps)
  • Verbose JSON payloads beyond API limits

How to fix it

  1. Raise the limit where appropriate (nginx, API gateway, function config)

  2. Chunk or multipart large uploads; compress payloads

  3. Send files to object storage via signed URLs instead of through the API

Related status codes

400 Bad Request

The server can't or won't process the request because the client sent something malformed — invalid JSON, bad query parameters, broken headers or framing.

414 URI Too Long

The request URL exceeds the server's limit — usually a symptom of stuffing data into the query string.

411 Length Required

The server insists on a Content-Length header and the request didn't include one (e.g. chunked uploads it refuses to accept).

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.