Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

How to Raise the All-in-One WP Migration Import Limit

Short answer

The All-in-One WP Migration import limit is your host's PHP upload limit, not a cap set by the plugin. Check Tools, Site Health, Info, Server for upload_max_filesize and post_max_size, then raise both above your .wpress file size in .htaccess, .user.ini, php.ini, or your hosting panel. If your host locks those settings, the Unlimited Extension or a smaller export is the next step.

Key takeaways

  • The free plugin has no hardcoded import cap as of November 2026; the number on the Import screen is your host's PHP limit.
  • WordPress reports the smaller of upload_max_filesize and post_max_size, so you must raise both values.
  • ServMask's example values are 512M for both PHP settings, with 256M memory and a 300 second time limit.
  • Cloudflare Free and Pro plans cap uploads at 100 MB, which can block an import even when PHP allows it.
  • The Unlimited Extension costs $69 per year for up to 50 sites as of November 2026 and uses chunked transfer.
  • Restoring a file from the Backups screen is a paid feature, so the free path is the browser upload on the Import screen.

What is the All-in-One WP Migration import limit?

The import limit is the largest .wpress file your destination server will accept through a browser upload.

A .wpress file is the single archive All-in-One WP Migration creates when you export a site. It holds the database, media, themes, and plugins in one file.

You upload it on the destination site under All-in-One WP Migration, then Import. The plugin is used by over 60 million websites worldwide, according to its WordPress.org plugin page.

The free plugin backs up and exports sites of any size, the same page says. The block appears at the other end, when the destination server refuses a large upload. That is why an export can finish with no trouble and the import can still fail.

Why does the plugin show a limit if it has no cap?

The plugin shows a limit because it reports your host's PHP upload cap, and it does not set that cap itself.

ServMask, the company behind the plugin, states this plainly in its upload limit guide: the plugin does not set this limit, and your hosting provider does. The number on the Import screen is WordPress's own wp_max_upload_size() value.

That WordPress function returns the smaller of two PHP settings, upload_max_filesize and post_max_size. The developer reference for wp_max_upload_size() describes it as the maximum upload size allowed in php.ini. So if one value is 512M and the other is 64M, the Import screen shows 64M.

Many older tutorials still claim a 256 MB or 512 MB plugin cap. ServMask says that claim is incorrect for the current version, which has no hardcoded file size limit. An older version did have a constant called AI1WM_MAX_FILE_SIZE, and ServMask says it was removed years ago.

How do you check your current import limit?

You check it in Site Health, where WordPress lists both PHP values side by side.

  1. Log in to the destination site as an administrator.
  2. Go to Tools, then Site Health, then Info, then Server.
  3. Find upload_max_filesize and post_max_size.
  4. Note the smaller of the two values.
  5. Open All-in-One WP Migration, then Import, and compare the number shown there.

The two numbers should match. If Site Health shows 512M for both and the Import screen still shows 64M, ServMask says the new values have not taken effect yet. A cached admin page, an edit to the wrong file, or a host-level override are the usual causes.

Also check the size of your .wpress file before you start. Right-click the file on your computer and check its size, or look at the export screen on the source site. You need both PHP values above that file size, with room to spare.

What do you need before you raise the limit?

You need admin access to the destination site, the size of your .wpress file, and a way to edit server settings or ask your host to do it.

Make a separate backup first, even though you are about to import one. Keep a copy of the .wpress file on your computer and keep the source site live.

ServMask advises keeping the old host active for 7 to 14 days as a safety net, and lowering DNS TTL to 300 seconds at least 48 hours before a move, according to the WordPress.org plugin page.

Plan for 30 to 60 minutes, including checks and one retry. A small file on a host that lets you change PHP settings takes minutes. A large file on a locked-down shared plan takes longer, because you may need to wait for host support.

Check your PHP version too. WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support, as listed on the WordPress requirements page. An old PHP version will not raise your upload limit, but it can cause other import errors.

Before you change anything, read our guide on how to back up WordPress so you have a restore point that does not depend on this one import.

How do you raise the limit in .htaccess?

You raise the limit in .htaccess by adding PHP values to the file in your WordPress root folder, but only on Apache servers that allow it.

Use your host file manager or FTP to open .htaccess in the folder where WordPress is installed. Add these lines above the WordPress section, using the values from ServMask's upload limit guide:

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

Set both upload values above your .wpress file size. If your file is 700 MB, 512M is not enough, so use a larger number such as 1024M for both. Keep post_max_size equal to or larger than upload_max_filesize, because the Import screen shows the smaller value.

Save the file, then re-check Tools, Site Health, Info, Server. If the site shows a 500 error after the edit, remove the lines at once. That error means your server does not allow php_value in .htaccess, and you should use another method below.

How do you raise the limit in .user.ini or php.ini?

You raise the limit in .user.ini or php.ini by editing the file your server actually reads, then waiting for PHP to pick up the change.

For .user.ini, create or edit the file in your WordPress root folder and add these lines from ServMask's upload limit guide:

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

For php.ini, add or update the same lines in the php.ini file your host uses. This method works only if you have access to that file, which is common on VPS and dedicated servers and rare on shared hosting.

Changes in .user.ini can take a few minutes to apply, because PHP caches the file. Wait 5 minutes, then re-check Site Health and the Import screen. If nothing changed, you may have edited the wrong file or the wrong folder, so ask your host which file it reads.

Do not try to raise these two settings with @ini_set() in wp-config.php. ServMask states that both directives are PHP_INI_PERDIR, so PHP will not change them at runtime. The lines look like a fix and do nothing.

How do you raise the limit from your hosting panel?

You raise the limit from your hosting panel by opening its PHP settings page and changing the two upload values there.

ServMask lists these panel paths in its upload limit guide:

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

Set upload_max_filesize and post_max_size above your .wpress file size, then save. Re-check Site Health and the Import screen to confirm the new number. If the panel has no upload settings, or the values reset after you save, your host has locked them.

If the settings are locked, contact host support and ask them to raise both values above your file size. Give them the exact file size in MB. If they refuse or cannot raise them, move to the smaller-export method or the paid extension below.

Your plan also matters here. A plan with tight CPU and RAM limits can still stall a large import after the upload limit is fixed, so read our guide on how to read a hosting plan's CPU and RAM limits before you pick a plan for a large site.

What else can block an upload even when PHP allows it?

A web server, firewall, or CDN in front of PHP can block a large upload that PHP itself would accept.

ServMask lists Nginx client_max_body_size, Apache LimitRequestBody, mod_security rules, and Cloudflare's upload cap as layers that sit in front of PHP. None of these show up in Site Health or on the Import screen.

You can set PHP to 512M, see 512M on the Import screen, and still fail at 100 MB because one of these layers rejects the request.

Cloudflare is the most common case. Cloudflare's own error 413 docs list a max upload size of 100 MB on Free and Pro plans, 200 MB on Business, and up to 5 GB on Enterprise.

A request over the plan limit gets a 413 error. Our guide on Cloudflare Free vs Pro for WordPress explains what each plan includes.

LayerWhere it blocksWhat to do
PHP settingsBefore the upload startsRaise both values above the file size
Nginx or ApacheAt the web serverAsk the host to raise the body size limit
CloudflareAt the edge, before your serverPause Cloudflare proxying or use chunked transfer
Firewall rulesDuring the uploadAsk the host to allow the upload or whitelist the request

If the Import screen number is high enough but the upload still fails, ask your host whether a server or firewall limit applies. Tell them the file size and the exact error message you see.

How do you shrink a backup file that is too large?

You shrink a backup by exporting without the parts you can move another way, then importing the smaller file.

On the source site, open All-in-One WP Migration, then Export, then Advanced Options. Exclude media files, spam comments, post revisions, and unused themes or plugins if those options are offered. Media is usually the largest part of a site, so an export without media is often a small share of the original size.

Then move the media another way. Copy the wp-content/uploads folder with FTP or your host file manager to the same folder on the destination site. After the import finishes, check that images load on posts and pages.

You can also clean the source site first. Delete unused themes and plugins, empty the trash, and remove old media you no longer use. Then export again and check the new file size before you try the import.

This method keeps the move free, but it adds steps and a chance to miss files. If the file is still too large after cleanup, the paid extension is the simpler path.

When should you use the Unlimited Extension instead?

You should use the Unlimited Extension when PHP is locked or an outer layer still blocks the upload after you raised PHP.

The Unlimited Extension costs $69 per year for up to 50 sites as of November 2026, according to ServMask's upload limit guide. It uses chunked transfer, so each request stays under the host limits you cannot change. No single request is large enough to trip the usual body-size caps.

It also adds one-click Restore from the Backups page. That matters because restoring a .wpress file from the Backups screen is a paid feature, not part of the free plugin. The free import path is the browser upload on the Import screen.

ServMask also lists a Pro plan at $99 per year for 50 sites and a Multisite Extension at $319 per year for 50 sites. For a multisite move, ServMask recommends at least 512 MB of PHP memory. If you do not need those extras, do not buy them for this one job.

If raising PHP fixed your upload, you do not need the extension. ServMask says so directly: the free plugin is all you need once the server allows the file.

How do you check that the import worked?

You check the import by confirming the site loads, the content matches the source, and the admin login works.

  1. Open the destination site home page and 3 to 5 inner pages.
  2. Check that images load and menus point to the right pages.
  3. Log in with the admin account from the source site, because the import replaces the destination login details.
  4. Go to Settings, then Permalinks, and click Save Changes to refresh the link rules.
  5. Clear all caches, including any caching plugin and Cloudflare cache if you use it.

The plugin page advises clearing caches and re-saving permalinks after a restore, per the WordPress.org plugin page. If pages show 404 errors, re-saving permalinks fixes most cases. If images are broken, check that wp-content/uploads moved in full and that folder permissions are correct.

For a domain move, also check redirects and search settings. Our guide on how to change hosting without losing SEO covers the checks to run after a move to a new host or domain.

What mistakes should you avoid?

Avoid raising only one PHP value, editing plugin files to chase the old cap, and importing without a backup.

  • Raising only upload_max_filesize while post_max_size stays low, because WordPress shows the smaller value.
  • Adding @ini_set() lines to wp-config.php for these two settings, because PHP ignores them at runtime.
  • Editing the plugin's constants.php file to change the old AI1WM_MAX_FILE_SIZE value, because that constant is gone in current versions and the edit will be lost on update.
  • Importing over a live site with no separate backup, because the import overwrites the destination database.
  • Deleting the source site or letting the old host lapse before you have checked the new site, because you lose your fallback.
  • Ignoring the Cloudflare or firewall layer, because a high PHP number does not remove those limits.

If the import stalls at 100 percent, that is a different failure from a size limit. Check max_execution_time and memory_limit first, then ask your host whether a timeout or firewall rule stopped the final step.

Frequently asked questions

What is the free import limit for All-in-One WP Migration?

There is no fixed free import limit in the current version. The free plugin imports any file your server allows, and the number on the Import screen is your host's PHP upload limit. Older versions had a 512 MB cap, but ServMask says that cap was removed years ago.

Can I raise the limit by editing wp-config.php?

No, not for the two settings that matter. Both upload_max_filesize and post_max_size are PHP_INI_PERDIR directives, so PHP will not change them at runtime. Use .htaccess, .user.ini, php.ini, or your hosting panel instead, or ask your host to raise them.

Why does my upload fail at 100 MB when PHP allows 512 MB?

An outer layer is blocking it. Cloudflare Free and Pro plans cap uploads at 100 MB, and Nginx, Apache, or a firewall can set a lower body size limit. These limits do not show in Site Health or on the Import screen, so ask your host or check your CDN plan.

Does the Unlimited Extension remove the import limit?

It works around host limits with chunked transfer, so each request stays under the caps you cannot change. It costs $69 per year for up to 50 sites as of November 2026. It also adds one-click Restore from the Backups page, which is not in the free plugin.

Can I import a .wpress file that is already on the server?

Not with the free plugin. Restoring a file from the Backups screen is a paid feature. The free path is the browser upload on the Import screen, which is why raising your PHP limits is the free fix. Upload the file through the Import screen after the limit is high enough.

How long does a large import take?

Allow 30 to 60 minutes for the full job, including checks and one retry. The upload time depends on your file size and connection speed, and the restore step depends on your server. A large media library takes longer than a small blog, even with the same settings.

Sources

  1. Why All-in-One WP Migration Shows an Upload Limit (And How to Fix It) ServMask
  2. All-in-One WP Migration and Backup WordPress.org
  3. Requirements WordPress.org
  4. wp_max_upload_size() WordPress Developer Resources
  5. Error 413: Payload Too Large Cloudflare Docs
  6. All-in-One WP Migration vs UpdraftPlus ServMask

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test