Kliplet
Web clipper for Joplin
Joplin has its own clipper, but if you also keep notes in Notion or Obsidian you end up juggling several. Kliplet saves to Joplin through its local Data API — the cleaned article, a selection, or highlights you mark are written straight to your notebook on your own machine — and the same extension also targets Notion, Obsidian, Logseq, Anytype, Bear and Markdown. A reusable template per target keeps notes consistent, and a local offline queue retries any clip that fails, so a dropped connection never loses an article.
Clip to your Joplin notes
Kliplet uses the Joplin Data API served locally by the Joplin app. Enable the Web Clipper service in Joplin, paste its token into Options → Targets, and saving writes the note directly to the notebook you pick. The request stays on your device.
What you can capture
- Full article as Markdown with the source link.
- Selection — only the part you chose.
- Highlights marked on the page.
One clipper for every tool
Keep a single shortcut and template system whether the destination is Joplin, Notion, Obsidian or Logseq, instead of a separate clipper per app.
FAQ
How does Kliplet connect to Joplin?
Through the Joplin Data API exposed by the Joplin app's Web Clipper service on your machine. Enable it, paste the token into Kliplet's Options, and clips are written locally to your chosen notebook.
Does the clip leave my device?
No. The note is sent from your browser to Joplin's local API. Kliplet ships no analytics; its backend handles only payments, licensing and optional sync/AI.
Can the same extension clip to Notion and Obsidian too?
Yes. Kliplet supports seven targets — Joplin, Notion, Obsidian, Logseq, Anytype, Bear and Markdown — chosen per clip.
What if a save fails offline?
It is queued locally in IndexedDB and retried when you reconnect, so the article is preserved.
What does it cost?
Free tier, Pro $3/month, or $49 one-time Lifetime via Polar. Install from kliplet.com.