Troubleshooting
WP All Import Stuck At 100: Causes and How to Fix It

Short answer
Records are processed but the final step failed or is still running. Check Manage Imports to see whether the data is already there, then look for server timeouts, slow deletion of missing records, image downloads, firewall blocks or plugin hooks that run after the import.
Key takeaways
- 100% means records were read, not that clean-up finished.
- Check Manage Imports and the log before re-running anything.
- Deleting missing records and downloading images are slow final steps.
- Security plugins and firewalls can block the last request.
- Smaller batches and the speed options make imports finish reliably.
Why is WP All Import stuck at 100%?
WP All Import usually sticks at 100% because the records are processed but a final step fails: deleting missing records, finishing image downloads, running after-import hooks, or a request that times out or is blocked by a security tool.
The progress bar tracks records. When it reaches 100%, every row in your file has been read, but the import is not complete until WP All Import finishes its clean-up work and marks the run as done.
That last stage can be heavy. It may delete hundreds of old posts, update counts, or run code from other plugins. If the server stops the request during that work, the screen freezes at 100% with no success message.
The good news: in most cases your data has already been imported. The fix is usually about letting the final step finish, not re-running the whole import.
If you are new to the plugin, our guide on how to use WP All Import covers the import screens this article refers to.
Has the import actually finished?
Before fixing anything, check whether the data is already there, because a frozen screen does not always mean a failed import.
Do these checks first:
- Open a new tab and go to All Import > Manage Imports.
- Look at the status and record counts for the import.
- Open the import's log, if available, and read the last lines.
- Check your posts or products list and spot-check a few records.
If the counts look right and the log ends normally, the import finished and only the browser lost the final response. You can leave the page.
If the log stops part way through the final step, or the status shows the import as still processing or interrupted, carry on with the causes below.
Is the server timing out at the end?
The final step can run longer than your server allows, so a PHP max_execution_time limit, a proxy timeout or a 504 error from the host can stop it right after 100%.
WP All Import splits the main work into small batches to avoid timeouts. The clean-up at the end is often one bigger chunk of work, especially when the import deletes or updates many records.
Signs of a timeout:
- The browser network tab shows a 500, 502 or 504 response.
- The server error log shows a fatal error or time limit message.
- It always stops at the same point on large files but not small ones.
PHP's max_execution_time setting controls how long a script may run, but hosts often add their own limits on top.
Fixes to try:
- Raise the PHP time limit. See our guide on increasing max execution time.
- Raise the memory limit too, using our guide on increasing the PHP memory limit.
- Ask your host whether a proxy or load balancer has a shorter timeout than PHP.
- Reduce the work done at the end, as described below.
WP All Import's own guide to terminated imports and exports explains how server limits cut runs short.
Is the delete missing records option slowing it down?
If the import is set to delete or change records that are no longer in your file, that work happens at the end and can take a long time on large sites.
In the import settings there is an option to remove or update posts that are not present in the new file. For a store with thousands of products, WP All Import has to compare the old and new lists and process every missing item.
This is a common reason for long pauses at 100%.
What to do:
- Wait longer. On large sites, this step can take many minutes.
- Test the import with this option turned off to confirm it is the cause.
- Instead of deleting, set missing items to draft or out of stock, which is lighter.
- Run deletions in a separate, smaller import if needed.
Always take a backup before running imports that delete content. If the final step fails half way, you can end up with some records removed and others not.
Are images still downloading?
Importing images from URLs is slow, and if image downloads or thumbnail generation run near the end, the import can look frozen at 100% while it works.
Each image is downloaded, saved to the media library and resized into several thumbnail sizes. On a slow server or with large images, this takes far longer than importing text.
Ways to speed it up:
- Use images that are already uploaded, by matching file names, rather than downloading them each time.
- Turn on the option to skip images that already exist in the media library.
- Reduce the number of registered image sizes your theme and plugins create.
- Import products first, then images in a second run.
Our guide on importing WooCommerce products with images covers image settings in more detail.
Is a security plugin or firewall blocking the request?
Security plugins and web application firewalls can block the AJAX requests WP All Import uses, especially large final requests, which leaves the progress bar stuck.
Wordfence, server ModSecurity rules and CDN firewalls sometimes see a long run of rapid admin requests as an attack. The request is blocked and the browser never gets a response.
How to check:
- Look in the security plugin's live traffic or firewall log for blocked requests during the import time.
- Ask your host whether ModSecurity blocked anything.
- Temporarily put the firewall in learning mode, or add an allow rule for your own IP, and run the import again.
There are several reports of this on the WP All Import support forum on WordPress.org, so it is worth checking early.
Turn protection back on after the test.
Is another plugin's code running at the end?
Other plugins hook into the import, and WP All Import also fires actions after each record and after the import, so slow or broken code there can hang the last step.
Multilingual plugins, SEO plugins, page builders and caching plugins often run code every time a post is saved. Over thousands of records this adds up, and at the end some run a big clean-up or cache purge.
To find the culprit:
- Enable debug logging using our guide on reading the WordPress debug log.
- Run a small test import with 10 to 20 records.
- Check the log for fatal errors or warnings near the end.
- Deactivate suspect plugins on a staging copy and test again.
Custom code you added with WP All Import's Function Editor, or hooks such as pmxi_after_xml_import, can also fail. Wrap custom code in checks and test it on a small file first.
add_action( 'pmxi_after_xml_import', function ( $import_id ) {
// Keep this light. Heavy work here runs at the very end of the import.
error_log( 'Import ' . $import_id . ' finished' );
} );
The WordPress Plugin Handbook on hooks explains how actions work if you are new to them.
Can you change settings so it finishes reliably?
Yes, lowering records per iteration, splitting large files and turning on the speed options in Advanced Settings make each request smaller and much less likely to time out.
In the import's Configure Advanced Settings area, look for:
| Setting | Why it helps |
|---|---|
| Records per iteration | Smaller batches finish within server limits |
| Split file into chunks | Large files are processed in parts |
| Disable do_action calls during import | Stops other plugins running code for every record |
| Skip unchanged fields | Fewer database writes on update imports |
The exact names can change between versions. The WP All Import speed optimisation guide describes the current options.
Start with a low number of records per iteration, such as 10 to 50, on shared hosting. You can raise it once imports run cleanly.
What about scheduled imports stuck at 100%?
Scheduled and cron imports need both a trigger request and repeated processing requests; if the processing calls stop, the import stays at 100% or processing indefinitely.
WP All Import Pro's cron imports use two URLs. The trigger URL starts the run, and the processing URL must be called again and again until the import finishes.
If the processing job only runs once, or the server cron is disabled, the import stalls.
Check:
- Your server cron calls the processing URL every few minutes.
- WordPress cron is working, if you rely on it. See our guide to fixing WP-Cron not running.
- The cron job is not blocked by a firewall or basic auth.
How do you recover a stuck import safely?
Confirm what was imported, cancel or reset the stuck run in Manage Imports, fix the cause, then re-run with update rules so existing records are matched rather than duplicated.
Steps:
- Back up the database.
- In All Import > Manage Imports, cancel or reset the stuck import if the option is shown.
- Fix the cause you found above.
- Run the import again using the same unique identifier so records are updated, not duplicated.
- Check a sample of records and the final counts.
If you are working with a different tool, the causes are not the same. Our guide on fixing a stuck All-in-One WP Migration import covers that plugin.
Frequently asked questions
Is my data imported if WP All Import is stuck at 100%?
Often yes. The progress bar reaches 100% once all rows are read, and the stall happens during clean-up. Check All Import > Manage Imports and spot-check your posts or products to confirm before running the import again.
How long should I wait at 100%?
Small imports should finish within a minute or two. Large imports that delete missing records or download many images can take much longer. If nothing changes after 15 to 20 minutes and the log has stopped, treat it as failed.
Can Wordfence stop WP All Import?
It can. Firewalls sometimes block the rapid admin requests an import makes. Check the firewall log for blocked requests during the import, and test with the firewall in learning mode or with your IP allowed.
Will re-running the import create duplicates?
Not if you use the same import and a stable unique identifier, such as an SKU or ID column. WP All Import then matches existing records and updates them. Back up first in case the match settings are wrong.
What is a good records per iteration value?
On shared hosting, start between 10 and 50 records per iteration. On stronger servers you can raise it. Lower values mean more requests but each one is smaller and less likely to hit time or memory limits.
Sources
- Terminated Imports and Exports WP All Import
- Speed Optimizations WP All Import
- WP All Import support forum WordPress.org
- Hooks WordPress Developer Resources
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


