1
Facebook Comments Scraper
Scrape every public comment on any Facebook post, video or reel — all 7 reactions & reply threads.
Trusted worldwide by the best
Export comments from Facebook — right now
Extract
Paste any Facebook post, photo, video or reel and get every public comment with its author, date and time, likes, the seven reaction counts, reply threads and attachments — 28 data points per comment.
Schedule
Automate Facebook data collection on daily, weekly, or monthly schedules.
Export
Export all comment data to Google Sheets, email, or S3 — fully automated.
Built for Agents
Run it from your stack.
Or hand it to your agent.
Facebook Comments Scraper ships with a Python SDK, a one-line CLI and a native MCP server your agents can plug into directly — no rate limits to dodge, no bot mitigation to bypass, no parsing errors to chase down.
# install once (Python 3.10+)
pip install lobstrio
# check your token
lobstr whoami
# find the scraper
lobstr crawlers search "Facebook"
# one call — launch, wait, download
lobstr go facebook-comments-scraper \
"<any Facebook URL>" \
--param max_results=200 \
-o results.csv28 data attributes per comment
Every scrape returns structured data you can export as CSV, JSON, or via API.
Unique Facebook identifier of the comment
Unique Facebook identifier of the post the comment belongs to
Canonical URL of the post the comment belongs to
Full text content of the comment, empty when the comment only carries a photo, GIF or sticker
Date and time the comment was posted, in UTC
Language Facebook detected for the comment
Display name of the comment author
Facebook identifier of the comment author, a pfbid token or a numeric user id
URL of the comment author's Facebook profile
Fast
312 comments per minute
Lightning-fast performance
Solid
99.95% task success rate
Dependable, reliable data every time
Cost-competitive
$0.5 per 1000 comments
Top affordability worldwide
Built to run.
Most scrapers break in silence. This one doesn't — and we show it, openly.
incident-free runs · last 90 days
Tracked from every run. Incidents stay on the record even after they're fixed.