Before you delete or deactivate: the export checklist

People delete their Instagram accounts in an evening, with the decision already made
three weeks earlier, and discover in the morning that the one thing they wanted — the
record of what those years looked like — was requestable only while the account still
existed. The export tool works on a living account. After deletion there is no account
to describe, no tool that can reach it, and no second window. Whatever the archive did
not contain by then, it will never contain.

This post is the last-days procedure, and nothing else. How to scope a request lives in
the requesting post, how the two deadlines behave lives in the waiting post, and what
each folder means lives in the reading post. What follows is the order of operations
for leaving: what to run first, what to verify before you trust it, and the five
consequences of deletion that people reliably meet afterwards.

1. 1minthe order: request, verify, then decide.
2. 4mindeactivate versus delete, and the five post-deletion surprises.
3. ongoing — the checklist to keep open on the second screen while you do it.

The order of the last days

The procedure has four moves, and their order is the entire content of this post:

1. Request the complete export, and let it finish.
2. Verify the archive opens and contains the sections you care about.
3. Decide between deactivation and deletion with the five facts below in hand.
4. Act — delete or deactivate, knowing what the tool will no longer do afterwards.

Steps two and three are the ones people skip, and they are the two that cannot be
repaired later. A failed export request discovered after deletion is not a bug report;
it is an absence. A deletion whose Threads consequences were never read is not a
surprise; it is the documented default. If you are reading this the night before you
intend to leave, budget the evening for steps one and two and treat step four as
tomorrow's decision, not tonight's.

The order also exists because each step buys information the next one needs. Requesting
first tells you how big your archive actually is, which tells you whether verification
will take five minutes or an hour — that number changes nothing about deleting, but it
changes when you should start. Verifying second tells you whether the account's export
tool even produces a complete archive for your history — the half-empty-archive
stories in the reading post are almost all people who found out during step three
instead of step two. And knowing the five facts below before step four is what makes
deletion a decision rather than a click you take because the page was already open.

Step one: request the complete export

The requesting post owns the scope decisions — the format, the date range, the sections
— and this post will not re-teach them. What matters here is only the sequence: the
request must exist, complete, and be downloaded while the account can still answer
it. Three timing facts turn the checklist into a schedule:

• The build can take days. Meta publishes one number for preparation and delivery —

  up to 30 days for the email to arrive, with plenty of accounts crossing weeks of that
  range — so a "delete tonight" plan starts with an export request made well before
  tonight. The full clock behaviour is in how long an export actually takes.

• The link dies about four days after it arrives. The download window is short and

  non-renewable; the moment the mail lands is the moment the download is owed. See
  the expired-link post if you have
  already learned this the hard way.

• One request at a time. If you have already fired a request this week, do not fire

  a second one because the deletion date is close — stack-jobs impatience is
  the pending post's whole subject, and
  the days before an account deletion are exactly when people fall into it.

A closing note on scope under deadline: the complete request is still the right request.
Trimming the scope to "finish faster" before a deletion date trades the only copy of
your archive for an afternoon — and the sections people trim first (messages, the old
years, the media) are the ones the deleting account will never be able to re-describe
anyway.

Step two: verify before you trust it

"The export completed" and "I have my archive" are different claims, and deletion makes
the second one permanent. The verification is small enough to do the same evening the
email arrives:

• [ ] The ZIP extracted without errors — a failed unzip is covered in

  why your export won't open.

• [ ] The index.html opens and shows the sections you expect.
• [ ] A JSON section you care about exists and parses — open one .json from

  messages/ or connections/ in any text editor and see braces, not an error.

• [ ] The date range you requested is actually represented — the oldest files are not

  from last year.

• [ ] The copy is in at least two places — your machine, and a drive or second folder

  that is not the same failing disk.

That last box is the one that matters most in this context: you are about to make the
account unable to produce a second export, which makes the existing copy a
single point of failure by your own choice. The whole reading post is the deeper
version of this check — including why an archive that looks half-empty often is not —
but the five boxes above are the floor for someone on a deletion schedule.

Verification is also the cheapest step in the entire procedure, which is what makes
skipping it hard to justify. The check takes minutes and requires nothing but the files
you were going to download anyway; the failure it catches — an archive that is
unreadable, incomplete, or sitting on one dying drive, discovered after the account is
gone — costs the entire record. There is no third outcome to plan for: the archive
either opens on the night you got it, or it does not, and only one of those answers can
still be acted on.

Deactivate or delete: different decisions

Both start from the same place — the account settings — and then they diverge in the
one way that matters: reversibility.

The deactivation row is why deactivation is the right move for anyone whose decision is
still ninety percent made: it costs nothing to undo and takes seconds to apply. The
deletion row is why deletion deserves the checklist — because everything below the
grace period line happens whether or not the account's owner had read the fine print.

A practical test for which row you are actually on: if imagining the account restored
next month produces relief rather than disappointment, deactivate. If imagining it
restored produces the feeling of starting the argument with yourself all over again,
delete — and then spend the thirty seconds this table has bought you reading the five
consequences below before you confirm. Both answers are defensible; the only bad one is
arriving at the confirmation dialog without having distinguished the two.

The grace itself is the one soft landing deletion offers: Meta's help describes a
30-day window during which simply logging in cancels the deletion. That window is also
the last moment the export tool can describe your account for you — after it closes,
the account's data is being removed and there is nothing left to build an archive from.
Treat the grace as a second verification opportunity, not as a safety net: a person who
cancels deletion on day 29 to "get one more export" starts the whole waiting cycle from
zero, with the same clocks as always.

The five things people learn after deleting

The deletion screen is short. The consequences list is not, and none of these five is a
bug — each is the documented shape of what deleting an Instagram account does:

1. Your Threads profile goes with it. Threads is attached to the Instagram account:

   deactivating or deleting one deactivates or deletes the linked other. People who
   enjoyed Threads as a separate habit discover the coupling only after the fact, which
   is worth reading while both accounts still exist.¹

2. Your username may not come back. The handle that identifies you is released

   when the account is — available for reuse by anyone, including someone who wants it,
   and not guaranteed to be reassignable to you even if you return. If the username
   itself is the thing you would miss, that is an argument for deactivation instead.

3. Meta's copies can outlive the deletion by months. Deletion begins a removal

   process; it is not an erasure event. Meta's own help notes that information may be
   retained for up to 90 days after deletion in backup copies — separate from the
   30-day grace that precedes it.² Neither window is something you can
   see into, which is the honest limit of this whole section.

4. Your messages stay where you sent them. Deleted account or not, the DMs already

   sitting in other people's inboxes remain theirs, and your side of the conversation
   keeps rendering you as the placeholder label an absent account gets — the same
   Instagram User label the messages post documents.³ An export does
   not change that; it only gives you a copy while the account existed. This is the
   consequence people read as a surprise and is in fact the plainest thing on the
   list: an inbox is the recipient's copy, and deletion operations on the sender's
   account have never reached into someone else's storage. Whatever you would not want
   still sitting in a thread a year from now was never yours to un-send — the account
   leaving does not renegotiate it.

5. Deactivation reverses, deletion mostly does not. After the grace period, the

   account is gone in the sense that matters: no login restores it, no export describes
   it, no support ticket reconstructs it. The only durable copy of the account that
   survives on your side is the one from step two.

Four of these five are facts you can hand yourself before deleting; the fifth is why
the procedure exists at all. What none of them can do is add anything to the archive —
deletion subtracts, from the account and from every future request alike.

What the export cannot give you once you have left

The honest boundary of this whole procedure: the export is a photograph taken while the
account was alive, and afterwards nothing updates it. Activity between the request and
the deletion — the last days of stories, the messages you sent that evening, the profile
edits you made while deciding — is in the account, not in the archive, if the request
completed before them. And a deleted account takes its future with it: the export will
never show what would have happened, only what was.

There is a second, narrower limit worth naming because it generates support threads: an
export cannot serve as proof-of-life for the account itself. It proves what the account
held on the day it was built. If you need identity, history or custody evidence after
deletion, the archive is the evidence — but only for its own snapshot date, and only
for you.

The last-days checklist

Keep this open beside the account settings page:

• [ ] Export requested, in JSON, complete scope — before anything irreversible.
• [ ] Downloaded in the same sitting the email arrived (four-day window).
• [ ] Unpacked, opened, JSON spot-checked, copied to a second location.
• [ ] Read what your linked Threads profile will do — deactivate or delete with you.
• [ ] Decided whether your username is a reason to deactivate instead.
• [ ] Accepted the 90-day backup horizon as something you cannot inspect.
• [ ] Accepted that your DMs remain in recipients' inboxes, labelled Instagram User.
• [ ] If deleting: know that logging in within 30 days cancels it, and that the export

  tool belongs to that same window.

• [ ] If deactivating: know that logging in reverses it, and that your archive does not

  need to be re-taken — unless the account changed in between.

Most of the list is done the evening you request the export. The rest is reading you do
with the settings page still unopened, which is exactly the position you want to be in
when the last box gets ticked. If the list stalls on the export boxes — the request is
out but the download has not landed — that is the two clocks from the waiting post doing
their job, and the correct move is to wait inside the window rather than to delete and
hope the email arrives to an account that still exists.

Where this was checked

¹: Meta/Threads help documentation on account linking: Threads profiles
are tied to an Instagram account, so deactivating or deleting the Instagram account
deactivates or deletes the linked Threads profile.
²: Meta Help Centre, account deletion documentation: the 30-day window
in which logging in cancels the deletion, and the separate statement that information
may be retained for up to 90 days after deletion in backup copies.
³: The rendering of an absent sender in DM records is documented in the
messages post on this site — label, timestamp and body survive; only the identity is
gone.