Obsidian Web Clipper: What the Official Extension Does and Where It Stops

The gap Obsidian Web Clipper fills, and who it is for

Copying a page into a notes app usually produces either a screenshot, a link with no context, or HTML that carries the site's markup into your vault. Obsidian Web Clipper takes a different position: the README says anything you save is stored as durable Markdown files that you can read offline and preserve for the long term. That sentence is the whole product thesis. The output is a file in a folder, not a row in a hosted database.

The target user is someone who already keeps notes in Obsidian and reads on the web. The extension lives in the browser toolbar, and the capture lands in a vault. If you do not use Obsidian, the extension has no destination, and the repository does not present a standalone note store. The four store listings (Chrome Web Store, Firefox Add-Ons, Safari Extensions for macOS, iOS and iPadOS, and Edge Add-Ons) are the intended install path for normal users, which tells you the maintainers expect people to install from a directory rather than build from source.

How capture works: defuddle extraction, templates, and a vault write

The README lists the third-party libraries the project depends on, and that list is the clearest description of the pipeline. defuddle handles content extraction and Markdown conversion, so the extension is not dumping raw DOM into your note. dompurify sanitizes HTML, which matters because page content is untrusted input flowing into a file you will later open. dayjs handles date parsing and formatting, which is what makes date variables in templates behave predictably. lz-string compresses templates to reduce storage space, a small but telling choice: templates are stored in browser extension storage, which has size limits. webextension-polyfill provides browser compatibility, so one codebase targets Chromium, Firefox and Safari rather than three forks.

The user-facing layer on top of that is templates, variables and filters, all documented on the Obsidian Help site rather than in the README. A template decides which fields get written and in what order; variables pull values such as the page title or URL; filters transform those values. The roadmap confirms template logic with if/for shipped in 1.1.0, and template validation shipped in the same release. That combination means the extension is closer to a small templating engine than to a bookmark button, and it is the part worth learning before you capture anything in volume.

Installing Obsidian Web Clipper and running a first capture

For everyday use, the README points at the official directory for your browser. Chrome, Brave, Arc, Orion and other Chromium-based browsers use the Chrome Web Store listing; Firefox and Firefox Mobile use the Firefox Add-Ons listing; macOS, iOS and iPadOS use the Safari Extensions listing; Microsoft Edge uses the Edge Add-Ons listing. After installing, the extension appears in the toolbar, and the capture destination is your vault.

If you want to run the source, the developer instructions start with a build. The README gives one command that produces all three targets.

npm run build

The README states this creates three directories: `dist/` for the Chromium version, `dist_firefox/` for the Firefox version, and `dist_safari/` for the Safari version. For Chromium browsers the README says to open `chrome://extensions`, enable Developer mode, click Load unpacked, and select the `dist` directory.

Firefox takes a different route. The README says to open `about:debugging#/runtime/this-firefox`, click Load Temporary Add-on, then navigate to `dist_firefox` and select the `manifest.json` file. Temporary add-ons do not survive a restart, and the README notes that running the extension permanently requires the Nightly or Developer versions of Firefox. In that case you set `xpinstall.signatures.required` to `false` in `about:config`, then use `about:addons` and the gear icon's Install Add-on From File option.

Tests run through Vitest, and watch mode is available for development:

npm test
npm run test:watch

The repository also exposes a CLI. The `package.json` declares a `bin` entry named `obsidian-clipper` pointing at `./dist/cli.cjs`, plus an `./api` export at `./dist/api.mjs`, and `prepublishOnly` runs `build:cli` and `build:api`. The README does not document CLI usage, so treat the CLI as present in the package layout rather than as a documented workflow.

Where the extension is the wrong tool

The architecture puts the browser in the middle of every capture. There is no server component described in the README, and no scheduled job. If you need to archive a set of URLs overnight, or clip pages from a machine without a browser session, the documented path does not cover it. The CLI and API entry points exist in `package.json`, but the README does not describe their flags, inputs or outputs, so anyone building on them is reading source rather than following documentation.

Browser coverage is a second boundary. Safari support reaches macOS, iOS and iPadOS, and Firefox support includes Firefox Mobile, but the related searches show people asking about Android, and the README's install list does not name an Android browser. That is a real gap for anyone whose reading happens on an Android phone.

The third constraint is storage and distribution. Templates are compressed with lz-string specifically to reduce storage space, which implies the storage budget is tight enough to design around. And the roadmap still lists sync settings across browsers as unfinished, so a template you build on your laptop will not follow you to a second browser automatically.

How it differs from Obsidian's own importer and from read-later services

Obsidian's core importer handles migration: it pulls an existing archive from another notes app into your vault once. Web Clipper handles the opposite direction and the opposite cadence. It captures one page at the moment you are reading it, repeatedly, with a template applied each time. The importer is a one-time conversion; the clipper is a habit.

Read-later services such as Pocket or Instapaper keep the article on their servers and give you a reading interface. Web Clipper writes a file into a folder you control, which is why the README can promise offline reading and long-term preservation. The trade-off is that you supply the storage, the backup and the search. There is no hosted index of what you clipped, and no recommendation feed. If you want someone else to keep the archive and sync it across devices for you, the extension is solving a problem you do not have.

Maintenance, licence, and what upgrading costs

The repository is not archived, and the last push was on 2026-09-22, one day before this writing. Releases have been frequent: 1.7.1 on 2026-07-22, 1.7.0 on 2026-06-16, and 1.6.3 on 2026-05-26. The README's roadmap shows a mix of shipped and open items, with annotate highlights, a template directory, and cross-browser settings sync still unchecked. Note that a shipped item can still be a moving target: the separate Web Clipper icon landed in 1.6.3, which means a version bump can change how the extension looks in the toolbar.

The licence is MIT, and the README states that all trademarks, icons, marketing copy and other marketing assets are excluded from that licence. In practice that means the code is reusable under MIT terms but the Obsidian name and visual identity are not part of the grant. This is a description of what the repository says, not legal advice; if you plan to redistribute a fork, read the LICENSE file yourself.

Upgrade cost is mostly template drift. Because templates support conditionals and loops and are validated, a change in extraction behaviour or variable semantics can alter output silently across many notes. There is no documented migration tool for existing clipped files, so the practical cost of upgrading is re-checking your templates against a few real pages rather than rewriting your vault.

Editorial conclusion

Adopt Obsidian Web Clipper if your notes already live in Obsidian and you want page captures as Markdown files you own, with templates controlling the output shape. Skip it if you need server-side clipping, scheduled archiving, or a headless pipeline that never opens a browser, because the documented path is a browser extension plus a local folder. Before committing, verify that your browser is covered (Chrome, Brave, Arc, Orion, Firefox, Firefox Mobile, Safari on macOS, iOS and iPadOS, and Edge are listed), that your target vault is reachable from the extension, and that the template variables you rely on behave as expected on one real page.

Frequently asked questions

Official sources

1. License: MIT
2. obsidianmd/obsidian-clipper on GitHub
3. Project website
4. README
5. Releases