Web clipper for Logseq

Logseq keeps your notes local and block-based, but capturing web pages into it usually means copy-paste. Kliplet clips directly to your Logseq graph through its local API: the cleaned article, a selection, or highlights you mark land as blocks in the page you choose, without leaving your machine. Set it up once in Options, then save with a shortcut. The same extension also targets Notion, Obsidian, Joplin, Anytype, Bear and Markdown, and a local offline queue retries any clip that fails so nothing is lost on a bad connection.

Clip into your local graph

Kliplet talks to the Logseq local API running on your machine. You enable the API and paste its token into Options → Targets once; from then on, saving writes blocks straight into your graph. Because the request is local, the page content never goes through a Kliplet server.

What you can capture

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.

Add Kliplet to Chrome

FAQ

How does Kliplet save to Logseq?

Through the Logseq local API on your own machine. Enable it in Logseq, paste the token into Kliplet's Options, and clips are written as blocks directly to your graph — nothing routes through a Kliplet server.

Can it also clip to other tools?

Yes. Kliplet supports seven targets — Logseq, Notion, Obsidian, Joplin, Anytype, Bear and Markdown — selectable per clip with a reusable template each.

What if a clip fails on a bad connection?

Kliplet stores it in a local IndexedDB queue and retries automatically when you reconnect, so the capture is not lost.

Is my data private?

Yes. Clips to Logseq stay on your device, and Kliplet ships no analytics. The backend handles only payments, licensing and optional sync/AI.

What does Kliplet cost?

Free tier, Pro $3/month, or a $49 one-time Lifetime via Polar. Install from kliplet.com.