Where we list / Listing guides
How to publish your extension on Microsoft Edge Add-ons
You register for the Microsoft Edge program in Partner Center with a Microsoft account, upload your extension as a zip, fill in Availability, Properties, Privacy and Store listings, and click Publish. Registration is free. Microsoft says certification can take up to seven business days.
Checked on Microsoft Edge Add-ons's own pages on 2026-11-12.
| Cost | Free. Microsoft states there is no registration fee for the Edge program. |
|---|---|
| Who can submit | Individuals or companies with a personal Microsoft account (Outlook, Live, Hotmail) or a GitHub sign-in. Work or school accounts cannot register. Company accounts go through business verification. |
| Review | Microsoft certification, which can take up to seven business days. Company account verification can take from a few days to a few weeks. |
| Fits | Chromium extensions, including Chrome extensions ported to Edge: productivity, shopping, accessibility, developer and AI tools with one clear purpose. |
| Time needed | 2 to 3 hours for the listing and privacy forms, plus account verification and up to seven business days of certification. |
Before you start
- A Microsoft account (or a GitHub account to create one). Individual accounts verify faster than company accounts.
- A publisher display name of 50 characters or less that you have the right to use.
- A zip with your manifest; the name and description in the manifest fill the listing and are read-only in Partner Center.
- A square logo, 300 x 300 px recommended and at least 128 x 128 px.
- Up to 6 screenshots at 640 x 480 or 1280 x 800 px, plus optional promo tiles at 440 x 280 and 1400 x 560 px.
- A description of 250 to 10,000 characters for each language in your package.
- A privacy policy URL, a short single-purpose statement, a reason for each permission, and test credentials.
How to list on Microsoft Edge Add-ons, step by step
Register in Partner Center
Sign in with your Microsoft account, open the Edge Developer Account Registration form, pick your country and account type, and accept the App Developer Agreement. Country and account type cannot be changed later.
Create the extension and upload the zip
In the Edge workspace click Create new extension and drop in your zip. Fix any validation error and upload again.
Set availability
Choose Public, or Hidden if you only want people with the link to install it. Leave all markets on unless you have a reason to limit them.
Fill in properties
Pick a category and add your website and support contact. The website must be a page on your own site, not the store listing.
Complete the Privacy page
Write the single-purpose description, justify every permission, declare any remote code, tick your data-use disclosures and add the privacy policy URL. Incomplete or inaccurate answers can delay or fail certification.
Write the store listing for each language
Add the description, logo, screenshots, promo tiles, optional YouTube video and search terms. You can draft the description with the built-in AI button and then edit it.
Add certification notes and publish
Click Publish, fill in Notes for certification with test logins and steps to reach hidden features, then publish. When it passes, the status changes to In the Store.
What the Microsoft Edge Add-ons form asks for
| Field | Limit | Tip |
|---|---|---|
| Publisher display name | 50 characters | Company accounts must use the registered business name. |
| Category | – | Choose the category a user would browse for your main feature. |
| Website | – | Link to a product page on your own site. |
| Support contact detail | – | A support page URL or an email address you monitor. |
| Mature content | – | Tick it if any content, including ads or linked content, needs an adult rating. |
| Single Purpose Description | – | One narrow, concrete sentence; vague or broad wording slows review. |
| Permission justification | – | Remove unused permissions from the manifest before you write these. |
| Are you using remote code? | – | Manifest V3 does not allow it; saying yes means extra review. |
| Privacy Policy URL | – | Make sure it loads and talks about Edge, not only another browser. |
| Description | 250 to 10,000 characters | Cover the full functionality and any dependency on other software. |
| Extension logo | 1:1, 300 x 300 px recommended, 128 x 128 px minimum | Use Duplicate to copy it to all languages. |
| Small promotional tile | 440 x 280 px | Optional, but it is how your extension appears beside others. |
| Large promotional tile | 1400 x 560 px PNG | Optional; useful if you want a bigger placement. |
| Screenshots | Up to 6, 640 x 480 or 1280 x 800 px | Avoid stretched or blurry images, which break policy. |
| YouTube video URL | – | Turn off ads on the video before you add it. |
| Search terms | Up to 7 terms, 21 words total, 30 characters each | Use real words users type; they are not shown publicly. |
| Notes for certification | – | Include test accounts, steps to locked features and what changed in an update. |
Why submissions get rejected
- More than one purpose in a single extension.
- Name, icon or description that misleads users, copies another extension, or references other browsers.
- Broken features, broken URLs or a server that is down during testing.
- Obfuscated code, inside the package or fetched from the web.
- Changing the new tab page, home page or search without clear user consent and disclosure.
- Requesting permissions you do not need, including 'future proofing'.
- No test account or explanation when the extension requires login.
- Missing or irrelevant privacy policy, or data shared with third parties without opt-in.
- Gambling, crypto mining, adult content, paywall bypassing, or bulk submissions of the same extension.
Tips that make a difference
- If only one language shows in Store listings, replace hardcoded name and description in the manifest with i18n message placeholders and set default_locale.
- The AI description tool is limited to 10 generations per hour, so give it your feature list in the prompt instead of retrying.
- Choose an individual account if you are a solo maker; company verification can take weeks and may involve phone calls.
- Disclose any paid features and price range in the listing, since paid features must be clearly described.
- Keep your backend live during certification; a server that is down counts as non-functional.
Example: what JustLaunched prepared
These are the texts Pushify prepared for JustLaunched, a real brand, before listing it on sites like Microsoft Edge Add-ons. See the full sample report ›
| Name | JustLaunched |
|---|---|
| Tagline | Launch board for founders and early adopters |
| Short description | JustLaunched is a free launch board where founders introduce new products and early adopters try them first, ask questions and share feedback. |
| Tags | product launch, launch platform, startup discovery, indie makers, early adopters, beta testers, launch deals, product hunt alternative, saas, startups |
Questions people ask
Is it free to publish on Microsoft Edge Add-ons?
Yes. Microsoft says there is no registration fee for submitting extensions to the Edge program.
How long does Edge extension certification take?
Microsoft says certification can take up to seven business days after you submit. Company accounts also need business verification, which can take days or weeks.
Can I publish my Chrome extension on Edge?
Yes. Edge is built on Chromium, and Microsoft provides a guide to porting Chrome extensions. You still submit it separately through Partner Center.
Should I choose an individual or company account?
Individual accounts have a shorter verification. Company accounts need your registered business name and an approver Microsoft can contact, and you cannot switch from company to individual later.
How do I appeal a failed certification?
Review the developer policies to find the cause, then use the Extensions New Support Request form. For a malware suspension, you must appeal by email within 7 days.
Sources
The Microsoft Edge Add-ons pages this guide was checked against.