[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-chrome-to-kill-manifest-v2-extensions-ending-ublock-origin-support":10},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":37,"persona_id":22,"persona_name":22,"section":22,"tags":38,"sources":42,"feedback":49,"feedback_at":22,"cost_usd":49,"total_tokens":49},926,"chrome-to-kill-manifest-v2-extensions-ending-ublock-origin-support","Chrome to kill Manifest V2 extensions, ending uBlock Origin support","Chrome 150 will disable Manifest V2, breaking uBlock Origin and other blockers and forcing users to move to newer extensions or other browsers.","Chrome is about to pull the plug on Manifest V2 extensions.\n\nStarting with Chrome 150, which rolls out to the stable channel on June 30, Google will remove the ExtensionManifestV2Disabled flag. That flag has been the last safeguard keeping older extensions alive. With its removal, any extension built on Manifest V2 – including the popular uBlock Origin – will stop working in Chrome.\n\nThe change matters because most ad‑blocking and privacy extensions still rely on Manifest V2 APIs. Users will lose real‑time content filtering unless they switch to a Manifest V3‑compatible version or an alternative browser. Developers also face a rushed rewrite deadline, and the ecosystem loses a layer of user‑controlled privacy.\n\nIn short, Chrome’s move will strip away a key privacy tool for many. Readers should audit their extensions now, look for a Manifest V3‑ready blocker, and consider browsers that still support V2 if they need continuity.","[\"chrome\",\"privacy\",\"extensions\"]","2026-06-15T07:34:58.000Z","2026-06-15T08:30:18.934Z","2026-06-15T08:30:25.866Z","published",null,[24,30,34],{"id":25,"reviewer":26,"round":27,"reason":28,"status":29},"editor-r1","editor",1,"Add a concise concluding paragraph that reiterates the impact and what readers should do next.","resolved",{"id":31,"reviewer":26,"round":32,"reason":33,"status":29},"editor-r2",2,"Add a concise concluding paragraph that restates the impact of Chrome disabling Manifest V2 and advises readers on next steps.",{"id":35,"reviewer":26,"round":36,"reason":33,"status":29},"editor-r3",3,"https:\u002F\u002Fcdn.xyz.onl\u002Farticle-images\u002Fchrome-to-kill-manifest-v2-extensions-ending-ublock-origin-support.webp",[39,40,41],"chrome","privacy","extensions",[43,46],{"name":44,"url":45},"The Next Web","https:\u002F\u002Fthenextweb.com\u002Fnews\u002Fchrome-manifest-v3-ublock-origin-content-blockers-disabled",{"name":47,"url":48},"The Verge","https:\u002F\u002Fwww.theverge.com\u002Ftech\u002F950005\u002Fgoogle-chrome-removing-ad-blocker-loopholes",0]