explaingit

likeabreeze-del/web-content-clipper

Analysis updated 2026-05-18

25TypeScriptAudience · generalComplexity · 2/5Setup · easy

TLDR

A Chrome and Edge browser extension that clips webpage content as Markdown and saves it straight into your Obsidian notes vault, with no cloud upload.

Mindmap

A visual breakdown will appear here once this repo is fully enriched.

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Clip an article from Bilibili, YouTube, or Reddit straight into your Obsidian vault as Markdown.

USE CASE 2

Save a full X thread or webpage highlights for later reading in Obsidian.

USE CASE 3

Save clipped images and attachments locally using the Obsidian Local REST API plugin.

USE CASE 4

Switch quickly between several Obsidian vaults when saving clips.

What is it built with?

TypeScriptChrome ExtensionObsidianNode.js

How does it compare?

likeabreeze-del/web-content-clipper8thpark/geodecodeweb-dev/spark-ui
Stars252525
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasymoderate
Complexity2/52/5
Audiencegeneralvibe coderdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Saving images and long articles requires installing the separate Obsidian Local REST API community plugin.

In plain English

Lyon's Magic Glove is a browser extension for Chrome and Edge that is built for Chinese language knowledge work. It converts the main content of a webpage into Markdown text and saves it directly into your Obsidian notes vault. The extension has dedicated extraction logic for a set of specific sites, including Feishu, Bilibili, YouTube, Xiaohongshu, X (formerly Twitter), WeChat public accounts, and Reddit. For any other website, it falls back to a general purpose content extraction tool called Defuddle. You can clip just a selected portion of a page, capture a page that requires scrolling to load everything, save an X thread, or save page highlights. Saved notes can include frontmatter, a reading status, the author, the publish date, and other custom properties, and you can switch quickly between multiple Obsidian vaults. There are two ways the extension saves into Obsidian. The first uses Obsidian's built in URI links, which needs no extra plugin and suits short, plain text clips, though it has a length limit and cannot save binary images directly. The second uses the Local REST API community plugin for Obsidian, which supports longer articles, checking whether a file already exists, overwriting files, and saving local image attachments, including images from Feishu logins and drawing boards. In this mode, the API key needed to talk to your vault stays only on your own device's local browser storage and is not synced through any account. The project deliberately stays local first: it does not upload anything to the cloud and does not use AI to summarize or rewrite content, limiting itself to accurate extraction, format conversion, preview editing, and local saving. Setting it up for development requires Node.js 20 or 22, after which the standard npm commands build the Chrome and Edge packages. The project is based on an existing open source clipper, adapted and rebranded with the original author's permission.

Copy-paste prompts

Prompt 1
Walk me through installing this extension in Chrome using the unpacked developer mode option.
Prompt 2
Help me set up the Obsidian Local REST API plugin so this extension can save images and long articles.
Prompt 3
Explain the difference between the Obsidian URI saving method and the Local REST API method here.
Prompt 4
Show me how to build and package the Edge version of this extension from source.

Frequently asked questions

What is web-content-clipper?

A Chrome and Edge browser extension that clips webpage content as Markdown and saves it straight into your Obsidian notes vault, with no cloud upload.

What language is web-content-clipper written in?

Mainly TypeScript. The stack also includes TypeScript, Chrome Extension, Obsidian.

How hard is web-content-clipper to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is web-content-clipper for?

Mainly general.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.