Evergreen updates happen automatically. Your app should be designed to handle the WebView2 control being updated in the background.
If the runtime is missing, EnsureCoreWebView2Async throws an exception. Handle it by downloading the bootstrapper:
Set CoreWebView2EnvironmentOptions.TargetCompatibleBrowserVersion if you require a specific baseline. evergreen webview2
The is Microsoft's recommended distribution mode for embedding web technologies into native applications. Unlike the "Fixed Version," the Evergreen runtime is shared across all applications on a device and updates automatically via Microsoft Edge, ensuring applications always have the latest security patches and features. Core Functionality & Architecture
Shipping the Fixed Version runtime adds ~150-180 MB to your installer. The Evergreen model keeps your app lightweight—sometimes as small as 100 KB for the bootstrapper. Evergreen updates happen automatically
So, how is Evergreen WebView2 being used in the real world? Here are a few examples:
A common concern with the Evergreen model is the risk of a browser update introducing a breaking change to an application. Microsoft mitigates this through rigorous testing and structured update channels. Update Channels Core Functionality & Architecture Shipping the Fixed Version
WebView2 offers two primary distribution modes: