Part 2 · 2.7
413 Request Entity Too Large: upload too large
Is uploading a large file, restoring a backup or importing a database not working? And do you see 413 Request Entity Too Large, in WordPress The uploaded file exceeds the upload_max_filesize directive in php.ini, or a time-out? Then you've hit a limit on size or duration. You can adjust most of these limits yourself.
Which limit is it?
| Setting | What is it for? |
|---|---|
| upload_max_filesize | The maximum size of a single uploaded file. |
| post_max_size | The maximum size of everything you send in one go. Set it slightly higher than upload_max_filesize. |
| max_execution_time | How many seconds a script is allowed to run. |
| memory_limit | How much memory a script is allowed to use. Set it higher than post_max_size. |
How to fix it
- In DirectAdmin, open Select PHP version under Extra Features.
- Go to the options and increase upload_max_filesize and post_max_size, and if needed max_execution_time and memory_limit.
The PHP options in Select PHP version - Save and try again.
- A large database? Compress the file as .sql.gz before you import it in phpMyAdmin.
- Many or large files? Use an FTP program such as FileZilla instead of your browser.
- Does your site run through Cloudflare with the orange cloud switched on? On the free plan, Cloudflare applies a limit of 100 MB per upload. That limit is set by Cloudflare, not by us.
When should you contact us?
Have you raised the limits and it still doesn't work? Then get in touch.
First ask the AI assistant in My WebOké, or create a ticket via Support centre and then Submit a ticket. Include:
- the full address of the page where it goes wrong
- the time it went wrong
- what you were doing at that moment, for example saving, uploading or logging in
- a screenshot of the message
- the size of the file
Never send your password.
Detailed explanation: Upload too large (error 413) or time-out and PHP options: upload_max_filesize, memory_limit and max_execution_time.