In short
- Hosts limit how large a single upload can be, often to a few megabytes.
- Quick Restore splits the backup into small chunks, so the limit never blocks the restore.
- The free version restores up to 512 MB; Pro restores any size for a one-time payment.
"The uploaded file exceeds the upload_max_filesize directive"
This is the most common reason a WordPress restore fails on shared hosting. PHP has a setting, upload_max_filesize, that caps how large a single uploaded file can be. On budget plans it is often 2 MB to 64 MB. A backup of a real site, with images, is almost always larger. You may also see “maximum upload file size exceeded” or an upload that stops at 100% and never finishes.
The usual fixes, and why they are hard
- Edit php.ini or .htaccess to raise the limit. Many shared hosts ignore or forbid these changes.
- Ask the host to raise it. It works sometimes, slowly.
- Upload by FTP and restore from the server. Possible, but technical.
- Buy a paid extension from your current plugin, often on a yearly licence.
How chunked upload solves it
Quick Restore sends the backup in small pieces, each well under typical upload limits, and reassembles them on the server. To PHP, every request is small. The restore works on the same hosting plan that rejected the single large upload, and you do not need to change any server setting.
Choose the backup
Pick your .wpqr file, or a .wpress file from All-in-One WP Migration.
Chunked upload
The file uploads in small pieces and is reassembled and validated on the server.
Confirm and restore
Nothing is overwritten until you confirm the restore.
Chunked upload is included on every plan, including free. It also works for .wpress imports.
Restore size limits by plan
| Plan | Largest backup it restores | Price |
|---|---|---|
| Free | 512 MB | Free |
| Pro | Any size | From $39.00, one-time |
| Pro Plus / Max | Any size, plus scheduled backups | One-time |
Very large sites on very restrictive hosts can still hit the host’s PHP time limit during the restore step. If that happens, ask your host to raise max_execution_time for the day of the move.
Why WordPress backups get so large
Most of a backup’s size is the media library: years of full-size photos, videos and PDFs. Other common causes are old backup files from previous plugins stored inside wp-content, cache folders, and unused plugins and themes. The database is usually a small part, unless the site keeps large logs or years of spam comments.
How to make a WordPress backup smaller
- Delete old backup files left by plugins you no longer use.
- Clear your caching plugin’s cache before backing up.
- Remove inactive plugins and themes you do not need.
- Delete spam and trashed comments, and old post revisions, with a cleanup tool.
- Compress large images before uploading them in future.
A smaller backup restores faster, and may keep you within the free version’s 512 MB restore limit.
Frequently asked questions
No. Chunked upload works within your host’s existing upload limit.
No. It is included on every plan. Only backups larger than 512 MB need Pro to restore.
Yes. .wpress imports use the same chunked upload.
No. It is a one-time payment with 12 months of updates, and the plugin keeps working after that.