You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-edge/extensions/developer-guide/best-practices.md
+72-9Lines changed: 72 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,24 +6,87 @@ ms.author: msedgedevrel
6
6
ms.topic: conceptual
7
7
ms.service: microsoft-edge
8
8
ms.subservice: extensions
9
-
ms.date: 11/20/2023
9
+
ms.date: 09/22/2025
10
10
---
11
11
# Best practices for extensions
12
12
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.
Build an extension that conforms to Microsoft's standards for security, privacy, transparency, and user experience.
65
+
* Minimize background activity and memory usage.
20
66
21
-
**Security**: Make sure that your extension doesn't pose any security threats to users.
67
+
* Avoid crashes, freezes, or excessive CPU consumption.
22
68
23
-
**Privacy**: Make sure that your extension handles user data appropriately.
69
+
* Test your extension across different versions of Microsoft Edge and supported platforms.
24
70
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).
Copy file name to clipboardExpand all lines: microsoft-edge/extensions/index.md
+38-8Lines changed: 38 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ An extension should include at least the following features:
25
25
26
26
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.
27
27
28
-
<!-- todo: equivalent of landing page cards -->
28
+
A Microsoft Edge extension:
29
29
30
30

31
31
@@ -132,19 +132,49 @@ After you've successfully submitted your extension, your extension undergoes a r
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.
136
136
137
-

137
+

138
138
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.**
140
140
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:
142
142
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
+

144
144
145
-
To help protect your browser settings, extensions that don't comply with the Best Practices for extensions are not badged.
146
145
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).
0 commit comments