Web Tidy
Blog

How to See Who Unfollowed You on Instagram Using Two Exports

Learn how to compare two dated Instagram follower exports to find possible unfollowers, new followers, and unchanged accounts—and understand what the files cannot prove.

Aug 24, 2026Instagram

Instagram does not provide a historical unfollower list. The most important point is simple: without an older Followers snapshot, you cannot reliably reconstruct everyone who unfollowed in the past. With two dated, comparable snapshots, you can find missing accounts that need review.

A current Followers file shows who appeared during that export. It does not show who was present last week, when an account left, or why. This workflow is a reviewable before-and-after comparison, not a real-time tracker.

Possible removals = Baseline Followers − Current Followers
Possible additions = Current Followers − Baseline Followers
Unchanged accounts = Baseline Followers ∩ Current Followers

Keep the word possible. Deletion, deactivation, renaming, access changes, partial exports, and different row ceilings can all create a missing result.

Disclosure: Web Tidy publishes this guide and develops Instagram Follower Exporter. Product facts were checked against current product materials on August 23, 2026. Other unfollower guides informed the question order and explanation of snapshot comparison, not Web Tidy product claims.

Start with what you already have

What you have nowWhat it can answerNext step
No old file, only a follower countIt cannot identify past departuresSave your first Followers baseline today
One current Followers fileIt shows who appeared now, not who appeared beforeKeep it unchanged and repeat the same export later
Two dated, comparable Followers filesIt can produce missing, new, and unchanged candidatesRun the set comparison and review each important difference
Current Followers and FollowingIt can find current non-followbacks, not historical unfollowsUse the current relationship workflow
Only changes in the total follower countIt shows net movement, not account identitiesBegin saving account-level snapshots

Any product that never observed an older Followers state lacks the baseline needed to recreate a complete historical unfollower list.

Why follower-count change is not enough

A count records only the net result. If seven accounts arrive while nine leave, a profile can move from 1,000 to 998. The -2 does not identify the nine missing accounts or reveal the seven additions.

Account-level snapshots can show which stable identifiers changed between two observed states. They still cannot explain the reason or exact event time.

Unfollowed and does not follow back are different

QuestionFiles requiredResult
Who does not follow me back now?Current Following + current FollowersAccounts you follow that are absent from the current Followers file
Who may have unfollowed since my last check?Older Followers + newer FollowersAccounts present in the older file and missing from the newer file

An account that does not follow you back may never have followed you. Historical change requires Followers at two dates, not Following versus Followers.

Make the two snapshots comparable

Keep these settings consistent:

  • the same Instagram source profile;
  • Followers for both runs;
  • the same row ceiling;
  • the same deduplication setting;
  • completed runs, or clearly recorded partial states and confirmed rows;
  • a date for each export.

Web Tidy currently offers 100, 200, 500, or 1,000 confirmed rows per run. If the profile exceeds the selected ceiling, each file is a bounded subset. A missing row may reflect changing coverage rather than a relationship event.

Step 1: export the baseline Followers snapshot

Open Instagram Follower Exporter:

  1. Use an Instagram session that can access the target profile.
  2. Open the profile and select Followers.
  3. Choose 100, 200, 500, or 1,000 rows.
  4. Choose XLSX or CSV and keep your deduplication setting.
  5. Run the task, check its terminal state and confirmed rows, then download the result.

Use a filename that preserves the profile, date, and ceiling:

instagram-followers-@account-2026-08-23-1000rows.xlsx

Keep the untouched original. Web Tidy creates each snapshot only when you start a task; it does not track the account in the background or create an unfollower event log.

Step 2: export Current Followers later

At the next review date, repeat the same workflow and settings:

instagram-followers-@account-2026-09-23-1000rows.xlsx

Before comparing, confirm that both files use Followers, the same source profile, comparable ceilings and confirmed rows, and distinct collection periods. collectedAt is export normalization time, not the time of a follow or unfollow event.

Step 3: create a stable comparison key

ColumnFieldComparison use
AidPreferred stable identifier when present
BpkPlatform key when returned
CusernameReadable fallback; it can change

Add comparisonKey to both worksheets:

=IF(A2<>"",A2,LOWER(TRIM(C2)))

Prefer id. A username-only difference requires extra review because a rename can look like one account disappearing and another appearing.

Step 4: compare Baseline and Current

Create worksheets named Baseline and Current. If comparisonKey is in column O, add this formula to Baseline:

=IF(COUNTIF(Current!$O:$O,O2)=0,"Missing in current","Still present")

Filter Missing in current to find possible removals.

In Current, use:

=IF(COUNTIF(Baseline!$O:$O,O2)=0,"New in current","Already present")

Filter New in current to find possible additions. Preserve long numeric identifiers as text when importing CSV.

Worked example

These usernames are fictional.

Baseline = @amber, @birch, @coral, @dune, @ember, @fjord
Current  = @amber, @coral, @ember, @fjord, @gale
ResultAccountsInterpretation
Missing in current@birch, @dunePresent before and not matched now; possible removals needing review
New in current@galePresent now and not matched before; possible addition
Still present@amber, @coral, @ember, @fjordMatched in both files

If @birch kept the same id but changed username, it belongs in Still present. If Current is partial, @dune may simply be outside the captured rows. The formulas find candidates; review determines the honest label.

The result is a detection window, not an event time

If the baseline was saved on August 1 at 09:00 and Current on August 8 at 09:00, a missing stable identifier supports only this statement:

The change was observed between the two recorded states.
Detection window = 2026-08-01 09:00 → 2026-08-08 09:00

Do not treat the later file's collectedAt as the moment the account unfollowed. More frequent snapshots shorten the detection window but add runs, files, and review work.

Review each missing candidate

Check these common explanations before using the word unfollower:

  • Username changed: the stable id still appears under a new name.
  • Account deleted or deactivated: disappearance is not an ordinary unfollow.
  • Access changed: privacy, blocking, login, verification, or availability affects what the session can see.
  • One task was partial: coverage ended before the selected ceiling.
  • Ceilings differ: 1,000 baseline rows versus 500 current rows naturally creates missing results.
  • The source changed during collection: relationship lists are live.

For important rows, add a review label such as missing_unverified, renamed_same_id, coverage_mismatch, or unavailable_needs_review. These are your audit columns, not fields added by Web Tidy.

What the files can and cannot prove

Two snapshots can show whether an identifier appeared in two recorded, comparable files. They cannot independently prove:

  • the exact time of an unfollow;
  • why an account disappeared;
  • whether the change was a deliberate action;
  • history before the first snapshot;
  • complete coverage beyond the selected and confirmed rows.

rowIndex is local output order, not a chronological follower rank.

How often to save a snapshot

  • Before and after a campaign: for one bounded review window.
  • Monthly: lower-maintenance routine records.
  • Weekly: a narrower window with more files and review work.
  • Once: creates a baseline; it cannot show change until a second export exists.

Keep a log with snapshot date, source profile, Audience, ceiling, confirmed rows, task state, filename, and notes. Preserve the original CSV/XLSX files separately from any formula-enhanced workbook.

Privacy and product boundaries

Web Tidy uses the Instagram session already open in the browser and creates local CSV/XLSX files. It does not request Chrome's cookies permission, track unfollowers continuously, send notifications, compare snapshots automatically, follow or unfollow accounts, send outreach, find contact details, or bypass private profiles, login, verification, or rate limits.

Frequently asked questions

Can I see who unfollowed before my first export?

Not reliably. The first export creates a baseline for future comparisons.

Can one current export show unfollowers?

No. Historical change requires an older comparable snapshot.

Does collectedAt show the unfollow time?

No. It records export normalization time.

Can two snapshots identify the exact day?

They provide a detection window between the two exports, not the exact Instagram event time.

Can I compare a complete account above 1,000 followers?

No. The current workflow has a 1,000-confirmed-row ceiling per run, so larger accounts produce bounded subsets.

Start with a baseline you can verify

If you have no older file, save a clearly labelled Followers baseline today. Repeat the same settings later, compare stable identifiers, and review every important candidate.

Export your first Followers snapshot

For the general export task, read How to Export Instagram Followers. For current non-followbacks, use Who Doesn't Follow You Back on Instagram.