Before you capture (quick checklist)
The goal is simple: capture the exact page you care about, at the moment it matters. A strong proof starts with the right URL, the right timing — and the right capture method.
- news articles and blog posts
- public social posts / public profiles (via URL)
- pricing pages, policies, Terms, Privacy, legal pages
- product pages, listings, “what was promised” pages
the URL is publicly reachable and a logged-out browser would render the same content. Fastest workflow, available on every plan.
the page is behind login, paywalled, or only renders inside a session — social media accounts, analytics dashboards, admin panels, customer portals.
Method A — Create a proof from the dashboard (all plans)
This is the standard workflow: sign in, paste a public URL, and create a proof. It’s the fastest way to produce a Proof ID and export an Evidence ZIP — as long as the URL is publicly reachable.
Step 1 — Open the dashboard
Go to /app and sign in (a magic-link email works). Inside the dashboard you’ll see the option to create a new proof.
Step 2 — Paste the public URL
Paste the exact URL you want to capture — the deep link to the article, post, or page. Example:
https://example.com/article
Step 3 — Create the proof
Start the capture. GPA fetches the URL from its servers and records what was visible at that moment. The result is a tamper-evident proof record (screenshot, captured HTML/DOM, extracted text, structured report).
Step 4 — Copy the Proof ID (and optionally export Evidence ZIP)
After creation you get a Proof ID in the dashboard . You can share the proof link, and if needed export an Evidence ZIP for case files, external review, or offline verification.
Dashboard capture is server-side: GPA fetches the URL from its own backend, so it only works for content the public internet can see. The following are out of reach for this method:
- pages behind login (Gmail, internal admin panels, customer portals, intranets)
- social media analytics & business managers (Meta Business Suite, X / LinkedIn analytics, TikTok Studio, YouTube Studio)
- subscriber-only or paywalled articles when the paywall blocks unauthenticated requests
- anything that needs cookies, 2FA, or a logged-in session to render the actual content
For all of those, switch to the Browser Widget — it captures using your real, signed-in browser session, so even private content can be turned into a verifiable proof.
If this is for a dispute, investigation, or formal review, export the Evidence ZIP and archive it. Later you can demonstrate the ZIP is original and unchanged using verification.
Method B — Create a proof with the Browser Widget (Enterprise & Business)
The Browser Widget is a Chrome extension that captures pages directly from your browser. Unlike the dashboard it can do BOTH — a server-side fetch of public URLs AND a real-browser snapshot of pages behind login. One tool for every situation.
Pick the right mode for the page in front of you — the widget supports both, no extra tools needed:
Same engine as the dashboard, triggered with one click from the page you’re already on. Best for public articles, blog posts, public profiles, pricing pages.
GPA captures exactly what your real browser is rendering — including pages that need login, 2FA, paid subscription, or a specific session. Ideal for analytics dashboards, internal admin pages, social media accounts, customer portals.
Widget capture is available on the Enterprise and Business plans. If you don’t see widget options, check your plan in the dashboard.
Step 1 — Install the Chrome extension (one-time)
Install the GetProofAnchor Browser Widget from the Chrome Web Store. After installing, pin the extension so the GPA icon stays visible in your toolbar.
Step 2 — Connect with your API key (one-time)
Open the GPA dashboard , copy your API key from settings, and paste it into the widget. This authorizes the extension to create proofs on your account — no separate login each time.
Step 3 — Open the page you want to capture
Navigate to the page in your normal browser session — public article, social media inbox, analytics dashboard, internal tool, whatever the situation calls for. Make sure the key content is fully loaded and visible (scroll if needed).
Step 4 — Click the GPA icon and capture
Click the GPA icon, pick your capture mode (server or browser snapshot), and confirm. The widget creates the proof and returns a Proof ID in seconds. From here the workflow is identical to the dashboard: open the proof page, export Evidence ZIP, verify later.
- the page is behind login or requires a specific session
- you’re capturing social media inbox, DMs, internal posts, or private profiles
- you need analytics dashboards, admin panels, or customer-portal screens as evidence
- you’re doing repeated captures while reviewing content (change tracking, investigations, OSINT)
Common mistakes (avoid weak proofs)
- Capturing the homepage instead of the specific page that contains the claim or content you care about.
- Capturing too late — after the content was already edited or removed. Capture as soon as it matters.
- Not waiting for the page to load — missing key text, images, or dynamic content because capture fired too early.
- Trying to capture behind-login pages from the dashboard. The dashboard is server-side and can’t see your session. Use the Browser Widget (Enterprise & Business) — it captures from your real, signed-in browser.
Next steps
Once you’ve created your first proof, the next skill is verification: how to prove the evidence wasn’t altered later.
Continue with: How to verify a Proof ID and Evidence ZIP.
Not legal advice. Admissibility depends on jurisdiction and circumstances.