How to Export Follower List Instagram: A 2026 Guide
You've got a campaign ready to launch, a carefully defined audience, and one practical problem: the followers you want to analyze are sitting inside Instagram, not inside a spreadsheet. Searching profiles manually is slow, while the phrase export follower list Instagram suggests a simple native download that usually doesn't exist for accounts you don't control.
The workable approach depends on ownership, account privacy, data freshness, and your tolerance for technical maintenance. Instagram's official download can provide follower and following information for your own account, while public-account extraction relies on paginated browser or cloud workflows. Private audiences remain a hard boundary, and any use of collected contact data also requires a legal review.
Table of Contents
- The access checks that matter
- Request the correct scope - Turn JSON into campaign data
- Three approaches, three trade-offs
- What the workflow looks like in practice
- Apply a practical compliance screen
- Diagnose the failure before rerunning
Introduction and Prerequisites
A small agency might begin with a public creator account, hoping to identify relevant partners for a campaign. The team opens the follower panel, scrolls, copies handles, and soon discovers that manual collection produces inconsistent records, misses pagination, and offers little context for prioritization. A founder auditing their own audience faces a different problem, the data is available, but it arrives as a JSON export rather than a ready-made CRM spreadsheet.
Before choosing a method, establish whose account is being exported. Instagram's official download flow is designed for an account owner and can include that account's followers and following information. It isn't a native way to download the follower list of an unrelated account. The Graph API can report follower counts in relevant contexts, but it doesn't provide individual follower usernames, IDs, or profile data for a public account, according to this technical comparison of Instagram follower access.
The access checks that matter
- Account ownership: Confirm whether you control the Instagram account. Ownership determines whether the official Accounts Center export is available.
- Privacy status: Public audiences may be visible to collection workflows, while private-account lists aren't legitimately available unless the viewer already has authorized access.
- Output needs: Decide whether you need usernames only, or structured profile attributes such as biography, follower count, category, verification status, and publicly listed contact information.
- Operational setup: Prepare a spreadsheet or database, a deduplication method, and a clear naming convention for source account, collection date, and campaign segment.
Instagram's legacy public API shut down in stages in 2018, with the final cutoff beginning on July 31, 2018, pushing third-party workflows toward account-owner downloads, browser-based exports, and public-web collection methods (historical API discussion). That history explains why modern export tools often look more like paginated collection systems than one-click platform features.
Practical rule: Decide the lawful use and required fields before collecting anything. It's easier to reduce scope at the start than to clean an oversized, unusable dataset later.
Official Instagram Data Download
For your own account, Instagram's native export is the cleanest starting point. It uses the platform's account-owner permissions, avoids third-party login sharing, and provides follower and following information through Accounts Center. The result is usually JSON, which preserves structured relationship data but requires a small amount of preparation before spreadsheet or CRM use.
Request the correct scope
- Open Instagram settings and enter Accounts Center.
- Select Your information and permissions.
- Choose Export your information.
- Select the relevant Instagram account.
- Choose Followers and following under Connections.
- Set the date range to All time.
- Select JSON as the format when you need structured processing.
- Submit the request and wait for the download notification.
The All time setting matters. A shorter date range returns only recent relationship data, which can make a complete audience graph look incomplete. The delivered ZIP may contain JSON files for followers and following, and the file structure can vary, so inspect every relevant file rather than opening only the first one.
Instagram says the export is typically delivered within hours but can take up to 48 hours, and the account export process is limited to about one request per 14 days per account (Instagram export guide). Treat that limit as a scheduling constraint. Batch your validation questions first, including whether you need followers, following, or both, before requesting the file.
Turn JSON into campaign data
After downloading the ZIP, preserve the original file as a read-only archive. Create a working copy, extract the follower and following JSON files, and map fields into columns such as username, profile URL, timestamp where available, source account, and export date. Remove duplicates by username, but keep the original raw record so you can investigate discrepancies later.
A spreadsheet can handle a modest file after conversion, while larger exports are better processed with a JSON parser or data platform. For a practical explanation of related Instagram download structures, see this guide to downloading Instagram profile data. If you're also reviewing how your organization handles personal data requests, managing your personal information with Inbox Wingman provides useful context around data access and control.
Browser-Based CSV Exports and Workarounds
Browser collection is useful when you're analyzing a public account you don't own and the native download doesn't apply. It's also the most fragile option. The browser displays a list in batches, and a script, extension, or manual process has to request the next page repeatedly while preserving the cursor and avoiding an aggressive request pattern.
Three approaches, three trade-offs
| Method | Where it fits | Main weakness |
|---|---|---|
| Manual CSV scraping | Small, occasional audience checks | Requires hands-on monitoring and cleanup |
| GraphQL request hacks | Technical teams examining browser responses | Interface changes can break the workflow |
| Browser extensions | Marketers who need a simpler setup | Access, permissions, and rate behavior vary by tool |
Manual console scripts can capture visible follower records and append them to a CSV. They're inexpensive and transparent, but they demand careful inspection of the browser session and pagination behavior. A script that records the first response but ignores the continuation cursor will inadvertently produce a partial file.
GraphQL request inspection can reveal how the browser retrieves additional records, but it isn't a stable public contract. Endpoint names, response shapes, and required parameters can change, so this method works better for controlled research than for an unattended production pipeline. Extensions reduce setup effort, yet they may depend on logged-in browser access and can expose your account session to third-party software.
Public-web retrieval commonly returns 25 to 100 followers per request, using cursors such as max_id to continue through the list. Sustained scraping can trigger blocks within 12 to 15 minutes, so workflows need delays, retry logic, and batches of 100 to 500 rather than aggressive parallel fetching (scraping workflow guidance).
A CSV isn't proof of completeness. Store the source profile, collection time, page or cursor markers, and row count so you can tell whether the file ended normally or stopped early.
For marketers turning public profile data into a compliant outreach process, this Instagram email guide from EmailScout adds useful context around publicly listed contact information and responsible handling. Keep the workflow focused on relevant business audiences, not indiscriminate collection.
Cloud Scraper Approach with HarvestMyData
A cloud workflow removes much of the local browser maintenance, but it doesn't remove the underlying constraints. The source still needs to be public, the data still arrives through repeated retrieval, and the resulting list still needs privacy and relevance checks. The advantage is operational separation, the collection job runs in the service environment instead of tying up a staff member's browser session.
A typical setup starts by selecting a public source, such as a follower list, following list, or hashtag audience. The marketer then chooses enrichment fields that support segmentation, including username, full name, biography, follower count, category, website, and contact information when it's publicly available. The output is delivered as a structured CSV rather than a set of copied browser fragments.
What the workflow looks like in practice
- Define the audience: Choose a public account or hashtag connected to the campaign.
- Set the fields: Keep only attributes needed for qualification and outreach.
- Run the job: Let the cloud process retrieve paginated public records.
- Review the CSV: Deduplicate, remove irrelevant profiles, and validate contact fields.
- Route the file: Deliver it to the team's approved workspace or outreach system.
HarvestMyData reports that jobs process roughly 1,000 profiles every two minutes, with enriched CSV email yields averaging 10% and reaching up to 30% for creator niches and mid-sized accounts (HarvestMyData). Those figures are benchmarks from the provider, not a guarantee for every audience. Results depend on how many profiles publish contact information and how narrowly the source audience matches the campaign.
The practical benefit is field-level prioritization. A real estate campaign can separate profiles with a relevant category or website, while a creator partnership campaign can review biographies and public business contact details before outreach. A broad follower dump creates more cleanup, so precise source selection matters more than maximizing rows.
For teams that need a separate reference on structuring lead-file delivery, how to export your leads offers a useful comparison point. The same principle applies here, define ownership, preserve provenance, and export only the fields your campaign can justify using.
Legal and Privacy Considerations
Technical access doesn't establish permission. Instagram's Terms prohibit automated access or collection without prior permission, even when a profile or follower list is publicly visible (legal analysis of Instagram scraping). Public visibility answers whether a person can see the information, not whether a marketer can automatically collect it, combine it, enrich it, and use it for outreach.
GDPR treats names and email addresses as personal data. The same legal analysis explains that GDPR, CCPA, and the EU AI Act can affect processing of publicly visible information, and that organizations need a lawful basis plus appropriate compliance reasoning when handling data connected to people in covered jurisdictions.
Apply a practical compliance screen
- Purpose: Write down the campaign purpose before collecting the audience.
- Minimization: Gather only fields needed for qualification or a clearly defined business process.
- Lawful basis: Identify the basis for processing and document the reasoning, especially for EU residents.
- Transparency: Make sure your privacy information explains relevant collection and outreach practices.
- Suppression: Maintain a reliable opt-out and suppression process.
- Security: Restrict access to the exported file and define retention and deletion rules.
- Platform terms: Review Instagram's current terms before automating collection.
Publicly listed business contact information can still belong to an identifiable individual. That makes Instagram email scraping a data-protection activity, not merely a marketing shortcut. Avoid assuming that a business category or public bio automatically creates consent for unsolicited communication.
A compliance review should also examine the vendor's access model. Login-based tools create account exposure and may create additional contractual risk, while cloud tools still need a legitimate basis for processing and responsible use. This compliance best-practices guide is a useful internal reference when documenting safeguards and campaign decisions.
Compliance checkpoint: If you can't explain why you collected a field, how you'll protect it, and how a person can object to its use, remove that field or pause the campaign.
Troubleshooting Common Issues
A common assumption is that a successful download is a complete download. It isn't. A file can open normally while missing later pages, excluding private profiles, or containing stale records from an earlier run.
Follower retrieval is paginated in chunks of 25 to 100 entries, and private accounts aren't accessible without authorized access (follower API documentation). That creates three distinct failure points: the workflow can stop before the cursor is exhausted, the source can contain inaccessible accounts, or the dataset can be older than the campaign requires.
Diagnose the failure before rerunning
- Broken exports: Reopen the original ZIP, confirm the selected format, and compare the extracted files against the expected folder structure.
- Missing records: Check whether the workflow stored every cursor, then merge all partial CSV files before judging the total.
- Rate blocks: Increase delays, reduce concurrency, and use retry logic. Rotating user agents or proxies may change request distribution, but it doesn't override platform rules.
- Private-account gaps: Mark inaccessible profiles rather than trying to bypass their privacy settings.
- Outdated CSVs: Add the collection date to every file and rerun only when the campaign requires current information.
Never delete partial output after a failed run. Preserve each chunk, identify the last successful cursor, remove duplicates, and resume cautiously if the tool supports continuation. If it doesn't, compare the new file with the old one and retain the union only after checking that records came from the intended source.
A quality check should flag empty usernames, malformed profile URLs, duplicate rows, missing source labels, and contact fields that don't meet your campaign's validation rules. These checks won't make an incomplete export complete, but they'll stop damaged data from reaching your sales or outreach system.
Conclusion and Next Steps
The right method depends on the account and the job. Use Instagram's official JSON download when you own the account and need first-party follower or following data. Use browser-based collection for small, public-account research when you can monitor pagination and accept maintenance. Use a cloud workflow when recurring public-audience exports and enriched CSV delivery justify a more operational setup.
Batch your questions before requesting an official export, select All time when you need full relationship history, and record the source and collection date for every public dataset. Treat pagination as a completeness problem, not a technical detail. Keep private accounts out of the workflow, collect only public fields that serve a defined purpose, and document the legal basis for outreach before importing contacts into a CRM.
Start with a small, relevant public audience, inspect the output manually, and verify that the fields support the campaign. Then scale the workflow only after the data, access method, and compliance checks are working together.
HarvestMyData provides cloud-based exports of public Instagram follower, following, and hashtag audiences, with enriched profile fields and CSV delivery for campaign analysis. If that fits your audience and compliance requirements, visit HarvestMyData to review the workflow and begin with a focused export.
We built HarvestMyData to handle all of this for you.
No proxies, no code, no account needed.