You finished a manual WordPress backup before a risky update. The snapshot sits in the plugin list. The host panel is flaky. SFTP credentials are in a password manager you do not want to open on a train. You need the archive on your laptop now: a real file you can keep, copy to cold storage, or hand to another environment. If the only path is “hope the server keeps it,” you do not have a backup habit. You have a hope habit.
Snapshotify includes Download Archives: pull any snapshot down from the dashboard. Snapshots are standard ZIP and SQL, readable without needing Snapshotify later. Free covers full manual backup, and you can download after a manual run. Pro adds schedules and cloud destinations when you want unattended offsite copies. This post is about getting the archive onto a machine you control from wp-admin.
Snapshotify is the DaftPlug backup, restore, and migrate plugin. This post is only about downloading backup archives from the dashboard. Not one-click restore as the sole focus, not cloud upload retries, not chunked upload of an existing ZIP, not migrate URL rewrite, not retention policy, not database-only backup as the focus, not batched large-site processing as the focus (mention as supporting context only). Those live elsewhere. For the portable format story these downloads rely on, keep WordPress portable backup ZIP and SQL without a plugin lock-in nearby.
What Snapshotify actually ships here
Stay inside the real feature set:
- Download Archives: pull any snapshot down from the dashboard
- Full snapshots as standard ZIP and SQL, portable and readable without Snapshotify
- Free path: run a manual backup, then download the archive
- Pro path (adjacent context): scheduled backups and cloud storage when you want copies that leave the server automatically
- Supporting reliability (mention only): batched work so large sites can finish the snapshot you are about to download
This post does not invent undocumented partial-file resume for browser downloads, custom encryption formats Snapshotify does not advertise, or claims that a local download replaces offsite copies forever. The product promise is dashboard download of portable archives. Stay there. Restore, migrate, cloud retry, and retention are parallel tools.
Why dashboard download matters
A backup you cannot take with you is incomplete. Server disks fail. Accounts get suspended. Hosts lock panels during incidents. A ZIP on your laptop or an external drive is a second root of trust.
Portable format makes the download meaningful. Snapshotify packages files and database as standard ZIP and SQL. You are not trapped in a proprietary blob that only one plugin can open. Download is useful because the bytes stay useful later.
Manual runs still need an exit ramp. Free Snapshotify covers full manual backup, upload, restore, and migration. After you click backup, Download Archives is how you take custody of that run without waiting for Pro cloud schedules.
Agencies and freelancers need client copies. Handing a client a dated archive after a milestone is professional. Hunting SFTP paths in a rush is not.
Download pairs with offsite strategy. It does not replace it. Pro schedules and cloud destinations (Google Drive, Dropbox, OneDrive) push copies off the server automatically, with reconnect and retry when uploads fail. Still download important milestone archives when you want a copy in your own hands.
How to download a backup archive in wp-admin
Assume Snapshotify is installed and the site can complete a snapshot (large sites benefit from Snapshotify’s batched processing so the job finishes before you download).
1. Create or locate the snapshot you care about
In wp-admin, open Snapshotify. For a fresh safety copy, run a full manual snapshot (files plus database) before the risky change. Wait until the run completes with a visible finished state. If you already have snapshots listed, pick the one whose timestamp matches the milestone you want (pre-deploy, pre-migration, monthly archive).
Database-only snapshots are a real Snapshotify feature for quick pre-update safety. They are not today’s focus. Prefer a full snapshot when the download is meant as a portable site copy.
2. Use Download Archives from the dashboard
Find the snapshot in the Snapshotify list and use Download Archives to pull it down from the dashboard. Save the file to a disk you control, not only the Downloads folder you empty weekly. Name it with site and date if the default filename is opaque. Confirm the browser finished. A truncated download is worse than no download because it creates false confidence.
3. Verify the archive is real
- Confirm file size is plausible for the site (tiny files after a “full” backup are a red flag).
- Open the ZIP listing locally and confirm you see WordPress files plus a SQL dump as Snapshotify’s portable story describes.
- Store a checksum if your process requires it (optional, good for agencies).
- Keep at least one copy off the laptop that created it (external drive or a cloud folder you control).
You do not need Snapshotify installed to inspect standard ZIP and SQL later. That is the point of the portable format.
4. Know free versus Pro for the wider habit
After a manual run, free can download. Pro adds scheduled automatic backups and cloud storage so copies leave the server on a cadence. If your only offsite plan is “remember to download,” you will forget on the week it matters. Use dashboard download for milestones and custody. Use Pro schedules and cloud for unattended continuity. Cloud retry (covered in a sibling post) keeps failed uploads from disappearing quietly.
5. Keep restore and migrate as separate drills
Downloading is custody. Restore is rehearsal. At least once on staging, restore a downloaded (or cloud) archive so you know the path works. Snapshotify restore handles extraction, import, and URL work when the destination differs. Migration rewrite and one-click restore deserve their own practice runs. Do not wait for an outage to learn the buttons.
6. Watch disk space on the server after downloads
Downloading does not always delete the server-side snapshot. Retention policy (Pro scheduling context) prunes automatic backups by rules you set. Manual snapshots are not the same as “delete after download.” If disk is tight, remove server copies you have already secured elsewhere, on purpose, after verification.
Who this is for
Solo site owners who want a file on a drive before updating WooCommerce or PHP.
Agencies delivering milestone archives to clients without sharing host credentials.
Teams mid-migration who need a portable ZIP+SQL bundle to move between environments.
Anyone on Snapshotify free establishing a manual backup-plus-download ritual before upgrading to scheduled cloud.
Operators who already use cloud destinations and still want an extra local copy of release candidates.
This is less sufficient alone for large organizations that need immutable object storage and formal RPO paperwork. Even then, dashboard download remains a practical custody tool between formal systems.
What good looks like
- Any listed snapshot can be pulled from the Snapshotify dashboard to a machine you control.
- The archive opens as standard ZIP and SQL without needing Snapshotify to inspect it.
- Free manual runs are downloadable; Pro schedules and cloud remain available for unattended offsite.
- One-click restore, cloud retry, chunked upload, migrate URL rewrite, retention policy, database-only focus, and batched large-site deep dives were not required for this win (batching may simply help the snapshot finish).
- You did not invent proprietary encryption claims or treat download as a full offsite program by itself.
- A teammate can run a manual backup, download it, and confirm the ZIP lists files plus SQL in under fifteen minutes.
If download fails at 99%, check host timeouts, proxy buffers, and whether the snapshot itself finished. A failed backup cannot be rescued by a download button.
Pitfalls (the ones that bite)
Downloading a still-running snapshot. Wait for completion. Partial archives create theatre.
Keeping the only copy in browser Downloads. Move it to durable storage and verify.
Assuming download replaces cloud. Same-building laptop and server still share some risk profiles. Pro cloud destinations exist for off-server copies.
Deleting server snapshots before verifying the download. Confirm size and ZIP contents first.
Confusing upload with download. Chunked upload of an existing ZIP is how you bring an archive in. Download Archives is how you take one out.
Skipping portable-format sanity checks. If you cannot see SQL and files, do not call the drill done.
Never rehearsing restore. A shelf of ZIPs without a restore test is a library of assumptions.
Practical checklist before you call it done
- Run a full manual Snapshotify snapshot (or pick a completed one).
- Confirm the run finished successfully.
- Use Download Archives to pull it from the dashboard.
- Verify file size and that the ZIP contains files plus SQL.
- Store the archive somewhere durable off the origin server.
- Optionally configure Pro schedules and cloud for unattended offsite (separate from this drill).
- Leave one-click restore practice, cloud retry tuning, chunked upload, migrate rewrite, retention rules, and database-only habits for their own sessions.
- Note batched large-site support only as the reason big snapshots can finish before download.
- Document where milestone archives live for the next person on call.
- Re-run the download drill after major host or PHP changes.
Takeaway
Backups that never leave the server are single points of failure with better marketing. Snapshotify’s Download Archives control pulls any snapshot from the dashboard as portable ZIP and SQL you can open without the plugin. Free lets you download after a manual run. Pro adds schedules and cloud when you want copies that leave on their own. Supporting batching helps large sites finish the archive you are about to take with you.
Snapshotify makes custody a dashboard action instead of an SFTP scavenger hunt. Run the snapshot. Download the archive. Keep a copy you actually control.
One Pro membership unlocks Snapshotify plus Progressify, Lightify, Generatify, and Rankify. New Pro plugins join existing memberships. Plans differ by site count only (Pro $37.99 for 1 site, Pro Plus $74.99 for 5, Pro Max $138.99 for 100), with a 14-day money-back guarantee. See pricing when a finished backup should become a file in your hands, not only a row in a server UI.
Download the archive. Open the ZIP once. When files and SQL are both there, the backup stopped being a status label and became something you can move.