Every few years, a bookmarking service dies and takes a decade of someone's saved links with it.
Delicious — once the default way the internet saved links — was sold, resold, and shut down. Google Reader vanished in 2013 with millions of reading habits inside it. Omnivore, the beloved open-source read-later app, gave users about two weeks' notice in late 2024. And in July 2025, Mozilla killed Pocket — the most mainstream "save it for later" product ever made — with a hard deadline to export your data before it was deleted forever.
None of these were bad products. Most had passionate users. They died anyway, because a bookmarking service is a database someone else pays to keep running, and eventually someone decides to stop paying.
There's a structural fix for this, and it's older than the cloud: keep the data on your own machine. That's what "local-first" means, and it's why a growing set of tools — and this article is honest that Bookmarker is one of them — are built that way.
What "Local-First" Actually Means
A local-first app stores your data in files on your computer, and treats any network features as optional extras rather than the foundation. For a bookmark manager, that means:
- Your library is a database on your disk — not rows in a vendor's Postgres cluster
- The app works entirely offline: saving, searching, reading, organizing
- There's no account, because there's no server to have an account on
- Export isn't a feature they grudgingly provide — the data is already yours, sitting in your home folder, included in your normal backups
Compare that to the standard cloud bookmarking bargain: your library lives on their servers, is reachable only while they're up and you're online and your subscription is current, and its long-term existence depends on their runway.
The Four Arguments for Local
1. Longevity: your library outlives the company
This is the Pocket lesson. When a cloud service shuts down, you get an export window and then it's gone. When a local app's company shuts down, the app keeps working. Your library sits in a standard database format on your disk; nothing expires. Even in the worst case — the app stops running on some future macOS — your data is right there to migrate, not behind a dead login page.
Ask one question of any bookmark tool: if this company disappears tomorrow, what happens to my library? For local-first tools the answer is "nothing."
2. Privacy: a bookmark library is a diary
Your saved links are a map of what you think about: medical questions, job hunting, financial research, competitive analysis, the interests you don't broadcast. Hosted services hold all of it, in plaintext, indexed, forever — an asset to be analyzed, breached, subpoenaed, or sold with the company.
A local library removes the trust question instead of answering it. There's nothing to leak because nothing is collected. No privacy policy can beat not having the data.
3. Speed: local is instant
Everything a cloud bookmark manager does involves a round-trip to a server. Every search, every list, every open. Local-first apps do these against a database that's microseconds away — search-as-you-type across thousands of full-text-indexed articles is completely ordinary when the index is on your SSD.
You feel this most in the habit loop: a tool that opens instantly gets used; a tab that loads gets postponed.
4. Offline: the feature you don't notice until you need it
Planes, trains, dead zones, conference Wi-Fi, ISP outages. A local library doesn't degrade — full search, full reading views, saved images and PDFs, all there. Read-later apps in particular are used most in exactly the situations where connectivity is worst.
The Honest Trade-Offs
Local-first is not free lunch. Be clear-eyed about what you give up:
No multi-device sync. Your library lives on one machine. If you need the same bookmarks live on your phone, a local desktop app will frustrate you — either use a relay habit (send links to yourself, paste them at your desk) or pick a cloud/iCloud tool and accept that bargain.
Backups are your job. The vendor isn't keeping copies; Time Machine or any normal Mac backup covers it, but you have to actually have one.
Sharing is manual. No public collection URLs. You export or copy links to share them.
If those trade-offs are dealbreakers, a cloud tool like Raindrop is a fine, honest choice — see our full comparison. The point isn't that cloud is evil; it's that the default for something as personal and long-lived as a bookmark library should be ownership, and you should opt into the cloud deliberately, not by default.
What to Look For in a Local-First Bookmark Manager
Not everything marketed as "private" or "offline-capable" is genuinely local-first. A checklist:
- Where exactly is the data? You want a named file/folder on your disk (Bookmarker, for example, keeps a SQLite database plus your images and PDFs in your Mac's Application Support folder). "Local cache with cloud sync" is a different architecture.
- Does it work with the network off? All of it — saving, search, reading — not just viewing.
- Is there an account? A required login usually means a required server.
- Standard formats in and out. It should import the exports of dying services (Pocket CSV, Raindrop CSV, browser HTML) and export something equally standard, so you're never the locked-in one.
- Local assets, not hotlinks. Saved images, article text, and cover images should be downloaded to your disk. A "saved" page that's just a URL still dies when the source does.
Where Bookmarker Fits
Bookmarker is our attempt at the full version of this idea on macOS: links, images, and PDFs in one local library; offline full-text search across article and PDF contents; a clean reading view with highlights; AI tagging that runs on-device via Apple's Foundation Models (the AI question has the same shape as the storage question — see the best AI bookmark manager); and one-click import from Pocket, Raindrop, and browser exports.
The business model matches the architecture: $99 one-time, because there are no servers to fund with a subscription. A 14-day trial, no account, no card. When you buy a local app once, the incentives point the right way — we never need your data, and you never need our uptime.
FAQ
What's the difference between "local-first" and "offline mode"?
Offline mode is a cloud app tolerating disconnection with a cache; the server is still the source of truth. Local-first inverts it: your disk is the source of truth, and the network is optional. The test is what happens if the vendor vanishes — offline mode dies at the next sync; local-first doesn't notice.
Can a local bookmark manager still use AI?
Yes — two ways. On-device models (Apple Intelligence–class Macs can tag and summarize locally, free and private) or bring-your-own API key, where the app calls a provider under your account with no middleman database. Both preserve the core property: no service accumulating your library.
How do I get my bookmarks out of cloud services and into a local app?
Every major service exports to CSV or HTML, and good local apps import those directly. We wrote a step-by-step for Pocket, Raindrop, and every major browser: how to move your bookmarks to a local Mac app.
What happens to my library if my Mac dies?
The same as any file: it's as safe as your backup. A local bookmark library is included automatically in Time Machine or any whole-disk backup — restore it and it works. That's a real responsibility, but it's one you already carry for your photos and documents.
