{"id":16130,"date":"2025-07-24T18:17:14","date_gmt":"2025-07-24T16:17:14","guid":{"rendered":"https:\/\/surver.nl\/?post_type=kennisbank&p=16130"},"modified":"2025-08-21T12:35:23","modified_gmt":"2025-08-21T10:35:23","slug":"status-code-413","status":"publish","type":"kennisbank","link":"https:\/\/surver.nl\/en\/kennisbank\/statuscode-413\/","title":{"rendered":"What does status code 413 Request Entity Too Large mean?"},"content":{"rendered":"
\"413<\/figure>\n\n\n\n

You send data to a server, such as a form with a file, an API call or a large JSON payload, and immediately get back an error message: 413 Request Entity Too Large. <\/p>\n\n\n\n

Status code 413 is a server's way of saying: what you send me is bigger than I want to accept<\/em>. Not because it's broken. Not because it is improperly constructed. Purely because of its size.<\/p>\n\n\n\n

What exactly happens at a 413?<\/h2>\n\n\n\n

A 413 error occurs when the server receives your request, reads the headers and then decides: this body (the body) is too large. The request is not processed further. No parse, no storage, no processing. Just cut off immediately.<\/p>\n\n\n\n

Sometimes this is caused by a file you upload. Sometimes by an oversized JSON array. And sometimes by something unexpected: a user filling a rich text field with huge embedded content, for example.<\/p>\n\n\n\n

The response usually looks like this:<\/p>\n\n\n\n

HTTP\/1.1 413 Request Entity Too Large<\/em><\/strong><\/p>\n\n\n\n

In practice, this means either reducing your payload or adjusting your server.<\/p>\n\n\n\n

What determines what is \"too big\"?<\/h2>\n\n\n\n

It depends on the software stack.<\/p>\n\n\n\n