The short answer
Reprint is a free, open-source tool from WordPress.org, announced on November 13, 2026, that copies a whole WordPress site: its files and its database, including themes, plugins, uploads, users, and settings. You install the Reprint plugin on the site you want to copy, then a command-line client on the receiving computer or server pulls the site over HTTPS. It can resume after a dropped connection, rewrite links to a new address (including serialized data), and copy only changed files on later runs. It is useful for moving to a new host and for making a private test copy. It does not switch your domain for you, does not merge changes, and a finished copy does not prove every plugin works on the new server.
What WordPress.org released
In its announcement, WordPress.org describes Reprint as "a free, open-source, PHP-based tool that copies a WordPress site’s files and database." The plugin is in the WordPress.org Plugin Directory, published by WordPress.org, and the command-line client used to run the copy is distributed alongside it. The post ties Reprint to WordPress’s Data Liberation work, which has aimed since 2024 to make moving a site as easy as exporting posts.
WordPress has long had an exporter for posts and pages. That has never covered the rest of a site: the theme, plugins, media uploads, and settings. Moving those usually meant a host’s migration service, a commercial migration plugin, or manual work with files and database dumps.
How Reprint copies a site
Reprint has two parts. The plugin goes on the site you want to copy (the source). The client, a PHP file called reprint.phar, runs on the computer or server that receives the copy. According to the Clone your site guide, the basic flow is:
- Install and activate Reprint on the source site, then open Tools, Reprint Server.
- On the receiving computer, generate a key with the client. It prints a Migration Token.
- Paste the token into the source site to authorize that one client.
- Run the client’s pull command. It downloads files and database data, imports the database into MySQL or SQLite, and can rewrite the site address for the copy.
Features that matter for real sites, per the plugin page and announcement:
- No giant archive first. Files and database rows stream in parts, so the old host does not need room to build one large backup file before the transfer starts.
- Resumable. If the connection drops or the host times out, running the same command again continues from the last saved point.
- Link rewriting. When the address changes, Reprint rewrites links in HTML, block markup, shortcodes, JSON, base64, and serialized PHP data, keeping serialized lengths valid. Broken serialized data is a classic cause of failed manual migrations.
- Incremental refresh. Later pulls skip unchanged files, so updates to a copy are smaller than the first run.
- Direct transfer. Data travels over HTTPS to the client you authorize, without passing through a Reprint cloud service, and no Reprint account or subscription is required.
- Old PHP on the source is OK. The plugin supports source sites on PHP 5.6.20 or newer, which helps when the site being moved is the outdated one. The client needs PHP 7.4 or newer on the receiving machine.
There is also an experimental browser option in WordPress Playground that copies a sample site with nothing to install, so you can see how it works first.
When Reprint helps
Moving to a new host
The Move to another host guide lays out a sensible sequence: copy the site to the new server while the old one keeps serving visitors, test the copy with a host preview or local DNS override, pause new orders and uploads, take one final copy, then change DNS through your host’s normal process. Keep the old site in place as your rollback until you have checked the new one.
Making a test copy
A private copy on a laptop or development server lets you try a WordPress update, a new plugin, or a layout change without touching the live site. SQLite works when you do not have a database server.
What Reprint does not do
The official documentation is candid about limits, and they matter for business sites:
- It does not switch traffic. Changing DNS or your domain routing is still a separate step.
- It is not a merge. A live copy is not a single frozen snapshot, and running the database pull again replaces data on the copy rather than merging edits. Plan a write pause and a final copy.
- A copy can still send real email or take real payments. Plugins on the copy may connect to live mail, payment, or other services. Turn those off or switch to test settings before you use it.
- It does not prove everything works. The guide says a successful transfer "does not confirm that every service works." Test pages, images, forms, logins, and key plugins.
- The copy contains sensitive data. Users, password hashes, personal data, and configuration secrets come along. Keep the copy private, and revoke the client’s token under Tools, Reprint Server when you are done.
- It needs command-line PHP. Someone has to run the client on the receiving machine. On most shared hosting that means a developer or your host.
Reprint is also new. The plugin directory lists it at a 0.x version number, published by WordPress.org in late October 2026. That is normal for a first public release, but test on a non-critical site first.
Is a copy tool enough for my site?
For a healthy site, a good copy tool plus a careful checklist is often all a host move needs. A copy faithfully brings along whatever is already there, though. If the site is hacked, has abandoned plugins, runs on an old PHP version, or throws errors, copying it to a new host moves those problems with it. In that case, fix or clean the site first, or use the fresh copy as a safe place to do that work. That is the kind of job our WordPress Rescue service handles.
What to do next
- Try the Playground demo to see how Reprint works.
- Make a test copy of a low-risk site before using it on your main business site.
- Before a host move, write down which plugins send email, take payments, or call outside services, so you can disable them on the copy.
- Keep your own backups. Reprint copies a site; it is not a substitute for scheduled backups stored off the server.
FAQ
What is Reprint for WordPress?
Reprint is a free, open-source plugin and command-line client from WordPress.org that copies a WordPress site's files and database to another computer or server. It was announced on November 13, 2026, and is available in the WordPress.org Plugin Directory.
Can Reprint move my WordPress site to a new host?
Yes. WordPress.org publishes a Move to another host guide. You copy the site to the new server, test it, pause changes on the old site, take a final copy, and then change your domain's routing. Reprint does not perform the DNS switch for you.
Does Reprint fix URLs and serialized data when the domain changes?
Yes. Given a new site address, Reprint rewrites links in HTML, block markup, shortcodes, JSON, base64, and serialized PHP data, and keeps serialized lengths valid.
Do I need SSH access to my old host to use Reprint?
No. Administrator access to the source WordPress site is enough to install the plugin and authorize the client. You do need command-line PHP 7.4 or newer on the computer or server receiving the copy.
Is Reprint a backup plugin?
Not exactly. It copies a site to a destination you control, and later runs only bring over changed files. It is not a scheduled backup system, so keep your regular off-server backups.
Is it safe to copy a live WordPress site with Reprint?
The source can keep serving visitors during the copy, but the copy is not one frozen snapshot. For a final move, pause new orders and uploads first. Also disable email, payment, and other live connections on the copy before using it.
Sources
- WordPress.org News, "Copy Your WordPress Site with Reprint" (November 13, 2026). https://wordpress.org/news/2026/11/reprint-your-site/
- WordPress.org Plugin Directory, Reprint. https://wordpress.org/plugins/reprint/
- WordPress Developer Resources, Reprint: Clone your site. https://developer.wordpress.org/reprint/getting-started/copy-a-site/
- WordPress Developer Resources, Reprint: Move to another host. https://developer.wordpress.org/reprint/guides/move-to-another-host/
- Make WordPress Core, "Data Liberation and WordPress migrations" (June 21, 2024). https://make.wordpress.org/core/2024/06/21/data-liberation-and-wordpress-migrations/