The web clipper

Saving a page

Click the Permanent Record icon on any page, then Save Page. Before saving you can:

• Collection — file the page into one of your collections.
• Tags — search your existing tags or create new ones.
• Notes — attach a note to the saved document.

The popup shows progress (capturing, building archive, saving), then offers View in Permanent Record. If a save is interrupted at the last step, the popup offers a retry. There is also a Download button if you want a local copy of the capture.

PDFs work too: if the current tab is a PDF, the clipper saves the PDF file itself.

Capture quality

The clipper archives the full page as it appears in your browser at the moment you save — text, layout, and styling, including content inside same-origin frames and shadow DOM. Scripts are neutralized in the archive, so the saved copy is a faithful snapshot rather than a running web app.

Anything you typed into forms on the page is cleared before the capture leaves your browser, and password or hidden fields are always stripped. See the capture policy for everything that’s deliberately excluded.

Known limitations

• Only standard web pages (http/https) can be saved — not browser-internal or extension pages.
• Captures are capped at 50 MB of page content.
• Content inside cross-origin iframes (for example, embedded third-party widgets) isn’t traversed.
• Interactive features of the original page (players, apps, comment forms) don’t run in the archived copy.
• Pages that match the capture safety rules — sign-in, checkout, banking, and similar — are blocked from saving. The popup tells you why. See the capture policy.

Extension permissions

The extension requests activeTab, scripting, storage, and downloads. It acts only on the tab you invoke it on, when you invoke it. It does not run in the background on pages you visit and does not collect browsing history.

Telemetry

The extension sends diagnostic telemetry to Permanent Record’s own servers (never to third parties), limited to:

• Error reports — error type, message, and stack trace when something in the extension fails, so we can fix it.
• Save performance — timing for each stage of a save, page-shape counts (number of DOM nodes, images, stylesheets), and capture sizes in bytes.

Telemetry never includes page content. URLs are reduced to origin and path — query strings are stripped — and values that look like credentials, tokens, or cookies are redacted before anything is sent.