Skip to content

Platform in Platforms

PWAs on Microsoft Edge (sidebar, store)

Published Updated

Microsoft Edge can install a PWA from its address bar or from Microsoft Store. On Windows, Edge manages installed PWAs and provides ways for pages to detect its deprecated sidebar context.

When Edge determines that a site is an installable PWA, it displays an App available icon in the address bar. Select that icon and then Install to install and run the PWA in Windows (Use Progressive Web Apps in Microsoft Edge, Microsoft Learn).

Microsoft Support also documents a menu route for installing any website: Settings and more > More tools > Apps > Install this site as an app. Apps installed this way are listed at edge://apps (Install, manage, or uninstall apps in Microsoft Edge, Microsoft Support).

Edge lists installed PWAs at edge://apps and under Settings and more > More tools > Apps > View apps. Microsoft Support says edge://apps can sort them by installation date, recent use, or name, and lets a user enable Auto-start on device login from an app’s details. On Windows, installed PWAs appear in the taskbar, Start menu, Alt+Tab switcher, and Apps & features settings. The installed window’s Settings and more button opens an App info menu. The menu contains the app icon, name, and publisher; Pin to taskbar, Pin to Start, and App settings commands; and Privacy, Extensions, and More tools submenus. A PWA can also expose manifest shortcuts in its taskbar right-click menu (Use Progressive Web Apps in Microsoft Edge, Microsoft Learn).

To publish in Microsoft Store, create an app reservation in Partner Center. Package the PWA with PWABuilder and submit the package to Microsoft Store. Microsoft states that publishing through this workflow does not require code changes (Publish a PWA to the Microsoft Store, Microsoft Learn). PWABuilder provides a .zip archive containing an .msixbundle and a .classic.appxbundle; Microsoft instructs publishers to submit both package files. Store review typically takes 24 to 48 hours.

A Store-installed PWA has a hard-coded start URL on its principal domain. If launch redirects to a locale-specific domain, Microsoft says that navigation is out of scope and Edge displays the URL and page title. By contrast, a PWA installed from Edge after the browser redirects to the locale-specific domain launches directly on that domain.

The edge_side_panel manifest member opted a PWA into Edge sidebar pinning. Microsoft’s sidebar documentation marks the feature as being deprecated in its 2026-07 update. The documented sidebar has a default minimum width of 376 pixels. An app can request its initial width with edge_side_panel.preferred_width; users can resize it above that preferred width or down to the 376-pixel minimum. The same documentation tells pages to look for the Edge Side Panel brand in Sec-CH-UA or navigator.userAgentData.brands when detecting the sidebar context, and says sidebar apps receive the desktop hint Sec-CH-UA-Mobile: ?0 by default.

Microsoft documents address-bar installation and PWA management in Microsoft Edge, with taskbar, Start menu, Alt+Tab, Apps & features, and Microsoft Store integration on Windows. Its Edge UX documentation also lists a Windows limitation: in an FSLogix environment a PWA can be installed, but the installed PWA is gone after the user logs off and logs back in. The sidebar context is specific to Edge and is deprecated.

Read the brand list only when User-Agent Client Hints are available. The fallback selects the regular layout without claiming that the page is installed.

function isEdgeSidebar() {
const brands = navigator.userAgentData?.brands;
if (!brands) {
return false;
}
return brands.some(({ brand }) => brand === 'Edge Side Panel');
}
const sidebar = isEdgeSidebar();
document.documentElement.classList.toggle('edge-sidebar', sidebar);

Microsoft recommends User-Agent Client Hints over parsing the User-Agent string for this check.

Showing an install button when Edge supplies the event

Section titled “Showing an install button when Edge supplies the event”

Keep the button hidden until beforeinstallprompt fires. If the event is unavailable, the code leaves the browser’s own install UI as the fallback.

const installButton = document.querySelector('#install');
let installEvent;
window.addEventListener('beforeinstallprompt', (event) => {
event.preventDefault();
installEvent = event;
installButton.hidden = false;
});
installButton.addEventListener('click', async () => {
if (!installEvent) return;
await installEvent.prompt();
installEvent = undefined;
installButton.hidden = true;
});

MDN marks beforeinstallprompt as limited availability and notes that calling preventDefault() can prevent browser-provided install UI from appearing on some platforms. The event is therefore not a universal installation interface.

Look for the documented Edge Side Panel brand within Sec-CH-UA. The sidebar documentation does not define a fixed string for the complete header. Browser and platform evidence for the custom install event is collected under install prompt compatibility.

Specifications

SpecificationStatus
None.