Skip to main content
Snapshotify makes complete backups of a WordPress site, restores them, and moves a site from one address to another. One archive covers all three, because a restore onto a different domain is a migration.
The Snapshotify backups page, listing existing backups with their contents, size, location, and date

​
The three jobs

Back up

Files and database in one archive, with a manifest describing what is inside. Manual, or on a schedule.

Restore

Put a site back as it was, from a backup in your list or from an archive you upload.

Migrate

Restore onto a different domain and Snapshotify rewrites the URLs, including the escaped forms page builders store.

Store off-site

Google Drive, OneDrive, or Dropbox. A backup on the same server as the site is not a backup.

​
How it runs

Backing up a site takes longer than a web request is allowed to last. Snapshotify does the work in ticks: short bursts of about twenty seconds each, saving progress after every one. That means a backup continues whether or not you are watching, and a job interrupted by a timeout resumes where it stopped rather than starting over.

How backups run

The tick pipeline, the three things that drive it, and why a job can finish after you close the tab.

​
What goes into an archive

Every backup contains database.sql and manifest.json, plus the files you did not exclude. You choose scope with five exclusions: core, media library, plugins, themes, and database. A full-site backup excludes nothing. Excluding all five is refused, since there would be nothing to back up. Some things are never included, deliberately:
This is why a Snapshotify archive is often two to four times smaller than an equivalent from another plugin. Uncompressed formats that include caches and dev artifacts are bigger without holding more of your site.

​
Where the plugin lives

Snapshotify adds a top-level Snapshotify menu with two pages.
Multisite is not supported and is refused outright. This is deliberate rather than missing. On a network, the table enumeration would silently omit the network tables and every other subsite, producing an archive that looks successful until someone needs it. Refusing is safer than a backup you cannot rely on.

Install Snapshotify

Requirements, installation, and your first backup.