Facebook Comments Scraper

Extract comments and replies from public Facebook post links in a clean, structured JSON format.

This Actor is designed for people who want a simple way to collect Facebook post discussions for research, monitoring, analytics, moderation workflows, archiving, or AI-ready datasets. Each output record represents one Facebook post and includes post-level details together with a nested comments tree.

What This Actor Does

• Collects comments from one or more public Facebook post URLs
• Supports multiple comment sorting modes
• Supports optional date-range filtering
• Optionally collects replies
• Supports reply depth 1 or 2
• Returns one dataset item per input post
• Produces user-friendly JSON with post details at the top level and nested comments under comments

Best For

• Social listening and brand monitoring
• Competitor research
• Audience research and sentiment review
• Comment moderation pipelines
• Dataset preparation for LLM and NLP workflows
• Archiving public discussions from Facebook posts

Input

Provide one or more public Facebook post links and choose how much discussion data to collect.

Input fields

• Facebook post links Add one or more public Facebook post URLs.

• Comments count to fetch Maximum number of top-level comments to collect for each post.

• Add replies Turn reply collection on or off.

• Reply depth Choose:

  • Level 1 Collect direct replies to top-level comments.
  • Level 2 Collect direct replies and nested replies one level deeper when available.

• Replies count each level Maximum number of replies to keep at each reply level.

• Comments sorting Choose:

  • All comments
  • Most relevant
  • Newest

• Date range for comments Optional filter for recent comments and replies. Accepted styles:

  • 2026-04-01
  • 1 day
  • 2 weeks
  • 3 months
  • 1 year

If a date range is provided, the Actor automatically uses Newest sorting to make recent-comment filtering work correctly.

Output

Each dataset item represents one Facebook post.

The output contains:

• top-level post details
• engagement data such as reactions and shares
• top-level attachments when available
• a nested comments tree under comments.items

Output shape

Each result record follows this general structure:

{
  "inputUrl": "https://www.facebook.com/example/posts/...",
  "postUrl": "https://www.facebook.com/example/posts/...",
  "postId": "1599471641539370",
  "authorName": "Example Author",
  "authorId": "100044296486382",
  "authorUrl": "https://www.facebook.com/example",
  "authorType": "User",
  "createdAt": "2026-04-09T16:32:07+00:00",
  "text": "Post text",
  "textFull": "Post text",
  "topLevelAttachments": [],
  "attachmentCount": 0,
  "attachmentsMayBePartial": true,
  "commentCount": 16920,
  "reactionCount": 289870,
  "topReactions": [
    {
      "type": "like",
      "name": "Like",
      "count": 183395
    }
  ],
  "shareCount": 2702,
  "shareCountLabel": "2.7K",
  "sortBy": "all_comments",
  "comments": {
    "items": []
  }
}

Comment fields

Each top-level comment and reply can include:

• id
• url
• depth
• parentCommentId
• createdAt
• text
• authorName
• authorId
• authorUrl
• authorType
• authorProfilePicture
• authorVerified
• reactionCount
• topReactions
• replyCount
• attachments
• replies

Example: Top-Level Comments Only

Use this when you want only the main comments and no replies.

Suggested input

• Add replies: false
• Reply depth: Level 1
• Comments count to fetch: 20

Example output shape

{
  "inputUrl": "https://www.facebook.com/Cristiano/posts/pfbid0vfFdv8NWUm6qSmFsJjnL9snyFAPsSPvJzSXLmdHQ3JZgjD3JF6mQTEA2YrEMqh6fl",
  "postUrl": "https://www.facebook.com/Cristiano/posts/pfbid0vfFdv8NWUm6qSmFsJjnL9snyFAPsSPvJzSXLmdHQ3JZgjD3JF6mQTEA2YrEMqh6fl",
  "postId": "1599471641539370",
  "authorName": "Cristiano Ronaldo",
  "commentCount": 16920,
  "reactionCount": 289870,
  "shareCount": 2702,
  "sortBy": "all_comments",
  "comments": {
    "items": [
      {
        "id": "951288517597139",
        "depth": 0,
        "text": "Please give me 1% of your football knowledge...",
        "authorName": "Snr Nelson",
        "replyCount": 9
      }
    ]
  }
}

Example: Level 1 Replies

Use this when you want direct replies to top-level comments.

Suggested input

• Add replies: true
• Reply depth: Level 1
• Replies count each level: 5

Example output shape

{
  "id": "951288517597139",
  "depth": 0,
  "text": "Please give me 1% of your football knowledge...",
  "authorName": "Snr Nelson",
  "replyCount": 9,
  "replies": [
    {
      "id": "1999023817367454",
      "depth": 1,
      "parentCommentId": "951288517597139",
      "text": "Snr Nelson you work harder than he had done",
      "authorName": "Trîplē Hay",
      "replyCount": 0
    }
  ]
}

Example: Level 2 Replies

Use this when you want nested discussion threads reconstructed one level deeper.

Suggested input

• Add replies: true
• Reply depth: Level 2
• Replies count each level: 5

Example output shape

{
  "id": "951288517597139",
  "depth": 0,
  "text": "Please give me 1% of your football knowledge...",
  "replies": [
    {
      "id": "962518329647471",
      "depth": 1,
      "parentCommentId": "951288517597139",
      "text": "yess i agree...",
      "replies": [
        {
          "id": "940132731958438",
          "depth": 2,
          "parentCommentId": "962518329647471",
          "text": "and messi never lost UCL final...",
          "authorName": "Mohale Malatji"
        }
      ]
    }
  ]
}

Sorting Options

The Actor supports:

• All comments Useful when you want a broader view of available comments.

• Most relevant Useful when you want the default Facebook-style ranking.

• Newest Best for recent-comment tracking and date-based filtering.

Date Range Filtering

Date filtering applies to comments and replies.

Supported examples:

• 2026-04-01
• 1 day
• 7 days
• 2 weeks
• 3 months
• 1 year

When a date range is set:

• sorting is automatically switched to Newest
• only comments and replies within the selected range are kept

Multiple URLs

You can submit multiple Facebook post links in one run.

The Actor returns:

• one dataset item per post URL
• each item with its own post data and nested comments tree

This makes it easy to process batches of posts in a single run while keeping each result clearly separated.

Attachments

The Actor can return attachment data when available.

Post-level attachment fields

• topLevelAttachments
• attachmentCount
• attachmentsMayBePartial

Comment/reply attachment fields

• type
• styleType
• url
• title
• label
• image
• viewerImage
• animatedImage
• playableUrl
• provider
• packName
• packId

This can be useful for comments that include stickers, GIF-style assets, images, or other supported attachment types.

Typical Use Cases

Collect only top-level comments

Recommended when:

• you want the fastest output
• replies are not needed
• you are creating simple monitoring dashboards

Collect comments with direct replies

Recommended when:

• you want conversation context
• you need direct audience responses
• you want a good balance between depth and speed

Collect comments with nested reply threads

Recommended when:

• thread structure matters
• you want to analyze back-and-forth conversations
• you are building richer moderation or analytics workflows

Notes

• This Actor is intended for public Facebook post links.
• Output shape may vary slightly depending on what is publicly available for a given post.
• Some posts may have no comments, limited replies, or limited attachment data.

Dataset-Friendly Design

This Actor is designed to be easy to use in downstream systems.

Why the output is useful:

• one clean record per post
• nested reply structure preserved
• user-friendly top-level post fields
• stable comment identifiers and URLs
• reaction summaries ready for analytics

Example Workflows

• Track comments on campaign posts every day
• Monitor recent replies on breaking-news posts
• Export nested discussions for moderation review
• Feed structured Facebook discussion data into AI pipelines

Need Consistent Filtering?

For best results:

• use Newest when freshness matters
• use a date range when you only need recent activity
• disable replies when you only need top-level discussion
• use Level 1 replies for lighter runs
• use Level 2 only when nested thread structure matters

Legal and Responsible Use

Use this Actor responsibly and make sure your usage complies with the terms and policies that apply to your use case, your jurisdiction, and the target platform.