HTTP 413 Payload Too Large Error - Meaning & Fix

The HTTP 413 Content Too Large status code indicates that the request is larger than the server's allowed limit. The server may terminate the connection if the request size exceeds what it can handle. This status was previously known as Payload Too Large.

Main causes

Uploading a file that exceeds the server's maximum allowed size.
Submitting a form with too much data.
Sending a request with too many batched operations or large headers.
Exceeding the server's limit on the length of URL or query parameters.

# Request example 
curl -X GET https://sandbox.oxylabs.io/ -H 'Accept: application/xml;q=0.9' -H 'Accept-Encoding: gzip, deflate' -H 'User-Agent: Safari/537.36'

Try Scraper API with 5K results

Common fixes

Verify the URL for any typing errors or outdated links.
Check if the resource has been moved to a different URL and update your request accordingly.
Contact the website administrator to confirm if the resource has been permanently removed.
Explore using an archived version of the resource if available via services like the Wayback Machine.

# Response example 
HTTP/1.1 413 Payload Too Large
Content-Type: text/html; charset=UTF-8
Content-Length: 49
Connection: close

413 Payload Too Large

Forget HTTP errors with Scraper API

Web scraper API

Self-Service

Public data delivery from a majority of websites

From

Try free for 1 week

Common scraping HTTP error codes

401 Unauthorized	403 Forbidden	404 Not found	405 Method not allowed	406 Not acceptable
407 Proxy authentication required	408 Request timeout	409 Conflict	410 Gone	411 Length required
412 Precondition failed	413 Payload too large	414 Uri too long	415 Unsupported media type	416 Range not satisfiable
417 Expectation failed	421 Misdirected request	422 Unprocessable entity	423 Locked	424 Failed dependency
426 Upgrade required	428 Precondition required	429 Too many requests	431 Request header fields too large	444 Connection: close
451 Unavailable for legal reasons	499 Client closed request	501 Not implemented	503 Service unavailable	505 Http version not supported
506 Variant also negotiates	507 Insufficient storage	508 Loop detected	510 Not extended	511 Network authentication required