An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

We're announcing a series of policy updates designed to provide clarity and consistency across our platform.

How to prepare your extension for the new extensions menu.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

We're excited to launch a set of UI changes making the Chrome Web Store Developer Dashboard more responsive and mobile-friendly. We hope this gives you a more convenient and accessible experience when monitoring store listing performance, making

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

This announcement includes a series of updates to Developer Program Policies page designed to encourage the development of high quality products, prevent deceptive behavior, and ensure informed user consent.

YouTube is enhancing platform security with Trusted Types to prevent cross-site scripting attacks, but it may impact your extension.

We sat down with the team that leads review in the Chrome Web Store.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

This week we're excited to launch a new feature that lets developers roll back their extensions to the previous published version in the Chrome Web Store. Our goal is to give developers increased peace-of-mind when publishing updates, especially with

In this post, the eyeo team shares their journey into the problem of testing extension service workers. In particular, how to to make sure that their Chrome Extensions works correctly when a service worker gets suspended.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

In December of last year, we paused the planned deprecation of Manifest V2 in order to address developer feedback and deliver better solutions to migration issues. As a result of this feedback, we’ve made a number of changes to Manifest V3 to close

Over the past year, we have been actively involved in discussions with the vendors behind several content blocking extensions around ways to improve the MV3 extensions platform. Based on these discussions, many of which took place in the

A summary of important changes in Chrome 120 for Chrome Extension developers.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Learn how to use DevTools to debug Chrome extensions.

Experience and advice on participating in Google Summer of Code.

Starting in Chrome 117, Chrome will proactively highlight to users when an extension they have installed is no longer in the Chrome Web Store.

A summary of important changes in Chrome 116 for Chrome Extension developers.

An overview of the changes so far this year in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Introducing the new Side Panel API for Chrome extensions.

Extension service workers can now stay alive as long as they're receiving events. This increases the reliability of extension services workers, but has a pitfall you should avoid.

Introducing the Offscreen Documents API for Chrome extension development.

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

The Extensions API has been updated to support back/forward cache, preloading navigations.

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

A better way to start the Chrome developer learning journey.

Google is rolling out a revamped item analytics experience for the Chrome Web Store Developer Dashboard. The new dashboard is easier to understand at a glance and consolidates the most useful information upfront.

Sharing details about the plan to move extensions to Manifest V3

Chrome extensions had Browser and Page Actions APIs for years, but Manifest V3 replaced both with a generic Actions API. This post explores the history of these APIs and what has changed in Manifest V3.

The Scripting API is a new Manifest V3 API focused on, well, scripting. Let's dig into the motivations for this change and how it's different.

Open source tool to convert extensions to Manifest V3. You'll still need to manually update any code with non-mechanical changes, such as adapting to use service workers or some script injection.

Web Accessible Resources for Manifest V3 is here! Now `manifest.json` supports permission definitions. Developers can restrict resources based on the requesting site origin or extension id.

Media Source Extensions (MSE) provide extended buffering and playback control for the HTML5 audio and video elements. While originally developed to facilitate Dynamic Adaptive Streaming over HTTP (DASH) based video players, MSE can be used for audio; specifically for gapless playback.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

We're announcing a series of policy updates designed to provide clarity and consistency across our platform.

How to prepare your extension for the new extensions menu.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

We're excited to launch a set of UI changes making the Chrome Web Store Developer Dashboard more responsive and mobile-friendly. We hope this gives you a more convenient and accessible experience when monitoring store listing performance, making

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

This announcement includes a series of updates to Developer Program Policies page designed to encourage the development of high quality products, prevent deceptive behavior, and ensure informed user consent.

YouTube is enhancing platform security with Trusted Types to prevent cross-site scripting attacks, but it may impact your extension.

We sat down with the team that leads review in the Chrome Web Store.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

This week we're excited to launch a new feature that lets developers roll back their extensions to the previous published version in the Chrome Web Store. Our goal is to give developers increased peace-of-mind when publishing updates, especially with

In this post, the eyeo team shares their journey into the problem of testing extension service workers. In particular, how to to make sure that their Chrome Extensions works correctly when a service worker gets suspended.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

In December of last year, we paused the planned deprecation of Manifest V2 in order to address developer feedback and deliver better solutions to migration issues. As a result of this feedback, we’ve made a number of changes to Manifest V3 to close

Over the past year, we have been actively involved in discussions with the vendors behind several content blocking extensions around ways to improve the MV3 extensions platform. Based on these discussions, many of which took place in the

A summary of important changes in Chrome 120 for Chrome Extension developers.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Learn how to use DevTools to debug Chrome extensions.

Experience and advice on participating in Google Summer of Code.

Starting in Chrome 117, Chrome will proactively highlight to users when an extension they have installed is no longer in the Chrome Web Store.

A summary of important changes in Chrome 116 for Chrome Extension developers.

An overview of the changes so far this year in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Introducing the new Side Panel API for Chrome extensions.

Extension service workers can now stay alive as long as they're receiving events. This increases the reliability of extension services workers, but has a pitfall you should avoid.

Introducing the Offscreen Documents API for Chrome extension development.

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

The Extensions API has been updated to support back/forward cache, preloading navigations.

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

A better way to start the Chrome developer learning journey.

Google is rolling out a revamped item analytics experience for the Chrome Web Store Developer Dashboard. The new dashboard is easier to understand at a glance and consolidates the most useful information upfront.

Sharing details about the plan to move extensions to Manifest V3

Chrome extensions had Browser and Page Actions APIs for years, but Manifest V3 replaced both with a generic Actions API. This post explores the history of these APIs and what has changed in Manifest V3.

The Scripting API is a new Manifest V3 API focused on, well, scripting. Let's dig into the motivations for this change and how it's different.

Open source tool to convert extensions to Manifest V3. You'll still need to manually update any code with non-mechanical changes, such as adapting to use service workers or some script injection.

Web Accessible Resources for Manifest V3 is here! Now `manifest.json` supports permission definitions. Developers can restrict resources based on the requesting site origin or extension id.

Media Source Extensions (MSE) provide extended buffering and playback control for the HTML5 audio and video elements. While originally developed to facilitate Dynamic Adaptive Streaming over HTTP (DASH) based video players, MSE can be used for audio; specifically for gapless playback.