Kliplet
Web clipper for Logseq
Logseq keeps your notes local and block-based, but capturing web pages into it usually means copy-paste. With the default loopback endpoint, Kliplet clips a simplified article, full page, selection, or URL-only record directly to your Logseq graph through its local API. If you configure a LAN or remote HTTPS endpoint instead, that endpoint receives the clip and credential. Set it up once in Options, then save with a shortcut. Separately, Alt+H stores page highlights locally and reapplies them on revisit, while Logseq writes are not durably replayed because a lost create response could otherwise produce duplicate blocks.
Clip into your local graph
Kliplet talks to the Logseq API endpoint you configure. With the default loopback endpoint, the request remains on your machine; a LAN or remote HTTPS endpoint receives the clip content and credential. If you separately enable AI, extracted clip text is sent to your chosen provider.
What you can clip
- Simplified article as readable blocks with the source link.
- Full page with the complete page content.
- Selection — just the passage you selected.
- URL-only — a lightweight record without the page body.
Persistent local highlights
Alt+H stores passages locally and Kliplet reapplies them when you revisit the source page. They are not written to Logseq by default. A paid user can include them only by explicitly creating a custom template with {{highlights}}; optional paid sync uploads disclosed highlight records only after separate consent.
Templates and one shortcut for every tool
Use a reusable template per target for consistent frontmatter and placement, and keep a single clipping workflow whether the destination is Logseq, Notion or Obsidian.
FAQ
How does Kliplet save to Logseq?
Through the Logseq API endpoint you configure. The default loopback endpoint stays on your machine; a LAN or remote HTTPS endpoint receives the clip and credential. Optional AI is a separate opt-in request to your chosen provider.
Can it also clip to other tools?
Yes. Kliplet supports seven targets — Logseq, Notion, Obsidian, Joplin, Anytype, Bear on macOS and Markdown — selectable per clip with a reusable template each.
What if a clip fails on a bad connection?
No. Kliplet does not durably replay Logseq writes because a lost create response could otherwise produce duplicate blocks. Inspect Logseq before saving again. Only an eligible ordinary Obsidian text write whose exact vault path was resolved before its first request can enter Kliplet's local queue, with up to four automatic attempts. Screenshots and writes to Notion, Joplin, Logseq, Anytype, Bear, and Markdown are not replayed.
Is my data private?
The Logseq destination write stays on your device with the default loopback endpoint; a LAN or remote HTTPS endpoint receives it if you configure one. The Kliplet extension ships no usage analytics. Optional AI and sync are separate disclosed flows; the backend also handles Notion OAuth, payments, and licensing.
What does Kliplet cost?
Free supports unlimited clips to one selected destination per action; Pro and Lifetime add simultaneous multi-target clipping. Install from kliplet.com and see the official site or Store listing for current pricing and terms.