language
Automatically detected

We have pre-selected English and US Dollar ($) for you.

Log In
softwarebay.de
softwarebay.de
Google Chrome Blocks Old Ad Blockers by End of June
News Internet & Platforms Google Chrome Blocks Old Ad Blockers by End of Jun...
Internet & Platforms

Google Chrome Blocks Old Ad Blockers by End of June

Google Chrome Blocks Old Ad Blockers by End of June

Google plans to end support for browser extensions based on the old Manifest V2 by the end of June 2026. This measure is part of the transition to Manifest V3, which promises a more secure and faster architecture for the popular browser. As early as March 2025, some extensions, including popular ad blockers like uBlock Origin, became unusable due to this transition. While users were temporarily able to access these extensions, this will no longer be possible with the latest version of Chrome. The flag "ExtensionManifestV2Disabled" in the code of Google Chrome will completely block the use of Manifest V2-based add-ons starting at the end of June 2026.

Reports suggest that this could partially take effect in Chrome 150, while the final deactivation may occur in Chrome 151. Uncertainty remains regarding the exact timing of the complete block; however, it is clear that after the switch to Manifest V3, there will be no return to the old extensions. The transition to Manifest V3 aims to enhance browser security while also improving speed. Google has emphasized that the new policies are intended to prevent extensions from deeply integrating into the system, which has led to security issues in the past. These measures are part of a broader strategy to ensure user integrity and security.

The blocking of ad blockers is not directly due to a decision by Google but rather a side effect of the transition to the new architecture. Many users could be affected by this change, as the use of ad blockers has been a common practice to avoid unwanted advertisements. However, Google has repeatedly taken a stance against the use of ad blockers, suggesting that the company may not be unhappy about the restrictions. Developers have the opportunity to adapt their extensions to the new requirements of Manifest V3. However, these adjustments could impair the functionality of the extensions, meaning users may not be able to expect the same performance as before.

The transition to Manifest V3 could also result in some features that were available in the old versions no longer being supported. For users who wish to continue using ad blockers, there are already alternatives that have been adapted to Manifest V3. This includes uBlock Origin Lite, which acts as a successor to uBlock Origin. While this new version offers fewer extensive features, it remains free and could be an option for users reliant on ad blocking. The transition to Manifest V3 is also being pursued by other browsers aiming for similar security and performance improvements.

The developments in the browser landscape indicate that user security is increasingly coming to the forefront. Adjustments to the new standards could lead to safer internet usage in the long term. The final blocking of Manifest V2-based extensions is expected to take effect with the release of new Chrome versions in June 2026. Users should prepare to review their extensions and potentially transition to the new standards to ensure a secure and functional browsing experience. The transition to Manifest V3 is seen as a significant step in the evolution of Google Chrome to meet the demands of modern web applications. However, the exact impact on users will only become apparent after full implementation. Google has announced that the complete transition to Manifest V3 will be completed by the end of June 2026.

Tags: Google Chrome Ad Blockers Manifest V3 uBlock Origin

💬 Comments (0)

Write a comment

info Will be published after moderation
chat_bubble_outline

No comments yet. Be the first to comment!

Live support available
Sarah E.
Sarah E.
check_circle Bucharest
Hello! I am Sarah. Do you have questions about our products or need help?
chat_bubble