Evergreen Webview2 [work] -

Review: Microsoft Edge WebView2 (Evergreen Distribution Model)

Rating: 4.8/5
Best for: Windows desktop developers needing embedded web content (OAuth, HTML UI, docs) with automatic updates.

Abstract

WebView2, Microsoft’s modern embedded browser control, introduces the Evergreen distribution model, which ensures that the underlying WebView2 Runtime is automatically updated independently of the host application. This paper explores the architecture, benefits, and implementation considerations of the Evergreen WebView2 model compared to the Fixed Version model. It highlights how the Evergreen approach enhances security, reduces maintenance overhead, and aligns with modern software lifecycle practices. We also discuss compatibility, deployment strategies, and real-world use cases for Windows desktop applications. evergreen webview2


4.2 Disk and Memory Efficiency

Because the runtime is shared across all WebView2 apps on a system, the overhead per app is negligible. For enterprises with dozens of WebView2-embedded apps, this saves gigabytes of disk space and reduces memory duplication via shared libraries. How it works: You ship the WebView2 binaries with your app

2. The Fixed Version (Non-Evergreen)

This allows you to bundle a specific, frozen version of WebView2 inside your app's installation folder. you embed a tiny WebView2

Case A: Embedded OAuth & Identity

Your WinForms app needs to log into Azure AD or Google. Instead of spinning up a separate browser or writing custom HTTP listeners, you embed a tiny WebView2, point it to https://login.microsoftonline.com. Evergreen ensures that the latest security headers, cookie policies, and FIDO2 (passkey) support are available. You never have to update your identity code.