Evergreen Webview2 Today
(WPF, WinForms, WinUI) are you building? Are your users mostly on Windows 10 or Windows 11 ?
By not bundling the runtime with your application, your installer size is significantly smaller. Instead of packaging a
Because the runtime updates independently, a web feature or JavaScript behavior could theoretically alter over time.
The is the recommended distribution model for embedding modern web content into Windows applications. Unlike traditional "Fixed Version" models that bundle a specific static engine, the Evergreen model uses a self-updating system maintained by Microsoft, ensuring your app always runs on the latest Chromium-based rendering engine. Core Architecture and Distribution evergreen webview2
The shared runtime model means better memory management and performance, as the operating system treats it as a shared resource. Evergreen vs. Fixed Version Distribution
For the vast majority of applications, the Evergreen distribution mode is not only the recommended choice but also the most practical one. It reduces application size, ensures that security patches are applied swiftly, and allows developers to focus on building rich features rather than managing runtime infrastructure.
WebView2 with CEFSharp or Electron for your specific use case. (WPF, WinForms, WinUI) are you building
For silent or unattended installation—critical for enterprise deployments and seamless user experiences—the bootstrapper supports command-line options:
By using WebView2, you bridge the gap between web capabilities and desktop performance. The Distribution Models: Evergreen vs. Fixed Version
All applications on a machine using the Evergreen model share a single installation, reducing disk footprint. Instead of packaging a Because the runtime updates
You don't need to push updates just to patch the browser engine. The evergreen model decouples the web platform updates from your application updates. Evergreen vs. Fixed Version Runtime
The Developer’s Guide to WebView2: The Evergreen Embeddable Web Runtime