Five questions your Instagram export will never answer

There is a family of questions that send people straight to their archive with the
search box open, and every one of them comes back empty. Who actually looked at my
profile. Who blocked me. Who watched my story. How my posts really did. Whether anyone
screenshotted the thing I sent. The export is comprehensive about your account and it
is silent about all five — and the silence is not a gap in the download, a setting you
forgot to tick, or a sign you should request the export again in a different format.

They fail for one shared structural reason, and this post is about that reason as much
as the questions: an export contains your account's records — things your account
holds, did, or was sent. It does not contain the platform's observations of you —
what other people did while leaving no trace in your data. Passive attention is the
second kind, and none of these five questions has an answer of the first kind. Every
section below is that one distinction, applied five times, plus the nearest thing the
file honestly offers.

1. 30swhy all five fail the same way.
2. 6mineach question, what the export does show, and where the partial answer lives.
3. ongoing — how to tell a new "is this in the export?" question from the same family.

1. Who viewed my profile

The export has no profile-view records because your account was never given any to
hold. Viewing a profile is a passive action by another person: it creates no content,
sends no message, and writes nothing into your data — so there is nothing for a request
to carry. The finding-people post answers the same question at more length and reaches
the same floor.¹

The substitutes are worth understanding precisely, because each one is a different
thing wearing the same costume:

• Interactions with your content — likes, comments, follows, replies — are in the

  export. They are actions, not views: someone who looked and left nothing behind is
  indistinguishable from someone who never arrived, and no analysis of your own files
  can tell those apart.

• Reach and impression numbers are platform-side analytics of the sort professional

  dashboards show. They were never part of a personal archive request, and their
  absence is not a setting.

• Third-party "who viewed your profile" tools answer this question only by

  inventing it. There is no data for them to read — your export does not contain the
  answer, so neither does any copy of it.

The honest limit, stated once for the whole question: you can know who engaged, and
you cannot know who looked. The archive draws that line correctly by keeping the first
and omitting the second.

Inference methods deserve the same direct treatment, because they fill the vacuum
immediately. Ranking "likely viewers" by who engaged most, by who followed you
recently, or by who appears in mutual lists is a real analysis of real records — of
engagement. Presenting its output as a viewer list is a category error dressed as a
feature: the inputs contain no view events, so the output cannot contain any either,
no matter how the ranking is dressed. A tool that answers this question honestly says
what the file says — these people interacted — and declines to convert interaction
into attention. That refusal is the same one this site makes in its own editorial
rules: where the file is silent, the honest output is silence.

2. Who blocked me

Being blocked is another account's decision, stored on their side of the platform's
records — and the export can only request what belongs to you. The person who blocked
you has a block list; you have no record that you are on it. This is the same
structural reason as the first question, one step less obvious: a block you issued
is an action you took, so your own list belongs to your account's records — and the
relationships post covers what happens when even that list is thin or absent in a
given export.²

What the archive does show of blocking is bounded in both directions:

• Your own blocks appear in the privacy section when the export carries them —

  an action you took, therefore yours. Where the list is short or missing entirely,
  that is a property of what the account's records held at request time, not a
  request you made wrongly.

• Their blocks of you appear nowhere, and cannot: your request reaches your

  account's data, and your account is not told when someone adds you to a list.

The asymmetry is stable across requests. Asking again, changing the date range, or
switching format moves nothing, because the data on the other side of it is not part
of the corpus being read. This is also why "block detection" tools cannot be reading
exports to do it — they are reading what the follower comparison above reads, and
naming the inference as if it were the record.

There is one inferential substitute people reach for — absence from your followers, or
a conversation that went cold — and it deserves its usual treatment: an unfollow you
can see, a block you cannot, and a followed-by-someone-who-once-commented being gone
proves nothing on its own. The archive supports statements about what it records; it
does not support detective conclusions about why a record changed.

The comparing two exports post supplies the
strongest version of the substitute and shows its ceiling: two snapshots of your
follower list months apart name exactly who
left the list — a fact about membership, not about mechanism. The departing account's
motivation (block, unfollow, deactivation, deletion) is recorded on their side or
nowhere, and the two exports cannot see across that line. The honest sentence this
combination supports is "these accounts are no longer in my followers as of this
date" — full stop, no verb about blocking after it.

3. Who viewed my story

Two separate absences stack here, and separating them is the whole answer:

1. The live story is mostly not in the export. The requesting post's FAQ draws the

   line carefully: a story that expired before the export context is not part of the
   persistent record — only stories still saved in your archive or in a Highlight can
   appear.³ So the ordinary case is an export with little or no story folder
   at all, which people discover by searching for it.

2. The viewer list is never in it, even then. Who watched is the second absence:

   that record has a persistence of about 48 hours on the platform's side and is not
   part of a personal archive in any format. A story can be present and its audience
   still absent — the container and the contents are different questions, and only the
   first one has an export-side answer.

So the question fails twice over — the container is absent and the contents would be
absent anyway. What remains in the activity records is your side of story life: the
stories you interacted with, the replies you sent, the reactions you made, laid out in
the activity post's account of that section. Someone else watching your story leaves
nothing in your files; someone else replying to it leaves a message, and messages are
in the export like any other.

4. How my posts performed

"Performance" is a metrics concept — reach, impressions, watch time, follower growth
over a window — and those numbers live in the platform's analytics products, not in a
personal data archive. The export gives you your posts, their captions, their media,
their dates and (where the record has them) the interactions attached to them; it does
not give you a scorecard of how they travelled.⁴

The distinction is worth one careful paragraph, because it is the difference between
counting and being told:

• Counting your own actions is possible. How many comments you left last year,

  which accounts you engaged with most, when your posting rhythm changed — those are
  your records, and the activity section carries them. The activity post walks that
  section in full.

• Counting reactions to your content depends on what the record kept. Where

  comments or reactions are present they are present as events; where an export
  carries none for a given post, that post's engagement story is not partially known —
  it is unknown, and the honest rendering draws a gap rather than a zero.

• Platform-side totals were never yours to request. Views of a post, its reach, its

  saves-graph — those are the platform measuring your content for its own purposes,
  and a personal export request does not carry them.

Any tool that displays a confident lifetime engagement number for an account whose
export never contained one is doing arithmetic on invented inputs. The question people
are usually really asking — "did anyone care" — is answerable from the records that
exist, as a shape rather than a scorecard: who came back, who replied, which periods
were dense. That reading is in the activity and relationships posts; this one is about
why the dashboard version of the question has no export-side answer.

Two further distinctions keep the counting honest. First, a total and a record are
different objects: the export can contain the events from which you count a total —
comments you made per month, for instance — and still contain no total anywhere,
because totals were computed by the platform at display time and never written into
your archive. Second, absence of an event is not a zero: a post whose reactions are
not in the records did not necessarily get none, and rendering its engagement as 0
invents a measurement the file never made. The half-life post's treatment of null
versus zero is exactly this rule applied to a neighbouring field, and it applies here
with the same force: draw the gap, label the gap, do not fill it.

5. Whether anyone screenshotted it

The purest member of the family: a screenshot is an action on someone else's device
that changes nothing about either account — no field anywhere receives it, yours
especially. The export cannot show screenshot events because none are recorded for it
to show, and the same absence that defeats your request defeats the folklore around
it: the archive contains no detection log, no notification history of captures, and no
per-message flags.

What makes this question worth its own section is that it fails differently from the
other four. Profile views and blocks are platform records that exist somewhere else;
screenshots may not be records anywhere at all. The honest answer is therefore two
levels deep: your export does not contain them, and nothing you can request does. The
closest real things are also in the export and also different — a forwarded or
re-shared message leaves message records, a downloaded media item is a file on a
device, and a reply quoting your post is a conversation. Capture without any of those
leaves silence, and silence is what the file honestly reports.

It is also the question where folklore does the most work, because the absence leaves
room for a claim in either direction: some platforms have had notification features
for captures in specific formats, and rumour hardens them into universal rules. The
export can settle none of it, and this post does not try: what it can say is only what
the file contains — no capture events, no flags, no indicator fields — and what you
do with that beyond the file is a question about the platform, not about your archive.
A reader who wants the platform-side answer should read the platform's current
documentation, because that surface changes and the export does not.

The test for any future question

The five are examples of one class, which means the class itself is the useful thing
to learn. When a new "is this in my export?" question shows up, three moves classify
it before you open the file:

1. Ask whose record it would be. "What did I post, say, follow, send, delete?" —

   your actions, your records, almost certainly in scope. "Who looked, watched,
   left, or thought?" — their behaviour, your archive almost certainly silent.

2. Ask when it would have been written. Records created by an action of yours get

   written when you act. Passive observations are written into the platform's own
   telemetry — a corpus no personal request reads from — or nowhere at all.

3. Ask what the partial substitute is. Nearly every absent question has a

   neighbouring present one: views → interactions, blocks → membership, performance →
   your own action counts, capture → the messages that do exist. Knowing the
   substitute turns a dead end into a redirect.

Run the three on each of this post's five and you get the table below every time —
which is the point. The questions change; the class does not. And the fourth rule,
which is really the first one restated: if a tool answers one of these questions
confidently, find out which records it read. If the answer is "your export," check
whether the field exists in it. It does not.

The five, and where each partial answer lives

Where this was checked

¹: The profile-view question and its dead ends are treated at length in the
finding-people post's FAQ; this post adds only the structural reason — passive actions
never enter your account's records.
²: The block list's behaviour inside exports, including exports where it is
empty or absent, is covered in the relationships post's FAQ — read that before treating
a short list as a wrong request.
³: The 24-hour formats' behaviour inside exports — expired stories absent,
saved or Highlighted stories possibly present, and the story viewer list (about 48
hours of persistence) never part of any archive — is covered in the requesting post's
FAQ on stories.
⁴: The activity section's exact contents, including which story and
reaction records exist and in what direction, are the activity post's subject.