How to Export LinkedIn Post Likers to a CSV

The blunt answer first: LinkedIn has no native export for post reactions. Not on personal posts, not on company pages, not in Sales Navigator, and not in the API tiers normal companies get. Every method is a workaround.

There are three practical options: manual copy-paste, extensions or DIY scripts, and session-free tools that capture public engagement without acting from your account. They differ mainly in speed, completeness, and account risk. Here is each one honestly, including the math on when the free one stops making sense.

Method 1: Manual Copy-Paste (Free, Fine Under 50 Likers)

Manual export is not glamorous, but it is still the right answer for small posts.

Open the LinkedIn post, click the reaction count, and work from the reaction modal. This is the modal workflow from the guide on how to find who liked a LinkedIn post, with the extra discipline of capturing durable rows as you go. Start with a two-column spreadsheet: Name and LinkedIn profile URL. That is it. Do not try to build the perfect lead record during the first pass.

Middle-click each name in the reaction modal so profiles load in background tabs while the modal stays open. If your trackpad setup makes middle-click awkward, right-click and choose "Open link in new tab." The point is to avoid opening a profile, losing the modal, going back, waiting for LinkedIn to reload, and then trying to find your place again.

Once you have a batch of tabs open, copy each profile URL into the sheet next to the person's name. Close the tab and move to the next one. When the modal stops showing new people, scroll down until LinkedIn lazy-loads the next batch, then repeat.

Keep the first pass intentionally narrow. Name and profile URL are enough to create a durable source file. The profile URL matters more than headline or company because it lets you enrich, dedupe, and verify later. A name alone creates false matches, especially for common names and people who change jobs.

Do not grab headline, company, location, email, and notes during the copy pass. It feels efficient, but it doubles the time and increases errors. Capture the stable identifier first, then enrich the sheet in a separate pass when you are not fighting the LinkedIn modal.

The time math is the reason to respect the limit. A clean manual process takes roughly 45 to 75 seconds per liker all-in once you include opening the profile, copying the URL, pasting it, and keeping your place. Thirty likers is fine. You can finish in half an hour and still have useful context in your head.

Three hundred likers is different. At one minute per person, the raw copy step is five hours before enrichment, qualification, deduping, email finding, or CRM import. At 75 seconds, it is more than six hours. That is a lost day for one post.

Use manual export when the post is small, the list matters enough to inspect personally, and account safety is non-negotiable. Stop using it when the work becomes recurring.

A Faster Manual Variant

There is a faster manual variant if you only need names and headlines. Scroll the reaction modal all the way to the bottom so LinkedIn loads the full visible list. Select the text in the modal, copy it, paste it into a spreadsheet, and clean the rows with formulas.

This can be useful for a quick market scan, but it has two hard limits. The modal lazy-loads, so you must scroll first. More importantly, profile URLs do not come with the copied text. You get names and snippets, not durable lead records.

Method 2: Extensions and DIY Scripts (Fast, Risky)

The second category is browser extensions, local scripts, and scraping recipes that read the reaction modal from inside your logged-in LinkedIn session.

Mechanically, these tools do some version of the same thing. They inspect the page, collect names and profile links, scroll the modal, and export rows to CSV. Some go further and call LinkedIn's internal endpoints from your authenticated browser context. That is why they feel fast: the tool can move through the modal faster than a human and can keep state cleanly.

That is also why the account risk is real.

LinkedIn's detection does not need to know your intent. It can look at request volume, scrolling behavior, click timing, endpoint patterns, and repetition across posts. A human does not open hundreds of profiles at perfectly regular intervals. A browser automation often does.

A restriction usually starts softly. You may see a warning, a temporary lock, a verification challenge, search limits, or profile-view limits. If the pattern continues, the risk becomes losing access to an account your pipeline depends on.

That is the part most "export LinkedIn likes" tutorials understate. If you run the extension from your founder's profile, head of sales profile, or main SDR profile, the downside is not just a broken workflow. It is your network, inbox, posting surface, and saved context.

There is a fair argument in the category's favor: it is fast and cheap. Some people run these workflows for years on secondary accounts, low-volume settings, or accounts they are willing to burn. If the account is disposable, this is your call.

If the account is not disposable, do not use it as the engine for scraping.

Method 3: Session-Free Tools (Safe, Paid)

The safer paid category is session-free capture: tools that work from a public post URL or a tracked public profile without logging into your LinkedIn account, installing a Chrome extension, or clicking through your session.

The input differs by tool. Some take a single post URL and return the visible people who reacted. Others let you track profiles over time so new posts and new engagement are captured automatically. The output can be a CSV, Excel file, webhook, outbound-tool export, or CRM push.

The important distinction is account boundary. A session-free tool is not automating your seat. It is not driving your browser. It is not making LinkedIn requests as you. That makes it the conservative route for teams that cannot afford an account restriction.

The per-lead math matters more than the sticker price. If a tool charges $20 to export a post with 400 likers, capture alone costs $0.05 per raw profile. If only 40 of those people fit your ICP, the effective cost is $0.50 per qualified candidate before email enrichment. If verified email costs another $0.10 to $0.30 per hit, your real unit cost depends on the qualified, contactable list, not the raw reaction count.

That is why a cheap raw export can still be expensive operationally. Someone still has to enrich, score, dedupe, and route the list. The safest tool is the one that avoids your LinkedIn session. The most useful tool is the one that also reduces the cleanup work after capture.

The Linked Panda Version: Export a Qualified List, Not a Raw One

A raw CSV of 400 likers is a chore, not an asset.

Some of those people are buyers. Many are peers, fans, recruiters, vendors, job seekers, students, or people outside your market. A spreadsheet does not tell you which is which. It just moves the sorting problem from LinkedIn into another tab.

Linked Panda is built for the qualified-list version of this workflow. Track the profiles whose posts attract your buyers: your own team, competitors, partners, customers, or category voices. When those posts get likes and comments, Panda captures the engagers without using your LinkedIn session.

Then the lead record gets built. The profile is enriched with B2B data, checked for a verified work email when available, scored against your ICP, and kept with source context: which post they engaged with, what action they took, and when it happened.

The export is not "everyone who clicked like." It is the shortlist: fit score, company, role, verified email, reaction source, and reason codes your sales team can actually use. Send it to CSV when you want a file. Push it to your CRM when you want reps to work the leads directly.

Pay-as-you-go starts with a $10 top-up, with no subscription and no card on file. At one credit per new profile and one additional credit when a verified email is found, that is roughly 100 profiles end to end when every profile gets a verified email.

What Your CSV Should Contain

A usable LinkedIn liker export should contain more than names.

At minimum, include name, profile_url, headline, current_company, reaction_type, post_url, capture_date, and source. If you enrich the file, add work_email, email_status, company_domain, seniority, location, icp_score, and qualification_reason.

The capture date matters because engagement is a timing signal. A like from yesterday can shape a timely follow-up. A like from nine months ago is mostly historical context, and the person's role or company may already have changed.

Most teams should treat the CSV as an intermediate file, not the final system of record. The real work is turning the raw CSV into scored records with current company data, verified contact details, and a clear reason each person is worth routing to sales.

FAQ

Does LinkedIn have a built-in way to export post likes?

No. There is no CSV export on personal posts, company page posts, or Sales Navigator. Company page admins get aggregate analytics such as totals and audience breakdowns, not the person-level list of people who reacted.

Can I export likes from someone else's post?

Yes, if the post and reaction list are visible to you. Reaction lists on public posts are visible to viewers, which is what makes competitor post mining work. Manual copying and session-free tools both handle this.

What you cannot reliably see is reactions from members whose privacy settings, network visibility, deleted accounts, or audience restrictions hide their activity from you. If the count and the visible list do not match, read why LinkedIn does not show all reactions before assuming your export missed something fixable.

Is exporting likers against LinkedIn's terms of service?

LinkedIn's terms prohibit automating your own account and scraping through automated access to their services. That is why the extension and DIY script category carries account risk.

Working from public data without automating your session is the conservative approach. This is not legal advice. Read the terms, understand your own risk tolerance, and keep your sales workflow compliant with the laws that apply to your market.

Can I export likes from a LinkedIn company page post?

Yes. The public reaction list on a company page post works much like the reaction list on a personal post, so the same three methods apply: manual copy-paste, session-based extensions or scripts, and session-free capture tools.

The admin analytics view is different. It can show totals and demographics, but it does not give you a native person-level CSV of everyone who liked the post.

How do I get emails for the people in my CSV?

A LinkedIn profile URL alone is not contactable. You need an enrichment step that finds the person's current company, identifies a likely work email, and verifies whether that inbox is deliverable.

We wrote up that exact workflow in the guide to finding work emails for LinkedIn post engagers.