Kliplet
Web clipper for Obsidian
Obsidian's own Web Clipper is excellent and local-first, but it only writes to Obsidian. If your notes are split across Obsidian and other tools, you end up running several clippers. Kliplet clips to your Obsidian vault through the Local REST API — the request goes to the API on your own machine (for example https://127.0.0.1:27124), so the page content never leaves your device — and the same extension also saves to Notion, Logseq, Joplin, Anytype, Bear or a Markdown file. You can capture the full article, a selection, or highlights you mark on the page, shape the note with a reusable template, and rely on a local offline queue that retries clips that fail on a bad connection.
How clipping to Obsidian works
Kliplet talks to the Obsidian Local REST API running in your vault. You paste the API key once into Options → Targets; from then on, pressing Save writes the note directly to your vault. Because the request is to localhost, nothing about the page goes through a Kliplet server.
What you can capture
- Full article — cleaned to readable Markdown, with the source URL and metadata.
- Selection — just the part you highlighted before saving.
- Highlights — passages you mark on the page, reapplied when you revisit it.
Templates and frontmatter
Map a reusable template per target so every clip lands with the frontmatter and folder you want — tags, source, date, and any properties your vault expects. Templates can sync across devices on the paid tier.
Why one clipper for many tools
If you also keep notes in Notion or Logseq, Kliplet means one keyboard shortcut and one template system instead of a separate clipper per tool. The offline queue (stored locally in IndexedDB) retries any clip that fails, so a flaky connection never loses the capture.
FAQ
Does Kliplet need the Obsidian Local REST API plugin?
Yes. Kliplet writes to your vault through the Local REST API community plugin. Install and enable it in Obsidian, then paste its API key into Kliplet's Options once. Requests go to the API on your own machine, so content stays local.
Does the page content reach a Kliplet server when clipping to Obsidian?
No. The clip is sent from your browser straight to the localhost REST API in your vault. Kliplet's backend handles only payments, licensing and optional sync/AI — never your clipped pages.
Can the same extension also clip to Notion or Logseq?
Yes. Kliplet supports seven targets — Obsidian, Notion, Logseq, Joplin, Anytype, Bear and Markdown download — selectable per clip, with a reusable template for each.
What if a clip fails because I am offline?
Kliplet stores the clip in a local IndexedDB queue and retries it automatically when you reconnect, so the article is not lost.
How much does Kliplet cost and is it on the Chrome Web Store?
Kliplet is a published Chrome (Manifest V3) extension; install it from kliplet.com. There is a free tier, Pro at $3/month, and a $49 one-time Lifetime, billed via Polar.