Up front, because it matters: this exporter does not bypass Facebook privacy. It can't read posts in groups you haven't joined, it can't see content from people who didn't accept your friend request, and it can't see anything Facebook has already hidden from your view. What it can do is export the comments and reactions on posts your own logged-in session already sees — closed groups you're a member of, friends-only posts from people who friended you back, private brand pages where you have admin or member access. Your auth token never leaves your browser. Here's how the Facebook Private Posts exporter works and the workflows it actually solves.

What "private" means here

Facebook's privacy model has more layers than Instagram's, so it pays to be explicit about which slices the extension can and can't reach.

What you can export:

  • Posts inside closed or private Facebook Groups you've been admitted to.
  • Friends-only posts from people who accepted your friend request.
  • Posts on private brand pages where you have admin, editor, or member-level access.
  • Your own personal posts, regardless of audience setting.
  • Posts with custom audiences (specific friends, specific lists) where you're on the audience.

What you cannot export:

  • Posts in groups you haven't joined or that haven't approved you.
  • Friends-only posts from people who didn't accept your request.
  • Posts hidden from you specifically (blocked by the author or filtered).
  • Anything deleted before you ran the export.
  • Messenger conversations — this is for posts and comments, not DMs.

The principle is the same as the Instagram exporter: if you can scroll to the post in your own logged-in browser, the extension can capture the comments. If you can't see it manually, the extension can't either.

Why a browser extension

This one has a specific history. Before 2018, Facebook's Graph API exposed a wide range of post and comment endpoints that third-party tools could use with user permission. The Cambridge Analytica fallout shut nearly all of that down. Today, the Graph API is locked to Pages you own (with a verified Business account), with strict review processes and zero access to private content from people you're connected to or groups you're a member of.

Practically, that leaves the browser extension as the only realistic path. It runs inside your own logged-in Facebook session, reads the same data the page already loaded for you, and turns it into a structured CSV, Excel, or JSON file. Nothing about your account credentials passes through ExportComments. The extension is doing manually what the API used to do programmatically — and only for content your own eyes can already see.

How to install the extension

Step 1: Install from the Chrome Web Store

Open the ExportComments browser extension page and add it to Chrome (Edge, Brave, and other Chromium-based browsers work too). It only requests access to facebook.com — that's the only page it needs to read.

Step 2: Log into Facebook normally

Open facebook.com in the same browser and log in. The extension reads from the active session, so the account you log in with determines what private posts are visible. If you want to export a closed group's comments, log in as a member of that group. If it's a friends-only post, log in as the friend.

Step 3: Open the post

Navigate to the post in question — in the group, on a friend's profile, on the private page, or in your own activity log. Click into the post so the comments tray is fully visible. The extension watches for the comment thread to render before it starts capturing.

Step 4: Click the extension icon and pick a format

Click the ExportComments icon in your browser toolbar. Choose Excel for sortable spreadsheets, CSV for downstream scripts, or JSON when you need clean structured data. The extension scrolls the comment thread, expands every "View N more comments" and "View N replies" link, captures reactions per user, and assembles the file in your browser.

Step 5: Save and review

The file lands in your default downloads folder. Open it in Excel, Numbers, Google Sheets, or any analysis tool. Each row is a single comment from the post you were viewing — sortable by time, by reaction type, or by author for whatever workflow you're running.

What you get in the export

One row per comment, with the columns Facebook actually exposes in the post view:

  • Author name — the commenter's display name as shown on the post.
  • Profile URL — direct link back to the commenter's profile (or page, for page comments).
  • Comment content — full text of the comment.
  • Reaction type per user — the specific reaction each reactor left, captured per user.
  • Like count — total Like reactions on the comment.
  • Love count — total Love reactions.
  • Care count — total Care reactions.
  • Haha count — total Haha reactions.
  • Wow count — total Wow reactions.
  • Sad count — total Sad reactions.
  • Angry count — total Angry reactions.
  • Created at — original timestamp in UTC.
  • Edited at — timestamp of the last edit, if the comment was modified after posting.

The six-reaction split (Like, Love, Care, Haha, Wow, Sad, Angry — Facebook removed the original positive/negative balance and ended up with seven if you count Like itself) is the column most analysts ask about. It lets you actually distinguish supportive engagement from sarcastic Haha reactions, which is harder to do at a glance in the Facebook UI.

Common workflows

  • Closed-group community moderation — pull the comment thread on a flagged post to review the full context with timestamps, before any moderator action that might prompt deletions.
  • Group-membership audit — export the comments on a series of posts to identify which members are actually engaging versus lurking, useful when reviewing a community for inactive purges.
  • Reaction-type analysis — sort by Angry or Sad columns to surface posts that landed badly, or by Love and Care to find the messages that resonated emotionally.
  • Brand-page private campaigns — for invite-only or members-only campaigns running on a private brand page, export the comments to measure response without needing API approval.
  • Personal-history archive — periodic backup of the comments on your own posts, especially before deleting an account or migrating to a new profile.
  • Closed-group giveaway picker — export the comments on a giveaway post inside a closed group, then pick a winner with a random-row formula or hand the file to the giveaway picker.

Privacy and safety

Will I get banned? The extension reads the page the same way your browser already does. It doesn't impersonate a different client, doesn't make hidden API calls, and doesn't request anything beyond what the page has already loaded. The traffic pattern looks like an unusually patient scroller. We've seen no enforcement actions tied to extension use, but Facebook does change its rules — for high-value accounts, run during off-hours and avoid bulk runs in the same session.

Does ExportComments see my data? No. The extension runs entirely in your browser. Your Facebook session token stays in the browser process. The file is generated locally and saved to your machine — it doesn't pass through ExportComments servers. The extension is open code in the published package; you can inspect it before installing.

Plan limits and API access

Free returns up to 100 comments per export, enough to confirm the format and verify your target post is reachable. Personal scales to 5,000 comments, Premium to 50,000, and Business to 250,000 — enough to archive even the busiest closed-group threads in one pass. The website-side exporters support bulk URL upload (one file per URL bundled in a single ZIP) for any public posts you're processing alongside private content. The REST API with webhook delivery handles public Facebook content; private content stays browser-extension only by design, because there is no Graph API endpoint for it. See the pricing page for the full grid.

FAQ

  • Can the extension join groups for me?
    No. It only reads content visible to your current logged-in session. If you haven't joined the group, or your join request hasn't been approved, the posts are invisible to your browser and to the extension.
  • Does it capture nested reply threads?
    Yes. The extension expands every "View N replies" link as it scrolls the thread, so reply chains appear in the file alongside the parent comments.
  • Why are there separate columns for each reaction type?
    Because the analysis question is usually "how did people actually feel about this," and a single "reactions" total flattens that. Splitting Like, Love, Care, Haha, Wow, Sad, and Angry into their own columns lets you sort by emotional response — particularly useful for surfacing sarcastic Haha clusters or genuine Care responses.
  • Will it work on private Facebook Pages I admin?
    Yes. If you have admin, editor, or any member-level access to the page and can see the post in your logged-in browser, the extension can export the comments. For Pages you own with a verified Business account, you can also use the official Graph API for programmatic access.
  • What about edits and deletions after I export?
    The exported file is a snapshot at the moment of export. If a comment is edited or deleted afterward, your file is unchanged — which is exactly why exports are useful for moderation and evidence workflows.
  • Why isn't there a Graph API option for closed-group comments?
    The Cambridge Analytica fallout in 2018 led Facebook to remove most Graph API endpoints that third-party apps used to read content from groups, friends, or other private surfaces. Today the API is scoped to Pages you own with verified business access — closed-group comment access via API has not existed for years and there's no signal it's coming back. The browser extension fills the gap by working only with content you can already see yourself.