The latest articles on DEV Community by Frontbuffer Editorial (@frontbuffer). https://dev.to/frontbuffer https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4072281%2F8375c8bc-3244-48ac-8366-e2cb787de2af.png https://dev.to/frontbuffer en Frontbuffer Editorial Tue, 11 Aug 2026 04:29:47 +0000 https://dev.to/frontbuffer/chrome-manifest-v2-is-gone-after-august-31-heres-what-actually-breaks-351p https://dev.to/frontbuffer/chrome-manifest-v2-is-gone-after-august-31-heres-what-actually-breaks-351p <p>If you've noticed Chrome extensions behaving differently lately, <br> you're not imagining it. Google's Manifest V3 transition is <br> forcing every extension to rewrite how it intercepts network <br> requests — and not all of them made it.</p> <h2> What Actually Changed </h2> <p>Manifest V2 allowed extensions to use <code>webRequest</code> API to <br> dynamically block or modify network requests. This is how <br> uBlock Origin, Privacy Badger, and most ad blockers worked.</p> <p>MV3 replaced this with <code>declarativeNetRequest</code> — a static <br> rule-based system. You define rules in advance; the browser <br> enforces them. No dynamic interception.</p> <p>The practical difference:</p> <ul> <li> <strong>Ad blockers</strong>: Reduced effectiveness for complex filters</li> <li> <strong>uBlock Origin</strong>: The original version stops working. uBlock Origin Lite (MV3 version) has fewer capabilities</li> <li> <strong>Privacy extensions</strong>: Most have migrated, some haven't</li> <li> <strong>Developer tools</strong>: Generally fine — most already updated</li> </ul> <h2> What's Happening August 31 </h2> <p>Chrome will disable MV2 extensions that haven't migrated. <br> Users will see a warning banner, then the extension gets <br> turned off. You can temporarily re-enable in developer mode <br> but that's not a permanent fix.</p> <h2> Extensions That Won't Survive </h2> <ul> <li>uBlock Origin (non-Lite) — the big one</li> <li>Some niche privacy tools built on dynamic request blocking</li> <li>Extensions that inject remote code (banned outright in MV3)</li> </ul> <h2> What You Can Do </h2> <p><strong>Switch to uBlock Origin Lite</strong> — it's the official MV3 <br> version. Less powerful but functional.</p> <p><strong>Try Firefox</strong> — Mozilla has committed to keeping MV2 support. <br> If you rely heavily on legacy extensions, this is the cleanest <br> escape route.</p> <p><strong>Check your extensions</strong> — Go to <code>chrome://extensions</code>, <br> enable Developer Mode, and look for any flagged as MV2.</p> <p>I put together a full breakdown of every affected extension <br> category and what the alternatives look like here:<br> <a href="https://frontbuffer.net/tech/google-chrome-manifest-v2-migration_HUB/" rel="noopener noreferrer">Chrome Manifest V2 Migration: Complete Guide</a></p> <p>The August 31 deadline is real. If you manage extensions for <br> a team or organization, now is the time to audit.</p> chrome webdev javascript security