The Most-Requested Bookmark Manager Features (And Where You Can Use Them Today)

Spend any time in productivity forums and community boards and you'll notice the same wishes coming up for bookmark managers, year after year: work offline, stop duplicate chaos, let one link live in two places, keep private things private, and track what's been read. They're requested everywhere because they solve everyday problems.

Here's an honest look at each one — and how onBookmarks handles it today.

1. Offline support

The most common wish of all: access your bookmarks when you don't have a connection.

In onBookmarks, this works today. The app is an installable PWA with real offline data, not just a cached splash screen:

• Browse offline. Your bookmarks, collections, and saved article content are cached locally, so the library you've already loaded stays readable on a plane or in a dead zone.
• Save offline. Add, edit, or delete bookmarks while offline — changes are queued locally and sync automatically (with retries) when your connection returns.

2. Duplicate handling

Everyone has saved the same article three times. What people want is simple: warn me when I'm adding a link I already have, and show me where it lives.

That's exactly what onBookmarks does:

• When you save a URL you already have, the form shows the existing bookmark right there, card and all, before you create a copy.
• When you bulk-import links, duplicates are flagged as "already exists" and skipped automatically.
• For the duplicates you already have, the built-in library cleanup scans your whole library for duplicates and dead links and helps you clear them in one pass.

3. One bookmark in multiple collections

Filing a bookmark under one folder only is a filesystem habit, not how people think. A React article is "work" and "reading list" and "frontend."

onBookmarks was built this way from the start: bookmarks live in as many collections as you like, with no duplicated copies to keep in sync. There's a whole feature page on it.

4. Private, hidden, protected collections

People keep sensitive bookmarks — medical, financial, personal — and they don't want them showing up on a shared screen or in a data breach.

onBookmarks covers this at three levels:

• Private collections are the default; nothing is public unless you explicitly share it.
• Password-protected collections shipped today. Set a password on any collection and its contents disappear from your main list and search until you unlock it — the password is never stored, only a bcrypt hash.
• Client-side encryption protects your most sensitive bookmarks with zero-knowledge encryption — encrypted on your device, unreadable by us, excluded from public pages and exports by design.

5. Reading list and read history

The reading-list workflow: mark what you've read, keep the reading list clean, keep the history.

This one shipped today too. Every bookmark now has a read/unread toggle, and the bookmark list filters to Unread (your reading list) or Read (your history) — with the date you read each one kept on the bookmark.

No roadmap required

Every feature on this list is live in onBookmarks right now — the last two shipped the same day this post was published. No vote counters, no "planned" labels, no waiting.

Try them yourself

Create a free account and bring your library with you — the importer handles exports from every major browser and bookmark service, duplicates included.