Pricing

from $0.60 / 1,000 comments

Try for free

Go to Apify Store

Instagram Comments Scraper — Scrape Instagram Comments, Replies

Try for free

Scrape Instagram comments and their replies for any post, reel or IGTV URL — text, author, likes, timestamps. No login. Replies open thread by thread until the run's reply budget is spent, and each comment says whether its thread was opened. A reply costs the same. From $0.60 per 1,000 comments.

Pricing

from $0.60 / 1,000 comments

Rating

0.0

(0)

Developer

Steadyfetch Team

Actor stats

Bookmarked

Total users

Monthly active users

a day ago

Last modified

Changelog

1.0.11 — 2026-09-14

An Instagram "share" link no longer collects a different post's comments and bills you for them. Instagram's Share button hands you an address like instagram.com/share/p/BAgXyZ12345 — the token on the end is a redirect, not the post's own code. This actor read the p in that address as the post marker and took the redirect token as the code, which decodes to a real post: somebody else's. The run then collected that stranger's comments, charged for every one of them, and wrote the post link on each row back as instagram.com/p/<the redirect token>/ — so the rows looked like the post you had asked for and there was no way to tell. A share link is now refused before anything is read: one uncharged row that says what the link is, why its token is not the post code, and the one move that fixes it — open it in a browser, copy the address it lands on, paste that into "Post URLs" and press Start. Nothing is bought for it and there is no result fee.
And four more addresses that were being read as posts are refused the same way. The fault was not the share link, it was how the address was read: this actor looked for p, reel, reels or tv anywhere in the path, and checked the site by looking for "instagram.com" anywhere in the text you pasted. So instagram.com/reels/audio/1234567890/ — Instagram's page for one sound — was read as a reel with the code "audio" and collected a post nobody had asked for; a direct-message address and any deep path with one of those four words in it did the same; and a look-alike address such as instagram.com.example.net/p/CODE/ or myinstagram.com/p/CODE/ was accepted as Instagram. The post marker is now only read where Instagram actually puts it — at the start of the path, or straight after the account handle — and the site is read as the address's own host. Every real post, reel, IGTV and /<handle>/p/CODE/ link still works exactly as before, an upper-cased link now works too, and a link that cannot be read is one uncharged row naming the field and the shape that works. No price, no input field, no output column and no charged event changed.

1.0.10 — 2026-09-14

A run that brings back no comments now tells you what to do about it — and counts the mistake it never showed. A run that delivered nothing used to name only the count and a reason code — "Delivered 0 comments of 1 asked for across 1 post. Not delivered: 1 not found" — and stop there, with no next step, because the run had ended cleanly and only a run stopped by a limit ever said anything further. Each reason now carries its own plain sentence: a link Instagram has nothing at tells you to open it in a browser and says a re-run returns the same answer, a post that really has no comments yet says so, a temporary read says to start the run again, an answer this actor could not map says it is ours rather than yours and asks you to open an issue, and the monthly collection allowance says it is ours and resets at the start of the month. And a value this actor could not read is now counted on that line at all: it was named on its own uncharged row but was missing from the run page's summary entirely, so a run whose only link was a profile address said "Delivered 0 comments of 1 asked for across 1 post." and nothing else. It now names the count and tells you which field to paste post links into and what one looks like. A run that did deliver comments is unchanged and says nothing extra.
What a run costs, and whether the same links tomorrow are worth it, are now on the first screen. You had to scroll past the column table and the sample row to learn that a comment is $0.60 per 1,000 on Gold and above ($2.40 per 1,000 on the Apify free plan) and that a reply is charged on that same event at that same price. The re-run advice was further down: comments keep arriving for days after a post goes up and the busiest hours are the first few, so the useful pattern is the same links again tomorrow — and the ones you already have are skipped rather than charged again, so a daily watch pays only for what is new. Both now sit in the opening block beside the actor id and the input. No price, no input field, no output column and no charged event changed.

1.0.9 — 2026-09-14

A run that can read your repeat memory but not write to it now says so, instead of letting your next run pay for everything twice. The previous entry covered a token that cannot OPEN that memory. This is the other half: an API token can be allowed to read key-value stores and not to write them — or to write them and not to create one you do not have yet — and such a run opens your memory, recognises every comment you already had correctly, and then remembers nothing it delivered. The run looks perfect and your NEXT run is charged for the whole delivery all over again. The run page now names it the moment the first write is refused, an uncharged row at the top of the dataset carries the cause and the fix in full, the receipt carries repeatWrite: "denied_scope", and the run log keeps Apify's own message and adds the permission to grant: key-value store Write (and Create), or Actor runs set to Full access, under Settings → API & Integrations. A write that fails for an ordinary reason is still just retried bookkeeping and says nothing. Both run-page sentences are also shorter and now read the same on every actor in the portfolio, with the whole fix on the row. No price, no input field, no delivered column and no charged event changed.
A run that set a field this actor does not have now reads as one sentence on the run page. The sentence naming the field you set and the field this actor reads carried a semicolon, which is the character the run page uses to separate one statement from the next — so anything reading that line saw two half-sentences instead of one. Same words, clearer line. Nothing about what is collected or charged changed.
A run that cannot open your account's repeat memory now says so instead of quietly charging you twice. This actor promises you never pay for the same comment twice: it remembers what it delivered to your account in a key-value store there, and skips those next time — which is the whole point of watching the same posts daily. A run started from the API with a scoped token in restricted-access mode cannot open that store unless the token is allowed to — so the check never ran, every comment you already had was collected and charged again, and nothing on the run page, the rows or the receipt said a word about it. The run page now names the cause and the fix, an uncharged row at the top of the dataset says the same thing for anything reading rows rather than the page, the receipt carries repeatCheck: "unavailable_scope", and the run log keeps Apify's own message and adds the permission to grant: key-value store Read, Write and Create, or Actor runs set to Full access, under Settings → API & Integrations. Every other reason the memory can be unreadable reads exactly as it did before. No price, no input field, no delivered column and no charged event changed.

1.0.8 — 2026-09-13

A post link sent under a slightly different field name is now collected instead of ignored. A run that put its links in postUrl, url, urls, link, links, post, posts, reelUrl, reelUrls or startUrls used to collect nothing: Apify passes a field this actor does not declare straight through, so the run looked like a Start with no post set and came back with one uncharged row naming a field you had never filled in. Those names are now read as the field they plainly mean — Apify's own {"url": …} Start-URLs shape included — a link sent under both names is collected once and charged once, and one uncharged row tells you which field to use next time so it stops appearing. A field name that matches nothing still gets an uncharged row, and that row now names the field you set as well as the field this actor reads. No price, no input field, no output column and no charged event changed.
The store card now says what a comment costs. The card said what comes back and what is never charged, and named no price at all — so a buyer comparing actors in the search results could not compare this one on price, and had to open the page to find it. It now carries the same headline the page does: from $0.60 per 1,000 comments, the cheapest paid rate on the ladder. The reply rule stays on the card, because a reply charged as a second unit is the thing that surprises a buyer most elsewhere. Nothing else moved: no input field, output column, charged event or price changed.
The store card now says how replies actually arrive. The card sold "comments and their replies" without saying that a run opens reply threads only while its own reply budget lasts: threads are opened one at a time, and once buying another one would cost more than the comments it returns are priced at, the rest are left unopened. That is unchanged behaviour — the page has described it since the actor was listed and every comment row carries repliesCollected — but a buyer reading only the card could expect a thread under every comment. The card now says replies open thread by thread until the run's reply budget is spent, and that each comment says whether its thread was opened. Nothing about the run moved: no input field, output column, charged event or price changed, and a reply is still charged at the same price as a top-level comment.

1.0.7 — 2026-09-13

Your result limit now holds even when Apify moves the run to another server part-way through. This actor already picks up exactly where it left off after such a move, and it works out how much of your limit is left from the comments it has already delivered — but it was counting only the comments that carried a fee. A comment your account already has comes back delivered and uncharged, and so does every row on a run that cannot be billed at all, so those were invisible to the count: the run believed more of your limit was unspent than really was, and could hand you more comments than you asked for. It now counts every one already delivered to you, whether or not it carried a fee. Nothing about what you are charged moves — a repeat is still delivered without a result fee, and only delivered comments are charged.

1.0.6 — 2026-09-13

The page now shows you a row before you spend anything, and its first line is the listing's own name. A new What a row looks like section carries one real delivered comment from a live run — text, author, likes, the reply fields and the charge record — and the heading at the top of the page is now the store title instead of a different name for the same product. No price, no input, no output column and no charged event changed.
A read that will never work is no longer reported as one that might. Two different answers used to arrive as vendor_unavailable, the row that says "this is temporary — please re-run": a post Instagram refuses to answer for outright, and an answer that arrives in a shape this actor cannot read yet. Neither changes on a re-run, so that row was selling you a second run for exactly the same answer. Each now has its own uncharged row — source_refused and unsupported_shape — saying what is actually true, what to check, and that a re-run will not change it. A genuine outage still ships as vendor_unavailable, still asks for a re-run, and still carries no result fee. No price, no input and no delivered column changes.
A run may now wait longer for a slow source before it gives up. How long a run can keep waiting is sized against what the comments it is still owed are worth, and this build lets that sizing draw on half of the run's own margin instead of a quarter — so a page that is answering slowly gets about twice as long to come back, and a delivery cut short on a slow page is rarer. Everything that bounds the waiting is unchanged: your run-time limit, your result limit and your cost cap still end it on the spot, no run ever waits less than it did before, and a small ask waits exactly as long as it always has. No input, no output column, no charged event and no price changes.
The input schema now speaks to an AI agent as well as to a person. An agent that finds this actor through Apify's MCP server never opens this page — it reads the input schema. So the schema's own description now opens with the call that works, says what one comment costs and what 300 comments come to, repeats that a reply costs the same as a top-level comment, lists what is never charged, says that the result limit is per post, and names the run option that caps the bill. The post links field leads with the value shape and examples, then what is never charged, then where a profile or hashtag link belongs, with the console sample instruction last. No price, no charged event, no input field and no delivered column changes.

1.0.5 — 2026-09-12

The time a run waits out a quiet source is now sized to what you asked for, instead of being the same fourteen seconds for every run. Since the last build a post that hit a quiet stretch was waited out twice — a short wait, then a longer one — and then given up on, whether you had asked for three comments on a two-minute run or five hundred on an hour-long one. A big ask on a long run now keeps waiting and reading the same page again, each wait longer than the last, for as long as the comments it is still owed are worth the run time it costs. A small ask waits exactly as long as it did before, so nothing gets slower or dearer; no run ever waits less than it used to; and no run waits past your own run-time limit, your result limit or your cost cap, all of which still end the waiting on the spot. Where the source comes back, the comments behind the pause are delivered and charged exactly as they always were. Where it does not, nothing changes: the comments in hand are yours, the rest carries no result fee, and the row still says a re-run is the fix.

1.0.4 — 2026-09-12

An answer this actor already paid for is never bought twice. When the source replies in a shape this build cannot read, waiting and asking again cannot change one byte of it — the run did it anyway, buying the same dead page three times and spending up to fourteen seconds of your run clock on it. From this build only the refusals that cost nothing and clear in seconds are waited out: a rate limit, a server error, a dropped connection, exactly as before. Nothing about what you are charged moves.
A post that came back blank is no longer reported as a post with no comments. A page holding nothing used to be read as Instagram's own final answer — "nobody has commented yet, that is a definitive answer" — even when the post itself says it has thousands of comments. That told you to stop asking on exactly the run where asking again was what would have got you your comments. Now the post's own published comment count decides: where it says zero, the answer stands as the definitive one it is; where it says otherwise, or says nothing at all, the row is marked temporary and asks you to re-run. Either way there was no result fee.
An aborted or migrated run now leaves its receipt from the first moment of the run, instead of only after start-up finishes. The record that says how a run ended was only put in place once the run had finished starting up — reading your input, opening its stores, working out what a previous attempt had already delivered and charged. A run stopped inside that window ended with nothing written about it at all, which mattered most on a re-started run, where the thing not written about was the earlier attempt's work. It is now in place from the run's first moment. Nothing else moved: no input field, output column, event or price changed, and a run that reaches its work behaves exactly as before.

1.0.3 — 2026-09-12

A cost build, and the honest-row copy that goes with it.

A post no longer ends because Instagram could not be reached for a moment. When the source went quiet part-way through a post's comments, the run used to stop collecting for that post on the spot — about five seconds after the first sign of trouble — and report every comment it still owed as not delivered. It now waits and reads the same page again: a short wait, then a longer one, spent once per post rather than on every page, and only while the run still has the clock for it and none of your own limits have been reached. Where the source comes back, the comments behind the pause are delivered exactly as they always were. Where it does not, nothing changes at all: the comments already collected are yours and charged as marked, the rest carries no result fee, and the row still says a re-run is the fix. A post that does not exist, one with comments turned off, and a run that has reached a limit are answers, not pauses, and are never waited on.
A link in your rows can never carry a network address, whatever form it arrives in. Every link this actor delivers already went through our own URL hygiene before reaching your dataset, and that pass had a gap: where an upstream body writes its links with HTML-escaped separators (& in place of &), the address parameter was not recognised by name and could survive into a row. It is now removed however the link is written — escaped, plain or legacy separators, upper or lower case, and inside a link that wraps another link. Nothing else in a link moves: the expiry, the signature and every routing parameter are delivered exactly as they were served, so the links keep working exactly as before. No column, no input, no price and no charge changes.
A run that has reached your maximum cost per run no longer fetches a page of comments it cannot deliver. It stops at the cap exactly as before, and the page it used to fetch first was never charged to you — so nothing about your rows, your charges or your prices changes.
The uncharged row for a post the run stopped before it ever opened now says so, instead of offering to pick up where it left off on a post it never read.
An uncharged row no longer denies a fee for comments you were already charged for, and no longer blames Instagram for one of this actor's own limits. A post whose comment feed went dark after it had delivered rows used to end on "There was no result fee — please re-run", sitting directly above the rows that were charged; it now opens with how many were delivered and charged, and offers the re-run for the rest. And a post cut by one of this actor's own bounds — at most 400 comment pages for a single post, or three pages in a row holding only comments you already have — used to be reported as "comments are turned off for it, or nobody has commented yet… that is a definitive answer". Those two bounds are ours, the row now says so, and it names the setting that lifts each. Nothing about your columns, your charges or your prices changes.
A post cut by one of this actor's own bounds is now recorded as this actor's bound, not as Instagram running out of comments. The uncharged row for such a post already said so in words; the status on it still read no_comments, the same code a post that genuinely has none gets. Those two rows now carry their own statuses — skipped.page_cap for the 400-page bound on a single post, skipped.all_repeat for the three-pages-of-comments-you-already-have bound — so a run's own record can no longer say Instagram had nothing more over a walk this actor stopped. Every sentence on those rows is unchanged, nothing is charged for them either way, and no price, input or delivered column moves.
A limit set higher than this actor's own no longer refuses the run. "Max comments per post" above 5,000, or a run clock outside 30 seconds to 1 hour, used to be rejected by the platform before the run started — no run, no rows, and nothing to tell you why, which is what a caller arriving with another scraper's numbers hit. From this build the run starts, continues at the nearest limit, and leaves one uncharged row naming what you asked for and what bound it. Your prices, your charges and every column are unchanged.

1.0.2 — 2026-09-11

A listing-copy build.

The store page now carries the plain note that this actor is unofficial and not affiliated with, endorsed by, or sponsored by Instagram or Meta Platforms, Inc., the same line the rest of the Instagram actors carry.
Internal only: our own record of what a licensed data feed costs us was corrected, and a request that feed rejects is no longer retried — nothing about your rows, your charges or your prices changes.

Nothing about the actor itself changed: the same inputs, the same columns, the same events and the same prices. There is no reason to re-run anything.

1.0.1 — first public build

Instagram comments and replies by post URL.

Paste post, reel or IGTV links (or the bare code at the end of one). Your limit is exact and it is per post: set 200 and you get 200 from each link, or an uncharged row says why not.
Replies are collected under the comment they answer and charged at the same price as a top-level comment, on the same single comment event. Nothing is charged for starting a run.
Honest uncharged rows for everything not delivered: post_not_found, no_comments, stopped_at_limit, vendor_unavailable, vendor_budget. A run that delivers nothing still finishes successfully and says why.
Repeat memory: comments already delivered to your account are skipped on a later run — not delivered again, not charged — and the slot goes to the next new comment, so a daily watch on the same posts costs only what is new.
Pressing Start with nothing set returns built-in sample rows at no result fee, so the output shape is visible before anything is collected.

Instagram Comment Replies Scraper

data_direct/instagram-comment-replies-scraper

Get the replies to one comment (its thread)

Data Direct

Instagram Comments Scraper - Comments, Authors & Likes

zaver.api/instagram-comment-scraper

Scrape all comments from any Instagram post or reel - comment text, author (username, verified), likes, timestamp and reply count. Bulk post URLs, deep export, no login. $0.99 per 1,000 comments. Export CSV, JSON, Excel.

Zaver

Instagram Comments Scraper API — Reels, No Login

funny_ground/instagram-comments-scraper-fast

Export public Instagram Reel and video-post comments with author, likes, timestamp, and thread fields. No login or residential proxy. Reply extraction is best-effort when Instagram exposes threads anonymously. $0.50 per 1,000 results.

Coor Yu

Instagram Comments Scraper

fetch_cat/instagram-comments-scraper

Extract public Instagram comments from post and Reel URLs with author usernames, text, timestamps, likes, reply counts, and source URLs.

Hanna Nosova

Instagram Comments Scraper

scrapesmith/instagram-comments-scraper

⚡ Instagram Comments Scraper – Extract comments, usernames, likes, replies & timestamps from any public post or reel. Bulk scraping, no login needed. Export to JSON, CSV or Excel. Starts at $0.50/1,000 results.

Scrape Smith

2.1K

4.4

Instagram Comments Scraper 💬

scriptbase/instagram-comments-scraper

💬 Export Instagram comments to JSON, CSV or Excel. Get comment text, author handle, likes, reply count and date from any post or reel. Paginated, no login, no Instagram API access needed.

Scriptbase

Instagram Comments Scraper

supreme_coder/instagram-comments-scraper

Scrape comments from instagram posts including replies. No cookies or login required. Costs just $0.3 per 1K

Supreme Coder

550

3.6

TikTok Comments Scraper – No Login

datascraperes/tiktok-comments-scraper

Collect public TikTok comments and replies from video URLs. Export comment text, likes, timestamps and public author details in structured results. Set limits for comments, replies and total results, and pay only $0.50 per 1,000 saved comments or replies. No login is required.

DataScraperES

Instagram Comments Scraper - Post & Reel Comments

dami_studio/instagram-comments-scraper

Scrape comments from a public Instagram post or reel. Replies sit under their comment, and both levels come back labelled. Every row has the author, the text, the time, likes and reply count. Nothing to log into, no cookie to paste. $0.40 per 1,000 rows.

Dami's Studio

Instagram Comments & Replies | $0.4/1K + Page Fees on Starter

publicsignallabs/instagram-comments-replies

Scrape public Instagram comments and optional nested replies from posts and Reels. Preserve thread relationships, public author details, timestamps, likes, and source media with bounded pagination. No login or proxy setup.

Public Signal Labs

Instagram Comments Scraper — Scrape Instagram Comments, Replies

Changelog

1.0.11 — 2026-09-14

1.0.10 — 2026-09-14

1.0.9 — 2026-09-14

1.0.8 — 2026-09-13

1.0.7 — 2026-09-13

1.0.6 — 2026-09-13

1.0.5 — 2026-09-12

1.0.4 — 2026-09-12

1.0.3 — 2026-09-12

1.0.2 — 2026-09-11

1.0.1 — first public build

You might also like

Instagram Comment Replies Scraper

Instagram Comments Scraper - Comments, Authors & Likes

Instagram Comments Scraper API — Reels, No Login

Instagram Comments Scraper

Instagram Comments Scraper

Instagram Comments Scraper 💬

Instagram Comments Scraper

TikTok Comments Scraper – No Login

Instagram Comments Scraper - Post & Reel Comments

Instagram Comments & Replies | $0.4/1K + Page Fees on Starter

Changelog

1.0.11 — 2026-09-14

1.0.10 — 2026-09-14

1.0.9 — 2026-09-14

1.0.8 — 2026-09-13

1.0.7 — 2026-09-13

1.0.6 — 2026-09-13

1.0.5 — 2026-09-12

1.0.4 — 2026-09-12

1.0.3 — 2026-09-12

1.0.2 — 2026-09-11

1.0.1 — first public build