Skip to main content
← Back to tutorials

Browser extension (every paid plan)

Capture what you see in your own browser — public pages or anything behind login. You get the same proof page and Evidence ZIP as from the dashboard, one click from the page you’re on.

The Chrome extension is the easiest way to capture content behind login, 2FA or paywalls yourself — analytics dashboards, social media inboxes, admin pages, customer portals. For public pages it can also start a server capture, just like the dashboard.

Tutorial Browser extension All paid plans Chrome ▶ With video ~7 min read
Quick overview

The GetProofAnchor browser extension runs in Chrome. After a one-time install + API key setup, you can capture from any page in your browser — including content behind login. Available on every paid plan, including the 9 € Starter Pack. No subscription is needed for it.

Requirements

  • Any paid plan – including the 9 € Starter Pack. (If you don't see extension options, check your plan in the dashboard.)
  • Google Chrome 116 or newer on Windows, macOS or Linux.
  • Active GetProofAnchor account with an API key generated in the dashboard settings.
  • The page you want to capture must be openable in your own browser — public, or one where you're already signed in. The extension captures from your real browser session.

Step 1 — Install the Chrome extension and connect your API key

The setup is one-time and takes about a minute. The video below walks through the entire flow — install, API key, first capture.

Video walkthrough (≈ 2 min) · Install the Chrome extension, paste your API key, capture content behind login.
Watch on YouTube ↗

1.1 — Install the extension

Add the GetProofAnchor browser extension from the Chrome Web Store. After installation, click the Chrome puzzle icon in the toolbar and pin GetProofAnchor so the icon stays visible.

1.2 — Connect with your API key

Open the GPA dashboard , go to settings, and copy your API key. In the extension popup, paste the key and confirm. The extension is now authorized to create proofs on your account — no separate login each time.

Tip for managed browsers

If your organization uses managed Chrome, ask IT to allow the GetProofAnchor extension and (optionally) pin it by policy. The extension needs no special permissions beyond reading the active tab when you click it.

Step 2 — Pick the right capture mode

The extension supports two capture modes. Both produce the same kind of record — the same proof page, the same Evidence ZIP, the same protection layers — but they reach different parts of the web.

Mode A · Server capture
Public pages

The extension tells the GPA backend to fetch the URL from its servers and render it in a clean, headless browser. Same engine as the dashboard. Use this for content that's reachable by anyone, no login needed.

Perfect for: public articles · blog posts · public social profiles · pricing pages · news

Mode B · Browser snapshot
Behind login (the killer feature)

The extension captures exactly what your real browser is rendering — including pages that require login, 2FA, paid subscription, or a specific session. The captured screenshot, DOM and text reflect what you actually see on your screen, in your account, right now.

Perfect for: analytics dashboards · social media inbox / DMs · internal admin pages · customer portals · subscription content · webmail

Privacy note

The browser snapshot uploads the captured page: screenshot, HTML and MHTML, extracted text, the network log and capture metadata. Before sealing, cookie values, authorisation headers and session tokens are masked, and every masking is recorded. Your saved passwords and browsing history never leave your computer. The extension only reads the active tab when you explicitly click capture.

Step 3 — Capture

Once the extension is installed and the API key is connected, capture is fast:

  1. Open the page you want to capture in your browser. For behind-login content, make sure you're already signed in and the key information is visible (scroll if needed).
  2. Click the GPA icon in your toolbar, then pick the mode — Server for public URLs, Browser snapshot for everything else.
  3. Confirm. The capture takes a few seconds (Server) or runs in your tab and uploads the artifacts (Browser snapshot).
  4. When it’s done, the extension shows a link to the proof in your dashboard.
Practical tips

A few small things that make captures cleaner — especially for behind-login content:

  • For behind-login content, sign in BEFORE clicking capture. The extension uses your current session — if you're not logged in, you'll capture the login screen instead.
  • For dynamic / lazy-loaded content (Twitter timeline, infinite-scroll lists, deferred images), scroll through the page first so the content you care about is rendered.
  • For single-page apps (SPAs), wait until the page is fully loaded — visible network spinners or skeleton screens mean content is still arriving.
  • If a cookie banner or modal is blocking the content, dismiss it first. (Server capture auto-handles many CMP banners; the browser snapshot captures whatever is on screen at the moment of capture.)

Step 4 — After capture (same artifacts as the dashboard)

Whichever mode you used, the result is the same kind of tamper-evident record as a dashboard capture:

  • a proof page — private by default; publish it in the dashboard when you want to share a public link that anyone can verify without an account
  • an exportable Evidence ZIP — portable, self-contained, offline-verifiable (manifest, hash chain, Bitcoin OpenTimestamps anchor, eIDAS qualified timestamp)
  • the same protection layers — the capture is added to the hash chain, sealed with a qualified eIDAS timestamp and anchored in Bitcoin. Note: the extension captures on your device and the timestamp proves when our server received it; for independent observation use a server capture, Assisted Capture or Forensic Browser
What to do next

Two natural follow-ups:

Extension vs dashboard — which to use?

Both produce identical, tamper-evident proof records. Pick based on the page you're trying to capture:

Reach for the extension when…
  • the page is behind login, 2FA, or a paywall
  • you're capturing analytics dashboards, social media DMs, internal admin tools, or customer portals
  • you want to capture quickly while reviewing content, without copy-pasting URLs
  • you're doing repeated captures (investigation, change tracking, OSINT)
Reach for the dashboard when…
  • the page is publicly reachable and a logged-out browser would render the same content
  • you have a list of URLs to capture from records or notes
  • you don’t want to install anything — the dashboard works on every paid plan
  • you're managing or browsing existing proofs in the workspace
Next tutorial

Continue with: How to verify evidence — proof link, Evidence ZIP, online and offline.

Not legal advice. Admissibility depends on jurisdiction and circumstances.