Every bookmark system fails in the same order: too many folders, filing gets slow, filing stops, the list becomes a graveyard. The fix isn't a better hierarchy. It's deleting more, nesting less, and being honest about which saves you were never going to file.
The instinct is to start categorising. Don't. Open your bookmark manager, sort by date added, and work backwards deleting anything you don't recognise or haven't opened in a year. Most people cut their list roughly in half.
This isn't just tidiness. Every link you delete is one you don't have to make a filing decision about, and filing decisions are the thing that kills the project on a Sunday afternoon.
Then clear the obvious debris: duplicates, links to pages that no longer exist, and anything you saved as a to-do that you've since done or stopped caring about.
The most common mistake isn't having no structure, it's having too much. Finance → Tax → 2024 → Receipts feels rigorous and is actively worse than a folder called Finance, because a deep path has to be remembered before it can be used. You end up searching your own filing system.
Keep the top level broad and small. Five to eight categories that match how you'd describe the thing out loud. If two folders are so close that you'd hesitate between them, that hesitation will happen on every single save from now on — merge them.
Here's the rule that actually keeps systems alive: if picking a folder takes more than a second, don't pick one. Leave it unfiled. Inventing a new folder to resolve an awkward save is how you get back to thirty folders, and an unfiled link in a small tidy system is easier to find than a filed one in a sprawling one.
The steps above work for links you save at a desk, deliberately, with a moment to think. That is not most of what you save.
The rest arrives in a hurry: a thread bookmarked on your phone mid-scroll, a LinkedIn post saved between meetings, a tab kept because closing it felt like losing something. Nobody has ever gone back and filed those, and a folder system that assumes you will is designing for a person who doesn't exist.
Those saves also scatter across places that don't talk to each other — X bookmarks in one silo, LinkedIn saved posts in another, Chrome bookmarks in a third. No amount of folder discipline in Chrome touches the other two.
Organising exists to make retrieval possible. If retrieval works without the filing, the filing was overhead.
That's the bet Zihin makes. Saves from X, LinkedIn and Chrome land in one library, get read and tagged automatically, and are searchable by meaning rather than by the words you happened to remember — so you find things by describing them, not by recalling where you put them. Saves you're about to forget resurface on their own instead of sinking. And because it keeps its own copy, an entry survives the original post being deleted.
Delete ruthlessly, keep a shallow structure for the deliberate saves, and let the hurried ones be handled without you. That combination survives contact with a real week.
Free during beta · Your credentials never touch our servers