Progressive Web Apps (PWAs) combine the reach of the web with the native ergonomics of desktop applications. By registering a Web App Manifest—a standardized JSON file declaring application metadata—web developers can allow users to install websites directly into the Windows taskbar, start menu, and desktop with custom window frames and offline support.
However, when a PWA fails to prompt for installation, displays broken application icons, or renders incorrect splash screen colors, diagnosing the root cause in code can be difficult. Microsoft Edge DevTools provides a dedicated Manifest inspector inside its Application panel. This tool visualizes parsed manifest properties, validates image asset dimensions, tests window controls overlays, and verifies installability criteria in real time.
Opening the Manifest Tool in Edge DevTools
To inspect the Web App Manifest of any progressive web application:
- Launch Microsoft Edge and navigate to your web application.
- Press F12 (or press Ctrl + Shift + I on Windows / Cmd + Option + I on Mac) to launch DevTools.
- Click the Application tab in the top navigation bar. (If hidden, click the More tabs (≫) button).
- In the left sidebar, locate the Application section at the top.
- Click Manifest.
Inspecting Identity and Presentation Properties
The Manifest panel visualizes key properties governing how Windows and Edge package the PWA:
- Identity: Displays the application
name,short_name, and uniqueid. Verify thatstart_urlpoints to the intended initial navigation route. - Presentation: Shows the configured
displaymode (e.g.standalone,minimal-ui, orfullscreen) andorientation. - Color Palette: Previews the
theme_color(which colors the native Windows title bar) andbackground_color(used on the startup splash screen).
Validating Icons and Maskable Assets
One of the most frequent causes of PWA installability failures is missing or misconfigured icon assets. Scroll down to the Icons section of the Manifest panel:
- Edge previews each icon declared in the manifest array alongside its declared dimensions (e.g.
192x192,512x512). - Click the Maskable toggle to test how Windows and Android crop the icon within circular and rounded square bounds.
- If an icon URL returns a 404 error or invalid MIME type, DevTools displays an immediate inline warning.
Testing Windows Controls Overlay
For modern desktop PWAs on Windows 11, the Window Controls Overlay API allows web content to extend completely into the native title bar, placing search bars or tabs directly alongside the Minimize, Maximize, and Close buttons.
In the Manifest panel, check the display_override array for ["window-controls-overlay"]. Edge DevTools provides an emulation toggle in the Application tool allowing you to test title bar geometry without installing the app.
Testing App Shortcuts and Protocol Handlers
Further down the Manifest inspector:
- Shortcuts: Previews quick actions that appear when a user right-clicks the PWA icon in the Windows Taskbar (e.g. New Document or Open Inbox).
- Protocol Handlers: Displays custom URI schemes (e.g.
web+chat://) registered by the web app to launch directly from external links.
Triggering Manual Installation Events
At the top of the Manifest inspector, Edge provides quick testing action buttons:
- Install App: Bypasses engagement heuristics and directly triggers the native Microsoft Edge PWA installation dialog.
- Add to home screen: Emulates mobile installation triggers.
If the web app does not satisfy Edge’s PWA installability criteria (such as missing a valid service worker with a fetch handler, lacking a 512×512 icon, or missing HTTPS), the Manifest panel displays an explicit list of unresolved requirements, making troubleshooting seamless.