{"id":7921,"date":"2025-01-08T16:28:26","date_gmt":"2025-01-08T22:28:26","guid":{"rendered":"https:\/\/infiniteuploads.com\/?p=7921"},"modified":"2026-10-23T18:02:43","modified_gmt":"2026-10-23T23:02:43","slug":"how-to-make-your-all-in-one-wp-migration-faster-with-infinite-uploads","status":"publish","type":"post","link":"https:\/\/infiniteuploads.com\/blog\/how-to-make-your-all-in-one-wp-migration-faster-with-infinite-uploads\/","title":{"rendered":"How to make your All In One WP Migration faster with Infinite Uploads"},"content":{"rendered":"\n

You drag your backup onto the Import screen of All-in-One WP Migration and get hit with a line like \"Your host restricts uploads to 64 MB.\"<\/strong> Or the upload races to 100%, and then just sits there. Either way, your migration is stuck, and the .wpress file is the problem.<\/p>\n\n\n\n

Here's the part most guides skip. A .wpress file is mostly your media library. Leave the media out of the export, and the file can shrink to a fraction of its size. On the test site I used for this post, an export dropped from 1 GB to 270 MB. Below I cover both ways out: raising the limit, and making the file small enough that the limit stops mattering.<\/p>\n\n\n\n

All-in-One WP Migration Upload Limit: The Short Answer<\/h2>\n\n\n\n

The limit isn't coming from All-in-One WP Migration. Your host sets it.<\/strong> The Import screen just reports WordPress's upload cap, which is the smaller of two PHP settings, upload_max_filesize<\/code> and post_max_size<\/code>. ServMask, the plugin's developer, says the same in their upload limit guide<\/a>, and adds that the free plugin has no import size cap of its own. You have three ways out:<\/p>\n\n\n\n

    \n
  1. Raise the PHP limit<\/strong> above the size of your .wpress file, using one of the methods below<\/a>, or by asking your host.<\/li>\n\n
  2. Make the .wpress file smaller<\/strong> by leaving the media library out of the export, and keep your media in Infinite Uploads so nothing gets left behind. That's my favorite, because it also fixes slow imports.<\/li>\n\n
  3. Buy ServMask's paid Unlimited Extension<\/strong>, which ServMask says uses chunked transfer to get under web server, CDN and firewall limits (Unlimited Extension<\/a>).<\/li>\n<\/ol>\n\n\n\n

    One more trap. The number on the Import screen is PHP only. Layers in front of PHP, like Nginx, a firewall or Cloudflare, can still reject an upload that looks small enough. ServMask lists these in the same guide<\/a>, including Cloudflare's 100 MB upload cap on its free plan.<\/p>\n\n\n\n

    \"All-in-One<\/figure>\n\n\n\n

    That line is the number to beat. Yours will show your own host's value.<\/p>\n\n\n\n

    How to Bypass the All-In-One WP Migration Free Version Import Limit<\/h2>\n\n\n\n

    \"Bypass\" is a strong word for what's really a host setting. You aren't breaking a plugin lock. You're raising a server limit, or sending a smaller file. I'll start with how to check your number, then the quickest fix on Apache hosting.<\/p>\n\n\n\n

    Checking the Current Upload Limit<\/h3>\n\n\n\n
      \n
    1. In your dashboard, open All-in-One WP Migration<\/strong>, then Import<\/strong>. Note the limit in the line that starts with Your host restricts uploads to<\/em>.<\/li>\n\n
    2. Open Tools<\/strong>, then Site Health<\/strong>, then the Info<\/strong> tab, and expand Server<\/strong>. Find upload_max_filesize<\/code> and post_max_size<\/code>. The Import number should match the smaller of the two.<\/li>\n\n
    3. As a third check, open Media<\/strong>, then Add New<\/strong>. WordPress shows the maximum upload file size there too.<\/li>\n<\/ol>\n\n\n\n

      If the Import number is already bigger than your .wpress file and the upload still fails, the block is in front of PHP. Skip ahead to asking your host about web server and CDN limits. If you're not sure how big your file is, check your downloads folder. The .wpress file lives where you saved the export.<\/p>\n\n\n\n

      Using the .htaccess File<\/h3>\n\n\n\n

      If your site runs on Apache, you can raise the limit in the .htaccess<\/code> file in your WordPress root folder. Back up the file first, because a typo can take the whole site down. Add these lines, using a number bigger than your .wpress file (ServMask's example is 512M):<\/p>\n\n\n\n

      php_value upload_max_filesize 512M\nphp_value post_max_size 512M\nphp_value memory_limit 256M\nphp_value max_execution_time 300\nphp_value max_input_time 300<\/code><\/pre>\n\n\n\n
      Save, then reload the Import screen. The number should jump. If it doesn't, your host probably doesn't read .htaccess for PHP settings, which is common on Nginx and LiteSpeed. Use the next section instead.<\/p>\n\n\n\n
      Increasing Max Upload File Size<\/h2>\n\n\n\n
      Pick the one method that matches your host, and then check Site Health and the Import screen again. Stacking all of them just makes a mess.<\/p>\n\n\n\n