cwspy.com · August 28, 2026 · 7 min read
Publishing Your Chrome Extension to the Edge Add-ons Store
The Microsoft Edge Add-ons store is built on Chromium, which means most Chrome extensions run on Edge with little to no code change. Developers who already have a working, ranking Chrome Web Store listing frequently skip publishing to the Edge add-ons store entirely — leaving install volume on the table for close to zero extra engineering work. This guide covers what is actually different about submitting there, and what to reuse versus rebuild.
What carries over from your Chrome listing
- The extension package itself. A Manifest V3 Chrome extension typically needs no code changes to run on Edge — Edge implements the same extension APIs.
- Your listing copy. Name, summary, and description translate directly; the same keyword thinking from your Chrome Web Store SEO work applies to the Edge Add-ons store listing.
- Screenshots and icons — the same assets work, though Edge's listing layout differs slightly, so double-check crops render well before publishing.
What is actually different
| Aspect | Chrome Web Store | Microsoft Edge Add-ons store |
|---|---|---|
| Developer account | Google developer account, one-time registration fee | Separate Microsoft Partner Center account, no fee |
| Review process | Google's own review pipeline | Separate Microsoft review, different turnaround and criteria — expect to test independently, not assume identical approval |
| Store search algorithm | Google's, largely undocumented (see our ranking factors breakdown) | Microsoft's own ranking, also undocumented — do not assume Chrome positioning predicts Edge positioning |
| Distribution channel | Default browser for the largest install base | Default on Windows for a meaningfully sized, often enterprise-heavy user base |
Publishing to Edge is close to free distribution for a Manifest V3 extension you have already built — the cost is a second developer account and a second review queue, not a second product.
How do you submit to the Edge Add-ons store?
- Create a Microsoft Partner Center developer account (separate from your Chrome Web Store account).
- Upload the same packaged extension you submit to Chrome — no separate build is usually required for a standard Manifest V3 extension.
- Fill in the Edge listing fields with the same keyword-aware copy as your Chrome listing.
- Submit for review; Edge's review timeline runs independently of Chrome's, so do not assume simultaneous approval.
- Once live, treat it as a separate listing to monitor — installs, ratings, and any keyword positions on Edge do not mirror Chrome automatically.
Why bother with a smaller store
Edge's install base is smaller than Chrome's, but it skews toward Windows-default users and enterprise environments where Edge is the mandated browser — an audience segment that may never encounter your extension on the Chrome Web Store at all. For an extension with a working, proven listing, the marginal cost of also maintaining an Edge listing is low relative to the incremental install volume, particularly since enterprise-managed deployments often run on Edge by organizational default.