On August 10, 2026, GoFullPage — for years the default answer to "how do I screenshot a whole scrolling page in Chrome" — disappeared from the Chrome Web Store amid a copyright dispute. A month later, on September 10, it was back. If you just needed the button to work again, nothing changed. But the gap month did something durable: tens of thousands of people who had never thought about where their full-page screenshots go suddenly had to pick a replacement, and a lot of them looked at the permission list for the first time.
That's the question this piece actually answers. Not "is GoFullPage good?" — it's fine, and familiar. The question is: once you've been reminded that a capture tool can vanish, upload, or change hands, do you want a full-page screenshot tool whose privacy depends on trust, or one whose privacy is enforced by the platform?
Why "it's back" isn't the whole story
Three things happened that don't undo themselves when a listing returns:
- Removal risk is real. An extension can be pulled for policy or legal reasons with no warning to users. If your workflow depends on one tool and it vanishes mid-project, you're stuck. Diversifying, or choosing a tool with a minimal attack surface, is a reasonable response.
-
Trust, once examined, is hard to un-examine. During the gap, users opened
chrome://extensionsand read permissions they'd ignored for years. Many full-page capture tools request<all_urls>— read and change your data on every site you visit. That's often necessary to stitch a page, but you should know you granted it. - "Back" can mean "changed." Ownership, privacy policy, and code all can shift during a dispute and its resolution. If you rely on the old behavior, re-read the current listing rather than assuming continuity.
None of this is an accusation against GoFullPage specifically. It's the general lesson: a capture tool that touches every page you visit deserves the same scrutiny you'd give a password manager.
The actual alternatives, judged honestly
1. Chrome DevTools — native, free, no install. Open DevTools (F12) → Command Menu (Ctrl/Cmd+Shift+P) → type Capture full size screenshot. Chrome renders the entire page and saves a PNG. Genuinely excellent for a one-off, zero permissions, nothing installed, nothing uploaded. Limits: no annotation, no PDF, no fixed-header suppression (sticky nav bars can smear or repeat), and it's clunky to reach for daily. This is the honest baseline everyone should know before installing anything.
2. Microsoft Edge — built-in "Web capture." If you're already on Edge (or Chromium Edge), Web Capture does full-page and region grabs with a markup panel. No install, local by default. Limits: Edge-only, markup is basic, and it's tied to a browser many teams don't standardize on.
3. Firefox Screenshots / FireShot. FireShot is a long-standing cross-browser extension with rich annotation and PDF export. It's capable and popular. The privacy trade-off is the same as most full-page tools: it needs broad host permissions to render and stitch, and it offers cloud/share features you must be careful not to trigger. Fine if you audit settings; not "zero-upload by architecture."
4. ShareX (Windows, open source). The power-user's choice: full-page capture via scrolling, annotation, and a huge automation pipeline. Open source, so verifiable. But it ships with upload destinations (Imgur, S3, FTP) and "after capture" tasks that can push an image to a server the instant you release the mouse. Privacy outcome depends entirely on settings many people never open. Excellent if you'll configure it; risky on default.
5. Local-only Chrome extensions (the category SnapPage is in). A newer approach: a capture extension that declares zero host_permissions and contains no remote code, so it operates only on the single tab you explicitly invoke it on, and Chrome itself blocks any attempt to transmit the result. This trades the "works on everything automatically" convenience of <all_urls> tools for a hard, platform-enforced guarantee that the capture can't leave the device.
The privacy-dimension comparison
| Tool | Full-page capture | Annotation | Host permissions | Uploads your capture? | Verifiable? | |
|---|---|---|---|---|---|---|
| Chrome DevTools (native) | Yes | No | No | None (built in) | No | Yes — it's the browser |
| Edge Web Capture | Yes | Basic | No | None (built in) | No | Yes |
| FireShot | Yes | Rich | Yes | Broad (<all_urls> typical) |
Optional / share features | Partly |
| ShareX (Windows) | Yes (scroll) | Rich | Via pipeline | N/A (desktop) | Only if after-capture tasks enabled | Yes — open source |
| GoFullPage | Yes | Basic | Yes | Broad | Per current policy — re-check | Partly |
| SnapPage (local-only) | Yes | Yes | Yes (Pro) | Zero | Never — no code path | Yes — inspectable manifest |
Read the "uploads" column against the "verifiable" column. Several good tools land on the safe side by default but you're trusting a setting or a policy. Only the last row is safe by architecture — the browser, not a promise, is what stops an upload.
Which should you pick?
- Need a one-off full-page PNG right now, nothing installed: DevTools native. It's free and already there.
- On Edge and want markup: Web Capture.
- Windows power user who will audit settings and wants automation: ShareX.
- Want cross-browser rich annotation + PDF and accept broad permissions: FireShot.
- Want GoFullPage's exact workflow back: it's returned — just re-read its current permissions and policy before you re-grant
<all_urls>. - Want a full-page tool where "never uploads" is enforced by Chrome, not promised: that's the gap the local-only category exists to fill.
Disclosure: I build **SnapPage* (full-page) and SnapLocal (region capture + annotation), so I'm not neutral — treat the comparison above as one developer's reading, and verify every permission yourself in chrome://extensions and the Network panel. Both are local-only with zero host_permissions, no account, no telemetry. SnapLocal is on the Chrome Web Store now; annotation tools are free, Pro is a one-time $19. SnapPage is $15 one-time (free = 3 captures/day). Full comparison notes: https://cj.66buff.com/blog/gofullpage-alternative-full-page-screenshot.html · SnapLocal: https://chromewebstore.google.com/detail/gmeldoinlnbnpieonbkienddaahcennf*
SnapPage's Chrome Web Store listing is currently under review — I'll update this article with the store link as soon as it's live. You can already get SnapPage today: purchase at https://payhip.com/b/gjBUT, or read more at the official site https://cj.66buff.com/
Top comments (0)