Manifest V2 vs V3: A Comprehensive Comparison and Migration Path

Manifest V2 and V3 are two versions of the web manifest, a JSON file that provides metadata about a Progressive Web App (PWA). Manifest V2 has been the standard for several years, but Manifest V3 is the new version that's being adopted.

Manifest V2 is being deprecated by Google, which means it will eventually stop working. This is because Manifest V3 offers several improvements, including better security and performance.

Manifest V3 is more secure than V2, thanks to its use of the Permissions API, which allows users to grant and revoke permissions more easily. This is a big deal, as security is a top priority for users.

Manifest V3 also offers better performance, thanks to its use of the Web App Manifest API, which allows developers to define how their app behaves and looks. This makes it easier to create PWAs that are fast and responsive.

Curious to learn more? Check out: Azure Premium Ssd V2

Migrating to Manifest V3 might seem daunting, but it's worth considering the benefits. In Manifest V3, the sandbox is used to treat the page as though it were loaded into an iframe with the sandbox attribute.

This effectively removes the page from associating with the main application in terms of the Same Origin Policy. As a result, the page can no longer perform certain actions, such as submitting forms.

The transition to Manifest V3 is bringing significant changes to Chrome extensions.

Manifest V2 is being phased out, with the Chrome Web Store stopping acceptance of new Manifest V2 extensions with public visibility.

Google is encouraging users to migrate their extensions to Manifest V3, which will become a prerequisite for featured badge extensions.

The modification of the WebRequest API in Manifest V3 is limiting the ability of extensions to intercept and modify network requests, affecting content-blocking extensions like uBlock Origin.

Manifest V3 brings several significant upgrades that improve the security and performance of Chrome extensions. One of the primary upgrades is the introduction of the 'declarativeNetRequest' API, which allows extensions to manage and process multiple network modification requests more effectively, saving time on each request and speeding up various operations for the browser.

This API replaces the old background pages, which had to run continuously and shared the same memory as the extension, causing performance issues. By running in a different process, service workers provide a more efficient and secure way for extensions to operate.

Another upgrade is the increased controllability provided by Manifest V3, which follows an event-driven architecture model. This allows for in-depth control over how the extension interacts with the browser, giving users extra control over the modifications an extension makes to a browser.

This controllability is achieved through the 'declarativeNetRequest' API, which provides users with extra control over the modifications an extension makes to a browser, and the extension developers are asked to justify their requirements for every sensitive permission.

Here are some key benefits of the 'declarativeNetRequest' API:

By migrating to Manifest V3, extensions can take advantage of these upgrades and provide a better user experience, while also improving security and performance.

In V2, scripts could be executed freely in the Tabs API. This allowed for a lot of flexibility.

However, in V3, the Scripting API now limits an extension's executions to script files and functions. This change restricts dynamic script executions.

Dynamic script executions are necessary for ad blockers to consistently block dynamic ads and ad block circumvention.

Take a look at this: Static vs Dynamic Websites

Manifest V3 brings a significant boost to performance with the introduction of 'declarativeNetRequest' and 'chrome.action' APIs. This allows browsers to manage and process multiple network modification requests more effectively.

The previous method of using background pages to handle these operations had its limitations, as it required continuous code execution, sharing the same memory as the extension. Google's service worker model, on the other hand, runs in a different process, giving the extension more freedom to operate.

With Manifest V3, the browser can save time on each request, speeding up various operations. This results in a better overall performance of the extension and the browser.

In MV3, all scripts must be included in the extension package, which are served from the chrome-extension:// protocol.

This means that any external scripts used in your extension must be packaged with the extension itself, making it a more secure environment.

You need to specify the domains you're loading styles, scripts, or data from in the Content Security Policy, which is another layer of security for your application.

For instance, if you're using a Vue CDN or another domain, you need to list this domain in the Content Security Policy to ensure everything is properly secured.

A page in your extension would be loaded from a URL like chrome-extension:///onboarding.html, which is served directly from the extension package.

For your interest: Content Marketing vs Seo

The new Manifest V3 is all about enhancing security and providing a better browsing experience. Google has updated the 'declarativeNetRequest' API and manifest.json file to replace the old 'webRequest' API that allowed extensions to interfere with network requests.

This change has limited the authority of extensions to modify network requests, making the entire experience feel more secure. With this new rule-based approach, websites and extensions can operate within pre-established guidelines.

The number of fraudulent and malicious extensions listed on the Chrome web store is expected to drop as businesses migrate to Manifest V3. This is a promising development for users who want to stay safe online.

Here are some specific changes that will help improve security:

Google's Manifest V3 restrictions aim to improve performance, but the evidence suggests otherwise.

The company claims that persistent background pages waste memory, but in reality, most websites consume much more memory than extensions.

Disabling privacy and security extensions reveals just how much memory is consumed by websites without them.

Repeatedly starting and stopping service worker-based extensions leads to greater CPU load, making them a poor fit for this model.

Extensions that rely on expensive one-time processing, like machine learning models, are especially affected by this ephemeral nature.

Arbitrarily shutting down extension service workers breaks functionality, causing issues like stale configuration data and delayed messaging.

In contrast, the declarativeNetRequest API can manage network modification requests more effectively, saving time on each request.

This results in faster operations for the browser, making it more optimal.

Updating API calls is a crucial step in migrating your extension to Manifest V3. To achieve this, you need to replace certain APIs that are no longer supported in the newer version of Manifest.

First, you'll need to replace "chrome.tabs.executeScript()" with "chrome.scripting.executeScript()". This change is necessary to ensure your extension continues to function as expected.

You'll also need to replace "tabs.insertCSS()" and "tabs.removeCSS()" with "scripting.insertCSS()" and "scripting.removeCSS()". This change will help you manage your extension's styles more efficiently.

Browser Actions and Page Actions are also replaced with Actions in Manifest V3. This change is significant, as it allows you to create more interactive and engaging experiences for your users.

To ensure seamless communication between service workers and other parts of your extension, you'll need to implement calls like "postMessage()" and message event handlers. This change will help you establish a robust connection between different components of your extension.

Finally, be sure to remove any APIs that are not compatible with Manifest V3. This will help you avoid any potential issues or errors that may arise during the migration process.

Here's a summary of the API changes you'll need to make:

The shift from Manifest V2 to Manifest V3 affects millions of users and thousands of developers worldwide. Google Chrome and Microsoft Edge are disabling older extensions, forcing both groups to adapt quickly to avoid disruptions.

Users will notice a potential loss of functionality in certain extensions, especially ad blockers, privacy tools, and automation extensions. Many of these relied on the WebRequest API, which is significantly restricted in Manifest V3.

In Singapore, users who depend on enhanced ad-blocking and tracker-blocking extensions may find limited options available. Popular extensions like uBlock Origin will lose some of their advanced filtering capabilities under Manifest V3.

If your favorite extensions stop working, check if they have Manifest V3-compatible versions or look for alternative browsers that still support Manifest V2.

Users and developers alike will feel the impact of the shift from Manifest V2 to Manifest V3.

For users, the most noticeable change will be the potential loss of functionality in certain extensions, especially ad blockers, privacy tools, and automation extensions.

Many users who depend on enhanced ad-blocking and tracker-blocking extensions may find limited options available, particularly in Singapore where digital privacy concerns are rising.

Popular extensions like uBlock Origin have already stated that some of their advanced filtering capabilities will be lost under Manifest V3.

Users who find their favorite extensions no longer working should check if they have Manifest V3-compatible versions or look for alternative browsers that still support Manifest V2.

Developers, on the other hand, face both challenges and opportunities with this transition.

Many extension creators need to rewrite large parts of their code to comply with Manifest V3 standards.

Developers can explore Google's migration tools and update their extensions early to stay ahead of the transition.

However, some developers argue that Manifest V3 limits innovation and customization, making it harder to build powerful extensions.

Here's a quick rundown of what you need to know:

Developers who fail to adapt to Manifest V3 risk having their extensions removed from the Chrome Web Store and Edge Add-ons marketplace.

It's essential for developers to communicate changes to their user base and be prepared for the transition.

Ad blockers are facing significant challenges with the transition to Manifest V3. The rule limit of 30,000 filters is a major obstacle, making it difficult for ad blockers to function effectively.

Many ad blockers, like AdBlock, are shifting to a customized adblock experience, where users can prioritize and choose filters based on categories like country and language. This approach helps avoid exceeding the rule limit.

The loss of remote filter updates also forces ad blockers to frequently release new versions of the extension, which can be time-consuming and delayed by the mandatory Chrome Store review process.

Ad blockers are also investing in VPN/environment-based blocking methods to combat Manifest V3's changes, but these workarounds are neither improvements nor long-term solutions.

The sustainability of adblockers' workarounds is already in question, and it's becoming virtually impossible to counter next-gen adblock recovery solutions like Ad-Shield, which helps publishers consistently recover over 90% of ad-blocked impressions.

The transition from Manifest V2 to V3 is a significant change that affects browser extensions. Google Chrome and Microsoft Edge are phasing out Manifest V2, and users and developers must adapt to Manifest V3.

For those who rely on privacy-focused extensions or advanced automation tools, alternative browsers like Mozilla Firefox and Brave are viable options. Firefox continues to support Manifest V2 extensions, while Brave offers built-in ad and tracker blocking.

If you're looking for alternatives, consider the following options:

Developing future-ready Chrome extensions requires a deep understanding of the changes introduced in Manifest V3. Google's official Chrome Developer's guide provides a comprehensive resource for migrating extensions to the new version. Our developers make sure to comply with every instruction mentioned, making extensions future-proof.

To ensure seamless migration, we follow a modular approach, which improves the performance of extensions. This approach involves breaking down complex code into smaller, manageable modules.

We also use stable APIs that receive regular updates, allowing us to ensure the compatibility of extensions. This is crucial in a rapidly evolving browser landscape where new features and security patches are constantly being introduced.

To stay ahead of the curve, we keep ourselves up to date with new changes and provide post-migration services accordingly. This ensures that extensions continue to perform without issues in the future.

Here's a summary of the benefits of migrating to Manifest V3:

Developing future-ready Chrome extensions requires a strategic approach, but the benefits are well worth the effort. By staying ahead of the curve, you can ensure your extensions remain competitive and continue to provide value to users.

Mozilla Firefox remains one of the few mainstream browsers that continue to support Manifest V2 extensions, making it a strong option for users who rely on extensions affected by Manifest V3.

Firefox developers have stated that they will maintain compatibility for privacy extensions and ad blockers while working on a long-term strategy to balance security and functionality.

Brave Browser comes with built-in ad and tracker blocking, making it a suitable replacement for Chrome, especially in regions like Singapore where digital privacy concerns are rising.

The future of browser extensions will depend on how well they adapt to Manifest V3, which some experts believe limits innovation and may drive users toward alternative platforms.

Developers who focus on privacy tools and productivity solutions will need to rethink their strategies to align with the new API limitations.

In the Singapore market, the shift could encourage innovation in independent browser development, benefiting tech startups and cybersecurity firms that rely on browser extensions for automation and data analytics.

Manifest V2 uses a simple notification format, but Manifest V3 introduces a more complex notification format that includes more attributes.

Manifest V3 notifications have a maximum size of 2MB, compared to Manifest V2's 4KB limit.

Manifest V3 requires a service worker to handle notifications, but Manifest V2 does not.

In Manifest V3, the ExecuteScript() function has undergone a change. It should be used like this: the function name remains the same, but the implementation is different from Manifest V2.

The key difference lies in how the function is executed. In Manifest V3, the function is no longer executed directly on the page, but rather it's executed in a different context. This change affects how developers use the function to inject scripts into web pages.

The webRequest API was used in Manifest V2 to modify, intercept, and block requests.

This API had no usage limitations, allowing developers to freely modify requests. However, it was replaced in Manifest V3 with the declarativeNetRequest API.

A fresh viewpoint: Chrome Manifest V3 Release Date

The declarativeNetRequest API requires declarative "rules" for network request modification, which is a significant change from the webRequest API. It's limited to 30,000 rules.

This means that all Chrome extensions in Manifest V3 can only modify, intercept, or block 30,000 requests. This change is likely to affect the way developers approach network request modification in their extensions.