Facebook holds the longest-lived comment threads on the internet. A local business post from eighteen months ago is still collecting questions; a Page video that went viral has 6,000 comments nobody has read past the first screen. Facebook lets you scroll them and gives you no way to keep them — and the Graph API, which could, stops at Pages you administer. Here's how to download Facebook comments free in 2026, with no developer app and no app review.
Permalink in, spreadsheet out
- Copy the post permalink. Click the post's timestamp, or use Share → Copy link, to get a direct URL to the post or video.
- Paste it at the Facebook comment downloader. No login, no token, no app.
- Check the preview and decide whether to include nested replies.
- Save as CSV, Excel or JSON. First 100 comments free on any post.
Free covers the first 100 comments per post with no account, no email and no daily limit, so checking twenty posts costs nothing. Bigger threads unlock with a one-time payment — for that post, or for a pass covering everything you touch over a few days. Nothing renews, and the preview always comes before the decision.
The Graph API dead end
Meta's comments edge is well documented and reliable — for content you own. Reading comments on a Page requires a Page access token for a Page you administer, plus permissions that go through app review. No version of that flow returns comments on a competitor's Page, a public group, or a viral video from an account you have nothing to do with.
That restriction has tightened steadily since 2018 and isn't loosening; the deprecation list in the Graph API changelog is a one-way street. So the split is the same as on Instagram: your own Page → Graph API; everything else → a downloader that reads the public thread.
What you can and can't get
- Public Page posts and videos — yes.
- Public group posts — yes, if the group itself is public.
- Private or closed groups — no. Not publicly visible, so not readable by anything.
- Personal profile posts set to Friends — no, same reason.
- Posts with comments turned off — an empty file, legitimately.
- Comments hidden by the Page's moderation filters — not public, so not in the file.
The rule is consistent: if a logged-out visitor can see it, it can be downloaded. If not, nothing can.
Facebook's real edge: threads that never die
Every other platform's comment lifecycle is measured in days. Facebook's runs for years, and that changes what the data is good for.
- Seasonal patterns become visible. Pivot the timestamp column by month on a busy local Page and the complaint cycle appears — the same issue every summer, the same question every December. No single-post analysis produces that.
- Old posts keep generating leads. A two-year-old post about a service still collects "is this available?" comments, and on a large Page nobody reads that far down. Downloaded and filtered, those are unworked leads sitting in public.
- Community memory is searchable. Local groups accumulate recommendations; searching the text column for a business category returns years of word-of-mouth in one place.
The trade-off is volume — Facebook threads get big and repetitive, which is exactly why a spreadsheet beats the feed.
Which columns do the work
Rows carry author, username, avatar_url, text, likes, replies, created_at, language, is_pinned, id and reply_to_id, with Facebook's reaction breakdown following behind. Two deserve attention:
- likes (reactions on the comment) — sort descending first. On Facebook the top-reacted comment is very often a complaint or a correction, which is the useful part rather than the embarrassing one.
- replies — the marker for arguments and for questions the Page never answered. High replies with low reactions is usually a fight; high replies with high reactions is usually a question everybody had.
For file type: Excel handles long multilingual comment text and reaction counts without an encoding step, CSV is smaller and universal if you import as UTF-8, and JSON suits dashboards and pipelines.
Four jobs a Facebook download does well
- Local reputation triage. A restaurant, clinic or shop Page repeats the same five complaints across dozens of posts. Download the busiest ones, filter for the product or service name, and the pattern appears in one pivot instead of six months of anecdote.
- Lead capture from a viral post. "Is this still available?", "How much?", "DM me" are leads with a name attached, and on a thousand-comment post most are never answered. Filtered, they're a call list.
- Competitor Page teardowns. Their unanswered questions are your FAQ page; their complaints are your positioning brief.
- Giveaway draws. Facebook competitions draw thousands of tag-a-friend entries. Download, filter for the condition, randomise a row, screenshot it — an audit trail that matters the first time a losing entrant disputes the result.
Public groups are the underrated source
Most people think Page posts when they think Facebook data, and skip the part that's often more valuable. Public groups — local buy-and-sell, neighbourhood boards, hobby and profession communities — carry conversations that exist nowhere else on the internet, and they are unusually commercial: people ask for recommendations by name and answer each other honestly, because nobody in the thread is selling.
Three things a public group thread gives you that a Page post won't:
- Unprompted brand comparisons. "Who do you use for X" threads are a local market survey with real respondents, and the replies name the businesses people actually rate.
- Price expectations. Members quote what they paid, which is a pricing study you'd otherwise commission.
- Language your customers use. Group posts are written casually and specifically — good raw material for ad copy that doesn't sound corporate.
The constraint is the same as everywhere: the group and the post have to be public. A closed group is invisible to every tool, including this one, and no amount of membership on your personal account changes what a logged-out visitor can see.
A reputation report in twenty minutes
Four pivots, and a client will actually read the output:
- Comments per week — an engagement trend that doesn't depend on reach numbers a Page owner may not share.
- Top 20 by reactions — the audience's own summary of what matters.
- Question-mark rows, grouped by topic — the FAQ the Page should have published, ranked by demand.
- Reply coverage — how many top-level comments got a Page response. Unanswered questions on a business Page are the most visible and cheapest failure to fix.
Run the same four against a competitor's Page and the comparison writes the pitch by itself.
Covering a whole Page, post by post
Facebook is the one platform where the useful unit is a Page rather than a post, because the same conversation is spread thin across dozens of threads. Doing it properly is mechanical:
- List the Page's highest-engagement posts from the window you care about — a quarter is usually enough, and the busiest ten posts carry most of the signal.
- Download each one. Free at 100 comments per post covers the small ones outright, and a single pass covers the whole list when the big threads matter.
- Stack the files into one sheet with a post column, so every row knows where it came from. This is the step people skip, and it's what turns ten files into one dataset.
- De-duplicate people, not comments. On a local Page the same twenty names appear everywhere. Counting unique commenters rather than comments is what separates a genuinely engaged community from a small group talking loudly.
- Then run the pivots. Recurring complaints, unanswered questions, seasonal spikes — all of them only appear once the posts sit in one table.
An hour of this on a competitor's Page produces a picture their own community manager probably doesn't have, because nobody inside the business ever reads the old threads.
Why you can trust these numbers
We build and run the Facebook downloader described here, so what follows is operating experience rather than a summary of Meta's docs:
- Facebook's comment counter is the least literal of any platform's. It counts replies, filtered comments and comments from deactivated accounts, so a 15–30% gap between the badge and the readable rows on an older thread is routine rather than a fault.
- Page-one responses are small. Facebook's comment feed returns very few comments on the first request and more on subsequent ones, which is why a preview fetches an extra page before showing you anything — without it, a healthy thread looks empty.
- Permalink shape matters. Some post URL formats carry the comment total and some do not; when one does not, the count takes longer because it has to be established another way. That is why we ask for the timestamp permalink rather than whatever link is in your clipboard.
Caps and column names here are the live values on the product, and every claim about Meta's platform rules links to Meta's own documentation so you can check it yourself.
Take the file before the thread goes
Facebook content feels permanent and isn't. Pages get unpublished when a business closes or rebrands. Posts are deleted when a promotion ends — routinely, with the comment thread attached. Groups go private with one admin click, putting years of public discussion out of reach in a second. Individual comments disappear constantly, disproportionately the complaints and buying questions.
None of it is recoverable from outside afterwards. If a thread will matter — for a reputation report, a competitor study, a compliance record, a lead list — take the file while the post is live. At the free tier that's two minutes.
Where the legal line sits
Analysing publicly visible content is standard practice; the obligations are downstream. Comments contain personal data, so under GDPR and similar regimes you need a lawful basis, a retention limit and a way to honour deletion requests — the GDPR overview covers it. Aggregate before you present, keep names out of published conclusions, and delete raw files when the project ends.
Download Facebook comments free → First 100 free, no signup, no daily limit — paid unlocks are one-time, never a subscription.
Related reading: Facebook comments to Excel · into Google Sheets · the longer Facebook guide.