A bookmark and a note look similar in a list view — both are a saved thing with a title, both sit in an app, both promise you'll return to them. Functionally they're close to opposites, and mixing them up is one of the quieter ways a personal knowledge system stalls out.
What each one actually records
A bookmark records a location. It's a pointer: this exists, here, and I may want it again. The content lives elsewhere; the bookmark's whole job is finding your way back to it. Read-it-later tools formalise this well — see read it later — but a bookmark is a bookmark whether it's in a browser folder, a Pocket queue, or a "saved" tab.
A note records a state of understanding. It's not a pointer to an idea; it is your version of the idea, in your own words, at the moment you wrote it. It survives even if the source disappears, because it never depended on the source remaining reachable.
The confusion happens because saving either one produces the same small hit of relief — an open loop closes, a "handle this later" feeling resolves — described in the collector's fallacy. Christian Tietze's naming of that fallacy is really about this exact substitution: bookmarking something and filing the feeling of having engaged with it, in place of the harder work notes require.
Where the substitution goes wrong
Bookmarks scale into a pile with no cost, because adding one takes no thinking — that's the whole point of a bookmark, and it's fine for its actual job (a receipt, a reference you might need the URL of, a purchase to make later). The problem starts when a bookmark pile gets treated as a knowledge base: a folder of four hundred saved articles feels like research, and it isn't, because nothing in it has been converted into something you actually understand or can retrieve without re-reading the source.
The tell is the same one used to catch collector's-fallacy hoarding: pick five bookmarks from last month and try to state, without opening the link, what each one argued. If most come back blank, they were never knowledge — they were an intention with a URL attached, and intentions don't compound the way understanding does.
A working boundary between the two
Bookmark when you might need to return to the source itself — a tool's documentation, a purchase link, a reference you'll need to cite exactly, something whose value is in being the original, not your summary of it.
Take a note when the value is what you extracted, not where you found it. A note should survive the source vanishing. If losing the link would make the note worthless, it was never really a note — it was a bookmark with extra steps.
The conversion step is the one people skip. Reading something worth keeping and writing one sentence, in your own words, about what it argued or why it mattered turns a bookmark into a note in under a minute — see how to write a summary. That one sentence is the entire difference between a pile that grows and a system that compounds; skipping it is the single most common reason a "read later" queue and a "notes" folder end up equally useless, just organised differently.