Skip to the content

413 Content Too Large

The body of the request is larger than the server accepts. The usual cause is an upload that exceeds a limit in the server's configuration.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110
Also known as
Payload Too Large, Request Entity Too Large

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When an upload or a POST is bigger than the limit. Every server sets its own, and there may be several in a row: the web server or proxy in front (client_max_body_size in nginx, 1 MB by default), the application behind it (upload_max_filesize and post_max_size in PHP), and a CDN before both.

What to do about it

As a visitor: make the file smaller, or split it.

As the owner: raise the limit at every layer the request passes, because the lowest one decides. The response can arrive before the upload has finished, and browsers then tend to report a broken connection without ever showing the 413.

Until 2022 the code was called Payload Too Large, and before that Request Entity Too Large, the name nginx still prints.

Not to be confused with

414 URI Too LongThe address is too long, not the body.
431 Request Header Fields Too LargeThe headers are too large.
411 Length RequiredThe server wants to know the length first.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12