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

If you want to know what bookmark manager users actually need, don't read marketing pages — read feature request boards. Thousands of people voting, over years, on the things their tools still don't do.

We did exactly that. Raindrop.io, the biggest name in the space, runs a public feature board, and the top of it is remarkably stable: the same requests have been accumulating votes for years, most of them still marked "planned" or "under review."

Here are the most-voted requests as of August 2026 — and an honest look at where each one stands in onBookmarks.

1. Offline support — ~2,900 votes, still "under review"

The single most-requested feature: 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 — ~2,300 votes, no status

"Warn users when adding a duplicate bookmark. This would show them where that link already exists, saving time from duplicate cleanup later on."

That's the request, verbatim — and it describes 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 — ~2,100 votes, "planned"

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 — ~900 votes, "planned"

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 goes further than the request:

• Private collections are the default; nothing is public unless you explicitly share it.
• 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. Archive read bookmarks — ~1,200 votes, "planned"

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

This one we won't pretend to have — it's not in onBookmarks yet either. It's in active development right now, and it's the next feature we ship. (Watch this space.)

The pattern

None of this is a knock on any competitor — building software is hard, and every product has a backlog. But if you've been waiting years for the features above, you don't have to keep waiting on a vote counter.

Four of the five most-requested features in the category are things you can use in onBookmarks today. The fifth is weeks away, not years.

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.