WordPress Reprint: We Copied a Site With It

On 13 November 2026 WordPress.org announced Reprint, a free, open-source tool that copies a whole WordPress site: files, database, plugins, theme, uploads and settings. You install a plugin on the site you want to copy, run a small command-line program on the computer that should get the copy, and it pulls everything across.
Last updated 21 November 2026. We installed the Reprint plugin 0.11.10 on a local test site (WordPress 7.0.2, PHP 8.4.26, MySQL) and copied it with the Reprint client 0.11.10 into SQLite on the same Linux machine. We didn’t test a real web host, an HTTPS source, a MySQL destination, Windows, multisite, an interrupted copy or the browser demo. Our source ran on plain HTTP, so we had to pass --insecure, which you shouldn’t need on a real site.
Here’s what Reprint is, what happened when we ran it, where it surprised us, and how it compares with the migration plugins you probably already know.
What Reprint is (and isn’t)
Reprint has two parts:
- The plugin, installed on the site you’re copying. It adds a hidden API and a settings screen under Tools > Reprint Server. Activating it starts nothing. The plugin needs WordPress 4.7 and PHP 5.6.20, so it runs on old hosts too.
- The client, a single file called
reprint.pharthat you run with PHP 7.4 or newer on the receiving computer. The requirements page lists the PHP extensions it needs. No account, no subscription, no cloud service in the middle.
The announcement names two jobs: moving to a new host, and making a test copy on your own computer. The client streams files and database rows in small parts, so your old host never has to build one giant archive. If the connection drops, you run the same command again and it carries on. Later runs only fetch files that changed. When the address changes, it rewrites links in the database, including blocks, shortcodes, JSON and serialized data.
Just as useful is what it doesn’t do. The handbook has a whole page called What Reprint does not do. The big ones:
- No push from the WordPress.org plugin. Sending changes back to a live site “needs a server build configured by the site’s host”. The plugin we downloaded has push switched off in its code:
define('REPRINT_PUSH_AVAILABLE', false). - No merging. Pulling the database again drops and recreates every table, so anything you changed on the copy is gone.
- No snapshot. The site keeps running during the copy. For a real move, pause orders, uploads and edits, then take one last copy.
- No code edits. It rewrites the old address in the database and stylesheets, but not in PHP, JavaScript or HTML files.
- Nothing switched off on the copy. Email, payments and scheduled jobs still point at your live accounts until you change them.
We also couldn’t find anything about scheduled backups, restoring from a backup screen, or storing copies in the cloud. It isn’t a backup plugin, and it doesn’t claim to be.
Our test, step by step
1. Install and generate a key
We installed the plugin with WP-CLI, downloaded reprint.phar from WordPress.org, and followed the Clone your site guide. The first command creates a key pair on the receiving computer:
php reprint.phar keygen 'http://127.0.0.1:8092/?reprint-api' \
--state-dir=./state --out=./reprint-key.pem --insecure
It printed a Migration Token ID and a long Migration Token. The token is the public half of the key. The private half stays in reprint-key.pem, which the client saved readable only by our user.
2. Authorize the client
On the source site, Tools > Reprint Server shows one box, “Authorize a client to copy this site”, with a plain warning under it: “Allows downloads of your database and files. Only authorize a client you trust. Never paste a private key.” Because our site used HTTP, the screen added: “If you use HTTP, pass –insecure to reprint pull too; site data, including passwords, travels unencrypted.”
We pasted the token and clicked Authorize client. A “Manage client access” table appeared with the token ID, the date and a remove button. Before that, a request to the API without a valid signature got a 403.
3. Pull the copy
php reprint.phar pull 'http://127.0.0.1:8092/?reprint-api' --insecure \
--private-key-path=./reprint-key.pem --state-dir=./state --fs-root=./files \
--target-engine=sqlite --new-site-url=http://localhost:8881 \
--start-runtime=none
It finished with exit code 0 in 9 minutes 40 seconds. Source and destination were on the same machine, so the network cost almost nothing. On a real host, expect longer.
| Step | What it moved | Time |
|---|---|---|
| Files | 23,331 index entries, about 386 MB | about 21 seconds |
| Database download | One SQL file of about 830 MB, 2,418 tables | about 1 minute 49 seconds |
| Import into SQLite | 9,675 SQL statements | about 7.5 minutes |
| Second run, files only, nothing changed | Nothing downloaded | 1.1 seconds |
Every plugin folder and the theme came across. Comparing file lists, the only two files it left out were logs (wp-content/debug.log and a server log), which matches the docs. It also skipped editor locks (_edit_lock rows) in the database. Our second run proves the “skip unchanged files” part only for the case where nothing changed. We didn’t change files on the source to test a real update.
4. Check the links
After the import, siteurl and home pointed at the new address. Links in our blog posts were rewritten, and so were URLs inside serialized options (a Rank Math setting, Contact Form 7 data). Our two addresses happened to be the same length, so we ran Reprint’s db-rewrite-urls command on the copy with a longer address. The stored lengths changed from s:21 to s:34 and from s:34 to s:47, and PHP’s unserialize() read both without errors. That’s the bit that breaks with a careless find-and-replace.
One address survived: WordPress’s own privacy policy draft still said “Our website address is: http://127.0.0.1:8092.” in plain text. The handbook says plain text gets rewritten, so this may be a bug, or the trailing full stop. Either way, search your copy for the old address before you trust it.
Three things that caught us out
It copied every table in the database, not just our site’s. Our test site shares one MySQL database with other test installs, each with its own table prefix. Reprint downloaded all 2,418 tables, though only 116 belonged to the site we were copying. That’s why the SQL file was 830 MB. Plenty of cheap hosting accounts put several WordPress sites in one database. If yours does, the copy holds the other sites’ users, password hashes and orders too. We didn’t find an option in the handbook to limit a single-site copy to one prefix.
wp-config.php comes across untouched. That includes the source’s database name and password, the security keys, and in our case hard-coded WP_HOME and WP_SITEURL lines. The generated start script overrides the database settings, but not those two. So our copy’s home page redirected back to the old address, and post pages loaded 89 links from the source site. Once we commented out those two lines in the copy, everything loaded from the copy, uploads worked and we could log in with the source admin account. The move guide does say to configure wp-config.php yourself and not reuse the old database password. It’s just easy to miss.
Local-only commands still wanted --insecure. db-rewrite-urls only touches the local database, but refused to run without the flag because the saved source address was HTTP. Over HTTPS you wouldn’t see it.
How it compares
We only tested Reprint. The other columns come from each plugin’s current WordPress.org readme (All-in-One WP Migration 7.113, Duplicator 5.2.0) and the WP-CLI docs, so treat them as “per vendor”. Host migration tools vary too much to put in one column, and we didn’t check any.
| Reprint 0.11.10 | All-in-One WP Migration (free) | Duplicator (Lite) | WP-CLI + SSH | |
|---|---|---|---|---|
| Cost | Free, no paid tier | Free; paid extensions | Free; Pro version | Free |
| How data moves | Client pulls files and rows over HTTPS | Export a .wpress file, upload it on the new site | Archive plus installer | wp db export, then copy files yourself |
| Needs on the destination | Command-line PHP 7.4+ | A WordPress site with the plugin | Web server for the installer | SSH and WP-CLI on both ends |
| Safe rewrite of serialized URLs | Yes (tested) | Yes, per vendor | Custom search and replace, per vendor | Yes, wp search-replace |
| Upload size limit on import | None, data streams in parts | Host’s limit; paid Unlimited Extension gets around it | Not checked | None |
| Scheduled backups | No | Listed under premium extensions | Pro | Do it yourself with cron |
| Resume after a dropped connection | Yes, per handbook (not tested) | Not checked | Not checked | Depends on your tools (rsync can) |
| Copy only changed files next time | Yes | Not checked | Not checked | Yes, with rsync |
| Push back to live | Not in the WordPress.org build | Not checked | Not checked | Yes, manually |
For scale: on 21 November the WordPress.org API listed Reprint at 100+ active installs, All-in-One WP Migration at 5,000,000+ and Duplicator at 1,000,000+. Reprint is three weeks old.
Security notes
A plugin whose job is to hand out your entire database deserves a careful look. From reading the plugin’s code:
- The API answers on any URL with
?reprint-apion the end, and it runs early, before most of WordPress loads. - Every request must be signed with an RSA key of at least 3,072 bits, and its timestamp must be within five minutes of the server’s clock. Hosts without OpenSSL fall back to a shared “connection token”, which works like a password.
- Only administrators can authorize or remove tokens, and those forms are nonce-protected.
The weak point isn’t the plugin, it’s what you do around it. Our advice:
- Use HTTPS. Over HTTP, the plugin itself warns that passwords travel unencrypted.
- Remove the token once the copy is done, then uninstall the plugin. Deleting it through WordPress, or with
wp plugin uninstall, runs its cleanup and removes the stored keys. We checked: the option was gone afterwards. A plain file delete skips that step. - Treat the copy like the live site. It holds password hashes, customer data and your
wp-config.phpsecrets. Don’t leave it in a public web folder or a shared drive. If your host was ever breached, our shared hosting breach checklist covers what to change. - Turn off outgoing email and payments on the copy before you click around, or customers may get real emails from your test site.
When to use it
Use Reprint if you’re comfortable in a terminal and want a local copy to test a plugin, a redesign or a WordPress update. Our WordPress 7.2 overview is a good list of things worth checking on a copy first. It’s also a good fit for moving a big site off a host that chokes on huge backup archives or upload limits.
Stick with what you have if you want backups on a schedule, a point-and-click restore, or to push a staging site back to live. Same if the source runs behind a Cloudflare browser challenge or a strict firewall that you can’t change. The handbook says Reprint stops there.
Whatever you pick, check three things on the copy before you switch DNS: wp-config.php, a search for the old address, and whether the copy can send email.
Frequently asked questions
Is Reprint a backup plugin?
No. Reprint copies a site’s files and database to another computer or server when you run its command-line client. It has no scheduled backups, no restore screen and no cloud storage. A copy you keep can work as a backup, but nothing runs automatically.
Does Reprint copy wp-config.php and my database password?
Yes. In our test the copied wp-config.php was unchanged, including the source database name, password, security keys and hard-coded site addresses. Edit it on the copy, use new database credentials, and keep the copy private.
Can Reprint push changes from my copy back to the live site?
Not with the plugin from WordPress.org. It only serves downloads. Push needs a server build that your host configures, and even then it replaces the live tables rather than merging changes.