HTTP 413 Content Too Large

Client error code, RFC 9110, section 15.5.14

What it means

The request body (an upload, for example) is bigger than the server is willing to accept.

A real response

This is the request and the answer our test server gave when we asked it to return 413.

GET /c/413 HTTP/1.1
Host: example.com

HTTP/1.1 413 Content Too Large
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 11

<p>demo</p>

If you run the site

RFC 9110 names this "Content Too Large". The limit is set by the web server, the proxy or the application, and the smallest limit wins. In nginx the setting is client_max_body_size. If the situation is temporary, send Retry-After. Show the user the limit before they start the upload.

If you are a visitor

Make the file smaller (compress the picture or split the document) and try again.

A common mistake

Raising the limit in the application while a proxy in front of it still has the old, smaller limit.

Registered in the IANA HTTP Status Code Registry as Content Too Large, defined in RFC 9110, section 15.5.14.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.