After [converting your extension](https://developer.chrome.com/docs/extensions/migrating/checklist) to Manifest Version 3, the next step is to release it on the [Chrome Web Store](https://chrome.google.com/webstore). Depending on the extent of the changes you made, it can be advisable to perform a step-wise roll out to ensure your Manifest V3 extension works as expected by testing it with a limited audience first. This article discusses a few ways to publish your new release in stages. For example, releasing a beta version to testers and gradually rolling out to your user base. We also recommend monitoring your extension review status and keeping an eye on user feedback to quickly publish any bug fixes if needed. ## Publish a beta testing version Publishing a beta release lets you gather feedback and identify any issues with a group of testers before releasing your extension to the rest of your users. Beta releases also go through the [Chrome Web Store review process](https://developer.chrome.com/docs/webstore/review-process). ### Label your beta version First, you must label the beta release as a testing version in the [manifest.json](https://developer.chrome.com/docs/extensions/mv3/manifest) by following these steps: 1. Add the label "BETA" at the end of the [name](https://developer.chrome.com/docs/extensions/mv3/manifest/name) of your extension. 2. Add "THIS EXTENSION IS FOR BETA TESTING" to the [description](https://developer.chrome.com/docs/extensions/mv3/manifest/description). > [!CAUTION] > **Caution:** Skipping this step may result in your extension being rejected for [repetitive content](https://developer.chrome.com/docs/webstore/troubleshooting#spam). Now that your beta version is clearly labeled, you can either distribute it to specified email addresses, to members of a Google group, or share it as a direct link. ### Distribute to testers by email Follow these steps to distribute to a small number of testers: 1. Go to the **Account tab** of the Developer Dashboard. 2. Scroll to **Management**. 3. Under Trusted Testers, enter email addresses separated by spaces or commas. ![Screenshot showing trusted tester accounts listed in a Chrome Web Store developer account page](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/screenshot-showing-truste-0f5ae3c473cbb.png) Trusted tester emails in the Chrome Web Store developer Account page. 4. Save changes at the bottom of the page. 5. [Upload](https://developer.chrome.com/docs/webstore/publish#upload-your-item) the beta version of your extension 6. Go to the **Distribution** tab 7. Set the Visibility to **Private**. ![Setting the Visibility as Private in the Distribution tab](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/setting-visibility-priv-0bfda9e9e6dcd.png) Visibility set to Private in the Distribution tab. ### Distribute to members of a Google group Once you've received enough feedback from your beta testers, you can expand distribution to members of a [Google group](https://groups.google.com/my-groups) that you own or manage. Go to the **Distribution** tab, set the **Visibility** to Private, and choose your beta tester Google group from the **dropdown menu**. ![Setting the visibility to private and choosing a google group to distribute the extension to](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/setting-visibility-priv-a56d3a05bfcc9.png) Distributing to members of a Google Group. ### Distribute to testers with a direct link Another alternative is to set the visibility to **Unlisted**. This way, only users who have the direct link to your store listing item can install the extension. ## Gradually roll-out your release To ensure that any unexpected problems will have minimal impact, you can roll out your update gradually by following these steps. This is only available for extensions with more than 10,000 active users. 1. [Upload](https://developer.chrome.com/docs/webstore/publish#upload-your-item) your new version. 2. Go to the **Distribution** tab. 3. Enter a percentage in **Percentage rollout** field. > [!NOTE] > **Note:** Percentage rollout only applies to existing users of your extension. New users will always receive the new version. ![Chrome Web Store fractional rollout field showing in Developer Dashboard](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/screenshot-percentage-rollout-initial.png) Setting the initial rollout percentage. To continue rolling out gradually, navigate to the **Package** tab of your item and increase the percentage located in the **Published** section. Note that the percentage can only be increased, and it doesn't trigger an additional review. ![Chrome Web Store update percent rollout field showing in Developer Dashboard](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/screenshot-the-chrome-we-04fafacc060a5.png) Updating the rollout percentage. ## Plan for review times We recommend planning enough time for your item to be reviewed as review times may vary based on [different factors](https://developer.chrome.com/docs/webstore/review-process#review-time-factors). Most extensions are reviewed within three days. Consider staging your release and regularly checking your item's status to make changes quickly if necessary. ### Stage your release The Chrome Web Store offers a way to stage a release by submitting it for review ahead of time. This way, when you are ready, you can officially release it. You can do this by unchecking the "Publish automatically" checkbox when you submit the item. ![Screenshot of the Chrome Web Store confirm submission dialog](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/screenshot-the-chrome-we-37c8eef4f714c.png) Checkbox to stage an extension update. Or you can do it later by choosing **Defer publish** in the three-dot menu on the top right. ![Screenshot showing the 'more' menu's defer publish option](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/screenshot-showing-more-a5743b120582d.png) Choosing deferred publishing in menu. > [!NOTE] > **Note:** Once your item is approved, you have up to 30 days to publish. After that period expires, the staged submission will revert to a draft, which will have to be reviewed again. You can check your staged submission expiration in the developer dashboard next to each listed item. ![Staged item > status in the developer dashboard](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/staged-item-status-the-d-ad0d34aafba1d.png) Staged item status in the developer dashboard ### Check your item status When your item has passed or if a violation has been found, you will receive a notification email, usually within 3 days. If you have not received an email in a week, check your item's status in the **Published** section of the **Status** tab. ![The Chrome Web Store Status Tab](https://developer.chrome.com/static/docs/extensions/develop/migrate/publish-mv3/image/the-chrome-web-store-stat-ed96d603197ea.png) Status tab in the Developer Dashboard. If your extension has been pending review for over two weeks, [contact developer support](https://developer.chrome.com/docs/webstore/review-process#support) to request assistance. ### If something goes wrong If you've released an extension update with bugs and want to rollback to the earlier version immediately, use the [Web Store rollback](https://developer.chrome.com/docs/webstore/rollback). ## Additional tips To stay on top of user feedback you can add a link to a [dedicated support site](https://developer.chrome.com/docs/webstore/support-users#provide-user-support) under the Support tab of your extension listing.