Kliplet
How to save web pages to Logseq
Getting web content into Logseq usually means copy-paste into a block. This guide shows how to clip pages straight into your Logseq graph with Kliplet, using the Logseq local API: enable the API, paste its token into Kliplet once, then save a simplified article, full page, selection, or URL-only record as blocks in the page you choose. The default destination request stays on your machine, and Logseq writes are not durably replayed because a lost create response could otherwise produce duplicate blocks. Optional AI is a separate opt-in data flow.
One-time setup
- In Logseq, enable the local HTTP API and copy its authorization token.
- Install Kliplet from kliplet.com, open Options → Targets, add Logseq, and paste the token.
- Optionally template how the blocks and properties are written.
Save a page
- Open the article and optionally select text if you want a selection clip.
- Trigger Kliplet, pick Logseq, and choose simplified article, full page, selection, or URL-only.
- The chosen clip content is written as blocks into your graph, with the source link.
Fail closed after an ambiguous create
With the default loopback endpoint, the Logseq destination write stays on your device; a LAN or remote HTTPS endpoint receives the clip and credential if you configure one. The Kliplet extension ships no usage analytics. If you separately enable AI, up to 12,000 characters of extracted clip text are sent to your chosen provider. 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.
Persistent local highlights
Alt+H stores page highlights locally and reapplies them on revisit. They are not written into Logseq by default; a paid user can include them only by explicitly creating a custom template with {{highlights}}.
Beyond Logseq
The same extension also saves to Notion, Obsidian, Joplin, Anytype, Bear on macOS and Markdown, so one workflow covers every tool you use.
FAQ
How does Kliplet save to Logseq?
Through the Logseq local HTTP API on your machine. Enable it, paste the token into Kliplet's Options, and the destination write goes directly into your graph. Optional AI is a separate opt-in request to your chosen provider.
Can I save a selection, and what happens to page highlights?
Yes. Select text before saving to use selection mode. Alt+H highlights stay local and reappear on the source page; they reach Logseq only when a paid user explicitly creates a custom template containing {{highlights}}.
Does the content leave my device?
With the default Logseq loopback endpoint, the destination write stays on your device. A LAN or remote HTTPS endpoint receives it if you configure one. If you enable AI, up to 12,000 characters of extracted clip text are separately sent to your chosen provider. The Kliplet extension ships no usage analytics.
What if a clip fails offline?
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.
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.