Obsidian web clipper saves locally

Obsidian’s web clipper is basically a browser extension for people who want the web to behave like files. You save a page, and instead of sending it into some company’s cloud bucket, the clip lands in your Obsidian vault as Markdown. That matters because Obsidian’s whole pitch is local-first notes, but web clipping has often been the part where that promise gets blurry. The new thing here is that Obsidian’s own official clipper now closes that gap cleanly. ### What is this actually saving? It saves web pages, highlights, and page metadata into Markdown files you can keep in your vault and read offline. Obsidian pitches that as “durable” storage — plain files, not a proprietary format trapped inside a service. The extension also lets you grab structured data from a page, including metadata, Schema.org fields, and selected elements, so a clip can be more than just a blob of text. ### Does it really save locally? Yes — that is the important part. Obsidian’s help docs say Web Clipper saves content locally to your Obsidian vault, does not collect your data, and does not gather usage metrics. In plain English, the clipper is not acting like a read-later service that needs to warehouse your articles first. It is acting like a capture tool for your own files. ### Why do Obsidian users care so much? Because Obsidian is not just a notes app. (obsidian.md) It is a folder of Markdown files with backlinks, templates, plugins, and a bunch of workflows layered on top. If clipped pages arrive as normal Markdown notes, they immediately become part of that system — searchable, linkable, taggable, and scriptable. You are not maintaining a separate archive somewhere else and then trying to bridge it back into your notes later. (obsidian.md) ### Who made it? It is the official extension from Obsidian, and Steph Ango has a page describing Web Clipper as an open-source browser extension that saves articles and pages from the web as Markdown files in Obsidian. The source code lives in Obsidian’s public GitHub repo under the obsidianmd organization, where the project is actively maintained. ### What can you customize? Quite a lot, turns out. Obsidian leans hard on templates, so you can decide how a page gets turned into a note — title, author, source, highlights, frontmatter, extracted fields, all of it. (obsidian.md) That makes the clipper useful for very different jobs: saving articles with citations, turning recipes into structured notes, capturing references for books or podcasts, or pulling academic papers into a cleaner format. ### Is this just a Chrome thing? (stephango.com) No. Obsidian offers versions for Chromium browsers, Firefox, and Safari, including mobile support on Firefox Mobile and Safari on iPhone and iPad. That sounds boring, but it matters — a local-first workflow falls apart fast if clipping only works on one desktop browser. ### Is it established or still early? It looks established now. Obsidian announced the clipper on November 11, 2024, and the GitHub releases page shows active updates, with version 1.6.2 published about two weeks ago. (obsidian.md) The Chrome Web Store listing also shows broad adoption, with roughly 700,000 users and a 4.8 rating at the time of writing. ### What’s the real takeaway? The big deal is not that Obsidian can save articles. Lots of tools can do that. (stephango.com) The big deal is that Obsidian’s official answer now matches the philosophy of the app itself — local files, open code, offline access, and enough structure to make clipped material usable inside a real knowledge system instead of a dumping ground. (obsidian.md 1) (obsidian.md 2)