What does 413 Request Entity Too Large mean? When does it appear? Do you have any ideas about how to remove it to upload your files successfully? Find possible solutions from this post on MiniTool Website now!

413 Request Entity Too Large

413 Request Entity Too Large, also called HTTP error 413 or 413 Payload Too Large, is an error you might encounter when using WordPress, Google Chrome or Microsoft Edge. It happens when a client makes a request that is too large for the end server to process.

413 refers to one of the 4xx error codes which means there is an issue between the browser and server. The entity in Request Entity is the information payload being requested by the client from the server.

Why Does the Request Entity Too Large Error Appear?

The 413 Request Entity Too Large Error usually occurs along with this error message: Your client issues a request that was too large. This error crops up mainly due to two conditions. One is the request body not preloaded during the handshake process, the other is the size of a client’s request exceeding the size of the server’s file.

How to Fix the 413 Request Entity Too Large Error in WordPress?

Fix 1: Upload Smaller Files

If you are trying to upload an image, you can use tools like TinyJPG or IMG3Go to reduce the size of the files.

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

Fix 2: Upload the Large File to Server via SFTP

You can circumvent the frontend interface and upload the large file to the server yourself. The best way of that is via SFTP.

To do so, you need to log into your site via SFTP and then upload a folder. Next, upload your file to this folder to see if it will be uploaded successfully.

Fix 3: Modify PHP.ini File

The PHP.ini file manages the file timeouts, file upload sizes and resource limits. Therefore, you can use it to resolve the 413 Request Entity Too Large Nginx error in WordPress.

Step 1. Open your host account and go to cPanel to find the PHP.ini file.

If you cannot find the PHP.ini file in cPanel, open File Manager in cPanel to find it in the public_html folder or in the folder named after your website.

Step 2. Right-click on the PHP.ini file and select Edit in the drop-down menu. You will 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 press Save Changes.

How to Fix HTTP Error 413 Chrome/Edge?

In the following content, we will take Google Chrome as an example to fix the Nginx 413 Request Entity Too Large error. The steps are similar to those of Microsoft Edge.

Fix 1: Clear Browsing Data

Clearing the browsing data is proven fruitful for many users. To do so:

Step 1. Launch Google Chrome and hit the three-dot icon to choose More tools > Clear browsing data.

Step 2. Choose a time range and check the browsing data you want to clear.

clear browsing data

Step 3. Hit Clear data.

Fix 2: Reset Chrome to Factory Default

This method will reset your startup page, new tab page, search engine and pinned tabs. At the same time, it will delete temporary data and retain some data like your bookmarks, history and saved password.

Step 1. Launch Google Chrome and click on the three-dot icon to select Settings.

Step 2. Go to Reset and clean up > Restore settings to their original defaults.

factory reset Chrome

Then, read the descriptions and follow the instructions on the screen carefully.

Fix 3: Reset the Network Adapter

The last resort to the HTTP 413 error is resetting your network adapter. Here’s how to do it:

Step 1. Type cmd in the search bar to locate Command Prompt and right-click on it to select Run as administrator.

Step 2. When the command window appears, type netsh Winsock reset and hit Enter.


What is ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY? How to address it? To get the workarounds, follow this guide now!

Read More

  • Linkedin
  • Reddit