Guide
Web clipper: what it saves and how clipping workflows differ
A web clipper moves material from an open browser page into another place for later use. The important difference is not the toolbar icon; it is whether the clip becomes a link, a readable copy, a screenshot, a selection, or a structured note.
This page defines what a web clipper captures (section 1) and how clippers differ by platform (section 2).
1. What a web clipper actually does
A web clipper is a browser extension or app feature that copies something from an open page — a link, the article text, a selection, or a screenshot — into a separate destination, so the material stays usable after the source page changes or disappears. What matters is which of those four a tool actually produces, since two clippers can both report a successful save while creating very different records.
Link only
Keeps: title, URL
Loses: the content itself
Article text
Keeps: main body, readable copy
Loses: nav, sidebars, ads
Selection
Keeps: marked passages, images, blocks
Loses: rest of the document
Screenshot
Keeps: visual appearance
Loses: searchable, editable text
A structured note can layer its own fields — source, author, tags, capture date — on top of any of these four. Two more dimensions sit outside the grid: the destination it writes to (a browser account, cloud workspace, local file, or reading queue), and whether it works offline.
2. How web clippers differ
Clippers are best compared by observable capability, not rank — a capability can vary by capture mode within one extension.
| Dimension | Possible behavior | Practical consequence |
|---|---|---|
| Capture output | URL, extracted article, screenshot, selection, or structured note | Determines what remains if the live page changes |
| Storage destination | Browser account, cloud workspace, reading queue, or local files | Determines where the clip is found and managed |
| Format fidelity | Plain text through to preserved layout and media | Determines how closely the clip resembles the source |
| Offline behavior | URL-only, cached content, or a local copy | Determines whether the clip opens without the source page |
| Account model | No account, browser sign-in, or a separate service account | Determines how clips move between devices |
A quick test reveals the real behavior: save one representative page, open it at the destination, go offline if that matters, and check what happened to headings, links, images, embeds, and metadata.
Account requirements matter too: a cloud destination syncs across devices after sign-in, a local file relies on that system for backup and sync — neither says anything about capture quality.
Platform availability
Availability is readable straight off each vendor's download page; the grid below covers the clippers in this guide series.
| Clipper | Chrome | Firefox | Edge | Safari | iOS | Android |
|---|---|---|---|---|---|---|
| Notion Web Clipper | Yes | Link present, store page 404 | Not documented | Yes, Mac only | Yes, Notion app share sheet | Yes, Notion app share sheet |
| Obsidian Web Clipper | Yes | Yes | Yes | Yes | Yes, Safari extension | Not documented |
| Evernote Web Clipper | Yes | Yes | Not documented | Yes, Mac only | Not documented | Not documented |
| Joplin Web Clipper | Yes | Yes | Not documented | Not documented | Not documented | Not documented |
Checked in July 2026 against obsidian.md/clipper, notion.com/web-clipper, notion.com/help/web-clipper, joplinapp.org, and the Chrome Web Store, Mozilla Add-ons, Microsoft Edge Add-ons, and App Store listings those pages link. “Not documented” means the destination was not found on the official sources checked, not that it is unavailable. The Joplin extension additionally requires the Joplin desktop application to be running, per Joplin's own documentation.
3. Workflow boundaries shared by web clippers
Capturing and returning are separate actions — fast capture doesn't surface unread items, connect material to active work, or remove what no longer matters, so a clean flow can still produce a large inactive archive.
Rich captures add maintenance choices: an article copy stays readable if the source changes but can go stale; a URL stays current but depends on that page staying up; screenshots preserve appearance but resist search and editing.
Portability matters too: a common file format moves between tools with less cleanup than a proprietary record, and export support, attachment handling, and link preservation matter when an archive needs to outlast the current app — none of which makes clipping ineffective, just separate from the reading, review, and archive systems that receive the material.
4. A deadline-based option for a temporary queue
Section 3's shared boundary is archive growth — capture gets easier every year while nothing forces a look back, so the pile just gets bigger.
Full disclosure: I built Burn 451. Its Chrome extension sends a page into a queue instead of an archive — that's the entire design decision.
A 24-hour read-or-remove deadline is what actually treats growth: it caps how long anything can sit unresolved, so the queue can't quietly become the same kind of pile section 3 describes.
It has no inline highlighting, no spaced-repetition review, and no native Android app — iOS only. The free plan allows 5 Flame saves per day, and Pro is $4.99/month.
5. Frequently asked questions
What is a web clipper?
A web clipper is a browser tool that moves something from the current page to another destination — depending on the tool and mode, that's a URL, extracted text, a screenshot, a selection, or a structured note.
Is a web clipper the same as a bookmark?
Not always: a bookmark stores a title and URL; a clipper can also copy content, images, metadata, or text into a workspace or file. A URL-only clip behaves like a bookmark.
Does a web clipper make pages available offline?
Only if the destination stores a usable copy and makes it available offline — a saved URL alone still needs the original page and a connection. Offline behavior depends on both format and destination.
What details matter before installing a web clipper?
The practical details: capture output, storage destination, account requirement, supported browsers, offline behavior, and whether the format can move elsewhere later.
Product availability and plan details verified against the official Chrome Web Store listing and first-party product records, July 2026.