Why browser bookmarks fail

Browser bookmarks haven't fundamentally changed in twenty years — a folder tree, basic title-and-URL search, and storage scoped to one browser. That model works fine for a small list and starts to struggle once an archive is doing real work.

The structural problems

1. Folders force a single category

You can only put a bookmark in one folder. Real information has many relationships at once. The first time you save a link that genuinely belongs in two folders, the system is already lying to you.

2. There is no graph

Two bookmarks about the same topic are not linked unless you put them in the same folder. There's no concept of "these articles cite each other," or "these are about the same author," or "this expands on that one." The archive grows but the connections don't.

3. Search is an afterthought

Browser bookmark search typically matches title and URL substrings — if it works at all. There's no description search, no topic filter, no date range, no boolean operators. By a few hundred entries, searching is unreliable enough that you give up and re-Google instead.

4. Vendor lock-in by design

Chrome bookmarks live in Chrome. Safari bookmarks live in Safari. Firefox bookmarks live in Firefox. Sync works inside each ecosystem but failure modes are silent: a profile reset, an iCloud sync error, or a switch to a new vendor can lose entries permanently.

5. The profile is the product

Browser bookmarks are part of your browser profile, which is part of your account, which is part of an advertising graph. Even when nothing visible goes wrong, your saved links are signal — to your browser vendor and, in many configurations, to their partners.

What replaces them

Any of:

• A tag-first bookmark service with proper search and an export option — better than folders, still vendor-locked.
• A note-taking tool used as a bookmark archive (Obsidian, Notion, Logseq) — flexible but heavyweight, and the data is often proprietary.
• A linked-data bookmark manager that stores in a personal data pod — portable, queryable, multi-tag, and not tied to one browser. (mnera.io is one of these.)

The migration

Any of these can import your existing browser bookmarks via the standard bookmarks.html Netscape export format. The folder tree maps cleanly to either tag prefixes or topic hierarchies. Once imported, you can keep using the browser's own UI for quick saves and reach for the dedicated tool when you actually want to find something.