--
title: "Snapshot Before You Delete: The Only Undo You Get"
description: "X deletion has no undo, so the archive ZIP is your only safety net. How to build a snapshot that lasts, and why the snapshot is also a risk."
tags: ["privacy", "backup", "twitter", "security"]
canonical_url: https://digital-footprint-health.shop/blog/snapshot-archive-before-clean
Backing up tweets before deleting sounds like boilerplate process advice, but it is the one step in a cleanup you cannot add later. X deletion is real deletion. No trash bin, no restore button. Once it runs, the only way to check what an old post said is a snapshot.
What counts as a snapshot
The official archive ZIP is the most complete option and you do not need another tool. It carries tweet text, timestamps, tweet IDs, media files, likes, and follow lists. The IDs matter more than people expect, because later you can hit an ID directly to confirm whether a specific tweet is gone.
Its one weakness is being static. The archive captures the moment you requested it, so a snapshot is not a one-time chore. Take one before cleaning, then refresh every six months.
Why order matters
Export after deleting and those tweets are already absent, so you get a post-cleanup account and no safety net at all. The saddest version I have seen: someone wiped 2014 through 2016, then wanted a conversation with an old friend from that period and found only memory left. That thread carried no privacy risk. A delete-by-year filter swept it up. With a snapshot it would have been a five-second lookup.
Building one that lasts
- Request the archive in X settings, clear password and SMS, then wait. Old accounts often take two or three days.
- Check the downloaded file size, then unzip and verify data/tweets.js opens.
- Copy the ZIP unchanged to a second location, ideally offline.
- Put the date in the filename, like x-archive-2026-08-18.zip.
- Extract anything you specifically want to keep as text or images now, rather than planning to dig through 27,000 files later.
Two copies minimum, one offline. A backup that exists in exactly one place is not a backup, because a dead disk puts you back to nothing.
The part people skip
Within the whole process, this archive is the single most concentrated file of sensitive data you own. It bundles a decade of scattered phone numbers, addresses, and locations into one object. So keep it in an encrypted folder, keep it off shared computers, and never hand it to someone else for analysis. That is also the argument for running any footprint check locally instead of uploading 200MB to a stranger.
Full guide: https://digital-footprint-health.shop/blog/snapshot-archive-before-clean
