Chrome Extension Edge Migration — Developer Guide

2 min read

Porting Chrome Extensions to Microsoft Edge

Microsoft Edge is built on the Chromium engine, which means most Chrome extensions can be ported with minimal or no modifications. This guide covers the key considerations for publishing your extension on the Edge Add-ons store.

Compatibility Overview

Edge is Chromium-based, so Chrome extensions typically work without changes. The chrome.* namespace is fully supported. Edge also supports the browser.* namespace (Promise-based, similar to Firefox) if you prefer cross-browser compatibility.

Manifest Support

Both Manifest V2 and Manifest V3 are supported in Edge. However, we recommend migrating to MV3 for future-proofing and better compatibility across browsers.

Key Differences

Edge-Specific APIs

Edge provides some unique APIs beyond Chrome:

Feature Detection

Always check for Edge-specific features before using them:

// Edge detection
const isEdge = navigator.userAgent.includes('Edg/');

if (isEdge && window.sidePanel) {
  // Use Edge-specific side panel API
}

Build Script for Dual Publishing

Create a build configuration that works for both stores:

// build.config.js
const config = {
  chrome: {
    store: 'Chrome Web Store',
    output: 'dist/chrome'
  },
  edge: {
    store: 'Edge Add-ons',
    output: 'dist/edge'
  }
};

module.exports = config;

Edge Add-ons Store

Submission Process

  1. Create a Microsoft account
  2. Register as an Edge extension developer
  3. Upload the same ZIP file (identical to CWS)
  4. Provide store-specific metadata:
    • Edge-specific keywords
    • Screenshots optimized for Edge store
    • Privacy policy URL

Store Listing Optimization

Analytics

Set up separate analytics for Edge users:

// Separate tracking for Edge
const analytics = isEdge ? 'UA-Edge-XXXX' : 'UA-Chrome-XXXX';

Review Process

Edge’s review process is similar to CWS but typically faster (24-48 hours). They have similar policies but may be more lenient on certain enterprise-focused extensions.

Testing

Load your extension in Edge for testing:

  1. Open edge://extensions
  2. Enable “Developer mode”
  3. Click “Load unpacked” and select your extension directory

Dual Publishing

Maintain a single codebase for both stores:

Cross-Reference

Turn Your Extension Into a Business

Ready to monetize? The Extension Monetization Playbook covers freemium models, Stripe integration, subscription architecture, and growth strategies for Chrome extension developers.

Part of the Chrome Extension Guide by theluckystrike. Built at zovo.one.

← Previous chrome-extension-keyboard-navigation Next → chrome-extension-migration-firefox