Clipwise saves any web page to your Notion databases — the whole article, not half of it. No account, no login, no paywall. Fill in your database properties before saving, and it remembers your last one. Everything stays on your computer.
Forum Threads
View all
Notion Web Clipper (Open Source )
@tehreem_fatima5 Thank you, Tehreem! The empty-page warning actually came from reading reviews of other clippers — the most frustrating complaint was people discovering weeks later that a page they'd saved was empty. Better to know before you hit save.
Out of curiosity, what do you usually clip into Notion — articles, research, recipes?
The "if a page comes out empty, it tells you instead of silently saving nothing" detail is the kind of thing you only add after getting burned by the alternative. Just left a review - the single-paste Notion connection instead of a full OAuth account flow is a nice touch too.
@galdayan Thanks for the review, Gal! Skipping the OAuth flow was deliberate — OAuth would have meant running a server, and the whole point was that nothing leaves your computer.
@roan_steenstra_perez that makes sense, and it's a good tradeoff for a solo-dev tool where the whole pitch is trust. one more question since you're a solo maintainer - if Notion changes their API on you, does a broken integration fail loudly with an error the user sees, or silently stop saving?
@galdayan Great question, and a fair one to ask a solo maintainer. The short answer is: loudly, for the most part.
Clipwise pins a specific version of the Notion API, and Notion keeps older versions running when they release new ones, so an update on their side won't quietly break things overnight. If a save does fail in the popup, you see Notion's own error message right there — never a silent "saved" that didn't actually save.
To be fully honest, there's one weak spot: the keyboard shortcut. When it fails, the icon turns red with a "!", but it doesn't tell you why, so you'd have to open the popup to find out. Your question made me look at that properly, so it's going into the next update. Thanks for pushing on it!
@galdayan Thanks Gal, that means a lot. And it's already done: in the next update the shortcut tells you exactly what went wrong instead of just showing a red "!". It's going through review now.