413 Request Entity Too Large
The request body is bigger than the server allows
Seen in nginx, Apache, APIs, CDNs
The upload or request body exceeds a size limit on the server, proxy or CDN (newer specs call this status 413 Content Too Large).
Common causes
- nginx's client_max_body_size is at its default of 1 MB.
- An application or framework body-size limit (e.g. a JSON parser limit).
- A CDN or platform upload limit (Cloudflare Free and Pro accept up to 100 MB).
How to fix it
- Raise the nginx limit in the http, server or location block: client_max_body_size 50m; then reload.
- Raise the matching limit in the app (e.g. LimitRequestBody in Apache, the body parser limit in Express).
- For very large files, upload directly to object storage with presigned URLs or in chunks.
Got a different message? Paste it into the error explainer.
Related errors
- 408 Request Timeout · The client took too long to send its request
- 431 Request Header Fields Too Large · The request headers are too big
- 400 Bad Request: Request Header Or Cookie Too Large · nginx rejected oversized headers or cookies
- 499 Client Closed Request · The client gave up before nginx answered
- Error 524: A timeout occurred · Your origin took longer than 100 seconds to respond
- Error 530 · Cloudflare could not reach the origin; see the 1xxx error on the page
- Error 1003: Direct IP access not allowed · A Cloudflare IP was requested without a hostname
- Error 1010: The owner of this website has banned your access based on your browser's signature · Your browser looks like a bot to the site's security settings
- Error 1015: You are being rate limited · You sent too many requests to a Cloudflare site
- Error 1020: Access denied · A Cloudflare firewall rule blocked your request
- Error 1033: Argo Tunnel error · The Cloudflare Tunnel for this hostname is not connected
- Error 1101: Worker threw exception · A Cloudflare Worker crashed with a JavaScript error