Blueprints

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.

{
  "$schema": "https://playground.wordpress.net/blueprint-schema.json",
  "steps": [
    {
      "step": "installPlugin",
      "pluginZipFile": {
        "resource": "wordpress.org/plugins",
        "slug": "query-monitor"
      }
    }
  ]
}

SandyWP validates the document when you save it. An incompatible recipe can still be saved, but errors must be corrected before it can run.

Describe it instead

Choose Describe and write what you want in plain words, for example “A WooCommerce store on PHP 8.3 with three sample products and the Storefront theme.” Claude writes the Blueprint, SandyWP validates it, and the JSON opens in the editor so you can review or change it before saving. Each workspace can generate a limited number of Blueprints per day.

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.

https://raw.githubusercontent.com/example/project/main/blueprint.json

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.

Bundle limit	Value
Compressed size	50 MiB
Expanded size	250 MiB
File entries	2,000

Compatibility

SandyWP reports compatibility changes before it executes a Blueprint. Informational and warning findings do not block a run; errors do.

Category	What SandyWP does
Natively provided	Removes known Playground flags that are always supplied by a SandyWP sandbox.
Automatically adapted	Rewrites supported legacy resources or compatible steps.
Ignored and reported	Removes unsupported metadata or steps and shows a finding.
Blocking	Stops a run for schema errors, unknown feature keys, unsafe paths, or unresolved local resources.

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. If the Blueprint sets landingPage to a path inside the sandbox, such as /wp-admin/plugins.php, the Template uses it as the Demo destination for public demos. Every rebake applies it again. Creating or applying a sandbox ignores it, and a full URL is reported as a warning and ignored. 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.

sandywp blueprint validate blueprint.json
sandywp blueprint bake plugin-recipe --wait

Getting started

Using sandboxes

Tools

Integrations

Connectors

Account

Automation guides

API Reference

Create a Blueprint

Describe it instead

Import from a URL or bundle

Compatibility

Run, apply, or bake

Automate Blueprints

​Create a Blueprint

​Describe it instead

​Import from a URL or bundle

​Compatibility

​Run, apply, or bake

​Automate Blueprints

Create a Blueprint

Describe it instead

Import from a URL or bundle

Compatibility

Run, apply, or bake

Automate Blueprints