A small tool for WordPress developers

Keep the good version.

Save a named snapshot of your WordPress development site before you experiment. Restore a saved state when you need to go back.

For WordPress development / Requires WP-CLI


State / saved

01 / The idea

Make changes without losing your place.

Development means trying things. Updates, experiments, quick fixes, and the occasional wrong turn.

SnapShots gives you a way to save a state before the next change, then return to a saved one from the WordPress admin interface or WP-CLI.

02 / The workflow

Save. Try. Go back.

  1. 01

    Save a state

    Create a snapshot of the development site before making a change.

  2. 02

    Name the moment

    Give it a useful name so you know which state you saved.

  3. 03

    Restore when needed

    Choose a saved snapshot and confirm restoration from WordPress.

Restoration changes stored site data. Review the confirmation and keep appropriate backups.

03 / The details

Small footprint. Useful details.

01 Named snapshots
Keep saved states easy to recognize.
02 Database + files
Restore WordPress database tables and supported files, depending on configuration.
03 Return to your place
The plugin can remember the page you were on and redirect after restoration.
04 Minimal admin UI
Create and restore snapshots from a small interface in the WordPress admin bar and Tools screen.
05 Configurable behavior
Settings are available through the admin screen, constants in wp-config.php, and filters for developers.

A better way to experiment

Keep moving.
Know where you can go back.

One intentional checkpoint before an experiment can save a lot of manual undoing.

04 / Before you install

A few things to know.

WordPress Check the current supported versions on WordPress.org before installing.
WP-CLI Required. SnapShots runs wp snapshot for save, restore, and delete.
PHP execution PHP must be able to call external commands via exec().
Recommended environment Development / local / staging.
Restore behavior A restore can replace data; do not treat it as a read-only preview.

SnapShots is a development convenience, not a substitute for a tested production backup and disaster-recovery process.

05 / Common questions

Good to know.

Does SnapShots need WP-CLI?

Yes. WP-CLI is required, and PHP must allow exec() so the plugin can run shell commands.

Can I save snapshots with names?

Yes. Named states make it easier to find the snapshot you want later.

What gets restored?

Database tables and applicable site files according to your options and configuration—not every file on the server, and not plugins, themes, or core as a separate bundle.

Should I use this instead of site backups?

No. Use SnapShots as a development checkpoint. Keep proper backups for production and disaster recovery.

Where do I download it?

From the official WordPress plugin directory.

06 / Release notes

Changelog

Synced from the plugin readme when the site is built for deploy.

Make room to experiment.

Save the state you have. Build the next thing.

Get SnapShots on WordPress.org