Skip to main content

​
Backups

Yes. The work is done in short ticks that save progress, so the job continues without the page open. Reopen the Backups page to see where it got to.A restore is different: stay on the page for that one.
Because it holds less that you do not need. Caches, node_modules, .git, log files, other backup plugins’ folders, and regenerable Elementor CSS are all excluded, and the archive is compressed.Two to four times smaller than an uncompressed format is expected and is not data loss.
No, deliberately. It holds your database credentials and salts, and a restore keeps the target site’s own file. That is exactly what makes restoring onto a different server or database work.
By how much work you would be willing to lose. A store taking orders daily should back up daily; a site that changes twice a year does not need it.Whatever the schedule, take a manual backup before anything risky.
More than feels necessary. Problems are often noticed late, and if every backup you hold is newer than the problem, they all contain it. Three daily backups is three days of history.
Yes, and that is what the tick design is for. Work happens in short bursts that save progress, so no single request has to survive long enough to back up the whole site.

​
Restores and migrations

Yes, and that is a migration. Snapshotify detects the address changed and rewrites URLs throughout the database, including the JSON-escaped form every major page builder stores.
Yes. Table names are rewritten during the import, and the prefix that lives inside the data, in role definitions and user capabilities, is repaired straight afterwards. Without that second step nobody could sign into wp-admin.
Possibly. The users table is replaced, so your session may no longer be valid. Snapshotify issues a re-login token valid for 30 minutes; after that, use the credentials from the backup.
No. Take a backup of the current state first. That backup is the only route back.
Only login-URL changers and SSL forcers, and only on a migration. A login-URL changer moves wp-login.php to a slug stored in the source database, so after moving, nobody could find the login page. An SSL forcer loops if the destination is not on HTTPS yet.A same-site restore never does this.
No. Core is included in a full-site backup and restored in two phases specifically so that a cross-version restore does not fatal partway through.

​
Storage

No. It uses a scope limited to files the app itself created, so your existing Drive is invisible to it. OneDrive and Dropbox use a dedicated app folder for the same reason.The consequence is that a backup you move by hand in the provider’s interface becomes invisible to the plugin.
The backup completes as a local backup and the reason is written to its activity log. You get a working backup in the wrong place rather than none.A row showing Local on a cloud-configured site is telling you an upload failed.
Yes by default, so you have two. Developers can turn that off with a filter when disk space is tight, accepting that a lost cloud file then leaves nothing.
Yes. The relay URLs are filterable, which is what you would change to run your own applications and your own token exchange.

​
Compatibility

No, and it refuses rather than trying. The table enumeration would use the current blog’s prefix and silently omit the network tables and every other subsite, producing an archive that looks fine and is not.
Yes, though there is little reason to. Snapshotify skips other backup plugins’ directories, so you will not end up backing up your backups.
Yes. Orders, products, and customers are in the database, which is in the backup. Take backups often enough that the gap does not cost you orders.
Caches are excluded from backups, since they regenerate. After a restore, clear your cache so the old pages are not served.

​
Licensing

Pro is part of the DaftPlug membership. One license covers Snapshotify and every other DaftPlug Pro plugin, and plans differ only in how many sites you can activate on.
Nothing is deleted. Existing backups stay in the list and can still be restored and downloaded. What stops is scheduling, retention, and cloud uploads.
No. Backup, upload, restore, and the URL rewriting are all free. Pro is for backups that happen without you.