Facebook Comments Scraper
Pricing
$8.99/month + usage
Facebook Comments Scraper
Facebook Comments Scraper SD - Facebook Comments Scraper is a social media data tool that extracts comments and replies from public Facebook posts, videos and reels with text, author, likes, reply counts and dates, page after page - Facebook comment extractor.
Pricing
$8.99/month + usage
Rating
0.0
(0)
Developer
Neuro Scraper
Maintained by CommunityActor stats
0
Bookmarked
6
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Share
Facebook Comments Scraper — comments and replies of public posts
The Facebook Comments Scraper exports the comments of public Facebook posts, videos and reels with text, author, likes, reply count and date, page after page, and can add the replies under each comment.
It runs on Apify, needs no Facebook login and no cookies, and exports to JSON, CSV, Excel or an API call. Every session key it needs (tokens, query ids, cursors) is read from Facebook on each run, so it keeps working when Facebook ships new code.
What the Facebook Comments Scraper does
- Finds the post's comment thread and follows Facebook's comment cursor.
- Supports Most Relevant, Newest, Oldest and All orders.
- Adds up to N replies under each comment when asked.
- Works with share links.
Who uses the Facebook Comments Scraper
- Brands doing sentiment analysis.
- Community managers collecting feedback.
- Researchers studying public discussions.
How the Facebook Comments Scraper works
Facebook serves public pages, videos and listings to logged-out visitors and embeds the first page of data in the HTML.
The Actor loads that page like a browser, reads the session values (LSD token, revision, query ids) Facebook writes into it, and requests the following pages from Facebook's GraphQL endpoint with the returned cursor.
Query ids that a page does not preload are read from the JavaScript bundles the page lists, and the variable names of each query come from its own module, so the request always matches Facebook's current code.
Nothing is guessed: if Facebook stops publishing a value the Facebook Comments Scraper needs, the run log names it and the item is skipped instead of being filled with a stale value.
Input of the Facebook Comments Scraper
| Field | Type | Default | What it does |
|---|---|---|---|
postUrls | array | ["https://www.facebook.com/reel/1549207066583030"] | Links to public Facebook posts, videos or reels. |
maxComments | integer | 50 | Top-level comments per post (paginated). |
scrapeReplies | boolean | False | Adds up to "Max replies" replies under each comment. |
maxReplies | integer | 20 | Only used with "Include replies". |
sortMode | string | Most Relevant | Comment order Facebook returns. |
maxTotalItems | integer | 0 | Stops the whole run after this many dataset rows. |
proxyConfiguration | object | {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]} | Facebook limits logged-out visitors per IP address. Residential proxies (the default) give the most reliable results; the Actor switches to a fresh IP when Face |
Example input for the Facebook Comments Scraper:
{"postUrls": ["https://www.facebook.com/reel/1549207066583030"],"maxComments": 50,"maxReplies": 20,"sortMode": "Most Relevant"}
Output of the Facebook Comments Scraper
Each dataset row is one comment. These are the fields the Facebook Comments Scraper produced in its test runs:
| Field | Meaning |
|---|---|
authorId | authorId |
authorName | Comment author |
authorProfilePicUrl | authorProfilePicUrl |
authorUrl | authorUrl |
commentUrl | commentUrl |
id | Platform id of the item |
inputUrl | inputUrl |
likesCount | Likes (or reactions) count |
parentCommentId | parentCommentId |
postUrl | Post the comment belongs to |
repliesCount | Replies under the comment |
scrapedAt | When this row was read |
text | Post or video text |
timestamp | Publication time (UTC, ISO 8601) |
Fields that Facebook does not publish for an item are left empty rather than guessed. Download the dataset as JSON, CSV, Excel, XML or HTML, or read it through the Apify API.
Example row from a Facebook Comments Scraper test run
A real row from the local test run (long values shortened):
{"id": "1745052216756755","text": "\"Everyone knows that Messi is favored by FIFA, so Ronaldo, you're still the greatest of...","authorName": "PAul le Géant","authorId": "100095372325816","authorUrl": "https://www.facebook.com/people/PAul-le-G%C3%A9ant/100095372325816/","authorProfilePicUrl": "https://scontent.fdac5-2.fna.fbcdn.net/v/t39.30808-1/790268773_906586135863789_91174516...","likesCount": 0,"repliesCount": 8,"timestamp": "2026-07-21T14:16:53.000Z","commentUrl": "https://www.facebook.com/reel/1549207066583030/?comment_id=1745052216756755","parentCommentId": null,"postUrl": "https://www.facebook.com/reel/1549207066583030/","scrapedAt": "2026-10-02T18:53:18.000Z","inputUrl": "https://www.facebook.com/share/v/1HDNKQAZTN/"}
Data quality of the Facebook Comments Scraper
- Every value in a Facebook Comments Scraper row is read from Facebook during your run; nothing is filled from a cache or an old snapshot.
- Rows are de-duplicated by id inside a run, so the same comment never appears twice in one dataset.
- Counts are numbers you can sort and sum (not "1.2K" text) wherever Facebook publishes the exact number.
- Dates are UTC in ISO 8601 format, which Excel, Google Sheets, Python and SQL all read directly.
Facebook Comments Scraper test results
These numbers come from live test runs of the Facebook Comments Scraper on 2026-10-03 (home connection, no proxy). Runs on the Apify platform use residential proxies and can be faster or slower.
| Test | Rows | Time |
|---|---|---|
| 60 comments paginated | 60 | 19 s |
| with replies, newest | 5 | 11 s |
| share link | 10 | 16 s |
Facebook Comments Scraper limits, stated plainly
- Measured locally: 60 comments in 19 seconds; 5 comments with replies in 11 seconds.
- Comments hidden by Facebook's filters are not shown to logged-out visitors.
How to run the Facebook Comments Scraper
- Open the Facebook Comments Scraper in Apify Console and fill in the input fields described above.
- Keep the default residential proxy unless you have a reason to change it; Facebook limits logged-out visitors per IP address.
- Start the run, watch the log, and download the dataset when the status says Done.
- To automate it, call the Facebook Comments Scraper from the Apify API, schedule it, or connect it to Make, Zapier, n8n or Google Sheets through an integration or webhook.
Python example with the Apify API client:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run_input = {"postUrls": ["https://www.facebook.com/reel/1549207066583030"],"maxComments": 50,"maxReplies": 20,"sortMode": "Most Relevant"}run = client.actor("neuro-scraper/facebook-comments-scraper").call(run_input=run_input)for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item)
Facebook Comments Scraper pricing
The Facebook Comments Scraper uses pay-per-event pricing: you pay per dataset row (event "result"), plus the Apify platform usage of your run. Free-plan users get up to 30 rows per run, which is enough to test the Facebook Comments Scraper on real data.
Set a maximum cost per run in Apify and the Facebook Comments Scraper stops cleanly when it is reached.
Tips for large runs of the Facebook Comments Scraper
- Start with a small limit to check the Facebook Comments Scraper output, then raise it; the first rows arrive within seconds.
- Split very large jobs into several inputs and run them in parallel tasks; each run gets its own proxy sessions.
- Set a maximum cost per run in Apify; the Facebook Comments Scraper stops cleanly when the budget is reached and keeps every row it already saved.
- Schedule repeat runs instead of one huge run when you track the same targets over time.
- Keep the residential proxy: datacenter IPs are refused by Facebook far more often for logged-out visitors.
Facebook Comments Scraper compared with copying by hand
| Facebook Comments Scraper | Manual work | |
|---|---|---|
| Speed | Seconds per page of results | Minutes per item |
| Fields | Every public field, same order every time | Whatever you copy |
| Format | JSON, CSV, Excel, API | Spreadsheet you build yourself |
| Repeatable | Schedule it daily | Start again each time |
| Errors | Logged per item | Unnoticed typos |
Using the Facebook Comments Scraper in a workflow
- Send every new row to Google Sheets or Airtable with the Apify integration and keep a live table.
- Trigger a Make, Zapier or n8n scenario with a webhook when the run finishes.
- Load the JSON export into Python or BigQuery for analysis and dashboards.
- Use the Apify API: start the Facebook Comments Scraper with a POST request and read the dataset items endpoint when the run finishes.
- Chain it: pass the Facebook Comments Scraper output to another Apify Actor (for example a downloader or a transcript Actor) in an Apify task.
- Export straight to Excel from the dataset tab when you only need a one-off report.
Troubleshooting the Facebook Comments Scraper
- The run ends with no rows: open the log. The Facebook Comments Scraper writes one line per target saying what Facebook returned, for example a login wall or a missing item.
- Fewer rows than expected: the target may have fewer public items, or Facebook may stop serving more pages to logged-out visitors. The log names the reason.
- Slow run: large limits mean many pages; the Facebook Comments Scraper waits briefly between pages so Facebook keeps answering. Split big jobs into several runs.
- Proxy errors: keep the RESIDENTIAL group. The Facebook Comments Scraper already switches to a fresh IP when one is blocked.
- Free plan stops at 30 rows: that is the free-plan cap of the Facebook Comments Scraper; any paid Apify plan removes it.
What changed in this version of the Facebook Comments Scraper
- Rebuilt in October 2026 on Facebook's logged-out web endpoints; every token, query id and cursor is read at run time.
- Pay-per-event pricing (one event per row) replaces the old monthly rental; free-plan users can test with 30 rows per run.
- Residential proxy by default, with automatic switch to a fresh IP when Facebook blocks one.
Is it legal to use the Facebook Comments Scraper?
The Facebook Comments Scraper reads only data that Facebook shows to any logged-out visitor. It never logs in and never touches private content. Personal data may still be in public posts, so check GDPR and the other laws that apply to you before you store or reuse it, and respect Facebook's terms.
Related scrapers
| Actor | Link |
|---|---|
| Facebook Posts Scraper | neuro-scraper/facebook-posts-scarper |
| Facebook Reels Scraper | neuro-scraper/facebook-reels-scraper |
| Facebook Video Details Scraper | neuro-scraper/facebook-video-details-scraper |
| Facebook Video Downloader | neuro-scraper/facebook-video-downloader |
| Facebook Reels Downloader | neuro-scraper/facebook-reels-downloader |
| Facebook Video Scraper | neuro-scraper/facebook-video-scraper-pro |
| Facebook Transcript Scraper | neuro-scraper/facebook-transcript-scraper |
| Facebook Photos Scraper | neuro-scraper/facebook-photo-posts-scraper |
| Facebook Reels Scraper Advanced | neuro-scraper/facebook-reels-scraper-advanced |
| Facebook Ads Library Scraper | neuro-scraper/facebook-image-photos-downloader |
| Facebook Pages Scraper | neuro-scraper/facebook-reels-downloader-and-facebook-video-downloader |
| Facebook Marketplace Scraper | neuro-scraper/facebook-video-posts-scraper |
Leave a review
If the Facebook Comments Scraper saved you time, please leave a star rating and a short review on its Apify page. Reviews help other users find the Facebook Comments Scraper and tell us what to improve next.
Frequently asked questions
Can the Facebook Comments Scraper read replies?
Yes. Turn on "Include replies" and set how many per comment.
Does the Facebook Comments Scraper need my Facebook login?
No. The Facebook Comments Scraper works logged out and never asks for your password or cookies. It reads only what Facebook shows to any visitor.
Do I need my own proxy for the Facebook Comments Scraper?
No. The Facebook Comments Scraper uses Apify residential proxies by default and switches to a fresh IP when Facebook blocks one. You can choose another proxy in the input.
What formats can I export from the Facebook Comments Scraper?
JSON, CSV, Excel, XML, HTML and RSS from the dataset tab, or any format through the Apify API, webhooks and integrations.
How fast is the Facebook Comments Scraper?
In the test runs above the Facebook Comments Scraper took between 11 and 19 seconds per run. Speed depends on how many items you ask for and on the proxy.
Why did the Facebook Comments Scraper return fewer rows than I asked for?
The Facebook Comments Scraper stops when Facebook has nothing more to show logged out, when your limit is reached, or when the free-plan cap of 30 rows applies. The run log always says which one happened.
Can I schedule the Facebook Comments Scraper?
Yes. Create a schedule in Apify Console to run the Facebook Comments Scraper daily or hourly and send the results to Google Sheets, Make, Zapier or n8n through an integration.
Can the Facebook Comments Scraper read private accounts or private groups?
No. The Facebook Comments Scraper reads public data only. Private content needs a login, and the Facebook Comments Scraper never logs in.
What happens when Facebook changes its website?
The Facebook Comments Scraper reads every key it needs from Facebook at run time, so routine changes are picked up automatically. If something can no longer be read, the log says so instead of returning wrong data.
Can I use the Facebook Comments Scraper with Make, Zapier or n8n?
Yes. Add the Facebook Comments Scraper as an Apify step in Make, Zapier or n8n, or send a webhook when the run finishes and fetch the dataset items from the Apify API.
Does the Facebook Comments Scraper work in every country?
The Facebook Comments Scraper reads Facebook through residential proxies that rotate across countries. Content that Facebook restricts by country follows those rules.
How do I collect only new items with the Facebook Comments Scraper?
Schedule the Facebook Comments Scraper and keep the item ids from earlier runs. Every row has a stable id, so a simple de-duplication against your previous export keeps only the new ones.
Can the Facebook Comments Scraper process many targets in one run?
Yes. Put as many targets as you like in the input; the Facebook Comments Scraper handles them one after another and a failing target never stops the others.