Skip to content

Update "Overview of Microsoft Edge extensions"#3768

Open
mikehoffms wants to merge 6 commits intomainfrom
user/mikehoffms/featured
Open

Update "Overview of Microsoft Edge extensions"#3768
mikehoffms wants to merge 6 commits intomainfrom
user/mikehoffms/featured

Conversation

@mikehoffms
Copy link
Copy Markdown
Collaborator

@mikehoffms mikehoffms commented Apr 7, 2026

Rendered article sections for review:

AB#60823027

@mikehoffms mikehoffms added the cat: extensions Extensions-related content. label Apr 7, 2026
@learn-build-service-prod
Copy link
Copy Markdown

Learn Build status updates of commit 8767faa:

✅ Validation status: passed

File Status Preview URL Details
microsoft-edge/extensions/index-images/example-extension-screenshot.png ✅Succeeded n/a (file deleted or renamed)
microsoft-edge/extensions/index-images/example-extension.png ✅Succeeded View
microsoft-edge/extensions/index-images/featured-badge-on-page.png ✅Succeeded View
microsoft-edge/extensions/index.md ✅Succeeded View

For more details, please refer to the build report.

@mikehoffms mikehoffms changed the title Update pngs in "Overview of Microsoft Edge extensions" Update "Overview of Microsoft Edge extensions" Apr 7, 2026
@learn-build-service-prod
Copy link
Copy Markdown

Learn Build status updates of commit 7ccae29:

✅ Validation status: passed

File Status Preview URL Details
microsoft-edge/extensions/index-images/example-extension-screenshot.png ✅Succeeded n/a (file deleted or renamed)
microsoft-edge/extensions/index-images/example-extension.png ✅Succeeded View
microsoft-edge/extensions/index-images/featured-badge-on-page.png ✅Succeeded View
microsoft-edge/extensions/index.md ✅Succeeded View

For more details, please refer to the build report.

Copy link
Copy Markdown
Collaborator Author

@mikehoffms mikehoffms left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Writer/Editor

@learn-build-service-prod
Copy link
Copy Markdown

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Copy Markdown

Learn Build status updates of commit a933606:

✅ Validation status: passed

File Status Preview URL Details
microsoft-edge/extensions/index-images/example-extension-screenshot.png ✅Succeeded n/a (file deleted or renamed)
microsoft-edge/extensions/index-images/example-extension.png ✅Succeeded View
microsoft-edge/extensions/index-images/featured-badge-on-page.png ✅Succeeded View
microsoft-edge/extensions/index.md ✅Succeeded View

For more details, please refer to the build report.

Comment on lines 32 to +53
* [See also](#see-also)
* [Microsoft Edge](#microsoft-edge)
* [Store](#store)
* [End-user docs](#end-user-docs)
* [Development](#development)
* [Google Chrome, or Chromium browser engine](#google-chrome-or-chromium-browser-engine)
* [Store](#store-1)
* [Development](#development-1)
* [Opera](#opera)
* [Store](#store-2)
* [Development](#development-2)
* [Brave](#brave)
* [Store](#store-3)
* [End-user docs](#end-user-docs-1)
* [Development](#development-3)
* [Apple Safari](#apple-safari)
* [Store](#store-4)
* [Development](#development-4)
* [Mozilla Firefox](#mozilla-firefox)
* [Store](#store-5)
* [Development](#development-5)
* [Non-browser extensions](#non-browser-extensions)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we make an exception and not display the detailed headings for the See also section?
These headings take a lot of space, as well as attention away from the more useful headings above.

Comment on lines 61 to +63
You can create a Microsoft Edge extension if you have an idea or product that is based upon either a specific web browser, or improvements to features of specific webpages. Examples of _companion experiences_ include ad blockers and password managers.

This article focuses mostly on Chromium-based extensions.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section is making things unnecessarily high level, as if we're documenting how to build extensions in all browsers. We're not.

Suggested change
You can create a Microsoft Edge extension if you have an idea or product that is based upon either a specific web browser, or improvements to features of specific webpages. Examples of _companion experiences_ include ad blockers and password managers.
This article focuses mostly on Chromium-based extensions.
You can create a Microsoft Edge extension to add features to the browser or improve to features of specific webpages. Examples of _companion experiences_ include ad blockers and password managers.

Comment on lines +73 to +75
In the **Search extensions, themes, and more** text box, you can enter various search terms, such as the extension owner [Microsoft Corporation](https://microsoftedge.microsoft.com/addons/search/microsoft%20corporation). Searching returns extensions and themes, such as the [Microsoft Bing Homepage and Search Engine](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage-a/hcfdaddfkgbmekbgcepcnpfiopaigpnn) extension:

![A Microsoft Edge extension](./index-images/example-extension-screenshot.png)
![The Microsoft Bing Homepage and Search Engine extension](./index-images/example-extension.png)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest moving this up to line 60, just after we've introduced the "store", and slightly rephrase to make it clearer what we mean by Search extensions, themes, and more:

Suggested change
In the **Search extensions, themes, and more** text box, you can enter various search terms, such as the extension owner [Microsoft Corporation](https://microsoftedge.microsoft.com/addons/search/microsoft%20corporation). Searching returns extensions and themes, such as the [Microsoft Bing Homepage and Search Engine](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage-a/hcfdaddfkgbmekbgcepcnpfiopaigpnn) extension:
![A Microsoft Edge extension](./index-images/example-extension-screenshot.png)
![The Microsoft Bing Homepage and Search Engine extension](./index-images/example-extension.png)
On the Microsoft Edge Add-ons site, you can enter various search terms in the **Search extensions, themes, and more** text box to find extensions and themes, such as the [Microsoft Bing Homepage and Search Engine](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage-a/hcfdaddfkgbmekbgcepcnpfiopaigpnn) extension:
![The Microsoft Bing Homepage and Search Engine extension](./index-images/example-extension.png)

* A JavaScript file that defines the function.
* HTML and CSS files that define the user interface.

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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this line is necessary. It's pretty high level and vague at this point in the article, and doesn't bring anything very concrete and useful to developers.

## Benefits of Chromium-based extensions

If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications.
If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari app extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari app extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications.
If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment.

Comment on lines +102 to +106
The following browsers are based on the [Chromium](https://www.chromium.org/Home) open-source browser project:
* Microsoft Edge
* Google Chrome
* Opera
* Brave
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not be definitive. There are other browsers. And the list can change quickly.

Suggested change
The following browsers are based on the [Chromium](https://www.chromium.org/Home) open-source browser project:
* Microsoft Edge
* Google Chrome
* Opera
* Brave
Microsoft Edge is based on the [Chromium](https://www.chromium.org/Home) open-source browser project. Other browsers are also based on Chromium, such as Google Chrome, Opera, and Brave.

Comment on lines +108 to 112
Chromium-based browsers use the same code package, and minimize the need to maintain parallel versions.

Benefits of creating a Chromium extension:
* Enables writing the fewest lines of code.
* Enables targeting the maximum number of extension stores and the maximum number of users who can find and acquire your extension.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Chromium-based browsers use the same code package, and minimize the need to maintain parallel versions.
Benefits of creating a Chromium extension:
* Enables writing the fewest lines of code.
* Enables targeting the maximum number of extension stores and the maximum number of users who can find and acquire your extension.
Chromium-based browsers use the same extension APIs and way to package extensions, which minimizes the need to maintain parallel versions.
By writing a Chromium extension, you write fewer lines of code and target more browsers.

* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)
* [Chrome Web Store](https://chrome.google.com/webstore/category/extensions)
* [Opera addons](https://addons.opera.com/extensions)
* [Chrome Web Store](https://chrome.google.com/webstore/category/extensions) - store for Brave extensions.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should remove this line. Even if it's for Brave, it's the same site as for Chrome.

* [Apple App Store](https://apps.apple.com)
* [Firefox Browser Add-ons](https://addons.mozilla.org/firefox/extensions)

Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's bring it back to Edge here. It's useful that the article mentions other browsers and other stores, but devs are here to build an Edge extension.

Suggested change
Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store.
Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store.
To make sure your users find your extensions in Microsoft Edge, publish your extension on the Microsoft Edge Add-ons site. See [Publish an extension at Microsoft Edge Add-ons](#publish-an-extension-at-microsoft-edge-add-ons).

Comment on lines +375 to +378
#### Non-browser extensions

* [Microsoft Edge DevTools extension for Visual Studio Code](../visual-studio-code/microsoft-edge-devtools-extension.md)<!-- link not in article -->
* [webhint extension for Visual Studio Code](../visual-studio-code/webhint.md)<!-- link not in article -->
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest removing these links. They're not related to browser extensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cat: extensions Extensions-related content.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants