Skip to content

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

Server upload limits

The Backup & Migrate module uploads a .emcp archive to your site in chunks, and the uploader adapts to whatever your host allows. If a chunk is rejected it automatically retries with a smaller one. So you rarely need to change anything. Raising your PHP limits simply lets large backups upload in fewer, faster requests.

The Server upload limits card on the Restore section of EMCP Tools → Safety → Backup & Migrate shows each setting’s current value next to the recommended one. A green value means you are already good; an amber value means raising it would help. Read the upload guide opens this page.

SettingRecommendedWhy it matters
upload_max_filesize64 MB or moreThe largest single upload the server accepts.
post_max_size64 MB or moreThe largest request body; should be at least upload_max_filesize.
memory_limit256 MB or moreHeadroom for packaging and restoring.
max_execution_time300 s or more (0 = unlimited)Time a single restore step may run.

The right place depends on your host. Try these in order; the first that your host honours wins.

Most managed hosts (SiteGround, Kinsta, Cloudways, WP Engine, cPanel “MultiPHP INI Editor”, etc.) expose these under a PHP settings / PHP options screen. This is the most reliable option on shared hosting.

If you can edit php.ini:

upload_max_filesize = 128M
post_max_size = 128M
memory_limit = 256M
max_execution_time = 300

Add to the site’s .htaccess:

php_value upload_max_filesize 128M
php_value post_max_size 128M
php_value memory_limit 256M
php_value max_execution_time 300

For memory, you can also add near the top of wp-config.php:

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

Some servers enforce a maximum request size that PHP can’t see, so the Server upload limits card may show 2 GB while the server actually rejects anything larger than about 77 MB. The most common culprits:

  • Apache mod_fcgid: FcgidMaxRequestLen (often around 64 to 77 MB).
  • nginx: client_max_body_size (often 1 MB by default).
  • Cloudflare: a hard 100 MB upload cap on the free plan.

You don’t need to know these values. The uploader detects a rejection and automatically retries with smaller chunks until it fits. Raising them (in your server config, or your host’s control panel) just makes large uploads faster.

For very large sites, or any host that fights browser uploads, skip the uploader entirely:

  1. Copy your .emcp file via FTP/SFTP or your host’s file manager into the upload folder printed on the Restore section. It is the uploads folder inside your backup folder, which since 3.20.0 is usually outside the web root or a wp-content/emcp-backups-… folder with a site-specific name, not wp-content/emcp-backups/.
  2. It appears in the Available to restore list on the Restore section with no browser upload at all.
  3. Restore it the same day: the daily cleanup deletes files in that folder that are more than a day old and not in use by a restore.

This has no size limit and never touches the request-size caps above.