Troubleshooting
WP All Export Not Working: Causes and How to Fix It

Short answer
WP All Export usually fails because the server hits a time or memory limit, a firewall blocks its background requests, or the filters match no records. Lower the records processed per iteration, raise PHP limits, check filters and folder permissions, and test for plugin conflicts.
Key takeaways
- Lower records per iteration when exports stall.
- Raise PHP memory and execution time limits.
- Firewalls can silently block export requests.
- A zero record count means the filters are wrong.
- Import CSV files into Excel as UTF-8.
Why is WP All Export not working?
WP All Export usually fails because the server runs out of time or memory, a security plugin blocks its background requests, the export filters match no records, or the export file cannot be written or downloaded.
The problem tends to show up in one of these ways:
- The export sits at 0% or stops partway through.
- The export finishes but the file is empty or missing rows.
- Custom fields, images or WooCommerce data are missing.
- The download link gives an error or a blank file.
- Special characters look broken when you open the file in Excel.
- A scheduled export never runs.
Find your symptom below and work through the fixes for it.
If the problem is with WordPress's built-in export tool instead, see our guide on fixing the WordPress export error.
Is the export stuck at 0% or stopping partway?
An export that stalls is usually hitting a server time or memory limit, so lower the number of records processed per batch and raise PHP limits.
WP All Export processes records in batches, sending repeated requests from your browser. If one batch takes longer than your server allows, the request dies and the progress bar stops moving.
Try these fixes in order:
- Open the export's advanced options and lower the number of records processed per iteration. Smaller batches are slower but far more reliable.
- Raise the PHP memory limit. Our guide on increasing the PHP memory limit shows how.
- Raise the maximum execution time, as explained in how to increase max execution time.
- Keep the browser tab open and the computer awake while the export runs.
PHP documents these limits in its core configuration reference. Many shared hosts set them low and may need to change them for you.
If you see a 504 or 502 error in the browser console, the web server timed out before PHP did. Our guide to fixing 504 gateway timeout covers that side.
Is a security plugin or firewall blocking the export?
Security plugins and web application firewalls can block the repeated background requests WP All Export makes, which stops the export without a clear error.
Exports send many requests to admin-ajax.php in a short time. Some firewalls see that as suspicious and block it.
Check for:
- Blocked request logs in your security plugin.
- A rate limit on admin requests.
- Host-level firewall rules, such as ModSecurity.
- A CDN or proxy that challenges admin requests.
Temporarily pause the security plugin and run a small export. If it works, add an exception for your IP or for WP All Export requests rather than leaving protection off.
Are the export filters matching no records?
An empty export usually means the filters exclude everything, so review the filter rules, post status and post type before running the export again.
WP All Export lets you filter records by date, status, taxonomy, custom field and more. One wrong rule can cut the result to zero.
Check these points:
- The export shows a record count before you run it. If it says 0, the filters are the cause.
- Post status filters may exclude drafts, private posts or scheduled posts.
- Date filters use your site's time zone.
- Several rules joined with AND must all be true at once.
Remove all filters, confirm the count, then add them back one at a time. The WP All Export documentation explains how each filter works.
Are custom fields or WooCommerce data missing from the file?
Missing data usually means the field was not added to the export template, needs a Pro feature or add-on, or is stored somewhere the export does not look by default.
Open the export template and check that each field is dragged into the columns area. Fields not added there are not exported.
Common gaps:
- Advanced Custom Fields and similar plugins: support for some field types depends on the Pro version or an add-on.
- WooCommerce orders and customers: check the plugin's current feature list to see what the free version supports.
- Images: decide whether you want URLs, file names or IDs.
- Serialized data: may need a custom PHP function to turn it into readable text.
Check the plugin's page on WordPress.org to see what the free version includes. For store data specifically, our guide on exporting WooCommerce orders to CSV covers other options too.
Does the download fail or give a blank file?
Download problems usually come from folder permissions, a full disk, or a security rule that blocks access to the export file in the uploads folder.
WP All Export saves files inside your uploads folder before you download them. If WordPress cannot write there, the export may appear to finish but the file will be empty or missing.
Check:
- That the uploads folder is writable by the web server.
- That your hosting account has free disk space.
- That no security rule blocks downloads from the uploads folder.
- That old export files are not filling the folder.
WordPress explains correct folder permissions in its file permissions guide. Ask your host if you are unsure how to change them.
Why does the file look broken in Excel?
Excel often opens CSV files with the wrong character encoding, which turns accents and symbols into strange characters, so import the CSV as UTF-8 or export to Excel format.
The data in the file is usually fine. The problem is how Excel guesses the encoding.
Fixes:
- Use Excel's import feature (Data > From Text/CSV) and pick UTF-8.
- Export in an Excel file format if your version offers it.
- Open the CSV in Google Sheets or LibreOffice, which handle UTF-8 better.
- Check the separator. If all data lands in one column, change the delimiter.
Long numbers, such as phone numbers or product codes, may be shown in scientific notation. Format those columns as text when importing.
Why isn't a scheduled export running?
Scheduled exports depend on cron jobs or the plugin's scheduling service, so an export will not run if the cron URLs are not set up or WP-Cron is not firing.
Scheduling is a Pro feature. It works by calling trigger and processing URLs on a timer.
Check:
- The schedule is saved and active in the export settings.
- If you use manual cron jobs, both the trigger and processing jobs are set up on your server.
- WP-Cron is working if your setup relies on it.
Our guide on fixing WP-Cron not running helps if scheduled tasks across the site are failing.
Could a plugin conflict be the cause?
Yes, other plugins that change admin AJAX, queries or post data can break WP All Export, so test on staging with other plugins turned off.
Run a conflict test:
- Make a staging copy of the site.
- Deactivate every plugin except WP All Export (and WooCommerce or ACF if you export their data).
- Switch to a default theme.
- Run a small test export.
- Turn plugins back on one by one.
The full method is in our guide to fixing a plugin conflict.
Also check your PHP error log for fatal errors during the export. See how to check PHP error logs.
Quick reference: symptoms and fixes
Use this table as a fast lookup.
| Symptom | Likely cause | Fix |
|---|---|---|
| Stuck at 0% or partway | Time or memory limit | Lower records per iteration, raise PHP limits |
| Stops with no error | Firewall blocking requests | Add an exception in the security plugin |
| Empty file | Filters exclude everything | Remove filters and check the count |
| Missing fields | Field not in template or Pro feature | Add the field, check plan features |
| Download fails | Permissions or disk space | Fix uploads folder access |
| Broken characters | Excel encoding | Import as UTF-8 |
| Schedule never runs | Cron not set up | Set up trigger and processing jobs |
What should you send to WP All Export support?
If nothing works, contact support with your plugin versions, the export settings, the record count, any error log lines and the results of your conflict test.
Pro license holders get direct support from the developer. Free users can post in the plugin's support forum on WordPress.org.
Include:
- WP All Export, WordPress and PHP versions.
- The post type and number of records.
- Records per iteration setting.
- Browser console errors and PHP error log lines.
- Whether the issue happens on staging with other plugins off.
If you also import data, our guide on how to use WP All Import covers the matching tool.
Frequently asked questions
Why is WP All Export stuck at 0%?
The first batch is usually failing because of a server time or memory limit, or a firewall blocking the request. Lower the number of records per iteration, raise PHP limits, and check your security plugin's logs for blocked admin requests.
Can WP All Export handle large exports?
Yes, but large exports need smaller batches and enough server resources. Lower the records per iteration, keep the browser tab open, and consider running big exports at quiet times. Cheap shared hosting may struggle with very large stores.
Why are my ACF fields not in the export?
Each field must be added to the export template, and support for some custom field plugins depends on the Pro version or an add-on. Check the field is in the columns list and review the plugin's feature list for your version.
Why does my export show strange characters in Excel?
Excel often guesses the wrong encoding when it opens a CSV directly. Use Excel's import from text option and choose UTF-8, or open the file in Google Sheets or LibreOffice, which handle UTF-8 files correctly by default.
Sources
- WP All Export plugin WordPress.org
- Export Overview WP All Import
- Description of core php.ini directives PHP.net
- File Permissions 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.


