Edge Add-ons

Microsoft Edge Add-ons distributes extensions to Microsoft Edge users. If you already have a Chromium-based extension, you can submit it to Edge with minimal changes.

This guide walks you through manual submission and optional automation, aligned with the official process.

Developer account

To enroll in the Microsoft Edge program you need to have a Microsoft account. If you don't have one, you can create one here.

Next, before you can publish your extension to Edge Add-ons, you need to register your developer account in Partner Center. Fill out the required fields and submit the form with Finish button. Wait for the email that your account has been verified - you're ready to submit your extension!

Submission

After your account is ready and the extension bundle is prepared, you can publish it. There are two paths:

• Manually: Upload your .zip package through Partner Center.
• Automatically: Use CI to upload new versions after the first manual submission.

The first submission should be done manually. Subsequent updates can be automated once you have your extension ID and required credentials.

Manual submission

To manually submit your extension to stores, you will first need to get your extension bundle. If you ran the build step locally, you should already have the .zip file in your extension's build folder.

If you used GitHub Actions to build your extension, you can find the results in the workflow run. Download the artifacts and save them on your local machine.

Then, use the following steps to upload your item:

Automated submission

TurboStarter comes with a pre-configured GitHub Actions workflow to submit your extension to web stores automatically. It's located in the .github/workflows/publish-extension.yml file.

What you need to do is fill the environment variables with your store's credentials and extension's details and set them as a secrets in your Github repository under correct names:

env:
  EDGE_PRODUCT_ID: ${{ secrets.EDGE_PRODUCT_ID }}
  EDGE_CLIENT_ID: ${{ secrets.EDGE_CLIENT_ID }}
  EDGE_API_KEY: ${{ secrets.EDGE_API_KEY }}

Please refer to the official guide to learn how to get these credentials correctly.

Once configured, you can manually trigger the workflow to upload the new version to Edge Add-ons 🎉

- name: 💨 Publish!
  run: |
    npx wxt submit \
      --edge-zip apps/extension/build/*-chrome.zip --edge-skip-submit-review

Review

After you submit your extension, it enters Microsoft's certification and publishing pipeline.

1. Preprocessing
   • Uploaded packages are queued and scanned. If errors are detected during preprocessing, you'll see a message and must resolve issues before re-uploading.
2. Certification
   • Security tests: packages are checked for viruses and malware.
   • Content compliance: human review of your listing and content for policy adherence.
3. Release and publishing
   • If you selected publish immediately, publishing begins right away; otherwise schedule/hold options apply.
   • While publishing, the submission status page shows rollout details. When complete, the status changes from "Publishing" to "In the Store".
4. Edge Add-ons curation and ranking
   • Discovery is influenced by quality, relevancy (name, description, popularity, user experience), and popularity (ratings and averages). Security and policy compliance are verified per the developer policies.

Microsoft may also perform spot checks after publishing to ensure ongoing compliance.

The review status of your item appears in the Partner Center under the Overview page of your item.

You'll receive an email notification when the status of your item changes.

You can learn more about the review process in the official guides listed below.