Everything DriftSync can do.

A side-by-side preview of every value that would be added, overwritten, merged or skipped — before a single byte is written.

Choose per apply how existing values are treated. Skip to protect the target, overwrite to force the source, or merge to combine.

A restore point is captured automatically before any change is applied, so any apply can be reversed in one click.

Every apply is recorded — what changed, when, and by whom — and every entry is reversible from the history.

Bundles are plain, human-readable JSON — never PHP, JavaScript or shell. Nothing in a bundle runs; it is only ever data applied to settings.

Scan on export with presets (none / secrets / secrets + URLs / strict). A withheld value is held, not blanked — applying never wipes the target’s existing key.

Because a bundle is just JSON, you can commit it, review it in a pull request, and diff it in any tool you already use.

The whole export → diff → apply → rollback loop across unlimited sites — no account, no cloud, no telemetry. Nothing leaves your server.

Export selected settings and option groups from core, themes and plugins, grouped so you sync intent rather than raw rows.

Move site-wide global styles and theme.json configuration between environments as part of a bundle.

Carry your synced patterns and reusable (synced) blocks across sites without copy-paste.

Sync both classic and block-based navigation menus, including their structure and items.

Move custom post type and taxonomy definitions so structure stays in step between staging and production.

Connect two sites and push or pull bundles between them directly (P2P), with the same dry-run diff and snapshot on the receiving end.

Apply one bundle to many connected sites at once, each with its own diff, snapshot and result.

Run a sync on a schedule instead of by hand, so downstream sites stay aligned automatically.

A shared library of versioned bundles your team can reuse, with a shared audit trail across everyone who applies them.

Gate a bundle behind an approval before it can be applied downstream, so changes are reviewed the way code is.

When two sites cannot reach each other directly, hand a bundle off through a mailbox and let the target pull it when it can.

Watch a fan-out roll out across every target from one board — applied, pending, held or failed, at a glance.

Explain-this-diff summaries and conflict suggestions help you understand a change and pick the right resolution.