LinkedSave, Saved Posts Library
Design Engineer · 2026

“Handing over the right to speak in your name is too much to give away for a search box.”
- 01
Imports about 630 saved posts in roughly 30 seconds, then stays in sync.
- 02
Read only by design. It can't post, like, message, or connect.
- 03
Local first. Your library lives on your machine, with an account as backup, and export is never locked.
LinkedIn's saved posts page has no search, no folders, and no export, and it cuts every post off after three lines. LinkedSave imports everything you saved, with full text, author, image, and date, from your own logged in tab. Then it keeps in sync and catches every Save or Unsave as you click. Search inside the post text, add labels, build smart folders that fill themselves, work through the unread backlog, and export to CSV or JSON. The library lives on your machine and works offline, and an account backs it up and syncs it across devices. It started as my own problem. Six hundred saved posts and no way to find one of them.
Context
Saving a post on LinkedIn is easy. Finding it again is close to impossible. I wanted a fix that asks for as little as possible. Read the list you saved, from your own machine, and nothing else.
How I worked
- 01 · Research
What saved post tools ask for, and what they skip
- 02 · Build
Extension, web library, sync, and export in about three weeks
- 03 · Audit
A UX audit ranked every issue by severity
- 04 · Fix
The top priority issues fixed the next day
Key decisions
Read only, on purpose
LinkedSave never asks for permission to write, so it can't post, like, message, or connect. The only request that uses your session reads your own saved list, from your own browser. Nothing is scraped from a server.Local first, and export is never locked
The library lives in the browser on your machine. When the trial ends, new imports stop, but everything already imported still opens, searches, and exports. A free tier would have shaped the product around the paywall, so there isn't one.I cut the original differentiator
The plan was to rank saved posts by how well they performed. Engagement numbers aren't in the saved list, and fetching them post by post turned a 30 second import into 16 minutes. I removed the feature instead of showing empty fields.Keeping the trust promise in the details
Images are copied to my own storage because LinkedIn's image links expire within days. Marketing visuals are drawn in HTML, not screenshots, because screenshots would show other people's posts and faces. There's no third party analytics, only my own event names and timestamps, so no one else sees what people save.Result
In development. The site is up at linkedsave.com and the Chrome Web Store listing is still to come. 343 commits in about three weeks, designed and built solo.