SandyWP / Blueprints

A WordPress setup you can read, run, and repeat.

Import a WordPress Blueprint, inspect the JSON, and run the recipe on a real disposable sandbox—not a browser tab.

Recipe to real WordPress

Keep the setup in JSON. Let SandyWP handle the machinery.

01

Bring the recipe

Import the original blueprint.json URL, paste JSON, or write the recipe directly.

02

Review the plan

SandyWP adapts Playground details and reports anything that needs attention before it runs.

03

Launch the site

Choose the Blueprint from New sandbox. A real WordPress container executes the saved recipe.

04

Freeze the result

Bake a successful recipe into a Template when you want snapshot-speed launches.

Playground, meet real WordPress

First-class support for WordPress Playground

Bring the same blueprint.json you use with Playground. SandyWP keeps its source context, resolves sibling files, adapts browser-only details, and runs the recipe inside a real WordPress container.

One format, practical jobs

Stop writing setup instructions nobody follows twice.

Plugin QA

The same test bed, every time

Install the plugin, enable debugging tools, set options, and seed the exact content your test needs.

Theme demos

Turn a repository into a showroom

Resolve theme ZIPs and content beside the recipe, then hand the finished build to a reusable Template.

Support

Make bug reports executable

Keep the environment in JSON so anyone on the team can recreate the same stack instead of following setup notes.

{ }

Blueprint + Template

Editable recipe first. Instant copies after.

Iterate on the Blueprint while the setup is changing. Once it is right, save it as a Template. SandyWP keeps the source relationship so you know when the recipe has moved on.

See how Templates work →

Good to know

Blueprint questions, answered.

Are these WordPress Playground Blueprints?

Yes. SandyWP imports the same JSON format, then adapts browser-specific details for a real container environment.

Why import from the original URL?

Blueprints often reference sibling files such as theme.zip or content.xml. The original URL gives SandyWP the context needed to resolve them.

How are Blueprints different from Templates?

A Blueprint is an editable recipe. A Template is a snapshot of the finished site. Build with a Blueprint; bake a Template for the fastest repeated launches.

Can a Blueprint run on an existing sandbox?

Yes. A compatible saved Blueprint can be applied from a ready sandbox’s actions menu.

Is execution available on every plan?

Blueprints are free to author and validate. Running PHP, SQL, and WP-CLI instructions requires a paid plan.

Make the environment part of the project.

Import a recipe, review it, and launch a real WordPress sandbox.