GoFullPage was removed from the Chrome Web Store

Updated 14 August 20267 min readNitesh Padghan

On 10 August 2026 the GoFullPage listing disappeared from the Chrome Web Store, and Chrome disabled the extension for a share of its 11 million users with a warning that it "violates the Web Store policy." That wording implies something it did not mean here. By the developers' own account this was a copyright complaint about a design element, not malware, not a data leak, not a sale to a shady buyer.

What actually happened

The sequence, as far as it can be reconstructed from the developers' statements and press coverage:

10 August 2026. The GoFullPage listing goes offline. Users start reporting the extension greyed out and disabled, with Chromium browsers showing the standard delisting warning.
11 August 2026. GoFullPage publishes an update confirming the removal, stating "this was not a security issue with GoFullPage" and attributing it to "a request to remove a particular design element that is not central to our brand."
13 August 2026. Press coverage picks it up. Developer Peter Coles describes the takedown as an overreach, says Google has been in contact and that work is underway to restore the listing, and specifically denies that the extension has been sold.

Two details are worth separating, because they get conflated everywhere. The delisting is a store decision. The disabling of your installed copy is a separate Chrome behaviour: when an extension leaves the store for a policy reason, Chrome flags it in installed browsers, whether or not the code was ever a problem. The scary red wording is generic. It is the same string Chrome shows for a genuinely malicious extension and for one caught in a trademark dispute.

Nothing here suggests your past screenshots were exposed. GoFullPage's capture happens in the browser. A store delisting does not retroactively send anything anywhere, and no party involved has alleged a data incident.

Do this first, before you touch anything

The single most damaging thing you can do right now is hit Remove. While the listing is down there is no way to reinstall it in Chrome: not from the store, not from a link, not from a cached page. The copy on your machine is currently the only copy you can get.

Open chrome://extensions in a new tab.
Find GoFullPage. If it is greyed out with a warning, try the toggle; many users have been able to simply re-enable it.
If it re-enables and still captures, you are fine for now. Leave it alone and skip to the next section anyway.
If Chrome refuses to re-enable it, do not remove it. An extension that is disabled can be re-enabled later if the listing returns; one that is deleted cannot come back until it does.

The same applies in Brave, Arc, Opera and Vivaldi. They install from the Chrome Web Store, so they inherit the delisting. Edge does not; see below.

Getting your existing captures out

If you keep a working library inside the extension rather than saving files to disk, treat that as at-risk data and export it while you still can. An extension you cannot reinstall is an extension whose stored data you cannot recover once it is gone. Download anything you would be sorry to lose, as ordinary PNG or PDF files, into a folder you control.

This is a good moment to notice the general lesson: a screenshot tool that keeps your work inside itself, or inside someone's cloud account, has a failure mode that a tool which hands you a file does not.

The Edge workaround

Microsoft Edge runs its own add-ons store, so the Chrome Web Store removal does not apply there. The GoFullPage team says the extension, including paid premium access, continues to work normally on Edge. If you have a premium subscription and a deadline, installing Edge for an afternoon is the least disruptive path available today.

Chrome's built-in capture, no extension needed

Chrome has shipped a full-page screenshot command for years. It is buried in DevTools, it has real limitations, and for a one-off it is entirely adequate:

Open the page you want.
Press F12 (Windows/Linux) or ⌘⌥I (Mac) to open DevTools.
Press Ctrl⇧P or ⌘⇧P to open the command menu.
Type screenshot and choose Capture full size screenshot.

What it will not do: it does not scroll the page first, so anything lazy-loaded below the fold may come out blank; it struggles with pages that scroll an inner pane rather than the document; it gives you a PNG and nothing else: no PDF, no cropping, no annotation. It is a fallback, not a replacement. There is a fuller walkthrough, including the failure cases, in how to take a full page screenshot in Chrome.

If you want a replacement instead

Plenty of people will decide that an 11-million-user extension going dark overnight is a reason to hold their screenshot tool a little more loosely. If that is you, the criteria worth applying are less about feature lists than about how much the tool can hurt you later:

Does it capture locally? If pages are rendered on someone's server, every page you capture, including anything behind a login, leaves your machine.
What permissions does it ask for? "Read and change all your data on all websites" is standing access to everything you browse. activeTab is access to one tab, at the moment you click, expiring on its own.
Does it require an account? An account is a second thing that can be discontinued, priced up, or breached.
Can you read the source? Not everyone will. But an extension whose code is public can be forked and loaded unpacked if its store listing ever disappears, which is exactly the situation this page is about.

A side-by-side of the realistic options is in the GoFullPage alternatives comparison, and a wider roundup in the best full-page screenshot extensions for Chrome.

The one I build

Full Page Screenshot is free, has no account and no premium tier, makes no network requests at all, and asks only for activeTab. It scrolls and stitches, handles sticky headers so they don't stripe down your image, and exports PNG, JPEG or PDF with cropping and annotation included rather than sold separately. The source is MIT licensed, so if it ever vanishes from a store, you can still load it unpacked.

Get it

Compare it against GoFullPage

Written by someone with an obvious interest in your choice, which is why the comparison page lists what it does worse, too.

Questions people are asking

Why was GoFullPage removed from the Chrome Web Store?

Per the GoFullPage team, over a copyright complaint concerning a design element, not a security or privacy problem. They say they believe the removal was in error and are working with Google to reverse it.

Is GoFullPage malware? Should I be worried?

There is no public evidence of compromise, and the developers deny it flatly. The alarming wording in Chrome's warning is boilerplate shown for any policy delisting, whatever the underlying cause.

Can I reinstall GoFullPage?

Not in Chrome while the listing is down. If you still have it installed, try re-enabling it at chrome://extensions rather than removing it. On Microsoft Edge the extension remains available through Edge's own store.

Will it come back?

The developers expect so and describe the removal as temporary. No date has been announced. Store appeals of this kind have historically taken anywhere from a few days to several weeks.

I paid for Premium. What happens to that?

The GoFullPage team says premium access continues to work on Microsoft Edge. Questions about billing during the outage are best directed to them, not to a comparison page like this one.

Are Brave, Arc and Opera affected?

Yes. They all install extensions from the Chrome Web Store, so the delisting reaches them. Edge is the exception because it runs a separate store.

Sources

GoFullPage, "GoFullPage Chrome Update", 11 August 2026: the developers' own account.
Android Authority, "Chrome just flagged a hugely popular extension as unsafe", 13 August 2026: user count, warning text, developer comment.

This page describes a live situation and reflects what was public on 14 August 2026. If GoFullPage has been restored by the time you read this, that is good news and this page is out of date.