---
title: "HTTP 413 Payload Too Large — What It Means & How to Fix It"
description: "HTTP 413 Payload Too Large: The request body exceeds the server's maximum allowed size. Common causes, fixes and how to monitor it."
url: https://uptrack.app/http/413
---

# HTTP 413 Payload Too Large

The request body exceeds the server's maximum allowed size. The server refuses to process the request because the payload is larger than it is configured to accept.

## What does HTTP 413 mean?

The request body exceeds the server's maximum allowed size. The server refuses to process the request because the payload is larger than it is configured to accept.

## Common causes

1. 1  
Uploading a file that exceeds the server's upload size limit (e.g., nginx default is 1MB via client\_max\_body\_size).
2. 2  
Sending a JSON or form body that is too large, often due to base64-encoded images or large data payloads embedded in the request.
3. 3  
A reverse proxy or CDN (e.g., Cloudflare) has a lower body size limit than your application server.

## How to fix it

1. 1  
Reduce the payload size. Compress files before uploading, or use multipart uploads for large files instead of sending them in a single request.
2. 2  
Increase the server's body size limit: client\_max\_body\_size in nginx, LimitRequestBody in Apache, or the equivalent in your application framework.
3. 3  
Check all layers of your stack — the CDN, load balancer, reverse proxy, and application server each have their own size limits. The lowest one wins.

## Monitor for HTTP 413 errors

If your upload endpoint suddenly returns 413 for files that previously worked, a configuration change likely lowered the size limit. Uptrack catches this by monitoring the endpoint's response codes.

## Catch HTTP errors before your users do

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 409 Conflict](https://uptrack.app/http/409)
- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 405 Method Not Allowed](https://uptrack.app/http/405)
- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422)
- [HTTP 403 Forbidden](https://uptrack.app/http/403)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 304 Not Modified](https://uptrack.app/http/304)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 301 Moved Permanently](https://uptrack.app/http/301)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 201 Created](https://uptrack.app/http/201)
- [HTTP 200 OK](https://uptrack.app/http/200)
