The web clipper exists to solve a single, decisive problem: **capture friction**. The moment you find something worth keeping is fleeting and badly timed — mid-article, mid-meeting, three tabs deep. Any step between "this is useful" and "it's saved" — copy the URL, switch apps, paste, tag, file — is a step at which the save quietly doesn't happen. Evernote's Web Clipper defined the category by collapsing those steps; every serious knowledge tool since (Notion, Obsidian, Raindrop, Readwise) ships one.

The quiet design truth is that clipper quality is measured in keystrokes, not features. A clipper that asks you to choose a notebook, add tags, and confirm is a clipper you will skip when you are busy — which is exactly when the best material flies past. The tools that win on capture are the ones where saving is reflexive: one action, no decisions, sort it out later.

There is a depth-versus-friction axis here too. A clipper can grab the bare URL, the cleaned article text, a full snapshot, or a highlighted selection — and richer capture usually costs more friction. The right default is the one that keeps the save reflexive while preserving enough to be useful when you return.