Title: Eizport
Author: Eizport
Published: October 14, 2026
Last modified: October 14, 2026
---
Search plugins
# Eizport
By [Eizport](https://profiles.wordpress.org/eizport/)
[Download](https://downloads.wordpress.org/plugin/eizport.1.0.1.zip)
* [Details](https://wordpress.org/plugins/eizport/#description)
* [Reviews](https://wordpress.org/plugins/eizport/#reviews)
* [Installation](https://wordpress.org/plugins/eizport/#installation)
* [Development](https://wordpress.org/plugins/eizport/#developers)
[Support](https://wordpress.org/support/plugin/eizport/)
## Description
Eizport gives Tools Export a new screen, built like WordPress’s newest admin screens,
and extends the WordPress Importer. Prefer WordPress’s Export screen untouched?
One setting moves the new one to its own Tools item; another brings back the classic
Export screen with the same choices added.
**The Export screen**
Built with DataViews and DataForm, it runs on the plugin’s abilities:
* **One list:** the content types, Attachments and Options. Check what to export;
nothing checked exports all content.
* **Items in a side panel:** each type’s items with search, filters and a checkbox
per item; what you check joins the export at once, and a Selection filter shows
the ones chosen. Items show their roles (Homepage, Posts page, Shop page…).
* **Options:** one by one in a side panel (Basics suggested). Settings that point
to the items chosen (homepage, posts page, privacy policy page, site icon, WooCommerce
pages) are suggested in the Options row and go with the export once it’s checked.
* **The file in a panel above the list,** summed up in a line until opened: format(
WXR XML, or WXRZ once media files or settings go with it, or a Playground .zip),
file name, media files, Playground themes and plugins.
* **Save as default, Reset and Clear defaults:** start with the same choices next
time (yours, or the site’s), or go back to them.
**On Tools Import WordPress**
* .wxrz and .zip bundles (and gzipped WXR files) are accepted, with their media
and content files.
* The importer looks like the Export screen — a header with the step’s main button,
the steps in cards, a file button in the admin’s language — unless Settings
General turns it off.
**On the classic Tools Export**
* **Several content types at once:** check pages and products, say, without posts—
or keep “All content”. Posts, pages, media, products and other custom post types.
* **By filters or by selection, per type:** WordPress’s filters for posts, pages
and media; for products and other custom post types, the same kind (dates, status,
author, and each taxonomy, like product categories). Or check the exact items
in a list (a tree for pages), with a box to filter it. Selected items bring their
attachments and their children of other types, like a product’s variations; product
reviews come with their product.
* **Bundle (.wxrz, or .zip):** download one compressed file with the WXR and, optionally,
more. Without it, the export is WordPress’s usual .xml file, named as usual.
* **Media used in content:** items exported bring their attached media and featured
images, as WordPress does, and also the images, galleries, covers and files their
content uses without being attached (Settings Export “Only attached media”
turns it off).
* **Save these choices as default,** and start with them next time.
**Bundle options**
* **File name:** of your choice; left empty, it’s WordPress’s usual `.WordPress.`.
* **Include media:** the files of the exported attachments (images, PDFs…), so
the importer doesn’t download them from the old site.
* **Content as .html files** (on by default, in Settings Export): each post’s
content in its own `post_content/.html` file instead of inside the WXR —
easy to read, edit and keep under version control.
* **Include settings:** groups of options (Basics, suggested; Reading, General,
Permalinks, Discussion, Media, privacy page, theme customizations, WooCommerce
pages) and any other option by name, in an `options.json`. When the homepage
or the posts page is exported, they can be set as such on import. IDs in the
settings (homepage, logo, menus…) are mapped to the imported items. Site URLs,
the admin email, keys, active plugins, roles and transients are never exported.
* **Include a Playground blueprint:** the download becomes a .zip ready for [WordPress Playground](https://wordpress.org/playground/):`
blueprint.json`, the plain WXR (.xml), the media and content files (as checked
above) and the themes and plugins you check that aren’t in the WordPress.org
directory (a child theme brings its parent; the directory’s are installed from
there, in the version this site has). Playground installs them, activates the
theme and imports the content. After the download, the screen shows the command
that runs it (`npx @wp-playground/cli@latest server --blueprint=./.zip`).
* **Keep a copy to open by link:** with the blueprint, a copy of the .zip stays
on the site for a while (a day by default), and a link opens it on playground.
wordpress.net.
**Settings**, from the plugin’s row in Plugins (built with DataViews and DataForm)
* **General:** replace Tools Export (on by default; off, WordPress’s Export screen
stays as it is and the new one is at Tools Eizport), or use the classic Export
screen; whose saved defaults are (each user’s, or the site’s), and clearing them;
how long copies are kept (1 hour, 12 hours, 1 day, 1 week or until deleted).
* **Export:** only attached media; when linked settings come along (when items
are checked, on export, both, never); bundles as .zip instead of .wxrz; content
as .html files.
* **Copies:** the copies kept (bundles, WXR files and Playground .zip files), listed
like the Media Library — search, sort, open in Playground, copy the link, download,
import, and delete one, many or all.
**On the WordPress Importer**
Upload a .wxrz (or .zip) bundle like any WXR file. Its attachment files are taken
from the bundle, so nothing is downloaded from the old site, which doesn’t even
need to be online. Attachments, image sizes and featured images are created by the
importer as usual. Content files are put back into the WXR before the import starts.
Gzipped WXR files (.xml.gz) are accepted too.
**The .wxrz format**
A .wxrz file is a gzipped tar archive:
* `manifest.json` — format version, the WXR file name and which attachment URL
each media file belongs to;
* the WXR file;
* `uploads/…` — the attachment files, in the same folders as on the exporting site;
* `post_content/.html` — post contents, when exported as files;
* `options.json` — settings, set when the import ends.
You can open it with any tool that reads `.tar.gz` files. With Settings Export “
Bundle as .zip”, bundles are plain .zip files with the same entries, which any computer
opens.
**Abilities**
The same export and import, for AI agents and scripts, through the WordPress Abilities
API (`/wp-json/wp-abilities/v1/abilities//run`, and as tools with the MCP
adapter):
* `eizport/get-export-options` — what can be exported: content types with their
terms, statuses and counts, settings groups, themes and plugins, the homepage
and posts page.
* `eizport/get-items` — a page of one type’s items (search, sort, the same filters
as the export), to pick what to export.
* `eizport/get-options` — the site’s options one by one (search, `group`, pages),
with their size and whether they hold post IDs; options never exported are left
out.
* `eizport/export` — exports to a temporary copy (a .wxrz or .zip bundle, WordPress’s
plain .xml with `bundle: false`, or a Playground .zip with `blueprint`) and returns
its link: `types` (post type => `ids` or `filters`), `media`, `media_used`, `
post_content`, `zip`, `options` (`groups`, `names`, `front_pages`, `linked`,
or `all`), `blueprint` (`themes`, `plugins`), `filename`.
* `eizport/get-export-defaults`, `eizport/save-export-defaults` and `eizport/clear-
export-defaults` — the choices saved as default (the site’s need `manage_options`).
* `eizport/get-copies` — the copies kept, with their links and expiry.
* `eizport/delete-copies` — deletes copies by `names`, or `all`.
* `eizport/import` — imports a `copy` kept on this site, or an `attachment_id`
of a .wxrz, .zip or .xml file, with media and settings.
* `eizport/get-settings` and `eizport/update-settings` — the plugin’s settings (
see Settings above); `manage_options`.
They follow the same rules as the screens: the `export` capability for exporting
and copies, `import` for importing. Only one export runs per request.
**For developers**
* `eizport_post_content` — filter the content an imported item gets from a bundle(`
$content`, `$item` with original `id`, `type` and `slug`, `$dir`).
* `eizport_wxrz_max_bytes` — the largest size a .wxrz may expand to when imported(
default 512 MB).
* `eizport_playground_blueprint` — filter the blueprint of a Playground .zip (`
$blueprint`, `$wxr_name`).
* `eizport_linked_options` — options that point to a post, with its role: `option
=> array( 'label' => 'Shop page', 'with' => array( … ), 'when' => array( option
=> value ) )`. They get the imported post’s ID on import, show on the items,
and come with them.
* `eizport_option_groups` — the groups of options offered (`key => array( 'label'
=> 'Name: what it holds', 'options' => array( … ) )`).
* `eizport_denied_options` — more options never exported (a plugin’s keys, tokens
or version numbers); WordPress’s own can’t be removed.
* `eizport_media_used` — attachments a post uses beyond its content (`$used`, `
$post`), like a product gallery.
* `eizport_register_compat` — action, after all plugins load, where compatibilities
hook those filters. The WooCommerce one ships with the plugin (`includes/compat/
woocommerce.php`: pages, a group, version options, product galleries); a plugin
can replace it with its own: `remove_action( 'eizport_register_compat', 'Eizport\
Compat\WooCommerce\register' );`.
* `eizport_post_id_options` — options that hold a post ID (by default the linked
options), mapped to the imported post on import.
* `eizport_selection_limit` — how many items each “By selection” list shows (default
1000, the latest).
* `eizport_copy_lifetime` — how long a Playground copy lasts, in seconds (default:
the one chosen in the settings; 0 keeps copies until deleted).
* `wp eizport import ` — WP-CLI command that imports a .wxrz (or .xml.gz,
or .xml) with the WordPress Importer, attachments included.
### External services
Eizport doesn’t run a service of its own and sends nothing to its authors. A few
features rely on WordPress.org services, as WordPress itself does, or on links you
choose to open:
* **WordPress.org plugin and theme API** (api.wordpress.org). When you build a
Playground .zip, Eizport asks WordPress for the update information it already
keeps about your plugins and themes, to know which ones come from the directory:
those are installed from there instead of being copied into the .zip. If WordPress
doesn’t know one of them yet, it runs its usual update check, which sends the
list of installed plugins and themes with their versions, the WordPress and PHP
versions, the site’s language and its address. On the other site, a plugin exported“
as plugin” asks the same API whether Eizport is in the directory, when its screen
is opened and Eizport isn’t installed: the request carries the name “eizport”
and what WordPress sends with every such request (its version, the site’s language
and address). WordPress.org privacy policy: https://wordpress.org/about/privacy/
* **WordPress.org downloads** (downloads.wordpress.org). “Install Now” installs
Eizport or the WordPress Importer from there, through WordPress’s own installer,
only when you click it. Inside WordPress Playground, the blueprint installs the
directory’s plugins and themes, in the versions your site has, from there too.
Same privacy policy.
* **WordPress Playground** (playground.wordpress.net), a WordPress.org project
that runs WordPress in the browser: https://wordpress.org/playground/. “Open
in WordPress Playground” opens it in your browser, only when you click it, with
the link of a copy kept on your site; Playground then downloads that .zip, with
the content you exported, from your site into your browser. The `$schema` address
in blueprint.json is only a reference for editors; nothing is requested from
it. Same privacy policy.
* **The site the content came from.** Like the WordPress Importer, an import downloads
the media files a plain WXR points to, or that a bundle doesn’t include, from
their original addresses. The files a bundle includes are served from your own
server.
* **GitHub** (github.com/eizport/eizport). When Eizport isn’t installed, a plugin
exported “as plugin” also shows a “Download Eizport” link to its releases there;
nothing is sent unless you click it. Terms: https://docs.github.com/en/site-policy/
github-terms/github-terms-of-service — privacy: https://docs.github.com/en/site-
policy/privacy-policies/github-general-privacy-statement
## Screenshots
[⌊Tools → Export: choose content types or exact items; the products and settings
they use are suggested.⌉⌊Tools → Export: choose content types or exact items; the
products and settings they use are suggested.⌉[
Tools Export: choose content types or exact items; the products and settings they
use are suggested.
[⌊Pick the exact items to export; the homepage, shop and checkout wear badges.⌉⌊
Pick the exact items to export; the homepage, shop and checkout wear badges.⌉[
Pick the exact items to export; the homepage, shop and checkout wear badges.
[⌊Settings travel too: the ones your pages point to are suggested; add any other
one by one.⌉⌊Settings travel too: the ones your pages point to are suggested; add
any other one by one.⌉[
Settings travel too: the ones your pages point to are suggested; add any other one
by one.
[⌊Export a WordPress Playground .zip with the theme and plugins you choose.⌉⌊Export
a WordPress Playground .zip with the theme and plugins you choose.⌉[
Export a WordPress Playground .zip with the theme and plugins you choose.
[⌊Set it once: media, linked settings, .zip bundles and saved defaults.⌉⌊Set it
once: media, linked settings, .zip bundles and saved defaults.⌉[
Set it once: media, linked settings, .zip bundles and saved defaults.
[⌊Every export is kept as a private copy for a while: download it again, open it
in Playground or import it.⌉⌊Every export is kept as a private copy for a while:
download it again, open it in Playground or import it.⌉[
Every export is kept as a private copy for a while: download it again, open it in
Playground or import it.
## Installation
1. Install and activate Eizport. Exporting works right away, from **Tools Export**.
2. To import, install the **WordPress Importer**: on **Tools Import**, click “Install
Now” under WordPress (the plugin’s links lead there while it isn’t installed),
then “Run Importer”.
## FAQ
### Is it safe to import a bundle from someone else?
Only import files you trust, as with any WXR file. When a bundle is opened, only
the files its manifest lists are written, only under a private folder, only with
file types WordPress allows to be uploaded (never PHP), and never outside that folder.
The folder is deleted when the import ends or is abandoned.
### Which plugins are supported?
WooCommerce, with its own support: products, orders and coupons, its pages as linked
settings, product galleries, the products its blocks show (suggested) and product
reviews. Advanced Custom Fields and Elementor aren’t officially supported yet and
weren’t tested: their data travels in custom fields, which the export carries, but
IDs inside them aren’t remapped on import. The docs explain what to expect: https://
eizport.github.io/docs/developers/compatibilities/
### What is an “as plugin” file?
A plugin .zip that holds the bundle. Install it on the other site (Plugins Add
Plugin Upload Plugin) and open its screen under Tools: it checks that Eizport and
the WordPress Importer are there, imports the bundle with one click, and then offers
to delete itself.
### Is there a size limit?
Uploads are limited by your server’s PHP settings (`upload_max_filesize` and `post_max_size`),
which apply to the compressed file. A bundle may expand to 512 MB by default; developers
can change it with the `eizport_wxrz_max_bytes` filter.
### Does it send data anywhere?
Not to its authors: Eizport has no service of its own. It uses WordPress.org’s plugin
and theme information and downloads, as WordPress does, and opens WordPress Playground
only when you click to; see “External services” for what is sent and when. When
importing a bundle, the importer’s attachment downloads are answered from the bundle
on your own server.
### What does the Playground blueprint do?
It installs the plugins and themes in the .zip and imports the WXR with Playground’s
own importer. With media or content files, they are written into Playground first
and a temporary must-use plugin answers the importer’s downloads from the media
files and puts each `.html` file into its post, and a second one sets the settings
when the import ends, with their IDs mapped; all of it is removed after the import.
The WordPress Importer is installed by Playground itself, from WordPress.org.
### Who can download a Playground copy?
Anyone with its link: the file name ends in a random 16-character token, so it can’t
be guessed, and it is served only until it expires (a day by default; see the plugin’s
Settings, where it can also be “until deleted”), then deleted. On a site on your
computer (like `localhost`), the link only works in your own browser. Don’t keep
copies of content that must stay private.
### Where are the files kept?
In `wp-content/uploads/eizport/tmp/`: Playground copies, and the folders of bundles
being imported. Everything there is temporary, and the `tmp` folder itself is deleted
once it is empty. Uninstalling the plugin deletes `uploads/eizport/` and the plugin’s
settings.
### Where is the source code?
The PHP is in the plugin, readable. The Export and Settings screens’ JavaScript
in `build/` is compiled; each file ships next to its unminified version, and its
source (TypeScript, in `routes/` and `src/`) is at https://github.com/eizport/eizport—
build it with `npm ci && npm run build` (@wordpress/build).
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Eizport” is open source software. The following people have contributed to this
plugin.
Contributors
* [ Eizport ](https://profiles.wordpress.org/eizport/)
* [ Gilberto Tavares ](https://profiles.wordpress.org/camaleaun/)
“Eizport” has been translated into 1 locale. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/eizport/contributors)
for their contributions.
[Translate “Eizport” into your language.](https://translate.wordpress.org/projects/wp-plugins/eizport)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/eizport/), check out
the [SVN repository](https://plugins.svn.wordpress.org/eizport/), or subscribe to
the [development log](https://plugins.trac.wordpress.org/log/eizport/) by [RSS](https://plugins.trac.wordpress.org/log/eizport/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.0.1
* Fixed: Settings Export “As plugin: allow importing again” is saved.
* Scripts and styles of the classic Export screen, the importer and the Export
and Settings screens are enqueued files.
* Keeping a Playground copy, which writes a file, needs the Export form’s nonce.
* readme: an “External services” section on what is sent to WordPress.org, WordPress
Playground and GitHub, and when.
#### 1.0.0
* Initial release.
## Meta
* Version **1.0.1**
* Last updated **17 hours ago**
* Active installations **Fewer than 10**
* WordPress version ** 7.0 or higher **
* Tested up to **7.1.3**
* PHP version ** 7.4 or higher **
* Languages
* [English (US)](https://wordpress.org/plugins/eizport/) and [Portuguese (Brazil)](https://br.wordpress.org/plugins/eizport/).
* [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/eizport)
* Tags
* [export](https://wordpress.org/plugins/tags/export/)[import](https://wordpress.org/plugins/tags/import/)
[media](https://wordpress.org/plugins/tags/media/)[migration](https://wordpress.org/plugins/tags/migration/)
[WXR](https://wordpress.org/plugins/tags/wxr/)
* [Advanced View](https://wordpress.org/plugins/eizport/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/eizport/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/eizport/reviews/)
## Contributors
* [ Eizport ](https://profiles.wordpress.org/eizport/)
* [ Gilberto Tavares ](https://profiles.wordpress.org/camaleaun/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/eizport/)
## Donate
Would you like to support the advancement of this plugin?
[ Donate to this plugin ](https://eizport.github.io/donate/)