Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
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
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WP All Import Error: Causes and How to Fix It

WP All Import Error: Causes and How to Fix It

Short answer

Most WP All Import errors come from server limits or problems in the import file. Lower the records per iteration, raise PHP time and memory limits, re-save your file as UTF-8, test image URLs, and use a stable unique identifier to stop duplicates.

Key takeaways

  • Terminated imports usually mean time or memory limits were hit.
  • Lowering records per iteration fixes many failures.
  • Invalid file errors often come from encoding or broken XML.
  • Images fail when URLs are private, blocked or slow.
  • A stable unique identifier prevents duplicate posts.

What causes a WP All Import error?

Most WP All Import errors come from server limits, such as execution time, memory or upload size, or from problems in the import file itself, like bad encoding, broken XML or unreachable image URLs.

The plugin does a lot of work in each batch. It reads rows from your file, creates or updates posts, downloads images and writes custom fields. If any of those steps hits a server limit, the import stops or throws an error.

File problems are the second big group. A CSV saved with the wrong encoding, an XML file with a missing closing tag, or a column layout that changed since you set up the import can all cause failures.

This guide groups the common errors by type, so you can match your message to a likely cause and fix it quickly. Take a backup before you re-run large imports.

Why does WP All Import say the import was terminated?

A terminated import usually means the server killed the PHP process because it ran too long or used too much memory, often during large batches or image downloads.

The vendor explains this in its guide to terminated imports and exports. The fix is to give each batch less work or give the server more room.

Try these fixes in order:

  1. Lower Records per iteration in the import settings, for example from 100 to 10
  2. Turn off image downloading for a test run to see if images are the bottleneck
  3. Raise PHP max_execution_time and memory_limit with your host
  4. Run very large imports with a server cron job instead of the browser

Our guide on increasing max execution time covers the time limit.

For memory, see fixing the memory size exhausted error.

Some hosts also have hard process limits that you cannot change on shared plans. If smaller batches still fail, ask the host what is killing the process.

Why will your import file not upload?

Uploads fail when the file is larger than PHP's upload_max_filesize or post_max_size, when a firewall blocks it, or when the file type or extension is not what the plugin expects.

The error often looks like a generic upload failure or a page that reloads with nothing selected. Check the file size against your limits under Tools > Site Health > Info > Server.

Ways around it:

  • Ask your host to raise upload_max_filesize and post_max_size
  • Upload the file by FTP or SFTP to the server, then choose Use existing file in the import screen
  • Use Download from URL if the file is hosted somewhere public
  • Zip the file if your import source supports compressed files

For more on upload limits, see how to fix the uploaded file exceeds upload_max_filesize error.

Why does WP All Import say your XML or CSV file is invalid?

An invalid file error means the parser cannot read the structure, often because of broken XML tags, mixed delimiters, a byte order mark, or text saved in an encoding other than UTF-8.

For XML files, one unclosed tag or stray character breaks the whole file. Open it in a code editor or an XML validator to find the line. Special characters like & must be escaped or wrapped in CDATA.

For CSV files, check:

  • The delimiter is consistent, usually a comma or semicolon
  • Text with commas or line breaks is wrapped in double quotes
  • The file is saved as UTF-8
  • The first row holds column headers

CSV formatting rules are set out in RFC 4180. Re-saving the file from Google Sheets or a good spreadsheet app as CSV UTF-8 fixes many issues.

If the file came from another system, ask for a fresh export in UTF-8 rather than fixing it by hand. It is usually faster and avoids new mistakes.

Why are images not importing?

Images fail to import when the URLs are not publicly reachable, redirect to a login, use an unsupported format, time out, or when your server cannot make outgoing HTTP requests.

Test a few image URLs in a private browser window. If you see a login page or an error, WP All Import will see the same thing.

Other common causes:

  • URLs contain spaces or special characters that are not encoded
  • The source server blocks bulk downloads or rate limits requests
  • Your host blocks outgoing connections or has an outdated SSL certificate bundle
  • The file is a format WordPress does not allow, such as some SVG or WebP setups on older versions

If you have the files locally, upload them to the server and point WP All Import at the folder instead. Our guide on importing WooCommerce products with images walks through image options.

Why is WP All Import creating duplicates?

Duplicates appear when the unique identifier changes between runs or is not unique, so the plugin cannot match rows in the file to posts it created before.

The unique identifier is set in step 4 of the import. It should point to a column that never changes, such as a SKU or a source ID. A title is a poor choice because titles change and can repeat.

If duplicates already exist:

  1. Delete the duplicate posts, or restore a backup
  2. Edit the import and set a reliable unique identifier
  3. Re-run the import with Existing Items matching turned on

Once the identifier is fixed, later runs update existing items instead of creating new ones. Our guide on how to use WP All Import explains this setting in more detail.

Why do you get a 403 or 500 error during import?

A 403 usually means a firewall or security rule blocked the import request, while a 500 error means PHP crashed, often from a fatal error, memory limit or plugin conflict.

Security tools such as ModSecurity can flag import requests that contain HTML or code in the data. Ask your host to check the firewall logs at the time of the error. They can whitelist the rule if it is a false positive.

For a 500 error, turn on debug logging and re-run a small import. The log will show the fatal error and the file that caused it. See how to enable debug mode in WordPress and then read the log for lines from around that time.

Our guide on fixing the 403 forbidden error covers other causes of access errors.

Could a plugin conflict cause WP All Import errors?

Yes, other plugins that run on every post save, such as SEO tools, translation plugins, cache plugins and search indexers, can slow imports down or crash them.

Each imported post triggers the same hooks as a manual save. A plugin that does heavy work on save multiplies that work by thousands of rows.

Test on a staging site with only WP All Import, its add-ons and the plugins your data needs. If the import works, add plugins back one by one. Our plugin conflict guide explains the process.

Why does a scheduled import not run?

Scheduled imports need cron URLs or the vendor's scheduling service to be triggered regularly; if the cron job is missing, wrong or blocked, nothing happens on schedule.

Check that the trigger and processing URLs are both set up, with the right frequency. The trigger URL starts the import, and the processing URL needs to run repeatedly until the import finishes.

If your host disables WP-Cron or blocks outside requests, the jobs may never fire. Our guide on fixing WP-Cron not running covers related causes.

How do you match the error to a fix?

Use the error message and the point where the import stops to narrow the cause, then apply the matching fix from the table below.

Error or symptomLikely causeFirst fix
Import terminated or stuckExecution time or memory limitLower records per iteration
File will not uploadUpload size limit or firewallUpload by FTP and use existing file
Invalid XML or CSVBroken structure or encodingValidate and re-save as UTF-8
Images missingURLs blocked or unreachableTest URLs, upload images locally
Duplicates createdUnstable unique identifierUse a SKU or source ID
403 errorSecurity ruleAsk host to check firewall logs
500 errorFatal PHP errorRead the debug log

If you still cannot solve it, post in the WP All Import support forum. Include the exact error, your PHP version and a small sample of your file with private data removed.

How can you prevent WP All Import errors?

Clean your file before importing, run a small test batch first, use a stable unique identifier, and keep server limits generous for large imports.

Good habits:

  • Test with the first 10 to 20 records before running the full file
  • Keep a copy of the original file and the import settings
  • Run large imports at quiet times
  • Use staging for the first run of any new import
  • Keep the plugin, add-ons and PHP version up to date

Checking your PHP settings ahead of time helps. The PHP manual's list of ini directives explains each limit your host can change.

Frequently asked questions

Why does my WP All Import keep stopping?

The server is usually killing the process because it runs too long or uses too much memory. Lower the records per iteration, run a test without images, and ask your host to raise PHP execution time and memory limits.

How do I fix an invalid file error in WP All Import?

Open the file in a code editor or validator. For XML, find unclosed tags or unescaped characters. For CSV, use one delimiter, wrap text containing commas in quotes, and save the file as UTF-8.

Why are my images not importing with WP All Import?

The image URLs may require a login, redirect, contain unencoded characters, or be blocked by the source server. Your host may also block outgoing requests. Test the URLs in a private window or upload the images to your server.

How do I stop WP All Import creating duplicate posts?

Set the unique identifier to a column that never changes, such as a SKU or source ID. Remove existing duplicates first, then re-run the import so later runs match and update items instead.

What records per iteration setting should I use?

Start lower on shared hosting, such as 10 to 20 records, especially when importing images. Increase it gradually if imports run smoothly. Faster servers can handle larger batches without timing out.

Sources

  1. Terminated Imports & Exports WP All Import
  2. WP All Import plugin support WordPress.org
  3. RFC 4180: Common Format for CSV Files IETF
  4. List of php.ini directives PHP Manual

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

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.