Obsidian Web Clipper: how to install it and capture a page

1. What Obsidian Web Clipper is and how to install it

Obsidian Web Clipper is a free, open-source browser extension from Obsidian. It can capture an article, a recipe, a reference page, an academic paper, or selected highlights. The result is stored locally in a chosen vault, so the saved material becomes part of the same file-based knowledge base as the rest of an Obsidian notebook.

1. Open the official Obsidian Web Clipper page.
2. Select the browser in the “More browsers” area: Chrome, Safari, Firefox, or Edge.
3. Add the extension and pin its icon to the browser toolbar.
4. Open the extension and connect it to the Obsidian vault that will receive clips.
5. Start with the built-in article template before creating site-specific templates.

Obsidian also lists Brave, Arc, Orion, and Vivaldi as supported through the Chrome extension route. This guide links only the official product page because that page keeps the current browser destinations together.

2. How to clip a page, highlights, and metadata

A first capture can use the default article template:

1. Open the page to capture and click the Obsidian Web Clipper icon.
2. Confirm the destination vault and note location shown by the active template.
3. Review the proposed note name and the properties extracted from the page.
4. Capture the page and open the new Markdown note in Obsidian.
5. Check the source property and a few paragraphs before using the same template at scale.

For a highlight-first capture, select text, images, or blocks on the page, then use the clipper to save those highlights. Obsidian says highlights remain visible when the page is revisited and can be clipped to the vault in one action.

Set up a reusable template

1. Create a template and give it a name tied to the content type, such as Article or Recipe.
2. Set a note-name pattern and a folder path, then select the default vault.
3. Add only the page properties needed in the resulting Markdown file.
4. Test the template on two different pages and inspect both notes.
5. Add an automatic rule after the manual template works across the intended sites.

The official page shows variables such as title, date, and published date in file-name patterns. It also documents extraction from meta tags, Schema.org variables, and page element selectors for more tailored captures.

3. Workflow boundaries to understand before adding automation

Every clip needs a destination vault and a file structure. That gives the saved content durable local ownership, but folder paths, note names, and properties still need a naming convention. Testing a template on more than one page prevents a rule built around a single site layout from quietly producing incomplete notes elsewhere.

The capture result is Markdown in Obsidian, not a separate web inbox with a built-in read/unread queue. A queue can be represented with folders, tags, or properties, but its state and review process are part of the vault design. That is flexible for an established knowledge system and extra setup for a simple temporary reading list.

Local storage and cross-device availability are separate concerns. The official clipper page says content is stored locally in the vault. Moving that vault between devices requires a sync arrangement outside the act of clipping, and the clipper itself does not replace that arrangement.

Advanced extraction is powerful but sensitive to page structure. Meta tags and Schema.org data are more reusable than a selector tied to one page layout. A small template set with inspected output is easier to maintain than many untested automatic rules.

4. A deadline-based option for a temporary reading queue

Full disclosure: I built Burn 451. Its Chrome extension sends a page to a 24-hour queue rather than a local Markdown vault. The free plan allows 5 Flame saves per day; Pro is $4.99/month. The extension is listed in the Chrome Web Store.

It has no inline highlights, spaced-repetition review, native Android app, local Markdown vault, or template engine. The native app is iOS-only. It covers short-lived reading triage, while Obsidian's clipper covers owned files and a configurable knowledge-base workflow.

5. Frequently asked questions

Obsidian features, storage behavior, and supported browsers verified on the official Obsidian Web Clipper product page, July 2026.

6. Related guides

• Web clipper: capture formats, destinations, and workflow boundaries
• Notion Web Clipper: installation and workspace capture
• How to save and organize bookmarks in Chrome
• How to save articles to read later