There is a naming collision at the heart of this topic and it wastes a lot of people’s afternoons. Search “obsidian bookmarks” and you will find two completely different conversations happening under one phrase, with people answering each other’s questions by accident.
One is about the Bookmarks core plugin, which pins things inside your vault. The other is people who assumed that plugin was a place to keep the web pages they save, and are now trying to work out why it will not do that.
Both are worth clearing up, because the second group has a real problem and the plugin was never going to solve it. Here is what Obsidian bookmarks actually are, how to get web pages into a vault when you want them there, and the part of your saving that no Obsidian setup reaches.
- The Bookmarks plugin pins vault objects, not web pages. Notes, headings, blocks, searches and tabs.
- It replaced the Starred plugin and does considerably more than starring ever did.
- Web pages need the Web Clipper or a community plugin, which is a separate step.
- Nothing arrives on its own. Every save into a vault is something you chose to do by hand.
- What you bookmark on X, Reddit or LinkedIn never reaches the vault at all. ContextBolt catches those saves as you make them, and any web page in one click, and on Pro the same agent that reads your vault can read that library too.
What the Bookmarks core plugin does
Obsidian Bookmarks is a core plugin that pins items from inside your vault to a sidebar for quick access. It is the successor to the old Starred plugin, and anything you had starred moved across when it landed.
What it can pin is wider than most people realize, and this is the genuinely useful part.
- Notes and folders, the obvious case.
- Headings and blocks, so you can jump to one section of a long note rather than the top of it.
- Saved searches, which is the sleeper feature. Bookmark a query and you have a live view that updates itself.
- Open tabs and graph views, for workspace states you return to.
You can group these into collapsible folders and reorder them by dragging. In practice it becomes a project dashboard. The three notes you are actively working in, a saved search for anything tagged with this month’s focus, and a couple of reference headings you keep checking.
Used that way it is one of the better core plugins. It is also entirely internal. Every single thing in that list already lives in your vault. The plugin is a navigation aid, not a capture tool, and the word “bookmarks” is doing everyone a disservice.
Four ways to use it that are actually worth the sidebar space
Since the plugin is a navigation aid, the question is what deserves permanent navigation. Four patterns hold up.
Bookmark a saved search, not a folder: This is the one most people miss. A bookmarked search re-runs every time you click it, so tag:#active -tag:#done is a live worklist that maintains itself. A bookmarked folder is just a folder with a shortcut.
Bookmark headings inside your long notes: If you have a 4,000-word reference note, the useful destination is a section of it, not the top. Bookmarking the heading takes you straight there.
Group by project and delete the group when it ships: Bookmarks accumulate the same way everything else does. Groups make them disposable, which is what keeps the sidebar meaningful. If you have not opened a bookmark in a month it is not a bookmark, it is a note.
Bookmark the daily note template, not today’s daily note: Bookmarking a specific dated note guarantees a stale link within 24 hours. People do this constantly and then wonder why the sidebar fills with dead entries.
Used like this it stays at eight or ten items and works. Used as a permanent archive of everything interesting, it becomes the thing it was supposed to fix.
Getting web pages into a vault
If what you want is the article rather than a pointer to it, you need something else.
The Obsidian Web Clipper is the first-party answer. It is a browser extension that turns a page into a note in your vault, with templates so you can control what gets captured and where it lands. This is the right tool if you want the text itself, in Markdown, sitting in files you own forever. That last part is the real argument for it. A clipped article survives the source going offline, which matters more than people think given how much of the web quietly disappears.
Community plugins cover the lighter version, where you paste a URL and get a note with the title, the link and some metadata. Useful when you want a reference rather than an archive.
Either way, notice what both have in common. You are at a desk, in a browser, deliberately deciding to capture something. That is the model Obsidian is built around, and for deep work it is the correct model. A vault is supposed to be curated.
The trouble is that curated capture and actual saving behavior have drifted a long way apart.
The gap: saving does not happen at a desk any more
Be honest about where your saves came from this month.
The bookmark icon on a thread in X, tapped on a phone, because it was faster than opening a tab. The save button on a Reddit comment that answered a question better than any blog post you found. The three dots on a LinkedIn post you meant to come back to. Each of those is a one-tap save inside an app, and none of them involved a browser, a clipper, or a decision about which folder.
None of it reaches Obsidian. Not because of a missing plugin, but because there is no export to plug into. On X the bookmark list has no real export path. On Reddit the saved list caps out around a thousand items and quietly drops the oldest ones off the end. LinkedIn gives you no search over saves at all. We went through the mechanics in why social bookmarks disappear.
| Where you saved it | Ends up in your vault? |
|---|---|
| Clipped an article with the Web Clipper | Yes, as a note |
| Pasted a URL into a daily note | Yes, if you remembered |
| Bookmarked a thread on X | No |
| Saved a Reddit post or comment | No |
| Saved a LinkedIn post | No |
So a well-tended vault ends up holding two things. What you wrote, which is the point of Obsidian and irreplaceable. And the fraction of what you read that you were at a desk for, and motivated enough to clip.
The gap is the rest. And it is not a small slice, because the one-tap saves are the ones you make most often, precisely because they cost nothing.
Why this matters more now than it did
For years this was a tidiness complaint. It changed when people started pointing agents at their notes.
Connect a vault to Claude and it can read everything in it, which is genuinely a step change for anyone who writes a lot. We compared the routes for that in Obsidian MCP servers, and the setup got easier this year.
But an agent reading your vault inherits your vault’s coverage. Ask it what you have collected on some topic and it answers from your notes plus your clipped articles, confidently, with no way of signaling that the best three sources you saw this year were saved on your phone and never made it in.
That is the failure mode worth worrying about. Not “I cannot find it”, which at least tells you something is missing. It is a complete-sounding answer built on a partial library, and neither you nor the agent can see the edge of it.
What to do about it
The framing that works is to stop treating the vault as the place everything goes.
Obsidian keeps what you wrote and what you deliberately clipped. That is its job and it is very good at it. Use the Bookmarks plugin for navigation, use the Web Clipper for articles you want to survive link rot, and keep the vault curated. Do not try to turn it into an inbox for everything you have ever found mildly interesting. That is how vaults become unusable, and it is the same failure as the Notion database that nobody opens.
Handle the one-tap saves with something that captures them where they happen: This is what ContextBolt does. It is a Chrome extension that picks up what you bookmark on X, Reddit and LinkedIn as you save it, keeps the post’s content rather than a bare link, saves any web page with its article text in one click, and tags each save with a topic automatically so nothing needs filing. Basic is free, with no account and no card, and it is capped at 150 bookmarks, which is enough to see whether the gap is as big as I am claiming before paying for anything. Pro is $6 a month, month to month, for unlimited bookmarks, cloud sync, and your own MCP endpoint, which means the same agent reading your vault can also search those saves by meaning rather than by keyword.
Two endpoints, one agent. The vault answers for what you wrote. The other answers for what you saved. Neither pretends to cover the other, and that is the version of this that does not quietly lie to you.
If you are building the wider system rather than fixing one gap, build a second brain from your bookmarks covers how saved links and written notes fit together without one swallowing the other. If you just want the gap closed, install the free plan and let the next month of one-tap saves land in a library that files itself. The endpoint is there on Pro when you want the agent reading it too.