TL;DR
Chrome 146 landed in early 2026 with Manifest V3 fully enforced—85% of Chrome extensions have been updated. The transition ended Manifest V2 support, forcing ad blockers and many other extensions to rebuild around new APIs. Convert: Web to PDF is fully MV3-native and works without limitations in Chrome 146 and beyond. Free, no account required.
What Manifest V3 Is and Why It Mattered
Manifest V3 is the extension platform architecture Google introduced to replace Manifest V2. The transition—which started in 2020 and completed with Chrome's 2025–2026 enforcement—changed how extensions interact with web pages, process network requests, and persist in memory.
The changes that got the most attention:
declarativeNetRequest replaced webRequestBlocking. The old blocking API allowed extensions to intercept and modify any network request in real time. MV3 replaced this with a declarative model where extensions declare rules ahead of time, and Chrome applies them. This significantly limited the sophistication possible for ad blockers.
Service workers replaced background pages. MV2 extensions could run persistent background pages that stayed active. MV3 uses service workers that start, run, and terminate on demand. This is more efficient for memory but requires extensions to be designed around an event-driven model.
Remote code execution banned. Extensions can no longer fetch and execute arbitrary JavaScript at runtime. All logic must be included in the extension package itself—an important security improvement.
Chrome 146: The Current State of Affairs
Chrome 146, which shipped in early 2026 with all-arch release parity for Arm/x64, represents the mature state of the post-MV2 Chrome extension platform.
MV2 extensions are blocked. Users who had MV2 extensions installed before the transition see a disabled state. Some enterprise users have policy overrides, but for consumer Chrome, MV2 is no longer supported.
85% of extensions have updated to MV3. The majority of the extension ecosystem has completed the transition. The holdouts are largely abandoned extensions or tools that depended heavily on webRequestBlocking for their core functionality.
uBlock Origin is the canonical story of MV3 impact. The original uBlock Origin—arguably the most capable ad blocker ever made—cannot be replicated under MV3's declarative rules system. uBlock Origin Lite, the official MV3 replacement, works but with reduced blocking capability. This is a genuine regression that continues to be debated between Google and privacy advocates.
Most non-ad-blocker extensions work fine. The MV3 transition primarily affected extensions that did deep network request interception. Extensions focused on page rendering, document conversion, UI enhancement, and productivity are generally unaffected in terms of capability.
How Convert: Web to PDF Works Under MV3
Convert: Web to PDF uses a conversion model that's entirely compatible with MV3's architecture:
Content script injection: When you activate the extension, it injects a content script into the current tab's page context. This captures the rendered DOM—the final, styled version of the page after all JavaScript has executed and ads have loaded.
Local rendering: The extension processes the captured content within the extension's own context, using a rendering approach that strips navigation chrome, ads, cookie banners, and page furniture that degrades the PDF output.
Downloads API: The generated PDF is passed to Chrome's Downloads API, which writes it to your Downloads folder. No network requests, no external servers.
None of these operations require webRequestBlocking, persistent background pages, or remote code execution—the three MV2 capabilities that MV3 restricted. The extension works fully and without limitation in Chrome 146.
What Chrome 146 Also Brought: Vertical Tabs
Chrome 146 introduced native vertical tabs—a feature that competing browsers (Arc, Vivaldi, Edge) have offered for years. For power users with dozens of open tabs, vertical tabs are a meaningful navigation improvement.
What Chrome's vertical tabs don't replace:
Tab group saving and restoration. Chrome has no native equivalent to extensions like Tab Groups Restore. If you use tab groups to organize research sessions, those still depend on the extension ecosystem.
Full-page capture. Chrome's built-in screenshot tool captures what's visible in the viewport. Full-page capture—getting everything from top to bottom, including content you'd have to scroll through—still requires an extension.
Clean PDF output. Chrome's Print to PDF is functional but preserves the page chrome: navigation menus, headers, footers, cookie banners. A dedicated conversion extension produces dramatically cleaner output for reading and archiving.
Vertical tabs being natively available is good news for users—but it highlights the continued value of the extension ecosystem for capabilities Chrome hasn't yet absorbed.
The State of Extensions After MV3: What's Better and What's Worse
The MV3 transition was controversial, and the reality is mixed:
What Got Better
Security. Banning remote code execution means extensions can't be silently updated to include malicious code after they pass Chrome's review. The extension you installed is the extension that runs—modifications require a new version that goes through review.
Performance. Service workers that terminate when idle use less memory than persistent background pages. On memory-constrained machines, this is a meaningful improvement for users running many extensions.
Transparency. The declarative rules model makes extension behavior more predictable and auditable. An extension's rule set describes exactly what it does, rather than running arbitrary JavaScript logic that could theoretically do anything.
What Got Worse (or Didn't Improve as Expected)
Ad blocking capability. This is the most documented regression. The 150-rule limit on dynamic rules (later raised but still a constraint) limits ad blocker sophistication. Fingerprinting-based tracking that doesn't operate via simple URL patterns can evade declarative filters that would have been catchable with the old blocking model.
Extension developer complexity. Service workers are a well-established web API, but the migration from persistent background pages was a significant engineering effort. Many smaller extensions were abandoned rather than updated.
Privacy tool limitations. Beyond ad blockers, extensions that did granular cookie modification, script injection, and request header manipulation faced significant constraints.
How to Verify Your Extensions Are MV3-Compatible
Chrome has made it straightforward to check:
- Navigate to
chrome://extensions - Enable "Developer mode" in the top right
- Extensions show their manifest version. MV2 extensions will show a warning or disabled state.
Alternatively, visit the Chrome Web Store listing for any extension. MV3-compatible extensions don't display any compatibility warnings in Chrome 146.
Why MV3 Makes Browser Extension Security More Important
One consequence of the MV3 transition that's underappreciated: the security baseline for remaining extensions is higher than it was under MV2, but the attack surface hasn't disappeared.
108 malicious extensions were removed from the Chrome Web Store in early 2026. These were sophisticated enough to pass Chrome's review processes. The MV3 security improvements reduced one attack vector (runtime code injection) while leaving others open.
Supply-chain attacks on extension developers remain viable. Several high-profile browser extension compromises over 2024–2025 targeted developers' Google accounts, allowing attackers to push malicious updates through official channels. MV3 doesn't prevent this class of attack.
Permissions still matter. An MV3 extension that requests access to all websites and your browsing history still has access to all websites and your browsing history. Reading permission requests before installing remains essential.
Choosing Extensions in the Post-MV3 Era
A practical checklist for evaluating any new extension:
- Is it MV3? In Chrome 146, any active extension is MV3. But verify if you're unsure.
- What permissions does it request? "Read and change all your data on all websites" is the most expansive possible permission. Narrow permissions are better.
- When was it last updated? Active maintenance indicates an extension is actively supported.
- How many users does it have, and what are the reviews? Large user bases with positive reviews are not guarantees but are positive signals.
- Is there a privacy policy? Extensions that collect any data should have documented privacy policies.
Frequently Asked Questions
Q: Do I need to reinstall Convert: Web to PDF for it to work in Chrome 146?
No. If you installed from the Chrome Web Store, you have the current version automatically. Extensions update silently unless you've disabled automatic updates.
Q: My previous extension for saving pages to PDF stopped working after Chrome 146. What happened?
It was likely an MV2 extension that wasn't updated. The extension has been disabled as part of Chrome's MV2 enforcement. You can replace it with Convert: Web to PDF, which is fully MV3-native.
Q: Does MV3 affect extensions differently on Chrome for Enterprise?
Enterprise Chrome policies allow administrators to maintain MV2 extension exceptions in managed environments. This was specifically provided to allow businesses time to transition legacy extension tooling. Consumer Chrome does not have this exception.
Q: What about Firefox? Does MV3 affect it?
Firefox implemented MV3 APIs for cross-browser compatibility but chose to retain MV2 support indefinitely. Firefox also chose to retain the blocking WebRequest API alongside the declarative approach, meaning Firefox ad blockers maintain their full capability. If ad blocking is critical to you, Firefox is the technically superior platform.
Q: Does Convert: Web to PDF work in Edge, Brave, or other Chromium-based browsers?
Yes. Any Chromium-based browser that supports the Chrome Web Store (including Edge and Brave) can install and run the extension. Brave's native ad blocking operates at the browser level and is unaffected by MV3 extension limitations.
The Bottom Line
Chrome 146 and the completed MV3 transition mark the end of an era for some extensions—particularly ad blockers that depended on the old blocking API. For most productivity and document tools, the transition is a non-event: the new platform is more secure and performs better without any capability regression.
Convert: Web to PDF is fully MV3-native and works without limitations in Chrome 146. The extension produces clean PDFs from any web page, with no ads, no navigation chrome, and no content sent to external servers.
For file conversion (Word, Excel, images, CSVs), Convert: Anything to PDF extends the same local-first approach.