LinkedIn saved posts

How to export all your LinkedIn saved posts

LinkedIn lets you save posts, but it does not provide a native full-content bookmark export. Here is the practical way to turn the entire saved-post list into files you can search, organize, back up, and reuse.

Why the LinkedIn Saved Items page is not an export

LinkedIn’s Saved Items screen is a reverse-chronological reading list. You can open or unsave individual posts, but there is no native button that downloads the complete bookmark collection with the post bodies intact. That distinction matters: a useful export needs the words you saved, not merely a route back to LinkedIn.

Full text is what makes the collection searchable. Author names let you group recurring sources. Original URLs preserve attribution. Dates provide context. Engagement counts, hashtags, and mentions can help with filtering. Without those fields, every research task sends you back into the same scrolling list.

Export LinkedIn saved posts step by step

  1. Install LinkedIn Bookmark Exporter from the Chrome Web Store.
  2. Open the extension and activate it with your license key.
  3. Sign in to LinkedIn in the same Chrome profile.
  4. From LinkedIn Home, select Saved Items, then Saved posts and articles.
  5. Open LinkedIn Bookmark Exporter and choose Markdown, CSV, or JSON.
  6. Start the export and keep the LinkedIn tab open. The extension auto-scrolls through the history and expands truncated “see more” text while it collects the records.
  7. When processing finishes, download the file to your computer and open it before closing the LinkedIn tab.

Everything is processed locally in the browser; the extension does not require you to hand over your LinkedIn password or upload the saved-post archive to a GrabKit server. It works with the LinkedIn session already open in Chrome.

What LinkedIn Bookmark Exporter captures

FieldWhy it is useful
Full post textSearch exact phrases, read offline, and analyze the substance of a post
Author name and profile linkFilter by source and return to the author
Original post URLVerify context, attribute ideas, and deduplicate records
DateSort by recency and avoid using stale advice without context
Reactions and commentsCompare response patterns without treating popularity as proof
Hashtags and mentionsCreate initial filters and identify people or topics referenced

The resulting file is a snapshot of what the saved-post page could load at export time. It cannot recover a post that was already deleted, made inaccessible, or removed from your saves before the export. That is why exporting periodically is more reliable than waiting until you urgently need an old bookmark.

Markdown, CSV, or JSON: which export format should you choose?

Choose Markdown for reading and knowledge tools

Markdown keeps headings, paragraphs, and links readable in plain text. It is the cleanest starting point for Obsidian, a document-style Notion page, Git, or a private AI research project. It is also resilient: you can open it without a particular spreadsheet or database product.

Choose CSV for sorting, tagging, and Notion databases

CSV is better when every post should become a row. You can filter by author, saved date, hashtags, or engagement; add columns such as Topic, Status, and Why I saved this; and import the result into Notion, Airtable, Excel, or Google Sheets.

Choose JSON for scripts and integrations

JSON preserves field names and nested values without flattening everything into cells. Pick it when you plan to write a script, load the archive into a database, or pass individual records through an automation. If you only want to read the archive, JSON adds friction without much benefit.

If you are unsure: choose CSV for a filterable working database and Markdown for a readable backup. You can run the exporter again in another format; you do not have to force one file to serve every use case.

Run a five-minute quality check

  • Compare the number of exported records with the count you expected.
  • Open a long post and confirm that the text was expanded rather than cut off at “see more.”
  • Click several source URLs and check that they point to the correct original posts.
  • Confirm non-English characters, emoji, and line breaks survived the export.
  • Check that author and date fields are not shifted into the wrong CSV columns.
  • Store an untouched copy before adding tags or editing rows.

Infinite-scroll pages can change, and posts can use different layouts. A successful download notification proves that a file was created; it does not prove that every record is complete. The spot check is the part that turns an export into a dependable archive.

Turn the file into something you will actually use

Do not begin by tagging every old post. Start with the task that made you want the export:

Refresh the archive without creating duplicates

LinkedIn does not expose a neat incremental bookmark feed, so treat each run as a dated snapshot:

  1. Export monthly if you save posts frequently, or quarterly if you save occasionally.
  2. Keep the untouched download with a date, such as linkedin-saved-posts-2026-08-28-raw.csv.
  3. Use the original post URL as the stable deduplication key.
  4. Append only unseen URLs to the working spreadsheet or database.
  5. Preserve manual columns such as Topic and Why saved when you refresh the raw data.
  6. Back up the working archive separately from the original export.

A dated raw snapshot plus a smaller curated working set is easier to trust than one endlessly edited file. The raw export answers “what did the extension capture that day?” The working set answers “what is useful to me now?”

If your next step is a knowledge system, see how to organize LinkedIn bookmarks in Notion or Obsidian. If you want to query the archive, use the source-preserving AI knowledge-base workflow.

Sources and further reading