What WordPress’s new Reprint tool does and when to use it
Reprint is a free WordPress.org tool that copies a site’s files and database. What it’s for, its limits, and how to handle the customer data it contains.
WordPress.org has released Reprint, a free, open-source tool that copies an entire WordPress site, including its files and its database, to another computer or host. It was announced on 13 November 2026 and covers two jobs many owners eventually face: moving to a new host, and making a test copy before big changes. It is useful, but it is an early release that needs the command line, and every copy it makes contains your customer data, so it needs careful handling.
What Reprint copies
WordPress has long had an export for posts and pages. Moving a whole site also means moving the theme, plugins, uploads and settings, which that export leaves behind. Reprint fills the gap. According to its plugin page, a copy contains “posts, pages, media, users, settings, themes, plugins, and their tables”. For a shop, that means orders and customer accounts come across too.
A few things are deliberately left out. Reprint always skips caches, logs, backup archives, temporary files and some developer files, and you cannot override this. By default it does copy host-specific plugins, such as the must-use plugins that hosts like WP Engine and WP Cloud install (these load automatically and cannot be switched off in the admin), along with cache add-ons. There is an option to remove them, which matters if you are leaving that host. You can also copy just the database or selected files.
How it works, in plain terms
Reprint has two parts: a plugin you install on the site you want to copy, and a separate command-line client on another computer that does the copying.
- Activating the plugin does not start anything by itself.
- The client gives you a “Migration Token”, which you paste into Tools > Reprint Server to authorise it.
- The client then downloads the files and database over HTTPS, an encrypted connection. The data goes straight to that client and does not pass through any Reprint cloud service. No account or subscription is needed.
It sends the site in pieces, so your current host does not need spare space to build one large archive, and an interrupted copy can pick up where it stopped. Later copies only fetch files that have changed. If the site address changes, Reprint rewrites links in the database, including in serialised data, a stored format that breaks if edited carelessly.
The practical catch is that you need a terminal and command-line PHP 7.4 or later on the receiving computer: macOS, Linux, or Windows via WSL (Windows Subsystem for Linux). You also need administrator access to the site, though not SSH (remote login) access to your current host. There is an “experimental” option that runs in the browser through WordPress Playground, and you can try it on a sample site without installing anything.
The WordPress.org plugin only copies from your site. Changes made on a copy cannot be sent back to the live site.
When a business might use it
Moving host. Visitors can carry on using the original site while you copy it. WordPress suggests checking the copy’s pages, images and forms, then pausing changes on the original, taking a final copy and pointing your domain at the new host. Reprint does not switch your domain over or delete the original site; that stays with you and your host. The official guide recommends keeping the original available as a fallback until the new site has been checked.
Making a test copy. A private copy lets you try a new layout with your real pages, see how a plugin fits, or check everything still works after a WordPress update before doing it on the live site. Given how often updates arrive, as with WordPress 7.1.4, a realistic test copy is a sensible habit.
The precautions that matter
A copy holds sensitive data. The plugin’s own FAQ warns that copies “may include private content, personal data, password hashes, and configuration secrets”. Store copies where visitors cannot reach them and keep the working folders private; the state/ folder holds credentials, transfer progress and the downloaded database. In our view, a downloaded copy deserves the same care as your live customer records, and copies you no longer need should be deleted.
A copy can behave like your live site. Its plugins may still connect to live email, payment and other services. Before opening a copy, turn off outgoing mail, scheduled jobs, payments and other live connections. These settings vary from site to site, and Reprint does not handle them all.
The live site keeps changing during a copy. The result is not one frozen snapshot. For a final move, pause new orders, uploads and other changes, then take one last copy.
It replaces rather than merges. Re-importing the database overwrites any posts, settings, orders or users changed on the copy.
A finished copy is not proof everything works. Test pages, login, forms and key plugins on the new host before going live. Do not reuse your old host’s database credentials there either.
Security services can block it. Cloudflare browser challenges, Wordfence request limits or proxies that strip headers can stop a copy.
Revoke access afterwards. Remove the client’s Migration Token under Tools > Reprint Server. Deleting the plugin removes its stored settings and credentials, but neither step affects copies already made.
Multisite networks are only partly supported: Reprint can move one site out of a network, but not copy a whole network.
A note for WooCommerce shops
WordPress’s guidance talks about payments and scheduled jobs in general terms; there is no WooCommerce-specific advice. From our own practice, on any copy of a shop we would put payment gateways into test mode or disable them, stop scheduled tasks such as subscription renewals, and make sure order and account emails cannot reach real customers. If you sell subscriptions, this is the step not to skip.
Is it ready for you?
Reprint is at version 0.11.8, with around 60 active installations and no reviews yet, and the browser option is labelled experimental. We found no reported security problems, but the tool is too new to have a track record either way. Although the plugin is tagged “backup”, WordPress describes it only as a tool for copying and moving sites, so it should not replace your backups.
What you should do
If we look after your website, you do not need to do anything. If you are thinking about moving host or want a test copy, talk to us first so we can agree how the copy is made, where it is stored and when it is deleted.
If you manage it yourself:
- Only use Reprint if you are comfortable with the command line, or try the sample site first.
- Before opening any copy, switch off email, payments and scheduled jobs on it.
- For a final move, pause orders, take a last copy and keep the old site running until the new one is checked.
- Remove the Migration Token when you finish, and delete the plugin if you no longer need it.
- Store copies privately and delete them when they are no longer needed.
If a host move is on your list for next year, our hosting team can talk through whether Reprint or another route suits your site.