413 HTTP Origin: Network Last updated 9 Oct 2026

HTTP 413 Content Too Large (Request Entity Too Large)

The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.

Exact message you may see request entity too largepayload too largecontent too largeclient intended to send too large body
Explore the map of this error Full error map →
Seen on: Nginx PHP Node.js Apache

Meaning

Every layer between the client and your code has its own maximum body size: CDN, load balancer, web server and language runtime. A 413 comes from whichever layer has the smallest limit. Nginx’s default client_max_body_size is only 1 MB.

Common causes

  • Nginx client_max_body_size (default 1m) too small
  • PHP upload_max_filesize / post_max_size limits
  • Apache LimitRequestBody
  • Framework body-parser limits (Express json({ limit }) default 100kb)
  • CDN/load balancer limits (Cloudflare Free: 100 MB, API gateways often 10 MB)

⚡ Quick fix

  1. Raise client_max_body_size in Nginx and reload
  2. Raise upload_max_filesize and post_max_size in php.ini (post ≥ upload)
  3. Raise the framework body-parser limit
  4. For very large files, upload directly to object storage with pre-signed URLs

Detailed fix by platform

Nginx

  1. In http, server or location:
    nginx
    client_max_body_size 50M;
  2. Run sudo nginx -t && sudo systemctl reload nginx.

PHP

  1. php.ini (or .user.ini on shared hosting):
    ini
    upload_max_filesize = 50M
post_max_size = 55M
memory_limit = 256M
  2. Restart PHP-FPM. Note: when PHP’s limit is exceeded, $_POST and $_FILES are silently empty rather than a 413.

Node.js

  1. Express:
    javascript
    app.use(express.json({ limit: '10mb' }));
app.use(express.urlencoded({ extended: true, limit: '10mb' }));

Apache

  1. Set LimitRequestBody 52428800 (bytes) in the vhost or .htaccess.

How to diagnose

  1. Size — How large is the request body?
  2. Response origin — Which layer answered — check the Server header and HTML body of the 413
  3. Limits — CDN → load balancer → web server → runtime → framework

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

100 — HTTP 100 Continue (HTTP)1001000 — Cloudflare Error 1000: DNS points to prohibited IP (Cloudflare)1000400 — HTTP 400 Bad Request (HTTP)400408 — HTTP 408 Request Timeout (HTTP)408411 — HTTP 411 Length Required (HTTP)411413 (Cloudflare 100 MB) — Cloudflare 413 Request Entity Too Large (upload over the plan limit) (Cloudflare)413 (Cloudflare 100 M…416 — HTTP 416 Range Not Satisfiable (HTTP)416431 — HTTP 431 Request Header Fields Too Large (HTTP)431413

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.