For WordPress sites that live on your computer
Move your local WordPress site to your web hosting.
Built your site in WordPress Studio, Local, Docker or MAMP? Reprint Relay copies it to your hosting: pages, images, plugins, settings, everything. No exporting, no FTP uploads of huge files, no database fiddling.
Free ยท No account ยท About 15 minutes
How it works
Your web hosting can't reach a site on your computer, and your computer isn't on the internet. Reprint Relay sits in the middle: your computer connects out to it, your hosting fetches the site through it.
- 1
Add two plugins to your local site
Reprint (by WordPress.org) and our small connector. The connector shows a short code like
K7QM-3XDA. - 2
Put one helper file on your hosting
Upload
reprint-web.phpwhere your site should live and open it in the browser. Enter the code. - 3
Approve and copy
Click Approve on your local site, then Start on your hosting. Your site appears at its new address.
What you need
- Your WordPress site running on your computer, and you can log in to its dashboard.
- Web hosting with PHP 7.4 or newer. Most hosting has this.
- An empty database on your hosting: its name, user and password (your hosting panel creates one in a minute).
- A way to upload one file: FTP or your hosting's file manager.
What gets copied
- All posts, pages, media, menus, users and settings.
- Your theme and plugins exactly as they are.
- Links inside your content are switched to the new address automatically.
- Your local site is not changed. It only gets read.
Is it safe?
๐ Only you can open the door
Nothing can be copied until you click Approve on your own site. Before you do, both sides show the same key fingerprint, so you can check you're approving your own hosting.
๐ Signed and encrypted
Every request is signed by your hosting's private key, which never leaves your hosting. The relay passes requests on but can't forge them. Connections use HTTPS.
๐งน Nothing is kept
Your site streams through and is never stored here. Each migration has its own random connection; nobody else's transfer can touch yours. The connection ends when you disconnect, or after 48 hours at the latest.
๐๏ธ One code, one destination
Once your hosting has used your code, no one else can use it. If someone else does try, your site shows their address and you just click Reject.
๐ No accounts, no tracking
This page has no cookies, no analytics and no third-party scripts. The password for your helper file is created in your browser and never sent to us.
๐ Open and standard
The copying is done by Reprint, the official tool from WordPress.org. The relay only carries its messages.
What exactly happens with my site and my data?The full, honest version
The short version
Your site travels from your computer, through our server, to your hosting, piece by piece. Nothing of it is saved on our server. We keep a few technical details about the connection for up to 48 hours, and a short log for 14 days. That's it.
1. What travels through our server
Everything your hosting needs to rebuild the site:
- Your files: WordPress itself, your theme, plugins and uploads (images, PDFs โฆ).
- Your database: posts, pages, comments, settings, and the user accounts of your site, including their email addresses and their encrypted passwords (WordPress never stores passwords in readable form).
- Your configuration: including
wp-config.php, which holds your local database password and WordPress security keys.
2. How it travels
- Your hosting asks for one piece at a time. Our server receives the piece from your computer and hands it straight on. It sits in memory for a moment while it passes, and is never written to disk, copied or kept.
- Both connections, computer โ relay and relay โ hosting, are encrypted (HTTPS).
- Every request carries a digital signature from your hosting. Your site checks it before it answers anything. The key for that signature exists only on your hosting. Our server can't create it, so it can't ask your site for data on its own.
3. Could you read my data?
Honestly: technically, yes, while it passes through. Like any server that forwards web traffic, ours unpacks the encryption of one connection and packs it into the other. We don't look at the content, don't analyse it and don't store it, but you should know that it's possible. If that's not acceptable for your site, you don't need us: put your site online somewhere temporarily and let Reprint copy it directly.
After moving, it's good practice anyway to give the new site fresh security keys (generator) and to change passwords you reused locally.
4. What we keep, and for how long
| What | Why | How long |
|---|---|---|
| Your site's contents (files, database) | Only passed on | Not kept at all |
| A random connection ID and your pairing code | To connect the right two sides | Until you disconnect, at most 48 hours. Kept in memory; only while we update our server is it written to disk for a few seconds, then deleted. |
Your site's name and address, e.g. http://localhost:8881 | So the hosting side can show "โ Found: My Site" | Same as above |
| The internet addresses (IP) of your computer and your hosting | Abuse protection and the "Requested from โฆ" check on Approve | Same as above |
| How many megabytes went through | Progress display and fair-use limits | Same as above |
| One check of your site's public address when you connect | To see whether you need the relay at all (we ask your site's Reprint once; it answers "key required" and nothing else) | Not kept, only the yes/no answer is used |
| Server log: time, IP addresses, site address, a short connection ID | Stopping abuse, fixing problems | 14 days |
| Total traffic of all users this month (one number) | Staying within our server's limits | Reset monthly, no personal data |
5. On this page
No cookies, no analytics, no ads, no fonts or scripts from other companies. Your progress through the steps is kept only in this browser tab and disappears when you close it. The password for your helper file is made in your browser. It is written into the file on your computer and never sent to us.
6. On your computer and your hosting
- Your local site is only read, never changed. The connector stores a few settings of its own; deleting the plugin removes all of them.
- Approving adds your hosting's public key to Reprint on your local site. You can remove it any time under Tools โ Reprint Server.
- On your hosting, the helper keeps its working files in a
reprint-datafolder (including a private key). Delete the folder andreprint-web.phpwhen you're done. The guide reminds you.
7. Stopping
Click Disconnect on your local site, or simply deactivate the connector plugin. The connection closes immediately and its details are forgotten. Nothing is shared with or sold to anyone. Details and your rights: Privacy notice.
Questions
My site is already online. Do I need this?
No. If your old site has a public address, Reprint can copy it directly. The relay is only for sites your hosting can't reach: on your computer, in a container or behind a company network. To keep it free for those, the relay checks when you connect: if your site's Reprint answers from the internet over HTTPS, the connection is declined and the connector shows you the address to use instead.
Does it cost anything?
No. Fair-use limits apply so the service stays fast for everyone: up to 50 GB per migration and a limited number of migrations per hour.
Do I have to keep my computer on?
Yes, until the copy is finished. Your local site is the source. Usually the connector keeps running on its own in the background. If your setup doesn't allow that, it asks you to keep its admin page open.
Something went wrong halfway. Do I start over?
No. Just press Start (or Resume) again. Reprint continues where it stopped and only fetches what is missing.
Which local tools work?
WordPress Studio, Local, Docker / docker-compose, MAMP, XAMPP, Laragon, DDEV, Lando, wp-env and plain PHP setups. Anything that runs WordPress with PHP.
What about emails, payments and scheduled jobs?
They are copied exactly as they are. If your local site has live payment keys or sends emails, check those settings on the new site before you announce it.