WordPress Just Launched Reprint — a Free Tool That Copies Your Whole Site. Here's What It Actually Does (and What It Doesn't)

WordPress.org just released Reprint, a free tool that copies your entire site — files, database, users, settings and all — to a new host or your own laptop. I read the announcement, the plugin docs and the first hands-on tests so you don't have to: here's how it works, what it copies, the limits nobody is talking about, and the safety checklist I'd run before touching it.

WordPress Just Launched Reprint — a Free Tool That Copies Your Whole Site. Here's What It Actually Does (and What It Doesn't)
WordPress Just Launched Reprint — a Free Tool That Copies Your Whole Site. Here's What It Actually Does (and What It Doesn't) — Technical Architecture & Overview

Table of Contents

Introduction

I have moved WordPress sites more times than I can count, and it has never once been the clean, one-click job the ads promise. A table doesn't come across, a plugin quietly breaks on the new host, or everything looks fine until a customer tries to check out and the payment gateway is still pointing at the old server.

So when WordPress.org announced a brand-new, official, free tool for copying a whole site on November 13, 2026, I paid attention. It's called Reprint, from the WordPress project itself — not a plugin shop or a host upselling a migration add-on. The announcement, written by Adam Zieliński on WordPress News, calls it "a free, open-source, PHP-based tool that copies a WordPress site's files and database" to a new host or your own computer. No account, no subscription, no outside service in the middle.

That sounds like the thing WordPress has been missing for years. But official and free doesn't mean right for every job — especially in version 0.11.8, where Reprint sits today. I read the announcement, the plugin docs and the first hands-on tests; here's the honest picture. If you run an Elementor site, this matters: your pages, templates and settings live in the same files and database Reprint copies.

What Reprint actually is

Reprint is two pieces. The first is a plugin called Reprint Server: install it on the site you want to copy, from the WordPress.org plugin directory, like any other plugin. It needs an administrator account, and activating it doesn't start a copy — it just makes your site ready to be copied.

The second piece is a command-line client, a single file called reprint.phar, that runs on the computer or server receiving the copy. You authorize it with a Migration Token pasted into Tools, then Reprint Server, in your dashboard, and the client then pulls your site's data over HTTPS. No SSH access to the old site is needed — plenty of cheap shared hosts don't offer SSH at all, and that used to be a hard wall for serious migration tools.

The copy goes directly from your site to the destination machine — nothing routes through a third-party service, and no account or subscription is required. That directness is the point: Reprint sits under the Data Liberation banner, the WordPress project's effort since 2024 to make it easier to move your site wherever you want, without host or vendor lock-in.

The receiving machine needs PHP 7.4 or newer, and the destination database can be MySQL or SQLite. There's also an experimental browser demo inside WordPress Playground that needs no install. One number for perspective: on announcement day the plugin showed version 0.11.8, tested up to WordPress 7.1.4, and installed on 20 sites. Twenty. This is a brand-new tool — test it on a copy first, which is exactly what it's for.

What it copies — and what it skips

The built-in WordPress exporter has always been the weak link in moving a site: it handles posts and pages, and that's about it. Your theme, plugins, media library, settings and users never came along, which is why moving a full site has always meant a paid migration plugin or asking your host for help.

Reprint copies the whole thing: posts, pages, media, users, settings, themes, plugins and their database tables. That last part matters most — a WooCommerce store's orders live in plugin tables, and an Elementor site's templates, Theme Builder conditions and global styles live in the database too. If it's in the database, it comes along: the difference between "I moved my content" and "I moved my site."

What it skips is equally deliberate: caches, logs, backup archives and temporary files — nobody needs a copy of your cache. Two limits: whole multisite networks are not supported, although a single site can be pulled out of one; and the copy is not a frozen snapshot, so if someone publishes or orders mid-copy, the copy may or may not include it. For a quiet blog that's a non-issue; for a busy store, copy during a quiet hour.

What Reprint deliberately does not do

This is the section most launch coverage skips, and it's the one that will save you from a bad day. Reprint copies a site; it is not a migration plan, and the handbook is direct about the gaps.

First, Reprint does not perform the traffic switch: it won't point your domain at the new host, change your DNS, or check that the new copy is the one visitors reach. The copy lands on the destination and waits for you to do the rest.

Second, it doesn't verify that everything works after the move — forms, email, checkout. The copy rewrites the site address, but the testing is your job. The first hands-on testers flagged exactly this: a "successful copy" and a "working site" are two different things until you test.

Third, the Playground route has hard limits: the in-browser import caps at 2 GiB, the tab must stay open until the copy finishes, and Playground is a different environment from your host, so some plugins will behave differently. A great way to try Reprint — not a way to move a five-gigabyte membership site.

The security catch nobody should skip

Here's the part I want every site owner to read twice. A full copy of your site is a full copy of your site: the plugin page warns that copies may contain private content, personal data, password hashes and configuration secrets. One early guide put it bluntly — a copy includes your users and settings, and stays wired to your live email and payment accounts.

In practice: copy your live store to your laptop to test a plugin update, and that laptop now holds your customers' data, your admin password hashes and your payment gateway keys. Send that copy to a developer, upload it to a shared drive, or leave it on a machine you later sell, and you've handed over the keys to your business.

So the rule is simple: treat a Reprint copy like your live site's backup. Don't pass one on without cleaning it, change or remove secrets before sharing, use a staging copy for testing instead of live credentials, and revoke the Migration Token when you're done. This isn't a reason to avoid Reprint — Duplicator packages and UpdraftPlus backups contain the same sensitive data — but Reprint is new, official and free, so first-time migrators will use it, and they deserve the warning before they click, not after.

Reprint vs the migration plugins I already use

If you've moved a site before, you've probably used Duplicator, All-in-One WP Migration, UpdraftPlus Migrator, Migrate Guru, or your host's own migration service. Reprint doesn't replace all of them on day one, so here's where it wins and where it doesn't.

Where Reprint wins is simplicity and ownership. It's free with no paid tier gating the features you need — no account, no upload to a vendor's server, no file-size limit forcing you into a premium plan. Your data goes straight from your site to your machine, and because it's from WordPress.org, hosts and other tools will likely build around it.

Where the established plugins still win is the finished job. Duplicator and Migrate Guru handle the search-and-replace, the domain switch and the post-move checks as part of the flow, with years of edge cases baked in. Reprint 0.11.8 has none of that scar tissue yet, and its command-line client is aimed, for now, at people comfortable in a terminal.

My honest read: developers and comfortable tinkerers should try it for staging copies today; business owners who need a guaranteed zero-downtime move of a live store should still pay for a managed migration. The free tool and the finished service are different products.

When I'd actually use it

The best use case, and the one WordPress.org pitches first, is testing. WordPress 7.2's release candidate lands today, and the final release arrives December 8 — exactly when a staging copy earns its keep: copy your live site, update the copy to 7.2, test your Elementor templates, forms and checkout, and only then update the live site. If something breaks, you find out on the copy, not in front of your visitors.

The second use case is host moves where you control both ends. If you're moving hosts and you're comfortable running a command on the new server, Reprint gives you the official, no-cost path: install the plugin, paste the token, run the client, and your files and database land on the new machine. You still handle DNS and testing yourself, but the heavy lifting is done.

I wouldn't use it for a same-day, zero-downtime move of a busy store, for a multisite network as a whole, or for a site over 2 GiB on the Playground route — use the command-line client there, not the browser demo.

My 7-step safe-copy checklist

Before I run Reprint on anything that matters, I run this checklist — short, boring, and the difference between a useful staging copy and a security incident.

One, copy during a quiet hour, when nobody is publishing, ordering or registering. Two, use a fresh destination — a clean folder or a fresh database beats copying over an old install. Three, revoke the Migration Token when the copy finishes. Four, the moment the copy lands, change the admin passwords on the copy and disconnect the live email and payment settings — a staging copy that can email real customers or charge real cards is a loaded gun. Five, test the things Reprint doesn't test: submit a form, place a test order, click through your Elementor templates and checkout. Six, treat the copy like a backup: encrypt it if it leaves your machine, don't email it or drop it in a shared drive, and delete it when you're done. Seven, keep your live site untouched until the copy proves itself.

What this means for Elementor users

If you build with Elementor, Reprint is good news with one habit change. Everything Elementor stores — pages, Theme Builder templates and their display conditions, global colors and fonts, popups, form entries — lives in the files and database tables Reprint copies. So a Reprint copy of an Elementor site should be faithful, templates and all — a big step up from the old exporter, which left your templates behind.

The habit change is about testing updates: Elementor, like WordPress core, ships updates that occasionally collide with a specific theme or plugin combination. The smart workflow is now free — Reprint your live site to a staging copy, run the updates there, click through every template, and only then update live. Twenty minutes, and it has saved me from broken layouts more than once.

Conclusion

Reprint is not the flashiest launch of November. It has no AI model in it and it won't write your content for you. What it does is quieter and, for people who run WordPress sites, more useful: an official, free, no-account way to copy your entire site — files, database, users, settings, themes, plugins and all — to a new host or your own computer.

The honest version is that it's early: version 0.11.8, twenty installs on launch day, a command-line client, an experimental browser demo, no traffic switch, no post-move checks, no multisite support, and a copy that carries your password hashes and payment keys. Treat it like a finished migration service and it will let you down; treat it like what it is — a copying tool built for staging, testing and host moves — and it's already one of the most useful things WordPress.org has shipped this year.

My plan is simple: Reprint for staging copies first, starting with a WordPress 7.2 test copy this week, and the paid migration plugins for zero-downtime client moves. Try it on a copy of a site you can afford to break. Run the checklist. When Reprint hits 1.0, I suspect a lot of us will wonder how we ever moved sites without it.

FAQ

Is Reprint really free?

Yes. It's free and open source from WordPress.org, and the plugin page states plainly that no Reprint account or subscription is required. You still need a destination — a new host or a computer with PHP 7.4 or newer — but the tool itself costs nothing.

Does Reprint work with Elementor sites?

Yes. Reprint copies files and the full database, including the tables where Elementor stores pages, Theme Builder templates, display conditions and global styles. A copy of an Elementor site should include your templates and settings, not just your posts.

Can Reprint move my site to a new host by itself?

It copies your site to the new host, but it doesn't finish the move: Reprint does not switch your domain or DNS, and it doesn't verify that forms, email and checkout still work after the move. You handle the traffic switch and the testing yourself.

Is it safe to share a copy Reprint makes?

Only after cleaning it. A copy contains users, password hashes, plugin keys and live email and payment settings. Change passwords and disconnect live services before sharing a copy with anyone, and delete copies you no longer need.

Do I need SSH or a developer to use Reprint?

You need administrator access to install the plugin, and the main copy runs from a command-line client on the receiving machine, so some terminal comfort helps. No SSH access to the old site is needed. There's also an experimental browser demo in WordPress Playground that needs no install, but it's capped at 2 GiB and the tab must stay open.

What WordPress version does Reprint need?

Version 0.11.8 is tested up to WordPress 7.1.4, and the source plugin supports PHP 5.6.20 or newer. The receiving machine needs PHP 7.4 or newer to run the command-line client.

Looking for more WordPress & Elementor tutorials?

Explore our complete directory of 53+ web performance, theme development, and Elementor architecture guides.

View Topic Sitemap XML Feed