On Windows 10 and 11, the Evergreen WebView2 Runtime is often already installed as part of the OS or alongside Microsoft Edge.
To help you decide, the table below outlines the core differences between the two primary distribution models for the WebView2 Runtime.
| Feature | Evergreen Runtime | Fixed Version Runtime | | :--- | :--- | :--- | | | Not packaged with the app; system-wide component. | Packaged directly inside the app bundle. | | Runtime Updates | Automatically updated by Microsoft in the background. | Updates only occur when the developer releases a new app version. | | Disk Space | Shared across all apps using the runtime, minimizing disk footprint. | Each app contains its own copy of the runtime; space usage is multiplied per app. | | Network Dependency | An internet connection is typically required for the initial installation (unless using the offline installer) and for automatic updates. | Can be installed entirely offline; no network dependency after app is deployed. | | Version Control | The app cannot specify or enforce a particular version of the runtime to be used. | The app uses exactly the version it ships with, providing perfect predictability. | | Recommendation | Microsoft's recommended default for most WebView2 apps. | Recommended only for applications with strict compatibility requirements or for deployment on air-gapped systems. | evergreen webview2
: On compatible systems, binaries for Microsoft Edge and the Evergreen Runtime are hard-linked, optimizing memory and disk usage. Deployment Best Practices
Developing desktop applications has evolved. Instead of choosing between the raw performance of native code and the rapid development cycles of the web, modern developers use hybrid architectures. Microsoft Edge WebView2 sits at the center of this shift, allowing native apps on Windows to host web content safely and efficiently. On Windows 10 and 11, the Evergreen WebView2
For developers looking to integrate the Evergreen Runtime deployment directly into their application's installer, Microsoft provides several official sample projects:
While rare, automatic updates can occasionally cause issues. Developers are encouraged to test their apps against Microsoft Edge Preview channels (Beta, Dev, or Canary) to catch upcoming changes. ⚠️ Common Hurdles | Packaged directly inside the app bundle
Keep your native desktop code (C#, C++, Electron, etc.) strictly separated from your frontend web code. Use secure communication bridges like PostWebMessageAsJson and window.chrome.webview.addEventListener to pass data safely.
What or framework you are using (WPF, WinForms, WinUI 3, C++) If your application needs to support offline environments How you currently handle app updates and deployment
The Definitive Guide to WebView2 Evergreen: Future-Proofing Desktop Apps
In the ever-evolving world of web development, staying ahead of the curve is crucial for success. One technology that has been gaining significant attention in recent years is Evergreen WebView2, a game-changing solution that is transforming the way we build, deploy, and manage web applications. In this article, we will delve into the world of Evergreen WebView2, exploring its features, benefits, and the impact it is having on the web development landscape.