How to increase the upload limit in All-in-One WP Migration

  • Posted:
  • / By: Yani I
  • / In: How-To

The upload limit shown on the Import screen is reported by the plugin from your host’s PHP settings — the plugin does not set it.

1. Verify: Site Health vs the plugin

  1. Open Tools → Site Health → Info → Server.
  2. Note upload_max_filesize and post_max_size.
  3. Compare them to the limit on All-in-One WP Migration → Import.

The Import screen shows WordPress’s PHP upload cap: the smaller of upload_max_filesize and post_max_size (via wp_max_upload_size()). Site Health lists those two values separately — match the plugin number to the smaller one. That number is PHP-only. It does not include Nginx, Cloudflare, or WAF body-size limits.

What you see What it means Next step
Plugin matches the smaller Site Health PHP value PHP is what the plugin is reporting Raise PHP if that value is too low (section 2)
PHP looks high enough but browser upload still fails An outer layer may be blocking (Nginx client_max_body_size, Cloudflare upload cap, mod_security, etc.) — those do not appear in the Import number Ask the host about non-PHP limits; if they stay locked, Unlimited (section 3)

2. Raise PHP

Use one method that matches your host. Then re-check Site Health and the Import screen.

.htaccess (Apache)

In the WordPress root .htaccess:

php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 256M
php_value max_execution_time 300
php_value max_input_time 300

.user.ini (LiteSpeed, Nginx, or when .htaccess does not work)

In the WordPress root .user.ini:

upload_max_filesize = 512M
post_max_size = 512M
memory_limit = 256M
max_execution_time = 300
max_input_time = 300

php.ini

If you can edit the server php.ini:

upload_max_filesize = 512M
post_max_size = 512M
memory_limit = 256M
max_execution_time = 300
max_input_time = 300

Do not add @ini_set( 'upload_max_filesize', … ) or @ini_set( 'post_max_size', … ) to wp-config.php. Those directives are PHP_INI_PERDIR and cannot be changed at runtime.

Control panel

  • cPanel: Software → Select PHP Version → Options
  • Plesk: PHP Settings for your domain
  • SiteGround: Site Tools → Devs → PHP Manager
  • Hostinger: Advanced → PHP Configuration

Ask the host

If the settings are locked, ask support to raise upload_max_filesize and post_max_size to at least the size of your .wpress file (512M is a common request).

If PHP raise works, you are done — you do not need Unlimited.

3. When PHP is locked or outer layers still block the browser upload

If the host will not raise PHP, or the Import number looks fine but the upload still fails because of web-server / CDN / WAF limits you cannot change, the Unlimited Extension uses chunked transfer to stay under those infrastructure body-size limits. It is not a plugin-side paywall on file size — the free plugin has no hardcoded import cap. The Import screen simply cannot show Nginx or Cloudflare caps; chunked transfer is how you get past them when the host will not.

Full background: Why All-in-One WP Migration Shows an Upload Limit.

Related