Kliplet
Web clipper for Notion
Saving web pages to Notion can produce a readable article rather than only a link, with the source fields you choose. Kliplet clips to Notion through the official API: a simplified article, full page, selection, or URL-only record goes from your browser to the database or page you selected, with a reusable template for properties such as title, source, tags, and date. Kliplet does not durably replay Notion writes because a lost create response could otherwise produce a duplicate; inspect Notion before saving again. Separately, Alt+H stores page highlights locally and reapplies them when you revisit the source page.
Connect once
Authorize the Notion integration for your target database in Options → Targets. The one-time authorization code and token response transit the Kliplet backend for OAuth exchange but are not persisted there; the returned access token is stored locally via chrome.storage.local and then sent only to Notion's API.
What you can clip
- Simplified article cleaned to readable blocks, with source URL and metadata.
- Full page with the complete page content.
- Selection — only the passage you selected before saving.
- 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 sent to Notion 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.
Database properties via templates
Map a template per target so each clip lands with the right Notion properties filled in. Templates can sync across devices on the paid tier after separate consent.
Fail closed after an ambiguous create
Kliplet does not durably replay Notion writes because a lost create response could otherwise create a duplicate page. Inspect Notion 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.
FAQ
Does Kliplet use the official Notion API?
Yes. Clips are written to your Notion database or page through Notion's API using an integration token you authorize once. The token is stored locally and used only to talk to Notion directly.
Can I auto-fill Notion database properties?
Yes. Create a template that maps title, source URL, tags and date to your database properties, so every clip arrives correctly structured.
What happens to a clip if I'm offline?
No. Kliplet does not durably replay Notion writes because a lost create response could otherwise produce a duplicate. Inspect Notion 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.
Does my page content pass through Kliplet servers?
The Notion destination write goes directly from your browser to Notion. Optional AI separately sends submitted text to your provider; optional paid sync separately sends disclosed template/highlight records after opt-in. The Kliplet extension ships no usage analytics.
How much is Kliplet and where do I install it?
Install the published Chrome MV3 extension from kliplet.com. Free supports unlimited clips to one selected destination per action; Pro and Lifetime add simultaneous multi-target clipping. See the official Kliplet site or Store listing for current pricing and terms.