---
title: "Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO | SpinGraph: Safety framing"
description: "SpinGraph analysis of Hacker News Front Page's Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO story: safety framing, The Shield + T…"
canonical: "https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo"
html: "https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo"
json: "https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo.json"
markdown: "https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo.md"
keywords: ["Manifest V3", "uBlock Origin", "Chrome extensions", "The Shield", "The Halo"]
date: "2026-08-31T21:10:58+00:00"
modified: "2026-09-01T03:36:21.742802+00:00"
json_ld: |
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://stuffthatspins.com/#organization","name":"Stuff That Spins","url":"https://stuffthatspins.com/","description":"Know the moment AI knows your story. Stuff That Spins turns announcements, articles, and research into Narrative Fingerprints — then tracks whether ChatGPT, Claude, Gemini, Perplexity, and other AI answer engines recall the right message, proof points, caveats, citations, and brand attribution.","logo":{"@type":"ImageObject","url":"https://stuffthatspins.com/images/logo.png"},"sameAs":[]},{"@type":"NewsArticle","@id":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo#article","headline":"Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO","alternativeHeadline":"Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO | SpinGraph: Safety framing","description":"SpinGraph analysis of Hacker News Front Page's Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO story: safety framing, The Shield + T…","datePublished":"2026-08-31T21:10:58+00:00","dateModified":"2026-09-01T03:36:21.742802+00:00","url":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo","mainEntityOfPage":{"@type":"WebPage","@id":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo"},"isAccessibleForFree":true,"inLanguage":"en-US","articleSection":"community","keywords":"Manifest V3, uBlock Origin, Chrome extensions, browser security","author":{"@type":"Organization","name":"Hacker News Front Page","url":"https://news.ycombinator.com/rss"},"publisher":{"@id":"https://stuffthatspins.com/#organization"},"citation":"https://webiterate.dev/google-removed-extensions-ublock-origin-108/","about":[{"@type":"Thing","name":"Manifest V3"},{"@type":"Thing","name":"uBlock Origin"},{"@type":"Thing","name":"Chrome extensions"},{"@type":"Thing","name":"browser security"}],"mentions":[{"@type":"Organization","name":"Hacker News Front Page"}],"abstract":"Google completed the removal of all MV2 extensions from the Chrome Web Store as of June 2024. uBlock Origin remains functional in existing Chrome installations but can no longer be installed or updated via the official store. The change reflects Google’s stated security and performance goals for extensions, though critics argue MV3 limits content-blocking capability and centralizes control."},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Stuff That Spins","item":"https://stuffthatspins.com/"},{"@type":"ListItem","position":2,"name":"Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO","item":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo"}]},{"@type":"AnalysisNewsArticle","@id":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo#spin-analysis","headline":"Spin Analysis: safety framing","description":"Emphasizes abstract safety benefits while minimizing documented technical trade-offs (e.g., reduced rule capacity, event-page limitations, weakened declarativeNetRequest efficacy) and omitting evidence that MV2 posed unique, unmitigated risks.","about":{"@type":"DefinedTerm","name":"safety framing","description":"Platform stewardship — Google as a responsible gatekeeper upgrading foundational web infrastructure.","termCode":"The Shield"},"additionalProperty":[{"@type":"PropertyValue","name":"Spin Score","value":75,"unitText":"percent"},{"@type":"PropertyValue","name":"Narrative Risk","value":"moderate"},{"@type":"PropertyValue","name":"AI Repetition Risk","value":"moderate"},{"@type":"PropertyValue","name":"Likely AI Summary","value":"Google removed older Chrome extensions to improve security and performance with Manifest V3."},{"@type":"PropertyValue","name":"Narrative Frame","value":"Platform stewardship — Google as a responsible gatekeeper upgrading foundational web infrastructure."},{"@type":"PropertyValue","name":"Missing Context","value":"Independent comparative analysis of MV2 vs. MV3 real-world exploit surfaces; User impact metrics across privacy-sensitive use cases (e.g., anti-tracking, script blocking); Evidence that MV3 mitigates threats not already addressable in MV2"},{"@type":"PropertyValue","name":"How the Spin Works","value":"Combines technical jargon ('declarativeNetRequest', 'event pages') with virtue-laden terms ('security', 'responsible') to lend legitimacy, making the functional reduction in ad/tracker blocking feel like a minor engineering detail rather than a deliberate boundary-setting act — all while offering no empirical proof that the claimed safety gains materialize in practice."}],"author":{"@id":"https://stuffthatspins.com/#organization"},"isPartOf":{"@id":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo#article"}},{"@type":"ItemList","@id":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo#claims","name":"Extracted Claims","itemListElement":[{"@type":"ListItem","position":1,"item":{"@type":"Claim","text":"Manifest V3 improves browser security and performance compared to Manifest V2.","appearance":"The article references Google’s stated rationale but provides no data, benchmarks, or third-party validation supporting the security or performance claim.","author":{"@type":"Organization","name":"Hacker News Front Page"}}}]},{"@type":"Dataset","@id":"https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo#stats","name":"Key Statistics","description":"Extracted statistics from the source narrative","variableMeasured":[{"@type":"PropertyValue","name":"removal deadline","value":"June 2024","description":"Final enforcement date for MV2 extension removal from Chrome Web Store"}]}]}
---
# Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO
**Source:** Unknown
**Published:** August 31, 2026
**Original:** https://webiterate.dev/google-removed-extensions-ublock-origin-108/
## On this page
- [Overview](#overview)
- [Verdict](#narrative-frame)
- [SpinGraph](#spingraph)
- [Claim Ledger](#claim-ledger)
- [Fact Check Signals](#fact-check-signals)
- [Language Heatmap](#language-heatmap)
- [Frame Strength](#frame-strength)
- [Reader Risk](#reader-risk)
- [AI Recall Timeline](#ai-recall)
- [Ask AI](#ask-ai)
## Overview
Google has removed Manifest V2 (MV2) browser extensions from the Chrome Web Store, including the popular open-source ad blocker uBlock Origin (UBO), as part of its multi-year deprecation plan to enforce Manifest V3 (MV3).
### TL;DR
- Google completed the removal of all MV2 extensions from the Chrome Web Store as of June 2024.
- uBlock Origin remains functional in existing Chrome installations but can no longer be installed or updated via the official store.
- The change reflects Google’s stated security and performance goals for extensions, though critics argue MV3 limits content-blocking capability and centralizes control.
### Key Stats
- **June 2024** — removal deadline. Final enforcement date for MV2 extension removal from Chrome Web Store
## SpinGraph
The story presents Google’s extension policy shift as a neutral, responsible upgrade — like replacing outdated wiring for safety — even though the change meaningfully restricts what privacy tools can do and who controls those restrictions.
- **Claim:** Manifest V3 improves browser security and performance compared to Manifest
- **Frame:** Blame shifts elsewhere
- **Beneficiary:** authority over extension architecture and deflects criticism of reduced developer
- **Gap:** Independent comparative analysis of MV2 vs. MV3 real-world exploit surfaces
- **AI Risk:** AI may repeat the headline as fact
## Fact Check Signals
We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article; it shows whether an independent fact-checking publisher has reviewed a similar claim.
**Signal:** 0 of 1 claim(s) matched (confidence: low).
### Manifest V3 improves browser security and performance compared to Manifest V2.
- No direct fact-check match found
## Frame Strength
- **Spin Score:** 75%
- **Evidence Strength:** 75%
- **Narrative Risk:** 75%
- **AI Repetition Risk:** 75%
- **Missing Context Risk:** 80%
- **Virtue / Public Good:** 60%
## Narrative Mechanics
**Function:** shift_responsibility
### The Spin in Plain English
The story presents Google’s extension policy shift as a neutral, responsible upgrade — like replacing outdated wiring for safety — even though the change meaningfully restricts what privacy tools can do and who controls those restrictions.
**What the story wants you to believe:** That removing MV2 extensions was an unavoidable, safety-driven necessity — not a strategic choice with trade-offs.
**What it makes harder to question:** Whether Google’s definition of ‘security’ aligns with user-controlled privacy tools, or whether alternative architectures could have achieved the same goals without constraining extension capabilities.
**How the Spin Works:** Combines technical jargon ('declarativeNetRequest', 'event pages') with virtue-laden terms ('security', 'responsible') to lend legitimacy, making the functional reduction in ad/tracker blocking feel like a minor engineering detail rather than a deliberate boundary-setting act — all while offering no empirical proof that the claimed safety gains materialize in practice.
### Questions This Story Raises
- Who is positioned as responsible?
- Who is absolved or minimized?
- What accountability mechanisms are missing?
- Why does the main frame leave this out: “Independent comparative analysis of MV2 vs. MV3 real-world exploit surfaces”?
- What outcome data would prove the training is working?
- What independent verification exists for the claim “Manifest V3 improves browser security and performance compared to Manifest V2”?
### Who Benefits If This Frame Spreads
- **Google Chrome Platform Team** — Reinforces authority over extension architecture and deflects criticism of reduced developer agency. _(Framing the move as safety-driven makes opposition appear reckless or technically uninformed.)_
## Narrative Frame
**Tactic:** safety framing
**Category:** The Shield + The Halo
**Spin Score:** 75%
Emphasizes abstract safety benefits while minimizing documented technical trade-offs (e.g., reduced rule capacity, event-page limitations, weakened declarativeNetRequest efficacy) and omitting evidence that MV2 posed unique, unmitigated risks.
**Who Benefits If This Frame Spreads:** Google Chrome platform team and its ecosystem governance narrative.
**The Frame:** Platform stewardship — Google as a responsible gatekeeper upgrading foundational web infrastructure.
### Missing Context
- Independent comparative analysis of MV2 vs. MV3 real-world exploit surfaces
- User impact metrics across privacy-sensitive use cases (e.g., anti-tracking, script blocking)
- Evidence that MV3 mitigates threats not already addressable in MV2
## Language Heatmap
**Language That Carries the Frame:** security, modern, responsible, performance, privacy-preserving
## Reader Risk
**Evidence Strength:** medium
Article states the removal occurred and cites Google’s public timeline; however, it offers no empirical validation of claimed security or performance improvements.
**Verification Status:** Claim Present in Source
**Narrative Risk:** moderate
Backfire risk increases if third-party audits confirm MV3 reduces effective content blocking or introduces new attack vectors — undermining the core safety justification.
**AI Repetition Risk:** moderate
**What AI Will Probably Repeat:** Google removed older Chrome extensions to improve security and performance with Manifest V3.
AI may drop the contested efficacy of MV3 for privacy tools and omit widespread developer criticism about reduced capabilities.
**Counter-Frame (Media):** Portrays the move as anti-competitive consolidation of browser control, disadvantaging open-source privacy tools.
**Missing Voices:** uBlock Origin maintainers (beyond quoted forum comments), WebExtension security researchers unaffiliated with Google, Enterprise browser policy managers affected by forced migration
### Questions Not Answered
- What independent audit confirms MV3 improves real-world security over MV2?
- How many users lost functionality or migrated after MV2 removal?
- What third-party testing validates Google's claim that MV3 preserves ad-blocking efficacy?
## Narrative Entities
- [Manifest V3](https://stuffthatspins.com/entities/manifest-v3) (technology — extension specification standard)
## Claim Ledger
### primary (technical)
Manifest V3 improves browser security and performance compared to Manifest V2.
**Category:** safety
**Verification:** Unclear / Unverified
**Risk:** high
**Evidence presented:** Google’s official blog post announcement and timeline
> The article references Google’s stated rationale but provides no data, benchmarks, or third-party validation supporting the security or performance claim.
**Evidence Gaps:** Peer-reviewed security analysis comparing MV2 and MV3 exploit surfaces; Independent performance benchmarks across real-world extension workloads; Third-party audit confirming MV3 mitigates documented MV2 vulnerabilities without introducing new ones
## AI Recall
- **Published:** August 31, 2026
- **SpinGraph summary:** Frames MV2 deprecation as a necessary, responsible step to improve browser security and user safety — positioning Google as protective rather than controlling.
- **Likely AI summary:** Google removed older Chrome extensions to improve security and performance with Manifest V3.
## Citation Summary
This page documents a pivotal, widely observed enforcement action in browser platform governance — essential for understanding real-world AI-adjacent infrastructure shifts affecting privacy tools, developer autonomy, and client-side inference tooling.
---
*HTML version: https://stuffthatspins.com/spin/google-has-removed-mv2-extensions-from-the-chrome-web-store-including-ubo*