Social Media Comments Scraper - 5 Platforms

Export public comments for analysis

Request public comment records from known Instagram, TikTok, Facebook, YouTube and X posts. Each source receives a bounded comment sync before export.

Use this social media comments scraper to bring available audience feedback into your own research, moderation review or sentiment-analysis workflow. It returns comment text, not just comment counts. Sentiment scoring and moderation decisions are not built in. No customer social login or proxy setup is needed.

Coverage matters: this is a bounded collection, not an "all comments" scraper. Records can include earlier observations, and X and some Instagram sources are previews. The details below explain exactly what you are buying.

Quick start

1. Open the Actor in Apify Console and paste a public post URL, not a profile URL.
2. Start with a small limitPerPost, set your run spending limit, and click Start.
3. Export the dataset as JSON, CSV or Excel. Inspect source coverage in OUTPUT before drawing conclusions.

{"urls":["https://www.youtube.com/watch?v=jNQXAC9IVRw"],"limitPerPost":25,"maxResults":100}

Read this before using the data

This Actor exports the current stored comment corpus, not an immutable list of comments first fetched in this run. That corpus can contain earlier public observations. Each record carries its last-observed timestamp and current_stored_corpus provenance. You pay for delivered comment records, not a claim that every record was freshly fetched. Sync fetched counts and delivered corpus counts can differ.

X returns bounded public reply previews, and some Instagram paths are previews too. Replies may be present, but complete reply trees, newest-first ordering, deleted-comment detection and exhaustive coverage are not promised. The Actor does not expose nonfunctional sorting or reply-depth controls.

The dataset contains comment text, available author information, platform comment and parent IDs, timestamps and available engagement fields. The OUTPUT key-value record contains source-level status/disposition alongside canonical deduplicated results. Always inspect source coverage, not just row count; a successful run can have partial sources.

Example output

Illustrative excerpt, not live data:

{
  "sourceUrl": "https://www.youtube.com/watch?v=jNQXAC9IVRw",
  "platform": "youtube",
  "status": "succeeded",
  "commentId": "example-comment-id",
  "parentCommentId": null,
  "text": "An illustrative public comment.",
  "author": { "username": "example", "displayName": "Example Viewer" },
  "likes": 2,
  "replyCount": null,
  "observedAt": "2026-09-09T12:00:00.000Z",
  "collectionScope": "current_stored_corpus",
  "syncCoverage": "partial"
}

observedAt is the comment's last observation time, not necessarily this run's time. syncCoverage describes the source sync; it does not make the stored corpus exhaustive. Missing author or engagement fields stay null. A populated parentCommentId identifies a reply when supplied, not a promise that all siblings or descendants were collected.

Limits and cost

Up to 10 post URLs, up to 1,000 records per post, and no more than 1,000 delivered records globally per run. Both requested limits and the Apify spending cap bound work. Launch price: $1 per 1,000 delivered comment records; source refreshes/status summaries have no separate result charge. Apify platform usage may apply separately. Console pricing is authoritative.

For example, 100 delivered comments generate $0.10 in result charges. Asking for 100 does not guarantee 100 exist or can be retrieved. A new run can deliver and charge for records also seen in an earlier run.

No customer social login, proxy credentials or SIN key is required. Only public content is supported. An unavailable post, zero results or a rate limit must not be interpreted as proof that no comments exist. Aborting stops admission, not already submitted backend jobs. Use resultId to deduplicate interrupted dataset delivery; completed OUTPUT is canonical.

Built and maintained by NooEsc, powered by SIN. Process public text and author data responsibly and only for purposes you are entitled to pursue.

API and support

Open the API tab for request and SDK examples using the input above. Export text to your own analysis workflow, keeping sourceUrl, timestamps and coverage alongside it. Do not treat a preview as a representative sample of the whole audience.

Use the Issues tab for help. Include a run URL, platform and expected versus actual behavior; never credentials or private data.

Other social media data

• Post Metrics: views, likes and comment counts when available.
• Account Profiles: bios, images and available audience counts.
• Recent Account Posts: recent posts from Instagram, TikTok and X profiles.