Optional WordPress plugin · Public preview

Turn a configured site
into a reusable blueprint.

You do not need this plugin to use SpawnWP. Its main job is to capture a site you have already set up — your usual plugins, theme, uploads and starting content — as a reusable blueprint on your own SpawnWP server, so you can spawn fresh sites from it in minutes. It can also publish one finished site to a separate, empty WordPress install. The plugin detects where it runs and shows only the part that applies.

Public preview: use disposable test sites first and keep an independent backup.

The SpawnWP Deploy plugin on an external site: capture a configured site as a blueprint, with the deploy panel below
Blueprint captureThe plugin's main job, on any WordPress you own.
Where this plugin fits

Four jobs around a site. This plugin does the last two.

Install SpawnWP sets up the lab and cockpit on your server — that is the one-line installer, not this page.

Create a site from the cockpit to spin up a disposable WordPress environment and work in it.

Turn a configured site into a blueprint is the plugin's main job: capture your usual plugins, theme, uploads and starting content as a reusable template on your own SpawnWP server (0.4.0+), then spawn new sites from it in minutes.

Move a finished site out is its other, optional job: copy one site to a separate, fresh WordPress install. Any backup or migration tool works just as well.

The main job

Capture a configured site as a blueprint.

  1. 1

    Add the plugin to the site

    On a site created inside SpawnWP, tick Install the SpawnWP Deploy plugin when you create it — it arrives ready. On your own WordPress, upload and activate the plugin ZIP.

  2. 2

    Pair with your SpawnWP server

    Generate a single-use pairing code on the cockpit's System page (SpawnWP 0.4.0+) and paste it into the plugin on the configured site.

  3. 3

    Choose what to capture

    Plugin files, theme, media uploads and database content are all included by default. Users and passwords are never captured, the source URL never leaves the site, and premium plugins are flagged up front.

  4. 4

    Spawn sites from it

    The capture is verified and installed atomically on your server and appears under Your blueprints on the Deploy page. Re-capture with the same id to replace it safely.

The other job

Or publish one finished site to another.

  1. 1

    Install the plugin on both sites

    Upload and activate the same plugin ZIP on the source site inside SpawnWP and on the separate, fresh target site.

  2. 2

    Connect the target briefly

    Generate a 15-minute connection key on the target WordPress site and paste it into the source.

  3. 3

    Review before transfer

    Run the compatibility checks, review the result and explicitly confirm before any content is copied.

  4. 4

    Verify or roll back

    The target stages and verifies the package, preserves its URL and administrators, and rolls back automatically if activation fails.

Before you transfer

Check it fits your case first.

Use it when both the source and the destination are single-site WordPress, run the same core and PHP version (major.minor), and the destination is a brand-new, empty install.

Your server needs PHP 7.4+ with the sodium and ZIP extensions, trusted HTTPS, a reachable REST API, local uploads and direct file writes. A single transfer can be up to 2 GiB. WordPress core, users, wp-config.php, MU plugins, drop-ins and SpawnWP's own dev tools stay behind on purpose.

Reach for another tool when the destination already has content or is live, or when you need repeated pushes, content merging, selective sync, Multisite or object-storage uploads.

Verify the download

Signed release files.

SHA-256 checksumEd25519 signaturePublic keyae8c55f3c8f97d82e5dd98f3ebe33de87aa331835378169bef8ce678e3bc74e8
Buy me a coffee