In mid-August 2026, one of the most popular and trusted Chrome extensions suddenly vanished from the Chrome Web Store. GoFullPage – Full Page Screen Capture, used by more than 11 million people, was pulled and flagged with a stark warning: “This extension violates the Chrome Web Store policy, and might be unsafe.”
For many users the message felt alarming. Was the extension compromised? Had it been sold to bad actors? Did it contain malware?
The answer, according to the developers, was none of the above.
What Actually Happened
GoFullPage was temporarily removed because of a copyright claim involving a design element. According to the team (including original creator Peter Coles and Claire from the GoFullPage team), a large corporation filed a copyright takedown request over a small visual asset that was not central to the extension’s branding.
Google’s automated systems appear to have treated the notice seriously and removed the extension from the store with little or no advance warning. Chrome and other Chromium-based browsers (such as Brave) then began showing the “unsafe” warning and, in many cases, disabled the extension for existing users.
The developers have been clear on several points:
- This was not a security or malware issue.
- The extension was never sold.
- The original team remains in control.
- They fixed the disputed design element quickly and are working with Google to restore the listing.
As of mid-August 2026, the extension continued to work normally on Microsoft Edge, and some Chrome users could manually re-enable it via chrome://extensions.
Why a “Small Design Element” Matters
Chrome Web Store policies are strict on intellectual property. Section on Impersonation & Intellectual Property states that developers must not infringe on the copyright, trademark, or other proprietary rights of others. Google responds to clear notices of alleged copyright infringement, and repeated or serious violations can lead to removal or account-level consequences.
In practice, even a minor graphic, icon, illustration, button style, or UI element that closely resembles someone else’s copyrighted work can trigger a takedown — especially when a large company files the complaint. Automated enforcement can move faster than human review, which is what appears to have happened here.
Lessons for Chrome Extension Developers
If you are building or maintaining a Chrome extension, this incident is a useful cautionary tale. Here are the practical takeaways:
1. Treat every visual asset as a potential liability
Icons, illustrations, decorative graphics, custom buttons, progress indicators, and even subtle UI flourishes can all carry copyright. “It’s just a small icon” is not a defense.
2. Prefer original or clearly licensed assets
- Create your own graphics whenever possible.
- If you use free or paid icon sets, read the license carefully. Many “free” libraries restrict commercial use, modification, or use in logos/branding.
- Prefer sources with explicit commercial licenses (e.g., MIT, Apache 2.0, CC0, or well-documented paid licenses).
- Keep records of licenses and attribution requirements.
3. Avoid anything that could be seen as copying a well-known brand’s visual language
Exact or near-exact copies of distinctive icons, color treatments, or interface patterns from major companies are high-risk. Even if unintentional, they can invite complaints.
4. Review store listing assets with the same care
Screenshots, promotional images, and the extension icon itself are part of the product experience under Chrome Web Store policy. Copyrighted material in the listing can also cause problems.
5. Have a plan for rapid response
Copyright notices can lead to fast removal. Know how to update assets quickly, contact Google support, and communicate with users (as GoFullPage did via their blog and social channels).
Temporary Workarounds for Users
While the situation is resolved:
- On Chrome, try re-enabling the extension at
chrome://extensions. - Microsoft Edge users can continue using the official Edge version.
- Chrome’s built-in full-page screenshot (DevTools → Command Menu → “Capture full size screenshot”) remains a reliable alternative for many pages.
Final Thought
GoFullPage’s case shows that even a well-regarded, privacy-conscious extension with millions of users can be disrupted by a single design-related copyright claim. For developers, the lesson is straightforward: visual assets deserve the same careful legal scrutiny as code and permissions.
In the Chrome Web Store, a small design choice can have outsized consequences. Building with original or properly licensed materials from the start is the simplest way to avoid becoming the next temporary “unsafe” warning.
Leave a Reply