Skip to content

Commit 8745ba9

Browse files
Merge pull request #3579 from MicrosoftDocs/main
main to live - 9/23/2025
2 parents cd75994 + a030bbe commit 8745ba9

File tree

4 files changed

+110
-17
lines changed

4 files changed

+110
-17
lines changed

microsoft-edge/extensions/developer-guide/best-practices.md

Lines changed: 72 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,24 +6,87 @@ ms.author: msedgedevrel
66
ms.topic: conceptual
77
ms.service: microsoft-edge
88
ms.subservice: extensions
9-
ms.date: 11/20/2023
9+
ms.date: 09/22/2025
1010
---
1111
# Best practices for extensions
1212

13-
Follow these Best Practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
13+
Follow these best practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Build an extension that conforms to Microsoft's standards for security, privacy, performance, and user experience. These principles help ensure your extension is safe, reliable, and valuable to users.
14+
15+
The Microsoft Edge extensions team continues to gather feedback from developers and users to evolve these best practices. To ensure that your extension remains compliant and competitive, review this guidance regularly.
16+
17+
Meeting these guidelines doesn't guarantee that your extension will receive the **Featured** badge; see [The Featured badge](../index.md#the-featured-badge) in _Overview of Microsoft Edge extensions_.
18+
19+
Follow these best practices, to improve the quality, reliability, and user experience of your extension, and to maximize your extension's visibility.
20+
21+
22+
<!-- ====================================================================== -->
23+
## Security
24+
25+
* Make sure that your extension doesn't pose any security threats to users.
26+
27+
* Request only the permissions that are necessary for core functionality.
28+
29+
* Use secure coding practices, and avoid third-party libraries with known vulnerabilities.
30+
31+
* Respond promptly to any flagged issues.
32+
33+
34+
<!-- ====================================================================== -->
35+
## Privacy
36+
37+
* Handle user data responsibly and in accordance with your published privacy policy.
38+
39+
* Clearly disclose what data is collected and how it is used.
40+
41+
* Avoid tracking or fingerprinting users without explicit consent.
42+
43+
44+
<!-- ====================================================================== -->
45+
## User experience
46+
47+
* Provide a clean, intuitive, and responsive interface.
48+
49+
* Avoid disruptive ads, pop-ups, or misleading prompts.
50+
51+
* Ensure the extension integrates seamlessly into the browsing experience.
52+
53+
54+
<!-- ====================================================================== -->
55+
## Store listing
56+
57+
* Provide clear and concise descriptions, to set accurate user expectations.
58+
59+
* Include high-quality screenshots that reflect the actual user experience.
1460

1561

1662
<!-- ====================================================================== -->
17-
## Design a high-quality extension
63+
## Performance and stability
1864

19-
Build an extension that conforms to Microsoft's standards for security, privacy, transparency, and user experience.
65+
* Minimize background activity and memory usage.
2066

21-
**Security**: Make sure that your extension doesn't pose any security threats to users.
67+
* Avoid crashes, freezes, or excessive CPU consumption.
2268

23-
**Privacy**: Make sure that your extension handles user data appropriately.
69+
* Test your extension across different versions of Microsoft Edge and supported platforms.
2470

25-
**User experience**: Make sure that your extension provides a clean, intuitive, and seamless user experience on the web without ads that can be interruptive.
71+
* Refer to [Minimize an extension's impact on page load time](./minimize-page-load-time-impact.md).
72+
73+
74+
<!-- ====================================================================== -->
75+
## Responsiveness to user feedback
76+
77+
* Monitor user reviews, and respond constructively.
78+
79+
* Address bugs and usability issues in a timely manner.
80+
81+
* Maintain a regular update cadence, to improve reliability and user trust.
82+
83+
84+
<!-- ====================================================================== -->
85+
## See also
86+
<!-- all links in article -->
2687

27-
**Store listing**: Make sure that your extension's store listing sets correct user expectations and clearly communicates what the extension does.
88+
* [The Featured badge](../index.md#the-featured-badge) in _Overview of Microsoft Edge extensions_.
89+
* [Minimize an extension's impact on page load time](./minimize-page-load-time-impact.md)
2890

29-
We'll continue gathering input about Developer experiences with extensions, and updating these Best Practices.
91+
External:
92+
* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)
119 KB
Loading
-102 KB
Loading

microsoft-edge/extensions/index.md

Lines changed: 38 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ An extension should include at least the following features:
2525

2626
To work directly with a specific part of the browser, such as a window or tab, you must send API requests, and must often reference the browser by name.
2727

28-
<!-- todo: equivalent of landing page cards -->
28+
A Microsoft Edge extension:
2929

3030
![A Microsoft Edge extension](./index-images/example-extension-screenshot.png)
3131

@@ -132,19 +132,49 @@ After you've successfully submitted your extension, your extension undergoes a r
132132
<!-- ====================================================================== -->
133133
## The Featured badge
134134

135-
A **Featured** badge is displayed on some extension listings at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The **Featured** badge indicates that the extension has been determined to follow Microsoft's recommended best practices related to security, privacy, transparency, and user experience.
135+
Extensions are curated to help users discover trustworthy and high-performing extensions. The **Featured** badge at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) highlights extensions that meet a high bar of quality, security, and user experience.
136136

137-
![The Featured badge to the right of the extension name](./index-images/featured-badge.png)
137+
![The Featured badge](./index-images/featured-badge.png)
138138

139-
When you hover on a **Featured** badge, the tooltip reads: **This extension follows all of Microsoft's recommended practices and has been verified**.
139+
The **Featured** badge is awarded to select extensions that align with [Best practices for extensions](./developer-guide/best-practices.md). When you hover over the **Featured** badge, the tooltip reads: **This extension follows all of Microsoft's recommended practices and has been verified.**
140140

141-
For example, the [Microsoft Editor: Spelling & Grammar Checker](https://microsoftedge.microsoft.com/addons/detail/microsoft-editor-spellin/hokifickgkhplphjiodbggjmoafhignh) extension has a **Featured** badge at Microsoft Edge Add-ons.
141+
For example, the [Microsoft Editor: Spelling & Grammar Checker](https://microsoftedge.microsoft.com/addons/detail/microsoft-editor-spellin/hokifickgkhplphjiodbggjmoafhignh) extension has a **Featured** badge:
142142

143-
The Microsoft Edge extensions team reviews each extension for adherence to [Best practices for extensions](./developer-guide/best-practices.md) before granting the extension a **Featured** badge. Badged extensions are curated solely for the purpose of providing Microsoft Edge users with secure browsing tools and high-quality experiences. Developers cannot pay to receive a **Featured** badge for an extension.
143+
![The Featured badge to the right of the extension name](./index-images/featured-badge-on-page.png)
144144

145-
To help protect your browser settings, extensions that don't comply with the Best Practices for extensions are not badged.
146145

147-
Just because an extension doesn't have a **Featured** badge, doesn't mean the extension is unsafe. It simply means that the extension doesn't meet Microsoft's security and quality standards to be badged as **Featured**.
146+
<!-- ------------------------------ -->
147+
#### What the Featured badge represents
148+
149+
The **Featured** badge indicates that:
150+
151+
* The extension aligns with Microsoft's best practices for security, privacy, performance, and user experience.
152+
153+
* The extension has been reviewed and selected through an automated system.
154+
155+
* The extension offers a reliable and high-quality experience for Microsoft Edge users.
156+
157+
The **Featured** badge is not a judgment of safety. An extension that doesn't have the **Featured** badge is not necessarily unsafe; the extension simply doesn't meet the current threshold for Featured status.
158+
159+
160+
<!-- ------------------------------ -->
161+
#### Why the Featured badge might be revoked
162+
163+
The **Featured** badge isn't permanent. An extension might lose the **Featured** badge if the extension no longer meets the evolving standards, or if the extension's quality signals degrade over time.
164+
165+
To maintain a high-quality ecosystem, Microsoft periodically re-evaluates all badged extensions. A **Featured** badge might be removed due to:
166+
167+
* Decline in user experience or performance metrics.
168+
169+
* Outdated or incomplete store listing information.
170+
171+
* Security or privacy concerns.
172+
173+
* Changes in Microsoft's evaluation criteria.
174+
175+
All decisions about the **Featured** badge are final and not subject to individual review. There is no manual application or appeal process. The **Featured** badge is awarded and revoked based on internal evaluation criteria and tooling.
176+
177+
To improve your extension's quality and eligibility for the **Featured** badge, see [Best practices for extensions](./developer-guide/best-practices.md).
148178

149179

150180
<!-- ====================================================================== -->

0 commit comments

Comments
 (0)