DEV Community: Eli

Every Way to Export LinkedIn and Sales Navigator Data (and When Each One Actually Works)

Eli — Mon, 03 Aug 2026 18:47:49 +0000

A few months back I was running Sales Navigator searches for a client project — filtering down to "VP Sales, fintech, based in Italy or Spain" type lists — and the results were genuinely good. 60, 80 leads that actually matched. Then I hit the part nobody warns you about: there's no button on that page that says "save this."

So I did what everyone does. Opened a spreadsheet, alt-tabbed back and forth, typed names and job titles by hand. Around profile 40 I gave up and went looking for a better way. This is what I found, roughly in the order I found it, including the tool I ended up building because none of the existing options quite fit what I needed.

First: the export LinkedIn actually gives you

LinkedIn has a real, built-in data export, and most people don't realize how narrow it is. It's under your profile photo → Settings & Privacy → Data Privacy → Get a copy of your data. From there you either tick specific categories (that email usually lands within minutes) or request the full archive, which takes closer to a day and sometimes arrives in two batches. Either way you get a download link that expires after 72 hours — and it's desktop only, the mobile app won't let you request one.

What you get back is genuinely thorough: connections, messages, your own profile history, activity, even the ad-targeting data LinkedIn holds on you. A couple of quirks worth knowing before you rely on it: some connections' email addresses will just be missing, because sharing an email on download is something each person opts into individually, and you won't get a list of who viewed your profile or any "People You May Know" data. If you're in the EU, EEA, or Switzerland, LinkedIn also runs a separate API for pulling your data on a schedule rather than as a one-off request.

Here's what this export is not built for, though: it has no idea what you searched for yesterday. It's an archive of your own account, not a way to capture a live search. Run a Sales Navigator query and pull 80 leads, and this tool won't touch them — those results aren't "your data," they're a page LinkedIn rendered for you a minute ago. If you want a yearly backup of your own connections and messages, or you're about to deactivate and want a copy first, start here and you're done. If you're trying to get a search result out of the browser, keep reading.

Second: the manual way, which is what most people actually do

Copy the name. Copy the title. Copy the company. Paste into a column. Repeat.

It's fine for five profiles before a call. It's genuinely miserable past fifteen — you lose track of who you've already copied, columns drift out of alignment, and an hour later you've got a spreadsheet that looks like it survived a fall down some stairs. I don't think anyone picks this method so much as ends up in it by default, since it's the only option that needs zero setup.

If you only do this occasionally, don't overthink it. A blank spreadsheet and fifteen minutes beats installing anything. It only turns into a real problem once you're doing it every week.

Third: browser extensions, which read what's already on the page

Once you're pulling data regularly, the next step people reach for is a browser extension, and it's worth understanding what these actually do under the hood — "LinkedIn tool" covers a wide range of behavior, and the range matters.

The category I trust reads the DOM of the page you're already looking at, the same rendered HTML your browser downloaded to show you the search results, and turns the visible fields into rows in a file. It doesn't call a private API, doesn't need anything beyond the session you're already logged into, and doesn't do anything you didn't ask it to.

The category I don't trust is the one that also automates actions on your behalf: auto-sending connection requests, auto-messaging, "warming up" a profile with likes. That's a fundamentally different product, and it's the kind of behavior that gets accounts restricted, because LinkedIn's abuse detection is watching for exactly that pattern — a lot of actions, very fast, in a rhythm no human clicks in. Reading a page you're already viewing and writing what you see to a CSV is a much smaller ask than pretending to be a human sending 200 connection requests an hour.

What I ended up building

I looked for something that just read search results — Profile, Company, Jobs, and Posts on regular LinkedIn, plus Lead and Account search on Sales Navigator — and either couldn't find it or found it bundled with a dozen automation features I didn't want anywhere near my account. So I built the Mastros LinkedIn & Sales Navigator exporter.

It's read-only, on purpose. You run a search, the extension recognizes the page and shows you every field it found before you export anything, so you know what you're getting instead of finding out after. Set a limit, hit export, and it drops a CSV, JSON, or JSONL file. CSV opens straight in Excel or Sheets and imports cleanly into a CRM — something like:

full_name,job_title,company,location
Marco Bianchi,Head of Partnerships,Nordic Robotics,Turin
Sara Klein,VP Marketing,Fjord & Co,Copenhagen
Tomás Silva,Founder,Casa Verde,Lisbon

A few decisions I made on purpose, mostly because they were the things that annoyed me about other tools:

Nothing leaves your machine. Extraction runs in your browser; the data never touches a Mastros server. We don't see the names or profiles you save, only that a save happened.
No email guessing. It doesn't derive or buy anyone's email address. What's on the page is what you get.
Only new records. Turn this on and it skips anything you've already exported, so re-running a search doesn't just duplicate last week's file.
Safety pacing. There's an hourly cap that's separate from your monthly plan quota, specifically so a big export doesn't turn into the kind of rapid-fire activity that flags an account. Same reasoning as the automation point above: reading slower, on purpose.
No actions, ever. It doesn't send invites, messages, or InMails, and it doesn't like, follow, or apply to anything. You trigger every export yourself; it never acts on your behalf.

It's free for 250 records a month across all six search types, no card required. Pro is $9/month for 10,000 records with rollover on unused ones, and Scale is $18/month with no record cap from our side — LinkedIn's own rate limits still apply, because claiming otherwise would just be a lie.

Picking one

Backing up your own connections and messages, or prepping to deactivate → LinkedIn's own export. It's free, official, and already good at this.
A handful of profiles before a call, once in a while → copy-paste. Don't install anything for five rows.
Recurring prospecting, recruiting pipelines, or keeping a CRM fed from live searches → an extension built specifically to read search results, with pacing and dedup baked in. That's the gap the LinkedIn exporter is built to fill.

One last thing, easy to skip past: whichever method you use, the data is still about real people who didn't sign up to end up in your spreadsheet. Export what you're actually allowed to see, follow LinkedIn's terms, and don't turn a clean CSV into a cold-email blast nobody asked for. That's not a legal disclaimer, it's just the difference between doing research and being the reason someone locks down their privacy settings next week.

If you want to try it: it's a free Chrome install, 250 records a month, no card needed.

Getting a Telegram group's members and media into files you can actually use

Eli — Thu, 16 Jul 2026 22:18:17 +0000

There is a particular kind of annoyance that hits when you need Telegram data in a hurry. You are in a group with a few thousand people, or a channel full of photos, and you want a member list or all the media in a folder. Telegram will let you have it, eventually, but the path is not obvious and the built in tools are shaped for backups, not for the small targeted export you actually want.

I have done this enough times that I have a mental decision tree now. This post is that tree, focused on the two things people ask for most: a clean list of who is in a group, and the media out of a chat or channel.

Know what "have access to" means

Before anything, the rule that governs all of this: you can export what your own account can already see. Members of a group you are in, messages in chats you are part of, media in channels you follow. You cannot conjure participant lists that a channel hides, or pull from places you have not joined. Any tool promising otherwise is selling you a ban risk. Keep exports to data you legitimately have in front of you, and keep the downstream use lawful.

Getting the member list

Say you run a 5,000 person community and you want a roster with usernames and ids, maybe to cross reference against your CRM or just to see who is actually active.

The Telegram Desktop export (Settings, Advanced, Export Telegram data) is the official path, but it is built for a full account archive. You get a big JSON or an HTML dump, and carving one group's members out of it is more work than it should be.

The faster path is to read the participant list directly. Telegram exposes it through the client API, so anything speaking MTProto can page through participants and hand you name, username, id, and role. If you write code, GramJS or Telethon will do it in a dozen lines. If you do not want to write code, a browser extension that connects with your own API credentials will do the same paging for you and drop a file at the end.

Whichever way you go, the output you want looks like this:

{"user_id": 204817, "username": "ana_growth", "name": "Ana", "role": "admin"}
{"user_id": 512044, "username": "dvd", "name": "Davide", "role": "member"}

JSONL like that is my default for anything over a few hundred rows, because it streams cleanly into scripts and databases. CSV is nicer if a non technical teammate is going to open it in Sheets.

Getting the media

Media is where the manual approach really falls apart. Right clicking and saving four hundred photos is not a plan. You want the whole set, with each file still tied to the message it came from, so a picture is not just IMG_0421.jpg with no context.

Two things make bulk media painless:

Preserve the reference. A good export keeps sender, timestamp, and source chat next to each downloaded file, so you can rebuild who posted what.
Respect the rate limits. Telegram throttles hard, and hitting it triggers a FLOOD_WAIT that pauses you for a set number of seconds. Any serious downloader needs backoff built in, or you will spend the afternoon babysitting errors.

Web mode versus API mode

If you use a browser tool for either of the above, you will usually see two modes, and it is worth understanding the difference because it decides what you can pull.

Web mode reads what Telegram Web has already rendered in the page. Zero setup, good for the messages in an open chat and your recent contacts. It is limited to what is on screen, same as the WhatsApp side of things.

API mode (sometimes called power mode) uses your own api_id and api_hash from my.telegram.org to talk to Telegram over MTProto. This is what unlocks full member lists, mutual groups, and bulk media, because it is not limited to the rendered DOM. Your credentials stay local to your machine. This is the mode you want for the two tasks above.

The extension I reach for when I do not feel like scripting is Mastros. Being straight with you: it is a commercial product with a free tier, not an open library, so if you want to read or self host the code, GramJS is the honest recommendation instead. What the extension saves you is the plumbing: paging participants, FLOOD_WAIT backoff, keeping media matched to messages, and writing it all out as CSV, JSON, or JSONL. One quota detail if you try it: each media file counts as one message against the monthly allowance, so a big channel archive adds up quicker than a text only export.

The short version

Need one group's members: page the participant list over the API, either with GramJS or a no-code tool, and export JSONL or CSV.
Need the media: use an API mode downloader that keeps each file tied to its message and handles rate limits for you.
Need a full account backup and nothing targeted: Telegram Desktop export is genuinely fine.
Grab your api_id and api_hash from my.telegram.org first if you are going the API route, and keep your exports to data you actually have access to.

If the no-code route fits, the Telegram exporter is here: https://www.mastros.online/telegram-scraper. I wrote up the WhatsApp equivalent in a separate post, since WhatsApp gives you a lot less to work with.

How to export WhatsApp Web group members and chats to CSV (without the API)

Eli — Thu, 16 Jul 2026 22:14:19 +0000

WhatsApp is great at holding your data hostage. There is no "export group members" button, no "download my contacts" option, and the one export it does give you (Export chat) spits out a plain text file for a single conversation. If you run a community, do recruiting, or use WhatsApp as an informal CRM, you have probably hit this wall and ended up copy pasting names into a spreadsheet at 1am.

I want to walk through what you can actually pull out of WhatsApp Web, what you cannot, and the different ways to get it into a CSV or JSON file you can work with.

First, set expectations: you can only export what you can see

This part matters, because a lot of "WhatsApp scraper" tools online promise things that are not real. You cannot export:

Phone numbers that WhatsApp hides from you
Deleted messages
Chats or groups you are not a member of
A full history without scrolling to load it

What you can export is the data already rendered in WhatsApp Web:

Group members: display name, phone number when the group shows it, admin or member role
Loaded messages from an open chat: text, sender when shown, timestamps, forwarded and reply markers
Recent contacts from your chat list: names, last message preview, unread counts, numbers when visible

If a tool claims more than that, it is either lying or doing something that will get your account banned. Stick to visible, user initiated exports.

Option 1: Export chat (built in, very limited)

Open a chat, tap the menu, choose Export chat. You get a .txt file of that one conversation, optionally with media. It is fine for archiving a single chat, useless for member lists, and not structured, so you will be writing regex to parse it if you want it in a table.

Option 2: The WhatsApp Business API (overkill for most people)

If you are a business with real volume, the Cloud API is the "correct" answer. It is also a project: you need a Meta developer account, a verified business, a phone number dedicated to the API, and you have to write code against it. For "I just need this group's members in a spreadsheet," it is wildly disproportionate.

Option 3: Read what is on screen with a browser extension

This is the pragmatic middle ground. WhatsApp Web renders the member list, the chat, and your recent conversations in the DOM. A browser extension can read that rendered data and hand you a clean file, entirely on your machine.

I have been using a Chrome extension called Mastros for this. It is a commercial tool with a free tier, and the reason I reach for it is that everything runs client side. It does not phone home with your contacts, which is the bare minimum I want from anything touching a messaging app. Full disclosure so nobody feels tricked: it is a paid product, though the free tier covers small jobs.

The workflow is boring in a good way:

Install the extension and open web.whatsapp.com
A sidebar shows up with three modes: Group Members, Current Chat Messages, Recent Contacts
Open the group or chat you care about, scroll once to load the members or messages you want
Pick a format and export

You get CSV for spreadsheets, JSON for feeding another system, or JSONL if the export is large and you want to stream it line by line. Group members and contacts count as "profiles," messages count as "messages," which is worth knowing if you are on a plan with monthly limits.

A concrete example

Say you manage a 400 person community group and want a roster. Open the group, tap the subject to open the member list, scroll to the bottom so all 400 render, then run the Group Members export. You end up with something like:

name,phone,role,source_group,exported_at
Giulia,+39 347 ...,admin,Founders Circle,2026-07-16T14:22:00Z
Marco,+39 348 ...,member,Founders Circle,2026-07-16T14:22:00Z
Studio Alfa,+39 076 ...,member,Founders Circle,2026-07-16T14:22:00Z

Numbers only appear where WhatsApp itself shows them. For contacts already saved in your phone, you often see names but not numbers, which is expected.

Tips that save you time

Scroll before you export. The extension can only read what has rendered, so load the members or messages first.
Use JSONL for big pulls. CSV is friendlier for humans, but line delimited JSON is nicer when you are piping into a database or a script.
Deduplicate later. If you export the same group twice or overlap contacts, clean it in your spreadsheet or with a quick sort -u.
Respect the humans in the file. Exporting a group roster is not a license to cold blast everyone. Depending on where you and your contacts live, GDPR and similar laws apply, and consent matters. Use exports for record keeping, migration, and analysis, not spam.

So which one should you use

One chat to archive: built in Export chat is fine.
Serious business volume with engineering time: the Cloud API.
"I need this group or chat list in a spreadsheet, today, without writing code": a local browser extension is the least painful path.

The theme across all of them is the same. WhatsApp will not hand you a clean export, so you either parse a text dump, build against an API, or read what is already on your screen. Pick the one that matches how much time you have.

If you want to poke at the extension route, the WhatsApp exporter I mentioned lives here: https://www.mastros.online/whatsapp-scraper. There is a Telegram version too, which I will cover in a separate post because Telegram plays by very different rules.