Alpha: the Chrome Web Store listing is still in review. Download the extension and load it unpacked. Download for Chrome
Export

Export LinkedIn post commenters to CSV

Listful exports post commenters from a post permalink to CSV — profile URL, name, headline, location, and comment_body when present. Free, no account, no row credits. Listful ceiling 3,000. Nested replies may not all appear.

Download for Chrome — free
Alpha download · load the folder in Chrome · no account, no card
URL pattern
/posts/… · /feed/update/…
01

Why this list

Intent — not a second pitch.

Commenters leave words, not just a reaction badge. That text is often the difference between a cold list and a reply you can quote. Listful pulls commenter profiles plus comment_body from the same permalink you use for reactions — separate job, same session.

02

What LinkedIn won’t give you

Native UI gaps on this surface.
The comments thread is scroll-only. LinkedIn will not export commenters or comment text to CSV. Nested replies are easy to miss by hand on long threads.
03

How it works

Three steps. No funnel.
01

Install Listful

Add the Chrome extension from the Chrome Web Store. CSV download needs no Listful account.

02

Open the post permalink

Same requirement as reactions: /posts/… or /feed/update/… with a post id. Company feed alone will not mount the export.

03

Export comments

Choose Export comments (not reactions). One row per commenter profile, with comment_body when LinkedIn returns it. Nested replies may be incomplete.

04

Worked example

A concrete scene.
Setup

A founder opens their own hiring post permalink and wants everyone who asked about remote policy.

Outcome

The comments CSV includes profiles plus comment_body so they can filter for “remote” in Sheets before outreach. Replies buried under long threads may be missing — the file matches what the comments API returned.

05

CSV columns

What lands in the file.
FieldDescription
profile_urlCanonical /in/ URL when LinkedIn provides one.
full_nameDisplay name as returned by LinkedIn.
headlineHeadline text. May be empty.
locationLocation string when present.
comment_bodyComment text as LinkedIn returned it.
first_nameFirst token of the commenter name.
last_nameRemainder of the commenter name.
summaryCommenter subtitle from the comment card.
linkedin_profile_idMember id decoded from the commenter profile id when possible.
sales_navigator_profile_idCommenter profile id from the comment payload.
linkedin_profile_handlePublic /in/ handle from the commenter URL.
profile_image_urlCommenter photo when the comment card includes it.
connection_degreeDegree text on the commenter card when present.
linkedin_people_post_search_urlContent search scoped to this profile id.
comment_timeComment created time when LinkedIn returns it.
comment_like_countReaction count on the comment when social counts are in the same payload.
comment_reply_countReply count when social counts are in the same payload.
linkedin_comment_urlComment permalink when present.
linkedin_comment_idComment id parsed from the social detail URN.
linkedin_post_urlThe post URL for this export.
linkedin_post_idActivity, ugcPost, or share id from that URL.
last_replyText of the first nested reply in the same comments payload, when one is present.
Sample rows · illustrative
  • Casey Quinn
    Product Manager · Marketplace · Berlin, Germany
    /in/example-i/
    comment_body Curious if this role is remote-friendly?
  • Avery Soto
    Engineering Manager · Consumer · Mexico City
    /in/example-j/
    comment_body Strong take — we saw the same hiring pattern.
06

Limits

As of September 2026. LinkedIn may stop returning pages earlier.
Up to ~3,000 when LinkedIn keeps returning pages
What you usually get
3,000
Listful ceiling (if LinkedIn keeps paging)
10×300
Page size × max pages
Needs a post permalink with an activity / ugcPost / share id.
Company-page commenters are skipped (parser ignores companyUrn actors).
Nested replies may not all appear — we export what the comments API returns.

Full limits table →

07

When not to use this

Company-page commenters as orgs (companyUrn actors skipped)
Guaranteeing every nested reply
Posts without an activity / ugcPost / share id

Full unsupported list: what Listful does not export.

08

Questions.

Short answers on this surface.
Q01Can I export LinkedIn post commenters for free?

Yes. Open a permalink, export comments. No Listful account or row credits for CSV.

Q02Is comment text included?

Yes when LinkedIn returns it — column comment_body.

Q03Do I get every reply under a comment?

Not always. Nested replies may not all appear; Listful exports what the comments API returns.

Q04How many commenters can I export?

Up to 3,000 rows. LinkedIn often stops around that same cap.

Q05Different from exporting likers?

Yes. Likers/reactions have no comment text. Use the post likers page for reactors.

Q06Does Listful scrape comments?

It paginates the comment list on a post you opened. Session stays in the browser.

Q07Why did company-brand comments disappear?

Company URN actors are skipped. Person commenters still export.

Q08Same URL as reactions?

Yes. Same permalink; reactions and comments are separate export jobs.

Q09Empty file?

Confirm the permalink (not a feed card), that comments are visible to your account, then re-run Export comments.

Q10Emails in the comments CSV?

No — only after optional enrichment.

Q11Will this post or reply for me?

No. Read-only export of the comment list.

09

Related

Free CSV

Export this listfrom Chrome.

No account, no row credits. LinkedIn’s own page caps still apply — see the limits guide.

Download for Chrome — free
Alpha download · load the folder in Chrome · no account, no card