How to export LinkedIn comments for reporting and moderation records

You need the comments off a specific LinkedIn post. Maybe it is for a monthly report, a sentiment check on how a launch landed, or a moderation record you want on file before you action anything. You open the post, look for the button, and there is no "export comments" anywhere. So you start copy-pasting by hand, and either you burn an hour at the end of every reporting cycle or the record disappears the moment the thread scrolls out of view.

Here is the thing most guides skip: they jump straight to installing a scraper. Decide what you actually need first. For a lot of reporting and moderation jobs, the honest answer is that LinkedIn's native export does not cover the case, and a third-party tool carries real terms-of-service risk you should weigh before you click install. By the end of this you will know exactly which method fits your need and what each one can and cannot give you.

Table of contents

• Before you start
• Decide what you actually need from the comments
• Check whether LinkedIn's native export covers your case
• Export a handful of comments manually
• Use a third-party export tool for bulk pulls
• Know what fields and format you will get
• Weigh the terms-of-service and compliance risk
• When exporting comments by hand stops working
• Put the exported comments to work this week

Before you start

This is a short list, not a setup ritual. Get clear on four things before you pick a method:

• Whose post is it. Your own post or Page versus someone else's changes what you can pull and how.
• Do you have admin rights on the Page, if it is a company Page rather than a personal profile.
• What the export is for: a report, a sentiment review, or a moderation/audit record. The use case drives everything downstream.
• Rough volume: a handful of comments on one post, or hundreds across many.

If you are a team of one pulling a few comments off a single post, you do not need any tooling at all. Skip ahead to the manual method. The rest of this matters most when volume climbs or when the record has to hold up later.

Decide what you actually need from the comments

Scope the job before you touch a tool, because the right method depends entirely on the shape of the data you need.

Two questions settle it. First: is this a one-off pull or a repeatable, ongoing export? Grabbing the comments on one campaign post is a different task from pulling comment data every week across a content calendar. Second: do you need the comment text and who said it (which is what a sentiment or moderation record runs on), or a flat list of who commented? Those are not the same output, and most tools optimize for one or the other.

For a reporting or moderation record, you almost always want three columns: author, timestamp, and the comment text itself. That is enough to build a sentiment split, track recurring themes, or document what was said before you moderate it. As an illustration, say you want to capture the five sharpest comments under a product-launch post for a monthly sentiment note. What you actually need is each commenter's name, the time they posted, and their exact words. Everything else is optional. If you are doing this seriously and want the sentiment read to reflect brand impact rather than raw positive-or-negative language, that is where brand-context sentiment scoring earns its place, since sarcasm and competitor praise get read the way a human would read them, not the way a keyword filter would.

Hold onto that data shape. It tells you whether native export, a manual pull, or a third-party tool is the honest fit.

Check whether LinkedIn's native export covers your case

This is the step nearly every guide gets wrong, so it gets the most room.

LinkedIn does have a native export, reached through Settings & Privacy, then Data privacy, using LinkedIn's data download tool. Request a copy of your data, choose the categories you want, and LinkedIn packages them into a file. One of those categories is Comments. Per LinkedIn's own documentation, the Comments category "Contains comments a member has made to posts, articles, shares, and collaborative articles. This includes the date and URL."

On turnaround: "If you select the larger download, you'll receive an email within 24 hours." Once it is ready, "The data will be available for download for 72 hours," so grab it inside that window or you request it again.

Now the limitation that trips people up, stated plainly. This exports the comments you posted, not the comments other people left on your post. Read that line from LinkedIn again: comments "a member has made." It is your outbound activity, keyed to date and URL. It is not the incoming conversation under your content. So if the job is "export the commenters and comments on my launch post," native export does not solve it. It never will, because that is not what the tool is for.

Where native export is genuinely enough: auditing your own brand account's outbound comments. If you comment from the brand handle on partners' or creators' posts and you need a record of what your account said and where, this is the clean, first-party, terms-compliant way to get it. For that specific job, stop here. You are done. For pulling other people's comments off your post, keep reading, and go in with clear eyes about the tradeoffs.

Export a handful of comments manually

For a small, one-off pull, the practical method is manual capture. Open the post, and copy the commenter name, profile link, comment text, and timestamp straight into a spreadsheet, one row per comment.

Watch for three things that go wrong. Replies collapse under "Load more replies," so a thread that looks short can hide a dozen comments you never expanded. Timestamps show as relative ("2d," "3w") rather than absolute dates, so convert them to real dates as you go or your record loses precision. And long threads are easy to lose your place in when you are scrolling and pasting at the same time.

The honest boundary: manual capture works for one post with a few dozen comments. Past that, it stops being worth your time fast.

Use a third-party export tool for bulk pulls

For larger or repeatable exports, practitioners reach for third-party browser extensions and export tools. The general workflow is consistent across them: install or authorize an extension (or connect through a login), point it at the post URL, run the export, and download the result as a CSV, Excel, or Google Sheets file.

Two things to understand before you rely on this. First, these tools act through your logged-in session. They are not tapping some official data pipe; they are reading the page as your account, which means the access is authenticated as you. Second, that same fact ties any risk to your account, which matters for the next step.

What typically goes wrong: these tools break when LinkedIn changes its markup, and they break quietly, so a pull that ran clean last month can silently return partial data this month. Results are often incomplete on long or heavily nested threads. And because the tool is acting through your session, any terms-of-service exposure lands on your login, not the tool's. Whatever you pick, spot-check the output against the live post before you trust it in a report.

Know what fields and format you will get

Set expectations for the file before you build anything on top of it. A typical export captures:

• Commenter name
• Profile URL
• Comment text
• Timestamp

Some tools also offer email enrichment, appending a guessed or matched email to each commenter. Treat that as a separate, higher-risk data practice, not part of core comment export. It is a different activity with its own privacy and compliance weight, and it is not something a sentiment or moderation record needs.

Formats are usually CSV, Excel, or Google Sheets. Reaction and like counts, plus reply threading (which comment is a reply to which), may or may not survive the export depending on the method, so if threading matters to your read, confirm it is there before you rely on it. For a sentiment or moderation record, the four fields above are the ones that carry the weight: text, author, and time are what you are actually reporting on.

Weigh the terms-of-service and compliance risk

This is the part the rest of the internet reduces to a single FAQ line. It deserves more, so here it is in full, without the panic.

Using an automated tool or extension to pull LinkedIn data typically runs against LinkedIn's own terms. LinkedIn's User Agreement, at Section 8.2, prohibits users from any effort to "Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services." That covers public and private data alike, and it covers the browser-extension route, since an extension is exactly one of the "browser plugins and add-ons" named in the text.

The real operational risk this creates is account-level: restriction or suspension of the account doing the scraping. That is a platform-enforcement question, and it is distinct from a criminal-law question, which is where the nuance comes in. In the hiQ Labs v. LinkedIn ruling (No. 17-16783, decided April 18, 2022), the Ninth Circuit addressed scraping of publicly available LinkedIn data. As the analysis of the case puts it, on a publicly available website there are no rules or access permissions preventing access, and so accessing that publicly available data cannot violate the U.S. Computer Fraud and Abuse Act (CFAA), the federal anti-hacking statute. In plain terms: for public data, the risk does not sit on the hacking-statute side. It sits on the contract side, meaning LinkedIn's own terms and the enforcement it can take against an account.

So how do you act on this? If you work for a regulated brand or you are running the export from a company account, check with legal before you point a third-party tool at LinkedIn. And where the volume allows it, prefer native export (for your own comments) or manual capture (for a one-off pull) over an automated tool. Both keep you clear of the terms question entirely.

When exporting comments by hand stops working

A spreadsheet workflow holds up until it doesn't. It breaks when the volume climbs across many posts at once, when comments come in across several languages, when activity lands after hours and nobody is capturing it, or when the record has to be continuous and defensible rather than a file someone pulled once. At that point the job quietly changes shape: it stops being "export a file" and becomes "continuously monitor and record the LinkedIn conversation." That is where an always-on moderation and sentiment layer fits, one that monitors LinkedIn comments and mentions as one covered channel and keeps a clear moderation audit trail as the record builds itself. The automation takes the volume off your plate so you spend your time on the judgment calls, not on copy-pasting; a human still reviews and decides.

One LinkedIn-specific reason the record matters more here than elsewhere: LinkedIn's hide mechanic is delete-only. There is no reversible hide the way some platforms let you tuck a reply out of sight and bring it back. Once you remove a comment on LinkedIn, it is gone, and so is your ability to reconstruct what was said unless you captured it first. That makes keeping your own export the difference between having a moderation record and having a memory of one.

Put the exported comments to work this week

You have the comments in a file. Here is the first concrete move, and it depends on why you pulled them.

If it was for a report, turn the raw rows into something a stakeholder can read in thirty seconds: a sentiment split (how much of the conversation was positive, negative, or neutral by brand impact), the recurring themes worth naming, and your response rate on the thread. If you want a repeatable structure for that, this walkthrough on building a social media report gives you the shape to pour the data into.

If it was for moderation, do one thing before you touch a single comment: save the export as a dated record first. Because LinkedIn hides by deleting, the moment you action a comment it is gone for good, and a record captured after the fact is no record at all. Export, date it, then moderate.

A one-off export answers this month's question. It does not keep answering next month's. If LinkedIn comments are a standing part of your work, the move is a routine that keeps the record continuous instead of rebuilt from scratch every reporting cycle, and this guide to managing social comments is a good place to start on the ongoing version of the job.