Joplin Web Clipper icon

Joplin Web Clipper

An open-source extension that saves web pages and screenshots into your Joplin notes.

Add to Chrome Open source · Chrome Web Store · Source on GitHub

Why it's a strong pick

Joplin Web Clipper is the clipper for Joplin, which its README calls a free, open source note-taking and to-do app. The extension is open source under AGPL-3.0-or-later and uses Manifest V3, Chrome's current extension format. The project updated the clipper's source in 2026. That date is a repo update, not a release.

What it does

It captures web pages and screenshots from your browser and saves them to Joplin. You can clip the complete page, the page as HTML, a simplified page, the URL or a selection. Clips go to the last notebook you selected. It talks to the Joplin desktop app through a local service.

Key features

  • Several clip types. Complete page, complete page (HTML), simplified page, URL and selection.
  • Screenshots. It can save screenshots as well as pages.
  • Shortcuts. Alt+Shift+J opens it, and Alt+Shift+C clips the complete page.
  • Last notebook. Clips go to the notebook you used last.
  • Local link. It connects to the Joplin desktop app.

Who it's for

It is for Joplin users who want one-click saving of articles and screenshots into their notebooks. If you do not use Joplin, it will not help you. The extension is free, and Joplin is described as free and open source. We did not check Joplin Cloud prices.

What permissions does Joplin Web Clipper ask for?

Its manifest asks for activeTab, tabs, scripting and storage, and for access to all sites. Access to all sites lets it read and clip any page you choose. This is the source manifest in the project repo, not the store listing. Read the install prompt before you add it.

Does it need the Joplin app?

Yes. The clipper needs the Joplin desktop app running, with the Web Clipper service turned on. The project's troubleshooting page says a firewall, a proxy or a stopped service can stop it working. The port is set in the desktop app.

Where do my clips go?

Per the project's clipper documentation, clips go to the Joplin desktop app through a local service, and the port is set in that app. We found no privacy statement in the repo. We could not read the developer's privacy policy when we checked; read it before installing.

FAQ

Is it free? The extension is free. Joplin is described as free and open source.

Does it work without Joplin? No. It needs the Joplin desktop app.

Is it open source? Yes, under AGPL-3.0-or-later.

Good to know

If a clip fails, check three things: the Joplin app is open, the Web Clipper service is on, and no firewall or proxy blocks the local port. The "last updated" date we use is a repo commit date, not a store release date. Clip a short page first to test your setup.

Other note-taking tools to compare

Joplin Web Clipper is one of 8 picks in our note-taking guide:

  • Notion Web Clipper: Made by Notion. Save a web page into a Notion page or database in a few clicks. Notion account needed.
  • Google Keep: Google's own extension for saving page info, selections and images into Keep notes. Free, Google account needed.
  • Evernote Web Clipper: Clip articles, full pages and screenshots into your Evernote account, then mark them up. Free extension, Evernote account needed.
  • OneNote Web Clipper: Microsoft's extension for clipping web pages into OneNote. Free to use, Microsoft account needed.
  • Obsidian Web Clipper: Obsidian's own free extension. It highlights pages and saves them into your local vault as Markdown. Needs the Obsidian app.
  • Hypothesis: Open-source extension for highlighting, annotating and tagging web pages and PDFs with your Hypothesis account.
  • SiYuan Clipper: Clips a selection or a whole page into your SiYuan notes. Needs the SiYuan app and its API token to work. Source on GitHub (Mulan PSL v2).

Also see: Evernote Web Clipper alternatives

This is a third-party extension, not built or maintained by Xplorekit. We link to the official Chrome Web Store listing — install and permissions are entirely between you and the extension's own publisher.