![Zach Warneke](https://web.dev/images/authors/zwarneke.jpg) Zach Warneke

<br />

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 the transition to Manifest V3.

## My extension has a live bug, what now?

From today, you don't need to submit a new version of your extension with a bug
fix and wait for it to pass review. Instead, you can initiate a rollback through
the **more** menu or the package page for your item.
![Developer dashboard screenshot showing the rollback action inside the](https://developer.chrome.com/static/blog/chrome-webstore-rollback/image/rollback-menu.png)

A rollback requires a new version number under which the previous version of
your extension will be re-published and a reason for the rollback. After filling
in the required information, confirm the rollback.
![Developer dashboard screenshot showing the rollback dialog asking for version and reason](https://developer.chrome.com/static/blog/chrome-webstore-rollback/image/rollback-dialog.png)

Once the rollback is finished, the rolled-back package will be pushed to users
through the normal Chrome auto-update process. You can verify that the rollback
was successful on the package page or status page.
![Developer dashboard screenshot showing the rollback status in the package status page](https://developer.chrome.com/static/blog/chrome-webstore-rollback/image/rollback-status.png)

Refer to the [rollback documentation](https://developer.chrome.com/docs/webstore/rollback) for more information, including how we
handle rollbacks in certain special cases. The version rollback feature is live
now, and the Chrome Web Store team is looking forward to continuing to improve
the rollout management process for developers.