πŸ“„
Webhosting

Resolving 413 Request Entity Too Large

πŸ“… 24 October 2026 ✏️ 24 October 2026 ⏱ 4 min leestijd

Getting a 413 error message when uploading or submitting forms? Read the causes here and how to quickly resolve this yourself.

The error message 413 Request Entity Too Large means your server is refusing a file or request because it is larger than the configured limit. This often happens when uploading large images, importing a database, or submitting a form with an attachment. The solution usually lies in increasing a few settings in PHP and your web server, or in reducing the size of the file itself.

What exactly is a 413 error?

A 413 error message is an HTTP status code that indicates the request you’re sending to the server is too large. This can happen when uploading a file via WordPress, importing a large database via phpMyAdmin, or even when submitting a contact form with a large attachment. The server stops the request before it’s fully processed, because a limit has been set on the maximum size of incoming data.

Common causes

The 413 error can be caused by multiple settings, depending on how your hosting is configured:

  • PHP upload_max_filesize is set too low for the file you’re trying to upload.
  • PHP post_max_size is smaller than the file size, causing the entire request to be rejected.
  • The web server (Nginx, Apache, or LiteSpeed) has its own limit on request size, separate from PHP.
  • A plugin configuration, such as a form plugin or import tool, further restricts the upload size itself.
πŸ’‘ Tip: First check whether the problem lies with PHP or with the web server. If your error message comes from Nginx or LiteSpeed (often without PHP formatting), the problem is at the web server level.

Resolving the 413 error: step by step

1

Check the current PHP limits

In Plesk, go to the PHP Settings of your domain and check the values of upload_max_filesize and post_max_size.

2

Increase upload_max_filesize

Set this value higher than the file you want to upload, for example from 8M to 64M, and save the settings.

3

Increase post_max_size accordingly

This value must always be equal to or greater than upload_max_filesize, otherwise the error will keep occurring.

4

Check web server limits

With Nginx, client_max_body_size plays a role; with LiteSpeed, there’s a similar setting. If in doubt, ask your hosting provider to check this.

5

Test again

Reload the page and try the upload or form again. If it still doesn’t work, clear your browser cache as well.

Preventing the 413 error

Large files remain prone to this error, even with more generous limits. Compress images before uploading them, split large database files when importing, and check with forms whether attachments are really necessary or could be better shared via a link. This way you not only prevent this error message, but also keep your website faster and more organized.

If you get stuck adjusting settings, you can visit the knowledge base for more explanation per situation, or check your web hosting via your web hosting package.

Frequently asked questions

Why do I get this error even with a small file?

It might not be the file itself but the total size of the request, such as with a form containing multiple fields and an attachment combined. Check both upload_max_filesize and post_max_size in that case.

Can I adjust these settings myself?

Yes, in Plesk you can usually do this yourself via the PHP settings of your domain, without needing your hosting provider’s involvement.

Does increasing the limit always work?

Not always. Sometimes the web server blocks the request before it even reaches PHP, in which case that limit needs to be adjusted as well.

Conclusion

A 413 error occurs because an upload or request is larger than the configured limit in PHP or the web server. By increasing upload_max_filesize and post_max_size, and checking the web server limit if necessary, you can usually resolve this quickly yourself.

View web hosting β†’

Was dit artikel nuttig?