Web Tidy
Blog

Export Instagram Followers to CSV: A Bounded, Verifiable Workflow

Choose Followers and CSV, run a bounded export, then verify the target, all 14 headers, confirmed rows, and terminal state.

Aug 31, 2026Instagram
On This Page

To export Instagram Followers to CSV, open a target that your current Instagram session can access, then use Instagram Follower Exporter to select Followers, a 100, 200, 500, or 1,000-row ceiling, and CSV. Accept the file only when the target is correct, audience is followers, the first row has all 14 headers in order, data rows equal confirmed rows, and the task is either completed or a confirmed-row partial terminal result.

That proves a bounded set of confirmed rows. It does not prove that you captured every follower on the account.

Disclosure: Web Tidy publishes this guide and develops Instagram Follower Exporter. Product behavior below was checked against its local runtime and artifact writer on August 31, 2026. Three freshly opened public guides informed coverage and structure; their vendor claims were not reused as Web Tidy evidence.

First, fix the direction and evidence boundary

Followers are accounts that follow the target. Following is the opposite direction: accounts the target follows.

This workflow covers one accessible target and one Followers-to-CSV handoff. It does not cover Following, native XLSX, historical unfollower comparison, or common-follower analysis. The exporter does not bypass private access, login, verification challenges, rate limits, or unavailable lists.

The four row choices are ceilings, not completeness settings. collectedAt is the local normalization time, not an exact follow time.

Export Followers to CSV in six steps

  1. In Chrome, open the Instagram profile that your current signed-in session can actually access. Record its username or profile URL.
  2. Open the product and confirm the target. Set Audience to Followers, not Following.
  3. Choose 100, 200, 500, or 1,000 rows. Start with the smallest ceiling that satisfies the task. Keep ID-based deduplication on unless an audit explicitly requires raw duplicates.
  4. Choose CSV and start. Watch discovered rows, confirmed rows, and state; do not treat a visible profile count as a file-row count.
  5. Wait for a terminal result. completed ends this bounded run normally. partial means confirmed rows exist but the run stopped or the source failed. attention is not terminal and cannot be downloaded.
  6. Download an exportable file, then verify its target, direction, 14-column header, confirmed-row count, and terminal state before importing or handing it off.

Completed and partial: the same input, different conclusion

Acceptance asset: UA-S32-GUIDE-COMPLETED-PARTIAL.

The following text-only example holds the anonymous three-row input constant. The ceiling, confirmed rows, header, and usable rows are identical. Only terminal state changes, so the permitted conclusion must change too.

account_id | username   | audience  | source
acct_001   | user_alpha | followers | sample_brand
acct_002   | user_beta  | followers | sample_brand
acct_003   | user_gamma | followers | sample_brand

Completed output:

ceilingconfirmedterminal stateheaderusable rowspermitted conclusion
2003completed / completedexact 14-column order3This bounded run ended normally with 3 confirmed rows; it does not prove that the account has only 3 followers.

Partial output:

ceilingconfirmedterminal stateheaderusable rowspermitted conclusion
2003partial / source_errorexact 14-column order3The 3 confirmed rows are usable with a partial label; do not call the run complete or the list exhaustive.

Verify all 14 CSV columns

CSV and native XLSX use this exact order:

id,pk,username,profileUrl,fullName,profilePicUrl,isVerified,followedByViewer,requestedByViewer,audience,sourceProfile,sourceProfileUrl,collectedAt,rowIndex

Use id as the primary match key. Optional display fields stay blank when the source does not return them; blank relationship flags do not automatically mean No. audience must be followers, while sourceProfile and sourceProfileUrl must identify the intended target. rowIndex is final local order after deduplication, not an Instagram rank.

Recovery branch for every stop state

StateInspect firstIs the current result usable?Rerun condition
login requiredCan the current tab still open the list manually?attention is not terminal; no downloadComplete a real login, confirm access, then explicitly start a new bounded run.
challengeIs Instagram asking for human verification?No; the exporter does not bypass itComplete the challenge on Instagram, then rerun manually.
rate limitDid the source return a limit/429 and stop requests?No automatic recovery is promisedWait, confirm access manually, then start a smaller run if still needed.
privateIs this session authorized to view the list?No private-access bypassRerun only if the session later receives normal access.
unavailableCan the target and list open in the current tab?No downloadConfirm a restored target and URL before a new run.
partial / stoppedConfirmed rows, reason, and the 14-column fileYes when confirmed rows are greater than zero, with a partial labelStart a new run only if the task needs more rows and access remains valid.
partial / source_errorConfirmed rows, failure point, and file-row countYes when confirmed rows are greater than zero, with a partial labelRerun explicitly after recovery; the task will not continue in the background.

Seven checks before you use the file

  1. The suffix is .csv, and the first line exactly matches the 14 names and order above.
  2. Every audience value is followers.
  3. sourceProfile and sourceProfileUrl identify the intended target.
  4. Data rows, excluding the header, equal confirmed rows and do not exceed the selected ceiling.
  5. The handoff records the true completed or partial state; a partial file also retains its reason.
  6. A sample of id, username, and profileUrl agrees within each row. Do not use fullName as a unique key.
  7. Import id, pk, and username as text in Excel or Sheets so long identifiers are not rewritten.

If the recipient requires a native workbook, select XLSX at task creation. Renaming a .csv file to .xlsx does not convert it.

Limits that remain after a clean verification

  • completed means the selected 100/200/500/1,000-row run ended, not that a large account was exhaustively covered.
  • Deduplication can make confirmed rows lower than discovered rows. Confirmed rows are the file acceptance count.
  • collectedAt is not follow time, and rowIndex is not follow order or ranking.
  • Only transient network errors and HTTP 5xx responses get bounded retries, up to three attempts per request. There is no unlimited retry loop.
  • Local History holds at most 20 terminal runs for review and re-download. It is not scheduled or background monitoring.
  • The product does not read a Meta account archive, export JSON, enrich email or phone data, automate follows or messages, or bypass access controls.

For a field-by-field reference, see the 14-column Instagram Follower Exporter dictionary. If the handoff requires a native workbook, use the Followers-to-Excel workflow. For the opposite direction, follow the Following-list CSV workflow.

After choosing Followers, a ceiling, and CSV, return to Instagram Follower Exporter and use this page as the acceptance checklist.

Frequently asked questions

Can Excel open the CSV?

Yes, but it remains a text file. Import long IDs and usernames as text. Choose XLSX from the start when a native workbook is required.

Does completed mean a complete Followers list?

No. It means this bounded run ended normally and remains constrained by the ceiling, current access, deduplication, and list changes.

Is a partial file always unusable?

No. A partial run with confirmed rows can export those rows, but the handoff must retain the partial label and reason.

Can collectedAt reveal the exact follow time?

No. It records local normalization time, not when the account followed the target.

Can the exporter bypass a private profile or challenge?

No. It only handles lists the current session can access normally.

Can one CSV identify unfollowers?

No. One file is a bounded current snapshot. Change detection requires at least two comparable Followers snapshots from different dates.

Does History monitor changes automatically?

No. It retains up to 20 terminal tasks locally and does not schedule background collection.