Pagium Web Clipper

Save the page you're looking at into your Pagium vault — a self-contained .html with inlined computed styles and images.

As of June 2026, Pagium Web Clipper has 1 users in the Productivity category.

Usersno change0%
1
1
Ratingno change0%
— reviews
Reviewsno change0%
Version
0.3.0
Manifest V3
90-day change · In the last 90 days this extension 1 version update.

History

3 snapshots

Tracking since May 26, 2026.

Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
DateUsersRatingReviewsVersion
May 26, 20260.2.0
Jun 2, 20260.2.0
Jun 8, 20260.3.0
Now10.3.0

Permissions & access

Permissions
activeTabcontextMenusstoragescriptingdownloadsdeclarativeNetRequestWithHostAccess
Host access
<all_urls>

Screenshots

Pagium Web Clipper screenshot 1Pagium Web Clipper screenshot 2Pagium Web Clipper screenshot 3Pagium Web Clipper screenshot 4

About

Pagium Web Clipper saves the active tab as one self-contained .html file — straight into a Pagium vault on your own disk. The whole capture happens locally, in two clicks, with no account and no clipping service in the middle.


TWO CAPTURE MODES

Reader — A clean single-column article, the way Safari and Firefox reader view does it. Comment threads, sidebars, author rails, and navigation are dropped. Content images are downloaded and embedded as data: URIs so the file opens offline even if the source ever goes down.

Snapshot — A full-fidelity copy of the whole page. The page's authored CSS is inlined, computed styles are baked in, and content images are embedded as data: URIs. Orphaned overlay and scroll-lock CSS is scrubbed so nothing covers the saved page when you reopen it.

In both modes, images are downscaled to fit 1600px and re-encoded as WebP so clips stay a sensible size.


HOW IT REACHES PAGIUM

There's no token to copy, no server to sign in to. The extension stages the cleaned HTML at ~/Downloads/.pagium-clipper/, then opens a pagium:// URL — exactly how Obsidian's URL scheme works. macOS hands the file off to Pagium, which sanitises it again on its side and atomically writes it into your vault. No network involved between the extension and the app.


WHAT GETS CAPTURED

Every clip lands as one .html file with a few meta tags so Pagium can index it:

  pagium:source    — the URL you clipped
  pagium:captured  — ISO-8601 timestamp
  pagium:title     — page title
  pagium:tags      — your tags (set in "Clip with options…")
  pagium:kind      — webclip

The clip is plain HTML you can open in any browser, attach to an email, or check into git. Nothing about the file phones home.


TRIGGERS

  • Toolbar icon — silent save to "Clippings/"
  • Right-click "Clip page to Pagium" — same
  • Right-click "Clip selection to Pagium" — saves only the selected text
  • Right-click "Clip with options…" — opens the popup so you can set title, tags, target vault
  • ⌘⇧S (macOS) / Ctrl+Shift+S — opens "Clip with options…"


MULTIPLE VAULTS

Add vault names in the options page. The first one becomes the default for silent clips; switch with the radio in the options list. If your vault list is empty, every clip goes to whichever vault Pagium currently has open.


REQUIREMENTS

  • Pagium desktop app 0.11.0 or later (macOS)
  • Pagium must be running with a vault open before you clip

Pagium is free at https://pagium.app.


PRIVACY

The clipper collects nothing, transmits nothing, and stores nothing remotely. Every clip is assembled in memory on your machine and written to your own disk. Full policy at https://pagium.app/clipper/privacy.

Questions: [email protected]

Technical

Version
0.3.0
Manifest
V3
Size
101KiB
Min Chrome
88
Languages
2
Featured
No

Metadata

ID
ijbgiciaecccjdnomgblkcppiepohlbk
Developer ID
ub4e866a8a9ecc72852318c51067a7c9d
Developer Email
[email protected]
Created
May 25, 2026
Last Updated (Store)
May 28, 2026
Last Scraped
Jun 8, 2026
Website
pagium.app

Data sourced from the Chrome Web Store · last verified Jun 8, 2026.