How to Fix '413 Request Entity Too Large' Error on WordPress (2023)

Themeisle content is free. When you purchase through referral links on our site, we earn a commission. Learn More

Looking for ways to fix the “413 request entity too large” error on your WordPress website? 🤔

Or, some situations, you might see this error as “413 payload too large.”

Either way, the “413 request entity too large” HTTP error appears when you are trying to upload a file that exceeds your server upload limit.

Because it’s a server-level HTTP error, it’s not specific to WordPress. However, a lot of WordPress sites can experience this error because of their server’s configuration.

The solution 🎯 to this problem is to upload smaller files or increase your web server’s upload limit if possible. Or, in urgent situations, you might bypass the error by uploading the file via FTP.

👉 In this article, we will show you how to fix the “413 request entity too large” error by reducing the file size and/or increasing the upload limit of your WordPress website.

Let’s get started.

📚 Table of contents:

  1. Upload smaller files
  2. Upload the file via FTP instead
  3. Modify PHP.ini
  4. Modify functions.php file
  5. Modify .htaccess file
  6. Modify nginx.conf file

How to fix the '413 request entity too large' #error on #WordPress 🐛

What causes the “413 request entity too large” error?

How to Fix '413 Request Entity Too Large' Error on WordPress (1)

Every hosting server sets an upload limit, which is generally sufficient for uploading a file to a WordPress website.

Some files, be it images, plugins, or themes, are larger than your typical files and demand more storage space.

When you try to upload such files to your WordPress site, they exceed the upload limit and overwhelm the server.

That’s when the server shows you the “413 request entity too large” error.

The error itself offers further insight into the problem when it’s broken down into the following parts: “413,” “request entity,” and “too large.”

(Video) How To Fix '413 Request Entity Too Large' WordPress Error using .htaccess?

  • “413” refers to the 4xx HTTP errors, which are generally related to problems between a hosting server and the browser.
  • “Request entity” refers to the request being made to the server.
  • And “too large” refers to the request being much bigger than what the server can serve.

Fortunately, the error can be easily 😎 overcome by reducing the file size or increasing the upload limit.

In the next section, we will show you how to fix the error and upload large files to your WordPress website. 👇

How to fix the ‘413 request entity too large’ error

Below, we’ll share six different solutions to this problem. The first two solutions are focused on bypassing the issue, while the final four solutions involve adjusting your server’s settings to fix the issue permanently.

⚠ Before you proceed, take a backup of your entire website just in case.

In the following tutorial, you will need to go to the backend of your website and make modifications to important WordPress files. This is risky business. A single misstep and you can end up with a broken website.

If things do go wrong, you can use the backup to get your site up and running in no time. So take a backup before you dive into the solutions.

1. Upload smaller files

The easiest solution is to upload a small file to your WordPress website.

If you are uploading an image, be sure to reduce the size using tools like TinyPNG and IMG2Go.

💡 On another note, using an image optimization solution like Optimole might help as well.

If you are uploading a plugin or a theme, then try finding an alternative plugin or theme that comes packed in a smaller size.

For many of you uploading a smaller file may not be possible. In that case, try the next solution.

2. Upload the file via FTP instead

Another way to bypass this issue is to try uploading the file via FTP instead of doing it from inside your WordPress dashboard.

Depending on your server’s configuration, this may or may not work. However, it’s good to check for two reasons:

  1. If it works, you’ll be able to get the file uploaded to your server.
  2. If it doesn’t work, you can be confident that it’s a server-level issue rather than anything wrong with WordPress itself.

For plugins and themes, you can upload them straight to the relevant folder.

For media files, you can upload them straight to the relevant uploads folder. However, you would need to use a plugin like Add From Server to register them to the WordPress Media Library if you want to access these files in the Media Library.

(Video) How to Fix HTTP 413 Request Entity Too Large Error in WordPress | Tutorial

👉 For more, check out our full WordPress FTP guide.

3. Modify PHP.ini

The PHP.ini files control file upload sizes, file timeouts, and resource limits. You can use this file to increase the upload limit of your WordPress website.

Here’s how to do it in cPanel – the steps at your host might be slightly different if your host doesn’t offer cPanel.

Step 1: Open your hosting account and go to cPanel and look for the PHP.ini file.

Some hosting providers have the file located in the File Manager. So if you can’t find the PHP.ini file in cPanel, open File Manager in cPanel.

Step 2: In the File Manager, you will find the PHP.ini file inside the public_html folder or in the folder named after your website.

How to Fix '413 Request Entity Too Large' Error on WordPress (2)

Step 3: Right-click on the PHP.ini file and select Edit. You should be able to see the following code:

max_execution_time (max time to upload)upload_max_filesize (max upload size)post_max_size (max post size)

Step 4: Change the values to a number of your preference. And hit the Save Changes button before exiting.

Now, open your WordPress dashboard and check if you can upload the file without encountering the error.

Need more help? ⌛ Then check out this guide on modifying the PHP.ini file.

4. Modify functions.php file

The functions.php file is part of your theme and it dictates how the theme functions on your website. It also enables you to add new functions to your website.

You can increase the upload limit of your website via the functions.php file.

While the function.php file can be accessed from the File Manager, we don’t recommend using it directly.

The function.php file is super important. So, changing it directly is too risky. Standard practice involves using a child theme or a free plugin like Code Snippets.

Creating a child theme is a time-consuming and difficult task. Therefore we recommend using the plugin.

(Video) How to Solve the “413 Request Entity Too Large” Error for Your WordPress Website

Step 1: Install and activate Code Snippets on your WordPress website.

Step 2: On the left-hand menu of your WordPress website, you will find a new menu called Snippets. Go to Snippet and select Add New.

Step 3: Copy and paste the following code into the Functions section:

@ini_set( "upload_max_size", "64M" );@ini_set( "post_max_size", "64M");@ini_set( "max_execution_time", "300" );

Be sure to enter a title and then hit the Save and Activate button before exiting the page.

If you still can’t upload a large file to your site, then try increasing the values of upload_max_size and post_max_size.

How to Fix '413 Request Entity Too Large' Error on WordPress (3)

5. Modify .htaccess file

If your WordPress site is hosted on an Apache server, then you can increase the upload limit by modifying the .htaccess file. Here’s how:

Step 1: Use a tool like iplocation and dnschecker to make sure your servers are running on Apache.

Step 2: Open your hosting account and go to cPanel → File Manager → public_html → .htaccess.

Right-click on .htaccess and then select Edit.

Alternatively, you can connect to your server using FTP and edit the .htaccess file that way.

Step 3: Then copy and paste the following code at the end of the file:

php_value upload_max_filesize 64Mphp_value post_max_size 64Mphp_value max_execution_time 300php_value max_input_time 300

Save the file before exiting and then try uploading large files to your WordPress website.

How to Fix '413 Request Entity Too Large' Error on WordPress (4)

6. Modify nginx.conf file

Besides these, there is another method involving the nginx.conf file, which you would need to use if your server uses Nginx instead of Apache (because Nginx doesn’t support the .htaccess file). To implement this method, you will need to have advanced technical knowledge. So, this method is best left to developers who know how to locate the file and make modifications to it.

(Video) How To Fix HTTP 413 'Request Entity' Too Large Error In WordPress | HTTP 413 Error Resolved

The nginx.conf file contains a directive that looks like this:

server { ... client_max_body_size 18M;}

All you need to do is modify the number to 64M and check if you can upload large files to your site.

Go to top

Fix the “413 request entity too large” error for good

The “413 request entity too large” message, AKA “413 payload too large,” is a common HTTP error that you might experience in WordPress.

How to fix the '413 request entity too large' #error on #WordPress 🐛

It appears when you are trying to upload a large image, plugin, or theme that exceeds your server upload limits.

In order to overcome this obstruction, you can either reduce the size of the file or increase the server upload limits.

To reduce the file size, 🧩 you can use image compression tools or find small-sized alternative plugins and themes.

To increase the server upload limits you can modify certain WordPress files like PHP.ini, functions.php, .htaccess, and nginx.conf.

📌 To learn more about these types of errors, you can check out our full guide to HTTP error codes.

(Video) WordPress Installation | white screen error fixed | 413 - Request Entity Too Large Fixed - Tutorial

That’s it folks! 🤩 With that, we have come to the end of this tutorial.

Have any questions about the “413 request entity too large” error? Then, let us know in the comment section below.


How to Fix '413 Request Entity Too Large' Error on WordPress? ›

How do I fix Error 413 Request Entity Too Large? A. The most common way to fix the HTTP 413 Error is to increase the media file maximum upload size. Other ways are: resetting file permissions, uploading files using an FTP client, and modifying your files (fuctions.

How to fix the page was not displayed because the request entity is too large? ›

Clear your Constant Contact cookies to fix the Request Entity Too Large error. Occasionally when navigating your account, you might see an error message that reads "Request Entity Too Large." When this happens, it means that your Constant Contact cookies have built up and need to be cleared.

What is server error 413 Elementor? ›

How to solve 413 Request Entity Too Large error. To solve this error, you simply need to increase the server resources whose limits lead to the error. Those are the file upload size and the maximum time allowed for executing PHP scripts.

How do I fix 413 content too large? ›

Fix 413 Request Entity Too Large Error — Modifying Upload Size
  1. Modify the Upload Size value (in Megabytes) to your preference.
  2. Finally, click Save Changes. Tip. If the file size you want to allow is greater than what we have set, adjust the Upload Size to be greater than the file size. Classic Interface. New Interface.

What does error 413 mean? ›

The 413 status code indicates that the request was larger than the server is able to handle, either due to physical constraints or to settings. Usually, this occurs when a file is sent using the POST method from a form, and the file is larger than the maximum size allowed in the server settings.

What is reverse proxy 413 Request Entity Too large? ›

What Does 413 Request Entity Too Large Error Mean? The 413 Request Entity Too Large error means that the client's request is too large to be processed by the server. The 413 error commonly occurs when uploading a file larger than the set server limit.

What is status code 413 in WordPress? ›

The 413 error means “Payload too large” so if you were uploading an export this could mean the file is too big. only supports . xml imports (not sql) with a maximum file size of 15MB. Maybe you can try splitting the large .

What is a 413 payload too large in WordPress? ›

If you encounter the 413 Request Entity Too Large error in WordPress, the most likely cause is that you're trying to upload a file larger than the maximum file upload limit on your site. The most common occurrence of the error is during plugin or theme uploads.

How do I fix Elementor in WordPress? ›

7 Reliable Ways To Fix Elementor Editor Not Loading Errors
  1. Enable Switch Editor Loader.
  2. Check Other Plugin Conflicts.
  3. Update PHP Version & Increase PHP Memory Limit.
  4. Update Elementor Latest Version.
  5. Check .htaccess File.
  6. Increase Apache Service Limit.
  7. Change Your Current Theme.
Jan 26, 2022

How do I fix error 413 on Chrome? ›

How to Fix the 413 Request Entity Too Large Error in WordPress?
  1. Fix 1: Upload Smaller Files. ...
  2. Fix 2: Upload the Large File to Server via SFTP. ...
  3. Fix 3: Modify PHP. ...
  4. Fix 1: Clear Browsing Data. ...
  5. Fix 2: Reset Chrome to Factory Default. ...
  6. Fix 3: Reset the Network Adapter.
Sep 27, 2022

What is error code 413 in nginx? ›

Error: 413 “Request Entity Too Large” in Nginx with “client_max_body_size” / Changes in Nginx config file. This is happening because your nginx server does not allow you to upload a file that is larger than the defined size in nginx config file. To solve it, you have to modify your nginx configuration.

What is Cloudfront 413 error? ›

The 413 request entity too large error means that a client has sent a request to a web server but the request is too large for the server to process. Normally, there is an HTTP request size limit has been setting for a server. So, if the request is over the limit, you will get the 413 error.

How do I fix error 413 Express? ›

To fix the “413 Request Entity Too Large” error in an Express application, you only have to update the server initialization file. This is generally called index. js or server. js and is where you initialize the Express server.

How do I remove proxy restrictions? ›

Disable proxy for Chrome on Windows
  1. Click the Chrome Menu in the browser toolbar.
  2. Select Settings.
  3. Click Advanced.
  4. In the System section, click Open your computer's proxy settings. ...
  5. Under Automatic proxy setup, toggle Automatic detect settings Off.
  6. Under Manual proxy setup, toggle Use a proxy server Off.
  7. Click Save.
Jan 11, 2023

How to bypass proxy server restrictions? ›

To bypass servers, use an asterisk ("*") as a wildcard to replace actual characters in the exceptions area of the Proxy Settings dialog box. Enter a wildcard at the beginning of an Internet address, IP address, or domain name that has a common ending. For example, use *. to bypass any entries that end in .

How to secure Apache reverse proxy? ›

3 Configuring a Security Encryption Key
  1. Activate Your Encryption Key.
  2. Create a Custom Encryption Key.
  3. Update Your Encryption Key.
  4. Delete Your Encryption Key.

How do I fix a WordPress error? ›

Beginner's Guide to Troubleshooting WordPress Errors (Step by...
  1. Research Your Error Message. ...
  2. Create a Complete Backup of Your WordPress Site. ...
  3. Clear Browser Cache. ...
  4. Clear Your WordPress Cache. ...
  5. Deactivate All Plugins Installed on Your Website. ...
  6. Switch to a Default WordPress Theme. ...
  7. Refresh Permalinks. ...
  8. Backup and Delete .
Apr 26, 2023

Why am I getting a WordPress error? ›

Getting started with WordPress error troubleshooting

You can start by clearing your cache. A cache helps your browsers load sites faster by storing data. Clearing it helps you get rid of outdated content, which may be enough to fix your issue. You should also consider updating your theme, plugins, and WordPress core.

Why do I keep getting a WordPress error? ›

There are 4 main types of errors on WordPress: HTTP, PHP, MySQL and JavaScript errors. These errors can be due to an incompatibility between plugins, a corrupted file, a server or memory problem, etc. Some of the famous errors include the 500 error, White Screen of Death and database connection error.

How do I change the size limit in WordPress? ›

Modify wp-config.php File

Open the file in any text editor and add the following code. @ini_set( 'upload_max_size' , '20M' ); @ini_set( 'post_max_size', '13M'); @ini_set( 'memory_limit', '15M' ); Save your changes, and it should increase your file upload size.

How do I reduce request size in WordPress? ›

Reduce HTTP requests on your WordPress site
  1. Combine CSS & Javascript.
  2. Minify code (HTML, CSS, Javascript)
  3. Enable lazy load.
  4. Remove unneeded images.
  5. Reduce image file size.
  6. Disable unneeded plugins.
  7. Reduce external scripts.
  8. Use a CDN.
Nov 17, 2021

Why am I getting a server error in Elementor? ›

These are a few of the most common: The website does not have enough memory – Elementor requires a minimum of 128MB of RAM to work correctly (if the website includes other plugins, we recommend 512MB). It is possible that the RAM assigned to the website is insufficient to satisfy its demands, resulting in a 500 error.

What is common Elementor error? ›

The most common list of Elementor errors includes the Elementor widgets panel not loading. Elementor widgets stop loading when you use a lot of plugins, multiple addons for elementor, or if there's limited PHP memory on the server. This is the users' most annoying problem, making the page builder unusable.

How do I increase my Elementor memory limit? ›

You can check your memory limit by navigating to wp-admin -> Elementor -> System Info. To increase your memory limit, you will have to modify the wp-config. php file of yours. Add this following line of code just above this line ” /* That's all, stop editing!

What is HTTP Error 400? ›

The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing).

What is error 400 on Google? ›

If you get an error that says “400 invalid_request” or “Access blocked: App sent an invalid request,” it means the app uses an authorization method that Google doesn't allow. Google has safe ways for you to sign in and share your Google Account data with third-party apps and sites.

What is the default size of NGINX 413? ›

The default value is 1 MB.

What causes an NGINX error? ›

The use of PHP-FPM with NGINX can improve the performance of websites and reduce resource consumption. Some of the possible reasons for the error are non-running NGINX or PHP-FPM, firewall blocking requests, the domain name not being allowed, or the server being unavailable.

How to enable HTTP in NGINX? ›

Here are the steps to configure SSL in NGINX.
  1. Open NGINX configuration file. Open terminal and run the following command to open NGINX configuration file. ...
  2. Setup HTTP/2. If you have enabled SSL in NGINX, you will already have the following line in your server configuration. ...
  3. Restart NGINX Server. ...
  4. Verify HTTP/2.
Dec 1, 2020

What does it mean if the request entity is too large? ›

What does “413 Request Entity Too Large” mean? A 413 HTTP error code occurs when the size of a client's request exceeds the server's file size limit. This typically happens when a client attempts to upload a large file to a web server, and the server responds with a 413 error to alert the client.

What is HTTP Error 413.1 Request Entity Too large WordPress? ›

What Is the “Error 413 Request Entity Too Large” Error? HTTP Error 413 indicates that the request made cannot be managed by the server, and this is because it involves a file or a block of data or, again, a group of files that are too large compared to the maximum limit that the server can manage.

How do I fix error 413 in Chrome? ›

How to Fix the 413 Request Entity Too Large Error in WordPress?
  1. Fix 1: Upload Smaller Files. ...
  2. Fix 2: Upload the Large File to Server via SFTP. ...
  3. Fix 3: Modify PHP. ...
  4. Fix 1: Clear Browsing Data. ...
  5. Fix 2: Reset Chrome to Factory Default. ...
  6. Fix 3: Reset the Network Adapter.
Sep 27, 2022

What does requesting entity mean? ›

Requesting entity means the Participating Entity that requests Mutual Aid under this Agreement as a result of an IT Incident under the terms of this Agreement.

What is IIS detailed error 413.1 Request Entity Too large? ›

IIS has a limit for the size of the files users can upload to an application. If the file size exceeds the limit, the application will throw “Error in HTTP request, received HTTP status 413 (Request Entity Too Large)” error. The default file upload size is 49 KB (49152 bytes).

How do I fix too many requests errors? ›

Wait to send another request.

The simplest way to fix an HTTP 429 error is to wait to send another request. Often, this status code is sent with a “Retry-after” header that specifies a period of time to wait before sending another request.

What is a 413 error in Axios post? ›

You get an HTTP error 413 because the client request exceeds the size limit defined in your application server configuration. For example, an Express application on a Node. js server limits the JSON request body to 100Kb by default.

Where is the function PHP file in WordPress? ›

The functions. php file for WordPress core is located in your wp-includes folder. Your theme's functions. php file is located in wp-content → themes → yourtheme.

How do I reset my Chrome size? ›

Windows and Linux: Press F11. Mac: Press ⌘ + Ctrl + f. Chrome OS: At the top of your keyboard, press the full screen key.
Next to "Zoom," choose the zoom options you want:
  1. Make everything larger: Click Zoom in. .
  2. Make everything smaller: Click Zoom out. .
  3. Use full-screen mode: Click Full screen. .

How do I clear my browser cookies? ›

Clear all cookies
  1. On your Android device, open Chrome .
  2. At the top right, tap More. Settings.
  3. Tap Privacy and security. Clear browsing data.
  4. Choose a time range, like Last hour or All time.
  5. Check Cookies and site data and uncheck all other items.
  6. Tap Clear data. Clear.

How do I get rid of Chrome connection error? ›

How To Fix the “Your Connection Is Not Private” Error
  1. Try Reloading the Page.
  2. Manually Proceed (Unsafe)
  3. Are You in a Cafe or Airport?
  4. Check Your Computer's Clock.
  5. Try in Incognito Mode.
  6. Clear Browser Cache and Cookies.
  7. Try Clearing the SSL State on Your Computer.
  8. Change DNS Servers.
Mar 29, 2023

How do you identify an entity? ›

How to identify entity from a given problem
  1. Search for nouns, like Teacher, Doctor, etc.
  2. Classify nouns to get a wider picture about the entities.
  3. Read the problem description repeatedly.
  4. Entities are like Persons, Students, Teachers, Courses.
Jun 15, 2020

What does an entity stands for? ›

In general, an entity (pronounced N-tih-tee ) is an existing or real thing. The word root is from the Latin, ens , or being, and makes a distinction between a thing's existence and its qualities. An entity exists and that's all it needs to do to be an entity.

What is an entity and how does it work? ›

An entity refers to a person or organization possessing separate and distinct legal rights, such as an individual, partnership, or corporation. An entity can, among other things, own property, engage in business, enter into contracts, pay taxes, sue and be sued.


1. How To Fix 413 Request Entity Too Large WordPress
(WP Devs)
2. 413 Request Entity Too Large in 2 mins
(Ceed Media)
3. How to Fix 413 Request Entity Too Large in MaMP in 2 Minutes | MaMP
4. HTTP Error: 413 Request Entity Too Large (3 Solutions!!)
(Roel Van de Paar)
5. How To Solve 413 Request Entity Too Large Problem In Cloudways WordPress?
6. "413 Request Entity Too Large" in Nginx with "client_max_body_size" set (3 Solutions!!)
(Roel Van de Paar)


Top Articles
Latest Posts
Article information

Author: Kieth Sipes

Last Updated: 04/10/2023

Views: 5869

Rating: 4.7 / 5 (47 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Kieth Sipes

Birthday: 2001-04-14

Address: Suite 492 62479 Champlin Loop, South Catrice, MS 57271

Phone: +9663362133320

Job: District Sales Analyst

Hobby: Digital arts, Dance, Ghost hunting, Worldbuilding, Kayaking, Table tennis, 3D printing

Introduction: My name is Kieth Sipes, I am a zany, rich, courageous, powerful, faithful, jolly, excited person who loves writing and wants to share my knowledge and understanding with you.