A backup sitting next to the site is not a safety net. It is a second copy of the same risk.
If the host dies, the account gets locked, ransomware wipes the disk, or someone with panel access deletes the wrong folder, the archive in /backups goes with it. Host snapshots can still help for a quick rollback. They are not enough when the failure is the host itself.
We already covered the wider failure modes in Why website backups fail when you need them most. This one is narrower: put at least one usable copy off the server, on a schedule you do not have to remember.
Same disk is the wrong place for the only copy
Most WordPress “I have backups” setups fail the same way. A plugin writes a ZIP into the hosting account. Or the host keeps nightly images inside the same control panel. Both feel done. Neither survives a dead server.
The point of a backup is to outlive the thing it protects. That means another place: Google Drive, Dropbox, OneDrive, or any storage you can still open when wp-admin will not load.
Snapshotify is built around that split. Free covers the full manual path: one-click full snapshot (database SQL plus site files in a standard ZIP), upload an archive you already have, restore in one click, and migrate to a new domain or host with URLs and serialized data rewritten for you. Pro is the half that runs without you: scheduled daily, weekly, or monthly runs, plus cloud destinations so the copy leaves the server.
What “off your server” looks like in Snapshotify
Under Snapshotify >Settings > Storage you connect Google Drive, Dropbox, or OneDrive. Each one gets a dedicated app folder. The plugin cannot see the rest of your Drive. That is deliberate.
Connecting a provider is not enough by itself. You also set Backups Location to that provider. Scheduled Pro runs then upload in chunks. If the upload fails, the backup still finishes locally. The row will show Local when you expected cloud, which is the cue to open that backup’s activity log instead of assuming success from a green checkmark.
Restore and download work from the cloud copy in the dashboard. You do not download to your laptop first, then re-upload into a broken site. Retention prunes old automatic runs (by count or age, per destination) and leaves manual and uploaded archives alone until you delete them.
That is the product difference most “backup” plugins bury behind a second purchase: schedule plus offsite plus restore from the offsite copy, in one licence.
Keep the restore path boring
Offsite only helps if you can put the site back.
Snapshotify packages a normal ZIP and a normal SQL dump. You can open them without the plugin if you ever have to. Restore handles extraction, import, and URL rewrite. Migration to a new host or domain rewrites paths and serialized PHP data without a search-and-replace script or a hand-edited wp-config.php.
Large or slow hosts are the usual failure mode for “it timed out at 40%.” Backup and restore run in batches. Database-only snapshots exist for the minute before a plugin update, when you need a fast safety copy of the part you cannot rebuild by hand.
Email notifications fire when a scheduled run finishes or fails, so a quiet failure does not wait until the day you need the archive.
Free for the manual path, Pro for the unattended one
Snapshotify is free on WordPress.org. Same plugin. Pro features locked rather than stripped. Free is enough to take a full snapshot, upload someone else’s ZIP, restore, and migrate. Pro unlocks the schedule and the cloud destinations on the Snapshotify product page.
It is also one of five Pro plugins on a DaftPlug membership. One licence unlocks Progressify (PWA), Lightify (performance), Generatify (AI), Rankify (SEO and GEO), and Snapshotify (backups). Plans differ only by site count: Pro $37.99/year for 1 site, Pro Plus $74.99/year for 5, Pro Max $138.99/year for 100. Features are identical across plans. New Pro plugins shipped while you are subscribed join the membership. Checkout is Freemius. Fourteen-day money-back. See pricing.
Take a full snapshot today if you have never restored anything. Then stop treating the copy on the same disk as the only plan. Schedule it off the server, and make sure you can restore from that copy without a hero weekend.