A Blueprint is an editable JSON build plan for WordPress. Save one when you need a setup to be reviewed, versioned, or rerun; use a Template when you need a fast snapshot of a finished site.
Create a Blueprint
Open Blueprints from the SandyWP app and select New Blueprint. You can import a URL or bundle, paste JSON, or start with a small recipe.
SandyWP validates the document when you save it. An incompatible recipe can still be saved, but errors must be corrected before it can run.
Import from a URL or bundle
Use the original blueprint.json URL when the recipe is self-contained. Relative resources resolve against that document’s URL, so direct raw-file URLs are preferable.
Use a ZIP bundle when the recipe and local assets belong together. The archive needs exactly one blueprint.json at its root or inside one top-level folder.
Compatibility
SandyWP reports compatibility changes before it executes a Blueprint. Informational and warning findings do not block a run; errors do.
Blueprint execution can run PHP, SQL, and WP-CLI. Creating, applying, or baking a Blueprint requires a paid plan, even though authoring and validation are free.
Run, apply, or bake
Create a sandbox from a saved Blueprint in the create form. To apply it to an existing ready sandbox, use the Blueprint actions for that sandbox.
Save as Template runs the recipe in a fresh scratch sandbox and snapshots the result. Use that workflow when you want a reusable, fast-to-restore starting point.
Runs are asynchronous. Watch the run status and inspect its findings or log before treating the site or Template as ready.
Automate Blueprints
The generated API Reference includes the standalone Blueprint endpoints. Use Blueprint API guidance for the validate, save, run, and bake workflow, or use the CLI as a practical wrapper.
