Instagram Followers List Scraper & Instagram Following Scraper
Pricing
from $0.50 / 1,000 followers
Instagram Followers List Scraper & Instagram Following Scraper
From $0.50 per 1,000 followers, plus $0.05 profile reads on accounts read fresh. Followers and following of any public Instagram account, by handle or profile URL: handle, name, user ID, verified and private flags. No login. You get up to your result limit; a row we cannot deliver is never charged.
Pricing
from $0.50 / 1,000 followers
Rating
0.0
(0)
Developer
Steadyfetch Team
Maintained by CommunityActor stats
0
Bookmarked
205
Total users
68
Monthly active users
1.3 hours
Issues response
a day ago
Last modified
Categories
Features
Share
Instagram Followers Scraper & Instagram Following Scraper
Paste the handles you care about and get the people who follow them, the people they follow, or both: handle, full name, user id, profile URL, profile picture, verified and private flags, and the position each one held in the list. No login, no cookies, no proxy to configure. You get up to your result limit — ask for 500 and you get up to 500, per account and per list. A list that ends sooner delivers fewer, never charged for the rest, and a row we could not deliver is never charged. Nothing is charged for starting a run; each profile a run reads fresh carries one $0.05 profile read. With "Include rows you already have" on, each account a run reads pays one $0.05 profile read per started 100 of its rows you already have that the run hands back, and at least one.
Using an AI agent? Pin this actor in Apify's MCP server with one link: https://mcp.apify.com?tools=steadyfetch/instagram-followers-scraper
- Actor id:
steadyfetch/instagram-followers-scraper - Input:
{ "usernames": ["nasa"], "mode": "followers", "resultsLimit": 500 }—usernamesis the one field you have to set. - Cap the bill: set
maxTotalChargeUsdon the run (a run option, not Actor input), e.g.0.50— the run stops cleanly when it reaches it. - Price: from $0.50 per 1,000 rows on Gold and above ($0.0005 a row), $2.00 per 1,000 on the Apify free plan — the same price for a followers row and a following row. Plus a $0.05 profile read for each profile a run reads fresh — with Include rows you already have on, one per started 100 of that profile's rows you already have that the run hands back (at least one per profile); a row we could not deliver is never charged. Full table below.
- How often it changes: follower lists churn daily on an active account, so a weekly or daily schedule is where this earns its keep — the rows you already have are skipped rather than charged again, so a schedule pays for what changed plus one $0.05 read per profile.
- Run it on a schedule: save your input as a Task (Actor page → Save as a new task), then add that task to an Apify Schedule (Console → Schedules → Create) with a cron such as
0 7 * * *for daily or0 7 * * 1for weekly. Each run rereads the same handles, and rows this account bought in the last 90 days are skipped and not charged.
Unofficial. Not affiliated with, endorsed by, or sponsored by Instagram or Meta Platforms, Inc.
What you get
One row per person, in the order the list served them:
| Column | What it holds |
|---|---|
username · fullName · userId | who they are, and Instagram's own numeric id |
profileUrl · profilePicUrl | their profile link, and their picture |
isPrivate · isVerified · accountBadges | their account flags, as Instagram reports them |
followerOf | this person follows the named account (a followers run) |
followingOf | the named account follows this person (a following run) |
direction · seedUsername · seedUserId · listPosition | which list this row came from, for which of your handles, and where it sat in it |
seedFollowerCount · seedFollowingCount | how many followers and following the handle you asked about has, as Instagram showed them when this run read it, on every follower row of that handle (a run that delivers no row for it shows no count), so a schedule's runs chart the account over time; null on the built-in sample, or when the run got no count |
source · input · sourceIndex · scrapedAt | always instagram, the exact value you typed, its place in your list, and when it was read |
repeat · charged · status · retryable · statusReason | whether your account already had this row, whether it was billed, and why |
followerOf and followingOf are not the same fact, and exactly one of them is filled on any row. A run in both mode returns both lists, and a person who appears in each gets two rows — that is two different facts, and the mutual-follow check people usually want is a join on those two columns.
What a row looks like
One delivered row from a real run — the following list of nasa, 2026-09-11. Every person on the list is one follower charge, and direction plus listPosition say which list the row came from and where it sat in it. Profile pictures are signed and time-limited by Instagram, so they are shown here as placeholders. The two seed counts are the ones Instagram showed for nasa that day.
{"userId": "3443079229","username": "jaxajp","fullName": "JAXA(宇宙航空研究開発機構)","profileUrl": "https://www.instagram.com/jaxajp/","profilePicUrl": "https://…","isPrivate": false,"isVerified": true,"accountBadges": [],"followerOf": null,"followingOf": "nasa","direction": "following","seedUsername": "nasa","seedUserId": "528817151","seedFollowerCount": 104378996,"seedFollowingCount": 91,"listPosition": 3,"source": "instagram","input": "nasa","sourceIndex": 0,"scrapedAt": "2026-09-11T10:25:49.238Z","repeat": false,"charged": true,"status": "delivered","retryable": false,"statusReason": null,"#k": "following:nasa:3443079229","#ce": {"follower":1},"#ask": {"delivered":1}}
Price
Two charged events: follower, which lands only on a row that was actually delivered, and profile-read, $0.05 per profile a run reads fresh — once, or with Include rows you already have on, one per started 100 of that profile's rows you already have that the run hands back (at least one). The row price covers both directions at the same price — a row from the followers list and a row from the following list cost the same, because they cost us the same.
| Apify plan | Per row | Per 1,000 rows |
|---|---|---|
| Free plan | $0.002 | $2.00 |
| Bronze | $0.0012 | $1.20 |
| Silver | $0.00075 | $0.75 |
| Gold and above | $0.0005 | $0.50 per 1,000 |
Platform usage is included in that price — there is no separate compute bill on top, no start fee, and no charge for "details" beyond the one $0.05 profile read: every column below is in the row at that one price. Set maxTotalChargeUsd on the run and it is a hard ceiling: the run stops cleanly under it and the last row says what is left.
The profile read, $0.05 on every Apify plan. Each profile a run reads fresh carries one profile read, new followers or not: a re-run that finds nothing new still pays it, because Instagram is read again to find that out. In both mode the two lists of one account are one profile read. With Include rows you already have on, it is one profile read per started 100 of the rows you already have that the run hands back (250 handed back is 3). It is never charged on the built-in sample, a private or missing account, a list your account's memory already knows has ended (no page of it is read), or an account the Apify free plan's daily limit held back. So a schedule costs one profile read per account per run, plus any new followers — with Include rows you already have on, one per started 100 of each account's rows you already have that the run hands back (at least one per account). Each profile read lands on a row of its own (status: "profile_read") naming the account, the count and why, and the run's last row counts them in chargedEvents. If what is left of your maximum cost per run cannot pay an account's profile read in full, that account is not read at all: its row says so and nothing is charged for it, and the run page counts the accounts not read and names the maximum that reads them all. The same holds when what is left would pay the profile read but not one new follower after it, unless "Include rows you already have" is on and you asked for more rows on that list than you already have there. A profile read that is made is always charged in full.
On the Apify free plan this actor makes at most 80 Instagram reads per account in any 24 hours (one read looks up an account or reads one page of a list: 25 rows of a followers list, or up to about 200 of a following list, so that is about 2,000 followers, or many more rows of a following list), and accounts on the free plan share one daily allowance on this actor. Past either, the run keeps everything it already delivered, ships one uncharged row saying when it resets (UTC), and charges nothing past it. Paid Apify plans carry no daily allowance.
Honest rows: what "not charged" actually means
Every run closes its own books. A row that was asked for and not delivered leaves an uncharged row of its own saying which of ten things happened, in plain words, and none of them is billed:
account_not_found— Instagram has no account at that handle. Told only when Instagram's own account lookup says so in as many words, or when its answer gave no reason and a second look agreed — never guessed from an empty list.private_account— the account is private, so Instagram publishes no follower list for it and nobody can read one without being approved by the account. Answered from the account lookup, before a single list read is spent.capped_by_instagram— the account is large enough that Instagram stops showing its list. See the section below; this is the one every competing actor leaves out.no_list— the list ran out before your limit did, not a limit on the run. When it ends at about the count the account itself reports, that is the whole list Instagram publishes for the account. When this run read it from its top and it ends well short of that count, the row names both numbers, and where the run can confirm that Instagram itself shows only about 50 of an account's followers, the row says so and that running again will not bring the rest. The one exception is a row that says some of the list did not come back on this run: then a run after a day, or sooner if that count changes by more than a couple of percent, reads it again.try_again— the read did not go through; or the account did not come back when it was looked up and nothing confirmed it gone, so its list was not read on this run and stays open for the next one; or, on a continued run, the list changed so much around the point your resume cursor stopped at that it could not be found. It says nothing about the account, and the row says when a re-run is the fix.source_refused— Instagram refused that read outright, and it refuses it the same way every time, so a re-run cannot change it. Check the handle in a browser; if it works there, say so on the Issues tab.unsupported_shape— Instagram answered in a shape this actor does not read yet. That is on us, not on the account — tell us on the Issues tab which handle it was and support for it will be added.limit_reached— this run reached its limit before it could finish, so it stopped rather than collecting more. Usually that is the limit for one run, and a new run continues, skipping rows you already have; rarely this actor is paused until the start of next month. The row says which.stopped_at_limit— one of your own limits, the run clock, the Apify free plan's daily allowance (see Price), or one of this actor's own reading bounds stopped it first: it stops after three pages in a row that held nothing but rows you already have (after the first page, when an earlier run already found the same and the list's published count has not risen since), and it reads at most 2,200 pages for any one list. The row names which one, so you raise the right setting. When a list is left unfinished this way, the run's last row carries aresumeCursor: pass that object back in Continue a stopped run, with the same usernames, and the next run carries on from the page each list stopped on; the lists that run finished are not read again.user_input— a handle, a list value or a setting could not be used. The row names the field and the fix, and the rest of your handles still run.
The last row of every run is a receipt: delivered, asked for, what was skipped, what stopped it, and the charged-event totals, so your invoice reconciles from the dataset itself. A time limit ends the collecting, never the delivering — rows already in hand are always written out.
Instagram caps very large accounts, and this actor says so
Instagram limits how much of a very large account's follower list it will show to anyone. No tool can go past it, however it is priced.
Measured live on 2026-09-11: nasa, with 104,378,996 followers, returned 49 follower rows and then stopped. An account with 19 followers returns all 19. The two look identical on the wire, so this actor decides the difference against the account's own stated follower count rather than guessing from a short list — and only an account with 100,000 followers or more is ever told it is over that limit. A smaller account whose list ends early gets a plain end-of-list row instead, naming how many rows Instagram listed and how many the account reports when the run read the list from its top — or, where the run can confirm that Instagram itself shows only about 50 of a smaller account's followers, saying so — and every list that ends before your ask also says so in the run log.
When it happens you get a capped_by_instagram row naming how many rows were reached and how many the account reports having — and the rows past the cap are not charged. This is Instagram's own limit, not a setting on your run, and raising your result limit will not move it. The "following" list is not capped this way in our measurements: nasa's 91 following walked to the end in four pages.
When the first page of an account's followers does not come through in a run, the run reads it again before it gives that account a retry row, and when that first page is Instagram's sample of a very large account and you asked for more, a second sample is drawn and only followers new to you are added from it, charged the same way.
So: this actor is at its best on the accounts whose lists are actually reachable — small and mid-size accounts, and the full "following" list of accounts of any size.
Settings
- Usernames — one handle or profile URL per line:
nasa,@nasa, or the profile URL you copied out of the address bar. A pasted block of links is split on link boundaries, and a value that cannot be used becomes one uncharged row naming the fix while the rest of your handles still run. - Which list (
mode) —followers,followingorboth. Defaultfollowers. - Max results per account (
resultsLimit) — per account and per list, default 100. Three handles inbothmode at 100 each asks for 600 rows, and every one of those 600 is either delivered or named by a row of its own. This actor delivers up to 50,000 rows per list; ask for more and the run still starts, continues at 50,000, and leaves one uncharged row saying what you asked for and what bound it. - Include rows you already have (
includeSeen) — hand back the rows your account already holds instead of skipping them. The rows stay uncharged, markedrepeat: true; each account the run reads pays one $0.05 profile read per started 100 of them, and at least one. The list is read in full from Instagram on every run, so it is the list as it stands today: rows you already have come back marked repeat and uncharged, and someone who has left is not handed back. - Report who left (
reportLeft) — with the option above on, once a list has been read to its end the run adds one uncharged row (status: "left") for each account an earlier run delivered to you from that list that has not been on it for the last two complete reads, with its user ID and when you first got it. Off by default. - Skip rows in this dataset (
resumeFromDatasetId) — carry the same memory across Apify accounts, or resume a chain, by naming a dataset whose rows should not be collected again. - Continue a stopped run (
resumeCursor) — paste theresumeCursorobject from a previous run's last row to carry on from the page each list stopped on; the lists that run finished are not read again. It positions the lists you ask for on this run, so keep the same usernames beside it; leave it empty to start from the top. A chain of runs begun before version 1.0.85 carries on as it did then. A value that cannot be read is refused on an uncharged row rather than quietly restarting the list from page one. - Max run seconds (
maxRunSeconds) — default 1800 (30 minutes). The clock ends the collecting, never the delivering. It runs between 30 seconds and 1 hour; set it outside that and the run still starts, at the nearest one, with one uncharged row saying so. No setting here is ever refused for being too big or too small — the run starts, it runs at the nearest limit, and the row tells you which. - How big an ask fits that clock — measured on a live run before each page's rows were written to your dataset in one go, this actor collected roughly 150 to 190 rows a minute on a typical list, so at that pace the default 30 minutes is about 4,500 to 5,700 rows, and the current build spends far less of its clock saving rows. Size the ask or the clock to match. And when the clock does end a run short, you are not left guessing: the run page does the arithmetic on that run's own measured rate and names the number to raise — or, for an ask bigger than an hour can hold, how many runs to split it across — and the last row's
resumeCursorcarries you on from the page it stopped on.
Press Start with nothing filled in and you get three built-in sample rows so you can see the column shape: nothing is read from Instagram on that run and there is no result fee for it.
How often this data changes, and the second run
Follower lists churn daily on an active account — people follow and unfollow constantly, so the answer to "who follows this account" is a moving one and a weekly or daily schedule is where this actor earns its keep.
Re-running the same handle would otherwise re-buy the rows you already have, so it does not. Every run remembers what it delivered to your account, in the key-value store ig-followers-account in your own Apify account, and a later run skips those bought in the last 90 days: not delivered again, not charged, and the slot goes to the next new follower instead — so you still get up to the number you asked for, and a schedule costs what changed plus one $0.05 read per profile. The memory is a key-value store in your own Apify account, so a run started with a scoped API token in restricted-access mode needs key-value store Read, Write and Create permission (Write is what lets the run remember what it delivered; without it every run pays again) or Actor runs set to Full access; without it the run says so on its status line and on an uncharged row, and cannot skip the rows you already have — so the schedule pays for them again until the token is allowed to open that store. Each run also remembers, per account and per list, the deepest point it reached, so a later run that asks for more rows than you already hold reads at most three pages of the ones you own, skips past the rest and continues below them, rather than stopping at the top of a list you have already collected. And a list read all the way to the end of what Instagram serves — its own limit on a very large account, or simply the end of a short one — is remembered as ended: while the account's own published count for that list has not risen, a later run answers from that record with one uncharged row and reads no page of the list at all, instead of reading three pages to be told what it already knows. The moment that count rises, the new rows at the top are collected and charged as ordinary new rows, and the record is re-armed. Include rows you already have reads the whole list from Instagram on every run, whatever the record says: rows you already have come back uncharged and marked repeat: true, and only the list as it stands today is handed back. A resumeCursor you paste in always wins.
Use it as an API endpoint (Standby)
The same scraper also answers plain HTTP requests, so an app or an AI agent can call it like an API and get the rows back in the response instead of starting a run and reading a dataset. The address and a ready-made call are on the actor's Endpoints tab; authenticate with your Apify API token as a Bearer header:
curl -H "Authorization: Bearer <YOUR_APIFY_TOKEN>" \"https://steadyfetch--instagram-followers-scraper.apify.actor/?usernames=nasa&mode=following&resultsLimit=10"
- Same input, same rows, same charge.
usernames,modeandresultsLimitmean what they mean in a run, and a request is charged exactly what a run with that input is charged: every row delivered, and one profile read for every account whose list it reads fresh, on a run or a request alike. The answer is JSON:rows(the very rows a run writes, then its receipt row),delivered,chargedandnotes(what was not returned, in plain words). A POST with the same fields as a JSON body works too. - One request is a slice of a list. It collects up to 1,000 rows in all, across up to 5 accounts (on the Apify free plan, 100 rows of one account). The receipt row's
resumeCursor, sent back with the same usernames, continues each list from the page the request stopped on and skips the lists it finished: no row from that page or above it is delivered or charged again. A row Instagram lists a second time further down the list can be charged again, and a list that changed so much around that point since the last request that it cannot be found is not continued (an uncharged row says so). After a request the Apify free plan's allowance stopped, the next one goes on from the following page, so rows you already got can be charged again if a page or more of followers joined in between. A chain of requests begun before version 1.0.85 carries on as it did then. For a long list in one go, start a run (up to 50,000 rows per list): with your account's storage on every run, no row your account bought in the last 90 days is charged again. - No account memory. A request carries no Apify account, so the endpoint cannot see the rows your account already has: every request reads fresh and is charged like a run on an account that holds none of those rows yet.
includeSeenandresumeFromDatasetIdread your own account, so a request that sends them is refused by name, before anything is collected. For schedules that skip what you already have, use a run. - Nothing is sent without its charge. The charge is made before the answer; if the rows' charge cannot be completed, no rows are sent and the answer says so. A profile read that cannot be charged is left off, and the rows are still sent.
On a Standby request, a row your account already has is charged like any other, and one bought there is not remembered for your runs; the 90-day memory applies to runs.
Reliability
There is nothing to log into and nothing to configure. When a read cannot be answered, the run says so on an uncharged row and finishes successfully — a failed read is never billed and never dressed up as an account with no followers.
Related actors
- One account's own posts and reels: Instagram Profile Posts Scraper — https://apify.com/steadyfetch/instagram-profile-posts
- The spoken words inside a reel: Instagram Reel Transcript Scraper — https://apify.com/steadyfetch/instagram-reel-transcript-scraper
Limits and good manners
Only public accounts return a list; a private one is answered as private and charged nothing. Instagram's own cap on very large accounts is described above and applies to every tool equally. Profile picture links are signed and time-limited by Instagram, and the requesting network address is stripped out of every link before it reaches your dataset. This actor may stop working if Instagram changes how the data is served; if it does, failed rows are never charged.
Support
Something off, or a column you need that is not here? Open an issue on the Issues tab — we usually reply within a couple of hours.
If it earned its keep, a rating helps other buyers find it, and saving the actor keeps it one click away.