# Error 413

import { Render } from "~/components";

## 413 Payload Too Large

The `413 Payload Too Large` status code indicates that the server refuses to process the request because the payload sent by the client exceeds the server's acceptable size limit. The server may optionally close the connection. If this refusal would only happen temporarily, then the server should send a `Retry-After` header to specify when the client should try the request again.

For more details, refer to [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110#section-15.5.14).

### Common use cases

The `413 Payload Too Large` status code often occurs when clients attempt to upload large files, such as videos or images, or send oversized request bodies, like JSON or XML payloads, that exceed the server's size limits. This can also happen during file transfers or API requests involving large datasets, prompting the server to reject the request.

### Cloudflare-specific information

For incoming requests to a domain proxied through Cloudflare, the upload limit depends on the domain's plan. Requests exceeding this limit receive a `413 Request Entity Too Large` error.

|  | Free | Pro | Business | Enterprise |
| - | - | - | - | - |
| Availability | Yes | Yes | Yes | Yes |
| Max upload size | 100 MB | 100 MB | 200 MB | Up to 5 GB |

Keep in mind, customers can adjust the **Maximum Upload Size** from the zone's **Network** page. Enterprise customers can self-serve any value up to 5 GB; uploads larger than 5 GB require additional configuration — contact your account team. Setting the limit below the size of an incoming request causes a `413`.

For uploads to a proxied domain, use smaller, separate requests if your application supports them, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/billing/manage/change-plan/).

### Outbound uploads from Containers and Durable Objects

Cloudflare limits each HTTP request body sent to an external service by a Durable Object or through a Container outbound handler to **100 MiB by default**. Increasing **Maximum Upload Size** for your application's domain does not increase this limit.

Check which request returned `413`: the incoming upload to your application or the outbound upload to another service. The destination service can also reject oversized requests.

For the applicable limits, upload guidance, and how to request an increase, refer to:

- [Containers outbound HTTP request body size](/containers/platform/limits/#outbound-http-request-body-size).
- [Durable Objects outbound HTTP request body size](/durable-objects/platform/limits/#outbound-http-request-body-size).