Modern desktop development is undergoing a fundamental transformation, driven by the need to deliver rich, web-powered user interfaces without the bloat of bundling entire browser engines. At the heart of this shift is Microsoft Edge WebView2—a Chromium-based embedded web control that allows developers to host modern web content directly within native applications. But one question consistently emerges as a critical decision point for developers:
When a user installs the Microsoft Edge browser (stable channel), the Evergreen WebView2 runtime is automatically installed and shared across all apps on the machine. It lives in a well-known system folder (typically C:\Program Files (x86)\Microsoft\EdgeWebView\Application ).
This is the standard, automatic-updating runtime. When you deploy an app that uses the Evergreen model, the WebView2 Runtime installs once on the user's machine. From that point forward, Microsoft silently keeps it up to date via Windows Update.
I can provide code samples and architecture patterns tailored exactly to your stack. Share public link evergreen webview2
| Feature | Evergreen | Fixed Version | |---------|-----------|---------------| | | Automatic via Windows Update | Manual—requires app recompilation | | Disk Space | Shared across all WebView2 apps | Separate copy per app | | Version Control | App cannot specify a particular version | Full control over runtime version | | Internet Requirement | Bootstrapper requires internet (offline installer available) | No internet required after packaging | | Recommended For | Most applications | Strict compatibility requirements | | OS Integration | Preinstalled on Windows 11 devices | Standalone packaged component | | Installation Method | Bootstrapper or offline installer | Bundled with application package |
In the context of modern Windows application development, the is the default and recommended distribution model for embedding web content into native apps. 🌐 What is Evergreen WebView2?
Always wrap your WebView2 initialization logic in try-catch blocks and verify the runtime version before loading complex web apps. It lives in a well-known system folder (typically
To begin developing with Evergreen WebView2, follow these standard steps:
First launch of WebView2 in a session can be slower than a native control, as the runtime initializes Chromium processes (~50-100ms extra). Caching helps.
While WebView2 comes pre-installed on modern Windows machines, robust applications must still verify its presence during installation or runtime initialization. From that point forward, Microsoft silently keeps it
Multiple apps share the same runtime binaries, significantly reducing the storage footprint compared to packaging a dedicated browser for every app.
env = await CoreWebView2Environment.CreateAsync();
If a user does not have Edge installed? No problem. When your app installs, you call the simple (a tiny 1.5MB executable) that downloads and installs the Evergreen runtime silently in the background.
As a developer, the shift to the "Evergreen" model is not just a technical update; it is a fundamental shift in how desktop applications interact with the modern web. What is Evergreen WebView2?