Local-first swipe file
Keep the good ones.
Paste a link, keep the screenshot, add the note. LocalStash tags it offline and keeps the whole archive in this browser — no account, no upload, no sync you didn't ask for.
Unlimited collections and a one-click Notion + CSV export pack.
Your stash is empty
Paste a URL above, or start with four references that show how the tags, notes and screenshots work.
What this is
A swipe file that lives in your browser
LocalStash keeps links, screenshots and the sentence that explains why you saved them. It is not a bookmark manager with a nicer font, and it is not a sync service: it is a small local archive you can export as a file whenever you like.
Three scenes it was built for
A designer collecting interface patterns before a redesign. Twenty screenshots of empty states, onboarding screens and pricing tables from products that do it well, each with one line about what specifically works — "three options, middle one pre-selected, and the price per seat sits under the button". Search "empty state" a month later and the screenshots, the notes and the tag come back together, on a laptop with no connection. Nothing was uploaded, so nothing had to be requested from a privacy team.
A developer keeping the docs that answered a question. The RFC that explained the retry strategy, the release note that broke a dependency, a blog post with the measurement that ended an argument. Each one is a URL, a title, two tags and a sentence saying why it is worth finding again — which is more than a bookmark ever held. At the end of a sprint the Markdown export goes into the team's notes, and the library stays here.
A writer assembling a swipe file of copy that worked. Landing pages, subject lines, opening paragraphs, a menu someone photographed. The note field is where the observation goes: which phrase did the work, and what the reader was supposed to feel at that point. Before changing laptops, the JSON export is one file, screenshots included; import it on the new machine and the archive is there.
Why it can be private: there is no server
The whole application is static — HTML, one stylesheet and four small JavaScript files, hosted as files. When you press Save, the reference is written into localstash-db, an IndexedDB database that belongs to this browser profile, with four object stores: items, images, collections and metadata. Screenshots are kept as blobs in their own store, so listing a library of five hundred references never loads image data into memory. Tags are assigned by a deterministic rule engine that maps domains and keywords onto a small vocabulary; it runs offline in well under a millisecond and you can read every rule that produced a tag. Search, sorting and the collection filter all run in the page.
Because of that there is no endpoint that could receive your library: no request carries a note or a screenshot, no account exists to be cancelled, and no analytics runs alongside. A service worker caches the shell, so the workspace opens with the network off and saving keeps working. The trade-offs are real and worth stating. The library lives in one browser profile, so moving it to another device or browser means exporting and importing. And the app does not encrypt the database itself — your device's disk encryption is the protection, and a shared computer deserves its own browser profile. The free workspace holds three collections and five hundred references; the export pack (JSON, Markdown, CSV, bookmarks, one zip) is available while the Pro pack is still in preparation.